Rename replicas and sites

To change the name of a database replica, you must delete the replica and create a new replica using a different name. Renaming sites requires planning and coordination between sites in the clan, particularly the site that is designated for renaming and the working master site. Synchronize all sites before renaming.

Renaming sites

Most HCL Compass clients specify connection information using a database set name. The database set names are stored in the Windows™ registry on each client machine and in files on Linux™ and the UNIX™ system. In MultiSite environments, these are typically named CQMS.CLAN.SITE; however, this naming scheme is optional. Most clients can use any name to access a HCL Compass MultiSite database set; however, the multiutil command constructs a database set name from separate clan and site arguments passed on the command line. Furthermore, the multiutil command verifies that the site name is valid for the clan by comparing the information in the database with the site name specified on the command line. Therefore, when accessing a database set from the multiutil command, the database set name must match the information stored in the database.

The renamesite command changes the database set name stored in the registry. If you are renaming the working master site, the database set name changes when you run the renamesite command. If you are renaming a different site, the database set name changes when the master database replica at that site receives notification of the name change during a syncreplica -import operation. Therefore, when the site name is changed, the connection information on the synchronization server at the renamed site must be updated before that server can perform more multiutil operations. This typically requires editing batch files or shell scripts. The considerations for updating other clients vary, depending on the reason for the rename; there are three renaming scenarios, listed here from simplest to most complex:
  1. You want to decommission a site and indicate this in the site name; for example, you rename Austin to Obsolete_Austin.

    In this case, you can use the rmreplica command to remove each user database at the site, thereby preventing continued access to obsolete databases.

  2. You want to continue using the user databases, but want a different name for the site; for example, you move operations from Vancouver to Toronto and want to rename the Vancouver site to Toronto.

    In this case, the site is renamed but the databases remain on the same server and the database set names do not need to be modified; however, you may choose to change the database set name to reflect the renaming of the site. If you move the databases to different servers, you also need to update the connection information on each client.

  3. You want to continue to access the site under a different name and create a new site with the old name; for example, after moving databases from Vancouver to Toronto, you create a new Vancouver site.

    In this case, the old databases continue to operate, but with a different site name. Clients that do not have updated database set information may seem to work, but they will connect to the wrong site. In the example, the user may think that the client is connecting to the new Vancouver site, when in fact it is connecting to the old Vancouver (now Toronto) site. Update the connection information on each client to ensure access to the correct databases.