Moving the registry to a host not configured for registry backups

In this scenario, primary host rgy1 has failed and prospective registry host rgy2 is not configured as a backup registry host. You must restore a file system backup of the rgy directory from rgy1 to the rgy directory on rgy2 and then reconfigure all clients of rgy1 to use rgy2 as their registry host. The following procedure, in which you restore registry database files from an ordinary file system backup and then run the rgy_switchover command, can partially automate this task.

1. Restore rgy1 registry files from backup to rgy2. Retrieve the DevOps Code ClearCase® rgy directory and the file client_list.db from backup and load its files into rgy/backup. When you are finished, the backup subdirectory includes all the registry data files. A registry host stores its client_list.db file in the same directory as the rgy directory (not in the rgy directory itself). If you do not have this file, rgy_switchover cannot reconfigure clients for you; you must reconfigure clients to use rgy2 as their registry host by following the procedure in Assigning a DevOps Code ClearCase host's registry and region.
2. Create a backup_list file. Create a text file named backup_list and put it into the backup directory. The first line of backup_list must be the name of the primary registry server, in this case rgy1. The remaining lines of the file backup_list must be the names of all the files in the rgy directory, one file name per line. List only the name of each file, not the path to the file. For example:

   bbase_object
   bbase_tag
   regions
   .
   .
   .
   view_object
   view_tag
   vob_object
   vob_tag
   vob_tag.sec

3. Promote rgy2 to primary registry host. Use the procedure described in Promoting a backup registry host to primary registry host.