Consolidating remote pools

Certain VOB move scenarios require you to consolidate remote pools and replace them with local ones.

About this task

If you are moving a VOB that has remote pools from Linux or from the UNIX system to Windows® (see Moving a VOB from Linux or the UNIX system to Windows), you must consolidate the remote pools before you move the VOB. You can also use this procedure to consolidate a VOB’s remote pools after the VOB has been moved to a NAS device (see Moving a VOB to network-attached storage).

Procedure

  1. Log on to the VOB server host.
    Log on as the VOB owner or privileged user.
  2. Stop HCL VersionVault on the VOB server host.
  3. Find the remote pools.
    Go to the VOB storage directory and determine the locations of all remote pools and the links that point to them. In this example, the find command on Linux or the UNIX system shows a single symbolic link to a remote pool.

    cd /vobstg/libpub.vbs
    find . –type l –exec ls –l {} \;
       lrwxrwxrwx   1 root           12 Dec 30  1999
       d/ddft_2 ->/net/vobsvr5/pools/libpub/d/ddft_2

  4. Replace each remote pool with a local directory.
    For each remote pool, replace the link with a local copy of the pool. You must preserve file and directory protection and ownership information during this operation. The commands in this step, which are supported on Linux and the UNIX system, remove the symbolic link d/ddft_2 and replace it with the contents of the link’s target, /net/vobsvr5/pools/libpub/d/ddft_2. (Note that if the target had a different terminal leaf, you would need to ensure that the contents were copied into a local directory named ddft_2.)

    rm d/ddft_2

    cd /net/vobsvr5/pools/libpub/d; tar –cf – ddft_2 | (cd /vobstg/libpub.vbs; tar –xBpf–)

  5. Verify that the VOB has no remote pools.
    Start HCL VersionVault on the VOB server host; then use the cleartool lspool command to verify that the VOB has no remote pools.

    cleartool lspool –long –invob /vobs/libpub

    The output of lspool must not include any link targets.
  6. Modify the VOB tag.
    If the consolidated VOB is not being moved to a new host (for example, if the VOB storage is being moved to a NAS device but the VOB server host remains the same) and has a tag in a Windows® region, the tag must be modified to remove the split pool map. Use the Registry Regions node of the HCL VersionVault Administration Console. The Properties page for the VOB tag has a Mount Options page that allows you to edit the split pool map if you are logged in as a member of the HCL VersionVault administrators group. If you cannot use the HCL VersionVault Administration Console, use cleartool rmtag and mktag to remove the VOB tag and re-create it without a split pool map.
  7. Verify that users can access the consolidated pools.
    After you test the VOB, you can delete the old remote pool storage.

What to do next

Note: Check and modify your VOB backup procedures after you consolidate remote pools. Verify that the newly consolidated pools are backed up with the rest of the VOB and that the old remote pools are no longer backed up. If you restore backups that were made before the pools were consolidated, the remote pools are re-created, and the restored VOB is not usable.