2.2 Replacing an Existing Primary Server with a New Primary Server

If you have only one Primary Server in the Management Zone and if you want to replace the device hosting the Primary Server with a new device that has the same host name and IP address as the old device, you must move the Primary Server to the new device.

The existing Primary Server and the new Primary Server must have the same version of the ZENworks 11 SP4 installed.

NOTE:This scenario is not supported on Windows to Linux and vice-versa. It applies to platforms having the same network identity.

  1. Take a reliable backup of the existing ZENworks Server.

    For detailed information on how to take a backup of the ZENworks Server, see Backing Up a ZENworks Server.

  2. (Conditional) Take a reliable backup of the certificate authority of the Primary Server.

    For detailed information on how to take a backup of the certificate authority, see Backing Up the Certificate Authority.

    During the ZENworks Server backup, certificates are backed up for Primary Servers having an internal Certificate Authority and the same network identity (IP, FQDN, and Cert). Also, during the ZENworks Server restore, the Certificate Authority is restored.

  3. (Conditional) Take a reliable backup of database in any of the following scenarios:

    • You are using an internal ZENworks database (embedded Sybase SQL Anywhere).

    • You are using an external database installed on the device hosting the Primary Server and you do not plan to use the device after uninstalling the Primary Server.

    For detailed information on how to take a backup of an internal database, see in Backing Up the Embedded Sybase SQL Anywhere Database in the ZENworks 11 SP4 Database Management Reference.

    To take a backup of an external database, see the documentation for the database.

  4. (Conditional) If the first Primary Server has ZENworks Reporting installed, take a reliable back-up of the reports.

    For more information about backup of ZENworks reports, see Managing the Export Settings in the ZENworks Reporting System Reference.

  5. Stop all the ZENworks services on the Primary Server.

    For detailed information on how to stop the ZENworks services on Windows, see Stopping the ZENworks Services in the ZENworks 11 SP4 Primary Server and Satellite Reference. For detailed information on how to stop the ZENworks services on Linux, see Stopping the ZENworks Services in the ZENworks 11 SP4 Primary Server and Satellite Reference.

  6. Take a reliable backup of the content-repo directory of the Primary Server.

    The content-repo directory is located in the ZENworks_installation_directory\work\ directory on Windows and in the /var/opt/novell/zenworks/ directory on Linux.

  7. Disconnect the device from the network.

  8. Install ZENworks 11 SP4 on the new server with the following settings that are same as that of the old Primary Server:

    • Installation drive and path. For Windows, ensure that the installation path points to C:\Program Files (x86).

    • ZENworks Ports

    • Management Zone name

    For detailed information on how to install ZENworks 11 SP4, see Installing a ZENworks Primary Server on Windows in the ZENworks 11 SP4 Server Installation Guide.

  9. Do the following on the new Primary Server:

    1. Restore the backed-up ZENworks Server.

      For detailed information on how to restore the ZENworks Server, see Restoring a ZENworks Server.

    2. (Conditional) Restore the backed-up database.

      For detailed information on how to restore the internal ZENworks database, see in Restoring the Embedded Sybase SQL Anywhere Database in the ZENworks 11 SP4 Database Management Reference.

    3. (Conditional) Restore the backed-up Certificate Authority.

      For detailed information on how to restore the certificate authority, see Restoring the Certificate Authority.

    4. Re-create all the default and custom deployment packages.

      Default Deployment Packages: At the server’s command prompt, enter the following command:

      novell-zenworks-configure -c CreateExtractorPacks -Z

      Custom Deployment Packages: At the server’s command prompt, enter the following command:

      novell-zenworks-configure -c RebuildCustomPacks -Z

    5. Copy the backed-up content-repo directory to the ZENworks_installation_directory\work\ directory on Windows or to the /var/opt/novell/zenworks/ directory on Linux. If you have any issues in copying content-repo directory in Linux, then run permissions.sh command.

    6. (Conditional) Run the following scripts:

      • delete from zzenserverroles where Roles = ‘ReportCMSServer’ or Roles = ‘ReportApplicationServer’

      • delete from zopaquedata where name = ‘boe.mysql.database.pwd’

      • delete from zopaquedata where name like ‘%zone.configuration.reports%’

    7. (Conditional) On the new Primary Server, install ZENworks Reporting.

      For detailed information on how to install ZENworks Reporting, see ZENworks Reporting 5 Installation Guide.

    8. (Conditional) If you install ZENworks Reporting on the new Primary Server, restore the reports that you backed-up in Step 4 by using the following zman command:

      zman rpld (source folder)

      For detailed information about the zman Report Commands, view the zman man page (man zman) on the server or see zman(1) in ZENworks 11 SP4 Command Line Utilities Reference.

  10. Ensure that the new server is running correctly. Subsequently, uninstall ZENworks 11 SP4 from the old device. For detailed information on how to uninstall ZENworks 11 SP4, see ZENworks 11 SP4 Uninstall Guide.

WARNING:After the new Primary Server starts running, you must disconnect the old Primary Server from the network and uninstall ZENworks, or disable ZENworks services so that it cannot register back to the zone.