This section describes how to upgrade an existing Novell Archive and Version Services 2.0 for NetWare server in a cluster configuration with Novell Cluster Services™. Use this upgrade procedure to apply ArkManager patches and operating system upgrades. ArkManager continues to use your existing configuration files for the archive server, versioning jobs, and ArkSQL. It also uses the existing archive database and archive data.
Unload the cluster resources to stop ArkManager and ArkSQL.
For each server in the cluster, upgrade to OES NetWare, using the install option.
For more information, see the OES NetWare Installation Guide.
The option upgrades your operating system and installs the latest version of ArkManager 2.0 on your server. It does not overwrite your existing configuration files, archive database, or archive data.
For each server in the cluster, upgrade to OES Cluster Services 1.7 for NetWare.
For more information, see the OES Novell Cluster Services 1.8.2 Administration Guide for NetWare.
(Conditional) If you upgrade directly from NetWare 6.5 SP1 to OES NetWare, you must modify the sys:\arkManager\arkSQL.cnf file before restarting ArkManager to prevent data corruption.
Compare and modify values of non-system-specific information in sys:\arkManager\arkSQL.cnf with the ones defined in sys:\arkManager\arkSQL_sample.cnf. Make sure to add the following parameter setting to the end of the file:
set-variable = transaction_isolation=READ_COMMITTED
After the upgrade completes successfully, if you have not already rebooted your server, reboot the server to start the MySQL server and ArkSQL.
Rebooting loads cluster resources that start the MySQL server, ArkSQL, and ArkManager.
Verify that the ArkManager service is running.
In iManager, verify that the jobs are available and functioning properly.
For information, see Section 11.1, Viewing a Jobs Report.