Archive and Version Services uses MySQL with InnoDB, which manages all tables within one tablespace. The potential size of the tablespace in the archive database depends on the combination of the following:
Number of versioning jobs defined
The scheduled frequency of each job
The expected number of source files and their modification frequency for each job
The delete policy for file versions
By default, the initial amount of space reserved for the archive database tablespace is 400 MB. The size of the reserved space is automatically extended by 8 MB every time the tablespace is filled.
You can specify a larger or smaller initial tablespace by modifying the innodb_data_file_path parameter in the sys:\arkManager\arkSQL.cnf file. The minimum tablespace size is 10 MB, as governed by the InnoDB constraints. The reserved size must not exceed the volume size. The maximum tablespace size on NetWare is 8 TB because the maximum size of an NSS volume is 8 TB. However, because your archive database and archive data files share the same volume, the practical limit of the tablespace is much smaller than 8 TB.
For information about configuring ArkSQL, see Section 11.5, Modifying the ArkSQL Settings.
You can also extend the existing tablespace manually by adding new components (raw partition or regular file). For information, see “The InnoDB Storage Engine” in the MySQL Reference Manual.