Backing Up the Siebel Gateway Registry

To back up the Siebel Gateway registry, perform the steps in the procedure that follows. It is strongly recommended to back up the Siebel Gateway registry periodically for safety reasons, so that, if something goes wrong, you will be able to restore the Siebel Gateway registry from a backup, as described in Restoring the Siebel Gateway Registry.

It is recommended to back up the Siebel Gateway registry at regular intervals, and before deploying Siebel Gateway clustering into your topology. Retain the backups, which you can use to restore the Siebel Gateway registry data in scenarios identified as caused by corruption in the Siebel Gateway registry. One of the known scenarios where a restore is required is if Siebel Gateway cluster deployment fails and the administrator experiences inconsistency in accessing profiles and deployments in Siebel Management Console. Where you have already deployed Siebel Gateway clustering, then you create the backup for only one of the deployed instances. For more information about Siebel Gateway clustering, see Siebel Installation Guide.

This topic is part of Backing Up and Restoring the Siebel Gateway Registry.

To back up the Siebel Gateway registry

1. (Optional) Shut down the Siebel CRM deployment, as described in Starting and Shutting Down a Siebel CRM Deployment.

2. For the instance of Siebel Gateway for which you are backing up the registry, do the following:

   1. Navigate to the directory GTWYSRVR_ROOT\registry\conf. (Prior to Siebel CRM 21.4 Update, the registry directory was named zookeeper.)

   2. Note the dataDir path in the registry.cfg file. (Prior to Siebel CRM 21.4 Update, this file was named zoo1.cfg.)

   3. Copy the version-2 directory to another name, such as one that includes the current date.

3. (If necessary) Restart the Siebel CRM deployment, as described in Starting and Shutting Down a Siebel CRM Deployment.