1.1 Backing Up a ZENworks Server

ZENworks allows you to back up and restore the configuration files for a ZENworks Primary Server. This enables you to maintain a ZENworks Server’s identity and configuration if a server fails or if you need to upgrade to new server hardware.

Server backup operation is version specific. When a server is updated to a higher version, the backup data needs to be collected for the specific version.The backup saves only the configuration files. The database and content repository must be backed up separately and they need to be in sync:

  • The content repository (bundle, policy, and image files). You should do a separate backup for the content repository if you only have one Primary Server in the Management Zone. If you have two or more Primary Servers and you’ve replicated all content to both servers, they serve as backup copies to each other.

  • The ZENworks database (if it resides on the ZENworks server). Backing up the ZENworks Server and backing up the ZENworks database are two separate processes. If your ZENworks database resides on the same server as one of your ZENworks Servers, first back up the database and then back up the ZENworks Server. Because the ZENworks database changes frequently, you should back up the database on a regular schedule. For information about backing up the database, see the ZENworks Database Management Reference.

When you back up a ZENworks Server using a zman command, all files in the Novell\ZENworks\conf directory on a Windows server or the etc/opt/novell/zenworks/ directory on a Linux server are stored in an encrypted backup file in a location that you specify. For more information on the files that are stored as backup, see List of files and folders stored as backup after running the zman zenserver-backup command.

  1. (Conditional) If the server you are backing up hosts the ZENworks database, manually back up the database file to a safe location.

    For information about backing up the database, see the ZENworks Database Management Reference.

  2. At a command prompt on the ZENworks Server, enter the following command:

    zman zenserver-backup path_to_backup_file_to_create

    For example:

    zman zenserver-backup c:\zcm_backups\zone_backup.bak

    or

    zman zenserver-backup /root/zcm_backups/zone_backup.bak

  3. When prompted, enter a ZENworks administrator name and password.

  4. When prompted, enter a passphrase (at least 10 characters) to be used for encrypting the backup file.

    Make sure you remember this passphrase. You must enter it if you ever need to restore the server.

  5. (Conditional) If this is the only Primary Server, or if this Primary Server contains all the content defined in your Management Zone, you must manually back up the content repository to a safe location, unless the content repository is hosted externally. In case of two or more Primary Servers in the zone, it is recommended to perform the file system backup of the local content-repo folder on the Primary Server to ensure that the replicated content is preserved.

    For information on the content repository, see Content in the ZENworks Primary Server and Satellite Reference.

    IMPORTANT:If this is the only Primary Server that contains all of your defined content for the Management Zone and you do not back up the content repository, you are not prepared for a full disaster recovery.

  6. Repeat Step 1 and Step 5 on a regular basis.

    The zman command documented in Step 2 through Step 4 only needs to be run once.

List of files and folders stored as backup after running the zman zenserver-backup command

Following files and folders are stored as backup for Windows:

  • ActionHandlersRegistration.xml

  • ActionUndoHandlersRegistration.xml

  • components.properties

  • database-migration.properties

  • DeviceData

  • DeviceGuid

  • DLUPolicyHandlerRegistration.xml

  • guid.txt

  • initial-web-service

  • ippman.conf

  • LCPRegistration.xml

  • logger-server-conf.xml logger-zman-conf.xml

  • logger-zmd-conf.xml

    logger.xsl

    lpm-server.properties

    monitor.conf

    novell-rm-audit.xml

    novell-rm-setting.ini

    novell-zenworks-configure.properties

    PolicyHandlersRegistration.xml/

    zman/properties/

    primary_server_version.dll

    RMHandlerRegistration.xml

    WGPRegistration.xml

    ZenMemoryCache.config

    ZenServerVersion.xml

    zenworks.uninstall.logger.config

    zenworks_database.conf

    security/

    datamodel/

    casa/

    fde/

    loader/

    loader-logging/

    pmconfig/

    preboot/

    quicktask/

    RMPolicy/

    Satellite/

    services

    zman/properties/

    server.xml

    casa/server.xml

    extcasa/WEB-INF/classes/casa_crypto.properties

    casa/WEB-INF/classes/casa_crypto.properties

Following files and folders are not stored as backup on Windows:

  • agentcomponents/

    datamodel/authsources

    datamodel/cache

    datamodel/default

    zman/resources/

    pru/

    resources/

    trusted-certs/

    LoggerConfiguration-windows.xml

Following files and folders are stored as a backup for Linux:

  • components.properties

    zenworks.properties

    monitor.conf

    version.txt

    database-migration.properties

    initial-web-service

    ZenServerVersion.xml

    primary_server_version.txt

    DeviceData

    DeviceGuid

    ippman.conf

    zenworks_database.conf

    guid.txt

    lpm-server.properties

    logger-server-conf.xml

    novell-zenworks-configure.properties

    logger-zman-conf.xml

    zenworks.uninstall.logger.config

    security/

    datamodel/

    casa/

    fde/

    loader/

    loader-logging/

    preboot/

    puppet/

    quicktask/

    services/

    zman/properties/

    server.xml

    casa/server.xml

    extcasa/WEB-INF/classes/casa_crypto.properties

    casa/WEB-INF/classes/casa_crypto.properties

    zentruststore/

Following files and folders are not stored as backup on Linux:

  • agentcomponents/datamode/lauthsources datamodel/cache datamodel/default conf/ pru/resources/trusted-certs/zman/resources