Moving VOBs
You cannot use an ordinary file-system copy utility to copy a VOB to another location. You must follow special procedures that maintain the integrity of VOB data and preserve permissions and ownership on VOB storage directories.
Procedures for moving VOBs are covered in the following scenarios:
- Moving a VOB to another disk partition on Windows® or to another Windows host in the same domain.
- Moving a VOB to a Windows host in a different domain.
- Moving a VOB to another disk partition on Linux or the UNIX system or to another host running Linux or the UNIX system with the same architecture.
- Moving a VOB to a host running Linux or the UNIX system, with a different architecture.
- Moving a VOB from a Windows host to a host running Linux or the UNIX system.
- Moving a VOB from a host running Linux or the UNIX system to a Windows host.
When moving VOBs, bear in mind that
- Two hosts are said to have the same architecture when they have the same binary data format. Binary data format is controlled by CPU type, so platforms with the same CPU type have the same binary data format. Whenever you move a VOB to a host with a different architecture, it must be reformatted to the new host's binary data format.
- In the case of ACL-protected VOBs, that platforms with the same architecture (such as Linux and the UNIX system) can have different ACL mechanisms that can require different copying and archiving procedures.
- You can use the mkreplica command to move a VOB. If the VOB is ACL-enabled, the ACLs may or may not be preservable, depending on the source and target operating system types (and in the case of replicated VOBs, the MultiSite configuration as well). If you are moving a VOB from Windows to Linux or the UNIX system or vice versa, you must create a non-preserving replica because these platforms do not share the same namespace.
- Lock the VOB before untagging and unregistering it to prevent lock failures on VOBs that reference other VOBs, such as a PVOB.
- Remove any trigger scripts from the VOB before moving it. After moving the VOB, point the trigger scripts to the new location of the VOB.