Moving a VOB that has no remote pools

Creating a registry entry for a VOB on a NAS device requires special options to the register and mktag commands.

About this task

To move a VOB that has no remote pools from a DevOps Code ClearCase® host running Linux or the UNIX system to a NAS device, follow the procedures in Moving a VOB on Linux or the UNIX system, but remember to use the –host, –hpath, and –gpath options to the register and mktag commands. The example here has been modified to register the VOB libpub that has been moved to /net/nasdevice/vobstg and is served by the host ccvobsvr1, which is running Linux or the UNIX system.

cleartool register –vob –replace –host ccvobsvr1 –hpath /net/nasdevice/vobstg/libpub.vbs –gpath /net/nasdevice/vobstg/libpub.vbs /net/nasdevice/vobstg/libpub.vbs cleartool mktag –vob –replace –tag /vobs/libpub –host ccvobsvr1 –hpath /net/nasdevice/vobstg/libpub.vbs –gpath /net/nasdevice/vobstg/libpub.vbs /net/nasdevice/vobstg/libpub.vbs

Example

The example here has been modified to register the VOB \libpub that has been moved to /net/nasdevice/vobstg and is served by the host ccvobsvr1, which is running Linux or the UNIX system.

A similar change is required when moving a VOB from a VOB server host on Windows® to a NAS device. Follow the procedure described in Moving a VOB on Windows, but modify the register and mktag commands as shown here:

cleartool register –vob –replace –host sol –hpath \\sol\vobstore2\libpub.vbs –gpath \\sol\vobstore2\libpub.vbs \\sol\vobstore2\libpub.vbs cleartool mktag –vob –replace –tag \libpub –host ccvobsvr1 –hpath \\sol\vobstore2\libpub.vbs –gpath \\sol\vobstore2\libpub.vbs \\sol\vobstore2\libpub.vbs

When moving Windows VOBs to a NAS device, you must also remove the network group from the ACLs before moving the VOB, or remove the "NETWORK deny write" permission after the VOBs have been moved.