8.3 Upgrading an Archive Server

This section describes how to upgrade an existing Novell Archive and Version Services 2.0 for NetWare server. 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.

  1. Stop ArkManager. At the server console, enter 

    arkstop

    Wait until ArkManager stops completely before continuing with the upgrade.

    For more information, see Section 12.2, Stopping ArkManager.

  2. Stop the MySQL server and ArkSQL. At the server console, enter

    mysqladmin -p shutdown --port=value

    Specify -p if root user’s password is set. Specify the --port if the port is not 3306.

  3. Upgrade to OES NetWare on your archive server, using the Basic install option.

    For information, see the OES NetWare Installation Guide.

    The Basic 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.

  4. (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

  5. After the upgrade completes successfully, if you have not already rebooted your server, reboot the server to start the ArkSQL instance on the MySQL server.

  6. Start ArkManager. At the server console, enter

    arkstart

  7. In iManager, verify that the jobs are available and functioning properly.

    For information, see Section 11.1, Viewing a Jobs Report.