Moving an ACL-protected VOB between Linux or the UNIX system and Windows

The procedure for moving a VOB with ACLs enabled is the same as the procedure for moving a VOB to a different operating system, however, there are some special requirements.

Execute the move operation as the VOB owner. The fix_prot and vob_sidwalk operations need be executed by a privileged user. Special requirements for moving a VOB between Linux or the UNIX system and Windows with ACLs enabled:

  • vob_siddump must be executed as the VOB owner on Windows, otherwise it fails because of no permission.
  • fix_prot must be executed as a privileged user, otherwise it fail with no permission on some files/directories.
  • vob_sidwalk (with -execute or -recover_filesystem options) must be executed as a privileged user, otherwise it fails with no permission
  • reformatvob -load should be executed as the VOB owner, otherwise the VOB owner will be limited on some permissions of the VOB during the next steps.
To move a VOB from Windows to Linux or the UNIX system, use the standard procedure. If you are using a filer for VOB storage, and the filer is accessible from both Windows and Linux or the UNIX system VOB servers, you may leave the VOB in place on the filer rather than copying it to the new server. However, there are a few extra steps:
  • After locking the VOB, unmount it from the VOB server host and all clients. (Do this for all VOB moves, not just Windows to Linux or the UNIX system.)
  • Before executing fix_prot on the VOB storage, you must update all the files in the VOB storage directory on the filer to have Linux or UNIX-compatible protections, which you can do with a recursive chown command to the VOB owner, such as chown -R vobadmin myvob.vbs. Then proceed with the remaining steps.
  • The reformatvob, register, and mktag commands require the use of -host, -hpath, and -gpath flags (as appropriate), because the VOB storage is on a filer. For example: 
    cleartool reformatvob -load -host linux-hostname -hpath /nfs-4-enabled/pathname/myvob.vbs /nfs-4-enabled/pathname/myvob.vbs


cleartool register -replace -vob -host linux-hostname \
 -hpath /nfs-4-enabled/filer/vobstg/myvob.vbs /nfs-4-enabled/filer/vobstg/myvob.vbs
cleartool mktag -vob -replace -tag /vobs/myvob -host linux-hostname -gpath /net/filer/vol/vobstg/myvob.vbs /nfs-4-enabled/filer/vobstg/myvob.vbs