Make sure your archive server and source servers meet the following prerequisites and guidelines:
The archive server can be the same or different server as the source server.
One archive server can have only one job defined for any one volume.
A single archive server can archive many volumes with only one job defined per volume.
A given volume can have only one job defined for it.
The archive server and the source server can be the same machine or different machines.
Archive and Version Services is compatible with OES NetWare and NetWare 6.5. An archive server and its source servers can run either operating system in a mixed environment. Make sure the servers are running the latest upgrades.
Make sure your server meets the system and software requirements for OES NetWare. For information, see the OES 2: NetWare Installation Guide.
ArkManager uses UTF-8 encoding for filenames. Either the Language Code pages of the NCP™ client and server must be the same, or you must use a current version of the Novell Client™ to provide UTF-8 support and enable the UTF-8 service in the client. CIFS clients have included UTF-8 encoding support since NetWare 6.0 SP 2 and NetWare 6.5. For information, see Section 11.11, Enabling UTF-8 Encoding Support for Clients.
Determine how much storage space you need for the archive database, given the following criteria:
How much data needs to be stored immediately by the versioning job
How much data there is to version (the physical storage requirements by versioning job)
How frequently the data must be versioned (the length of time in an epoch by versioning job)
How long you need to store the versions (maximum keep time and maximum versions to keep by versioning job)