Special procedures for moving snapshot views on Windows®

When you move a snapshot view on Windows®, you must preserve both the ACLs of the view storage directory and the modification times of loaded elements in the snapshot view directory.

About this task

You can use the Windows® xcopy utility to copy the snapshot view directory, but you must use the HCL VersionVault ccopy utility (described in Preserving NTFS ACLs when copying a VOB or view storage directory) to copy the view storage directory. You must run the copy utility on the host to which the view is being moved. In the following example, the view storage directory view.stg is a subdirectory of the snapshot view directory v5_integration.vws.

C:\VersionVaultStorage\views>
net use E: \\boron\viewstg
C:\VersionVaultStorage\views>
xcopy /e/v/i/r/h/k E:\v5_integration.vws v5_integration.vws
C:\VersionVaultStorage\views>
rmdir v5_integration.vws\view.stg
C:\VersionVaultStorage\views>
ccopy E:\v5_integration.vws\view.stg v5_integration.vws

xcopy normally preserves the modification times but not the attributes, unless the /k option is used to preserve the attributes. Failure to use the /k option can cause VersionVault processes to consider all checked-in files as hijacked files.

Additionally, by using xcopy, the parent directory's ACL can be inherited by the copied snapshot view of the storage directory, which can cause problems with the view access. ccopy preserves NTFS ACLs as required by HCL VersionVault but does not preserve file modification times. Failure to use ccopy to copy the view database (located in .view.stg) can cause unknown style permissions and other errors when trying to register the snapshot view in its new location.