This section provides information on how to migrate Novell Archive and Version Services running on NetWare 6.5 SP8 to OES 11 SP3. In this section, the NetWare server is referred to as the source server and the OES 11 SP3 server is referred to as the target server.
For general information on the OES 11 SP3 Migration Tool, see Section 1.0, Overview of the Migration Tools.
The Archive server is installed on NetWare 6.5 SP8. For more information, see NW 6.5 SP8: Novell Archive and Version Services 2.1 Administration Guide.
Install the NSS file system on the OES 11 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.
In the Migrate scenario, the data and configuration on the source server is overwritten.
In this scenario, the target server is installed in the same tree as the source server. After a 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.
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 the arkConfig.xml file.
Database records from the MySQL database to the PostgreSQL database.
Install the OES 11 server as the target server for the Archive and Version Services 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.
To stop the Archive and Version Services on the source server and continue to run the MySQL database, enter
arkstop
To stop the Archive Service on the target server, enter
rcnovell-ark stop
This command stops the Archive server and the default instance of the PostgreSQL database.
If you have configured the Archive server with the default configuration, restart the PostgreSQL database with the following command:
/opt/novell/arkmanager/bin/pg_restart.sh
Migrate data from the Archive volume on the NetWare server to the OES 11 server.
The migration is from the NetWare NSS source volume to the OES 11 NSS target volume, where the source and target servers are in the same eDirectory tree. For more information, see OES 11 SP3: NSS File System Administration Guide for Linux.
IMPORTANT:You need to migrate the Archive volume before migrating the Archive and Version Service; otherwise, versions of files created on the NetWare server are unusable on the OES 11 server.
(Optional) Migrate data from the Primary volume on the NetWare server to the OES 11 SP3 server, using either command line utilities or the GUI interface. For more information, see OES 11 SP3: NSS File System Administration Guide for Linux.
Decide how to migrate Archive and Version Services.
The Migration Tool GUI has a plug-in architecture and is made up of command line utilities with a GUI wrapper. You can migrate Archive and Version Services by using either of the following methods:
Click Computer> More Applications> System > Novell Migration Tools to launch the Migration Tool GUI.
For more information, see Section 5.0, Using the Migration Tool GUI.
Authenticate to the source and target server. Archive and Version Services is listed in the Service panel.
Select the Migration Type as Migrate for migrating the Archive service, or to Transfer ID for the Transfer ID scenario.
In the Services to Migrate panel, click Add, then select Novell Archive and Versioning Services.
The Status of the service is Not Configured.
Select Novell Archive and Versioning Service, then click Configure.
Fill in the fields, using the information in the following table:
Parameter |
Description |
---|---|
MySQL User Name |
Specify a user name for the administrator of the MySQL database on the source server. |
MySQL Database Password |
Specify a password for the MySQL user. |
MySQL Database Port |
Specify a port number used for the archive database communications on the source server. Port 3306 is the default. |
PostgreSQL Database User Name |
Specify a user name for the administrator of the archive database (the PostgreSQL database for the archived data) on the OES 11 server. IMPORTANT:The Postgres user must be an unprivileged user, not the root user. |
PostgreSQL Database Password |
Specify a password for the PostgreSQL user. |
PostgreSQL Database Port |
Specify a port number to use for the archive database communications on the OES 11 server. Port 5432 is the default. |
Click OK.
The Status of the service is Ready.
Click Start to proceed with the migration. The Status is Migrating.
In the Status pane, Service tab, you can view the progress of the migration. After the migration completes, the Status changes to Migrated.
NOTE:If you encounter any errors during the migration, check the Logs tab in the Service pane. After resolving the errors, execute the migration procedure again.
To run the Archive and Version migration utility through the command line, run /opt/novell/migration/bin/migark.sh with the following details:
Option |
Description |
---|---|
--mysqldb-user=<opt> |
Specify a user name for the administrator of the MySQL database. |
--mysqldb-passwd=<opt> |
Specify a password for the MySQL user. |
--mysqldb-port=<opt> |
Specify a port number used for the archive database communications on the NetWare server. Port 3306 is the default. |
--hostname=<opt> |
Specify the host name or IP address of the NetWare server on which Archive and Version Services resides. |
--username=<opt> |
Specify the fully distinguished eDirectory name and context of the administrator user. For example, cn=admin.o=novell NOTE:Use the dot (.) format for specifying the eDirectory name and context, not the comma (,) format. |
--password=<opt> |
Specify a password for the Admin user. |
--pg_db-user=<opt> |
Specify a user name for the administrator of the archive database (the PostgreSQL database for the archived data) on the OES 11 server. IMPORTANT:The Postgres user must be an unprivileged user, not the root user. |
--pg-db-passwd |
Specify a password for the PostgreSQL user. |
--pg_db-port=<opt> |
Specify a port number to use for the archive database communications on the OES 11 server. Port 5432 is the default. |
For example:
/opt/novell/migration/bin/migark.sh --mysqldb-user=root --mysqldb-passwd=novell --mysqldb-port=3306 --hostname=192.168.1.255 --username=cn=admin.o=novell --password=novell12 --pg_db-user=arkuser --pg_db-passwd=novell12 --pg_db-port=5432
NOTE:If you encounter any errors during the migration, check the archive_migration.log file in the /var/opt/novell/log/migration/ folder. After resolving the errors, execute the migration procedure again.
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 arkConfig.xml 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 check 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
To start the Archive Service on OES 11 SP3 server, enter:
rcnovell-ark start
To verify that the migration completed successfully, check the availability of file versions by using the NSS File Version Utility.