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.
You can create the NSS volumes on an OES 2 Linux server. If the NSS volume is on an OES Linux server, you must move it to a cross-compatible OES 2 Linux server before it can participate in your Archive and Version Services solution.
Create an NSS storage pool and volume to use exclusively for your archive database and archive data that meets the following guidelines:
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.
The archive volume must be a local 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 SP3: NSS File System Administration Guide.
We recommend that the archive volume and the source volume should reside in separate storage pools, but this is not a limitation.
We recommend you to use different storage devices for the pool for the archive volume and the pool for the source volumes, but this is not a limitation.
For easy backup, we recommend you to store the archive database and archive data in a directory in the archive volume. The archive data is always stored in subdirectories at the base of the archive path.