19.1 Migrating Novell Archive and Version Services to OES 11 SP3

This section provides information on how to migrate Novell Archive and Version Services running on OES 1 SP2, OES 2 SP3, or OES 11 to OES 11 SP3.

19.1.1 Prerequisites

  • The Archive server is installed on the target server.

  • The NSS file system is installed on the target server.

  • The Archive server and the Primary volume must reside in the same eDirectory tree.

  • The Archive server, PostgreSQL database, and Archive volume must be installed on the same machine.

19.1.2 Migration Scenario

Transfer ID - Same Tree

In this scenario, the target server is installed in the same tree as the source server. After successful completion of Transfer ID, the target server functions with the same credentials (such as IP address and hostname) as the source server, and the source server node is no longer available in the network.

What Is Migrated

The following data is migrated from the source server to the target server:

  • The Archive volume that contains the versions of your files.

  • The configuration details stored in arkConfig.xml file located at /etc/opt/novell/arkmanager/conf/.

  • Database records from the source PostgreSQL database to the target PostgreSQL database.

19.1.3 Migration Procedure

  1. Install the OES 11 SP3 server as the target server for the Archive and Version Service into the same eDirectory tree as the source server.

    For more information, see Setting Up Archive and Version Services in the OES 11 SP3: Novell Archive and Version Services Administration Guide.

  2. Run the /opt/novell/arkmanager/<backup script> file on the source server. For information about the backup script, see Section 19.1.5, Back up Script.

  3. Copy the configuration files.

  4. Using the Migration Tool, migrate the data from the archive volume to the target server, retaining the same volume name and directory structure.

  5. Using the Migration Tool, migrate the date data from the primary volume to the target server retaining the same volume and directory structure. For more information, see Using the Migration Tool GUI.

The archive admin is the proxy user. No specific proxy scripts are required for proxy migration.

19.1.4 Post-Migration Procedure

  1. Before restarting the Archive server, ensure the following:

    • Migration of the Archive volume is successful.

    • (Optional) Migration of the Primary volume is successful. In the arkConfig.xml file under the job tag, ensure that the server name and context reflect the configuration details of the target machine.

    • The migrated data from the volumes and database is consistent.

    • Edit the arkConfig.xml file to update the Archive volume path under the archivePath tag on the OES 11 server.

    • Ensure that the admin is a member of the novlxtier group. For more information, see Caveats on Upgrading from OES 2 to OES 11 SP3 in the OES 11 SP3: Novell Archive and Version Services Administration Guide.

    • Ensure that the admin is LUM-enabled on the target server running Archive and Version Services.

    • Ensure that the read-only attribute is not set on the ARK volume.

      To see if the ARK volume has the read-only attribute, enter attrib /media/nss/ARK. The output of this command includes the read-only (ro) attribute.

      To delete the read only attribute, enter attrib -c ro /media/nss/ARK.

  2. To start the Archive Service on OES 11 SP3 server, enter:

    rcnovell-ark start

  3. Run /opt/novell/arkmanager/<restore script>. For information about the backup script, see Section 19.1.6, Restore Script.

Verifying the Migration

To verify that the migration completed successfully, check the availability of file versions by using the NSS File Version Utility.

19.1.5 Back up Script

Before you upgrade to OES 11 SP3, run the script to back up the Archive database on the OES 2 server. The user must have execute permissions to run the script. The script backs up the archive database to the arkdatabackup.sql file.

  1. Save the following script to a file, then run the file on the terminal:

    #!/bin/bash
set -e 
echo 
echo "Backing up Archive Versioning archive_database"
echo

ARKUSER=arkuser
DATABASE=archive_database
DATA_PATH=`cat /etc/opt/novell/arkmanager/conf/arkdatadir.conf`
BACKUPFILE=$DATA_PATH/arkdatabackup.sql

echo "Provide password for $ARKUSER"
su $ARKUSER -c "pg_dump --clean $DATABASE > $BACKUPFILE"

    You are prompted for the arkuser password.

    NOTE:If the arkdatabackup.sql file is empty, repeat Step 1 to generate the contents.

19.1.6 Restore Script

When upgrading to the OES 11 SP3 server, you must restore the Archive database in order for Archive and Version Service to be available. The user must have execute permissions to run the script. The script restores the archive database from the arkdatabackup.sql file to the OES 11 SP3 server.

  1. Configure Archive Version and Services using the same credentials used on the OES 2 server.

  2. Save the following script to a file, then run the file on the terminal:

    #!/bin/bash
set -e 
echo 
echo "Restoring Archive Versioning archive_database"
echo

ARKUSER=arkuser
DATABASE=archive_database
DATA_PATH=`cat /etc/opt/novell/arkmanager/conf/arkdatadir.conf`
BACKUPFILE=$DATA_PATH/arkdatabackup.sql
LOGFILE=$DATA_PATH/restorelog.txt
PORT=543
HOST=localhost

if [ -z DATA_PATH ]
then
  echo "Unable to locate $DATABASE location"
  exit 1;
else
  echo "Provide password for $ARKUSER"
  su $ARKUSER -c "psql -f $BACKUPFILE -d $DATABASE -h $HOST -p $PORT" >>$LOGFILE 2>&1
fi

    You are prompted for the arkuser password.

    After successful restoration of the archive database, the file versions are available on the OES 11 SP3 server.