Moving a VOB between hosts that run Linux or the UNIX system and have the same architecture

About this task

You can use the following procedure to move a VOB to another disk partition on a host running Linux or the UNIX system or to another host running Linux or the UNIX system that has the same architecture.

Procedure

  1. Log on to the source VOB server host.
    Log on as the VOB owner or privileged user.
  2. Lock the VOB for all users.
  3. Stop HCL VersionVault on the source VOB server host.
  4. Rename the old VOB storage directory before you restart HCL VersionVault on the source host.
    If you omit this step, the VOB is available in its old location as soon as the VOB server starts on the source host, which can cause a variety of problems for users who try to access it.
  5. Copy the VOB storage directory.
    The procedure you use depends on whether you are moving the VOB within the same disk partition or to another disk partition. If you are moving the VOB to another disk partition, use tar or a similar command to copy the entire VOB storage directory, but not the remote storage pools, to the new location. For example, to move a VOB to a different disk partition on the same host:

    cd /vobstore

    tar –cf – libpub.vbs | ( cd /vobstore2 ; tar –xBpf – )

    To move a VOB to a different host:

    cd /vobstore

    tar –cf – libpub.vbs | rsh vobsvr04 'cd /vobstore2 ; tar –xBpf –'

    If you are moving the VOB storage directory within the same disk partition on Linux or the UNIX system, use the mv command.
    Note: The –B option to the tar command might not be needed on some platforms. Also, the rsh command might have a different name, such as remsh, on some platforms. See the reference pages for your operating system.
  6. Replace the VOB object and tag with new ones that reference the new VOB storage directory.
    Use the HCL VersionVault Administration Console or the following commands (this example applies to the destination on server sol):

    cleartool register –vob –replace /net/sol/vobstore2/libpub.vbs

    cleartool mktag –vob –replace –tag /vobs/libpub /net/sol/vobstore2/libpub.vbs

  7. Unlock the VOB
  8. Verify that all clients can access the VOB at the new location.