Chapter 19. Changing the Location of Network-Wide Resources

This chapter describes procedures for changing which hosts provide ClearCase network-wide resources and services. This includes the ClearCase release area, the license server, and the registry server. It also includes the renaming of server hosts.

The special cases of moving VOBs and views are not discussed in this chapter; these cases are covered in Chapter 11 and Chapter 12.

Changing the Location of the Release Area

To change the location of the ClearCase network-wide release area, follow these steps:

  1. Reload the distribution medium—Create a new release area, using the procedure in the ClearCase Notebook.

  2. Reinstall hosts, as appropriate—Reinstall any host whose previous installation involved one or more symbolic links to the network-wide release area. (The default installation mode copies some files and links others.) Use the procedure in the CASEVISION/ClearCase Rlease Notes.

  3. Remove the old release area—When all hosts have been reinstalled, you can remove the old release area.

Renaming the Release Host

If you rename the network-wide release host, reinstall any host whose previous installation involved one or more symbolic links to the network-wide release area.

Moving Licenses to Another Host and Renaming a License Server Host

On Silicon Graphics platforms, ClearCase licensing is handled through NetLS. Refer to Chapter 7 of the CASEVision/ClearCase Release Notes to learn more about ClearCase licensing. Read the NetWork License System Administration Guide to learn more about NetLS.

Moving the ClearCase Registry

Use this procedure to move the ClearCase storage registry directory tree to another host.

  1. Copy the entire `rgy' directory tree to the destination host—Perform the copy as root, and make sure that root has remote-access rights on the destination host. For example:

    # cd /usr/adm/atria
    # tar -cf - rgy | rsh ccsvr04 'cd /usr/adm/atria ; tar -xBpf -'
        (-B option is not necessar,and not supported if remote host is an HP-UX system)
    # exit
    %
    

  2. Reconfigure the “old” host not to be a registry server host—Remove the file that identifies the host as a registry server host:

    # rm /usr/adm/atria/rgy/rgy_svr.conf
    

  3. Switch registry server host assignments—On all ClearCase hosts, replace the rgy_hosts.conf file, so that it contains the name of the new registry server host:

    # echo "ccsvr04" > /usr/adm/atria/rgy/rgy_hosts.conf
    

  4. Stop and restart ClearCase processing on all hosts—Execute the startup/shutdown script (for example, /etc/rc.atria) with a stop argument; then execute it again, with a start argument.

Renaming the Registry Server Host

ClearCase client hosts cache the name of the registry server host. To rename the network's registry server host:

  1. Shut down ClearCase processing on all client hosts—Use the architecture-specific command (see the init_ccase manual page):

    # /etc/rc.atria stop   (shutdown command varies with architecture)
    

  2. Switch registry server host assignments—Do this on all ClearCase hosts, as described in Step #3 in the preceding section.

  3. Rename the registry server host—Make the change using the vendor-supplied procedure or tool.

  4. Restart ClearCase processing on all hosts—Use the architecture-specific command.

Renaming a ClearCase Host

You must make registry-level adjustments when you rename a host that holds the physical storage for one or more VOBs or views. From the registry's perspective, the rename-host procedure is quite similar to the move-storage-directory procedures described in Chapters 11 and 12:

  1. Make sure that the storage directories are not being used—If the host is home to one or more VOBs, make sure that all clients unmount those VOBs (cleartool umount). If the host is home to one or more views, terminate all processes using the views. (Watch out for shells that are not set to the view, but have it as the working directory view)

  2. Shut down ClearCase processing on the host—Use the architecture-specific command (see the init_ccase manual page):

    # /etc/rc.atria stop   (shutdown command varies with architecture)
    

  3. Rename the host—Make the change using the vendor-supplied procedure or tool. In most cases, this involves a restart of the operating system, which will also restart ClearCase processing. In any event, make sure that ClearCase processing is restarted on the host.

  4. Adjust the registry entries for each storage director—Use register –replace to update object registry entries; use mktag –replace to update tag entries.