Make sure your archive volume and source volumes meet the following prerequisites and guidelines:
The source and archive data volumes must be Novell Storage Services™ (NSS) data volumes that use the OES NetWare and NetWare 6.5 media format.
You can create the NSS volumes on an OES NetWare server, an OES Linux server, or a NetWare 6.5 server. If the NSS volume is on an OES Linux server, you must move it to a cross-compatible OES NetWare server before it can participate in your Archive and Version Services solution.
If you are upgrading an existing archive server:
Back up your existing archive database and the archive data before you begin the upgrade to OES 2 NetWare. For information, see Section 11.8, Backing Up the Archive Database and Section 11.9, Backing Up the Archive Data.
Verify that ArkManager is not running when you begin the upgrade. For information, see Section 11.2, Stopping ArkManager.
After the upgrade, continue to use the same NSS pool, volume, and directory for your upgraded archive database and archive data.
If the volumes with files you want to version reside on NetWare 6.0 and earlier servers, perform the following operating system upgrades, as appropriate:
Upgrade the source server to OES 2 NetWare or NetWare 6.5 SP 7. For information, see the OES 2: NetWare Installation Guide .
If you are upgrading from NetWare 6.0, your NSS media format upgrades in the background over a period of up to 21 days. The format update process is accelerated automatically if the volume begins to participate as a source volume before the conversion is complete; the upgrade requires no outside action on your part.
If you are upgrading from NetWare 5.x, you must upgrade your NetWare 5.x NSS volumes and Traditional volumes. For information, see Upgrading Legacy NSS Volumes and NetWare Traditional Volumes to NSS on NetWare Volumes in the OES 2: NSS File System Administration Guide.
Create an NSS storage pool and volume to use exclusively for your archive database and archive data that meets the following guidelines:
Do not place the archive volume in the system (sys) pool.
For each archive server, use the information from your planning session to design the physical storage media for its archive database.
Make sure your implementation allocates enough space to meet your immediate archive needs and is scalable to accommodate future growth.
The NSS volume you use for your archive database cannot contain data that you plan to archive. The archive volume and the source volume cannot be the same volume.
If you plan to version files from an encrypted source volume, the archive volume should also be an encrypted volume so that data continues to be protected in the archive database. For information about Encrypted Volume Support, see Managing Encrypted NSS Volumes in the OES 2: NSS File System Administration Guide.
The archive volume and the source volume should reside in separate storage pools, but they can be in the same pool.
The pool for the archive volume and the pool for the source volumes should use different storage devices, but this is not required.
You should store the archive database and archive data in a directory in the archive volume for easy backup. The archive data is always stored in subdirectories at the base of the archive path.