Any subset of replicas in a VOB family can preserve identities and permissions. Within this set of replicas, the owner, group, and access mode of an object are kept the same across all the replicas. Adding a replica to or deleting it from the set has no immediate effect on the replica’s objects. However, future changes to identities are propagated among all of the replicas in the VOB family that preserve identities and permissions. Future changes to permissions are propagated among all of the replicas that preserve identities and permissions or permissions only.
Note: On UNIX, preserving changes to identities across all sites is possible only if all sites support the same user-group accounts. On Windows, ownership modes (UIDs and GIDs) are not consistent across domains. Therefore, if all replicas in a VOB family are not in the same Windows domain, the entire set of replicas cannot preserve identities and permissions. You can preserve identities and permissions in a subset of replicas in the same domain. In a mixed environment, you cannot preserve identities and permissions on the entire set of replicas. For more information, see Identities and Permissions Strategy for VOB Replicas.
You can change a replica in the following ways:
To change a replica’s preservation property:
On UNIX or Windows, you can use the chreplica command.
To change from identities and permissions preserving or permissions preserving to nonpreserving:
multitool chreplica –npreserve boston_hub@/vobs/dev Updated replica information for "boston_hub".
To change from identities and permissions preserving to permissions preserving:
multitool chreplica –perms_preserve boston_hub@/vobs/dev multitool: Warning: Although replica now preserves only permissions, existing objects may still reflect previous identities- and permissions-preserving state. multitool: Warning: In a permissions-preserving replica, cleartool protect operations will fail on client machines running ClearCase versions associated with feature level 3 or lower. Updated replica information for "boston_hub".
To change from permissions preserving to identities and permissions preserving:
multitool chreplica –preserve boston_hub@/vobs/dev multitool: Warning: Although replica now preserves identities and permissions, existing objects may still reflect previous permissions-preserving state. Updated replica information for "boston_hub".
To change from nonpreserving to identities and permissions preserving:
multitool chreplica –preserve boston_hub@/vobs/dev multitool: Warning: Although replica now preserves identities and permissions, existing objects may still reflect previous non-preserving state. Updated replica information for "boston_hub".
To change from nonpreserving to permissions preserving:
multitool chreplica –perms_preserve boston_hub@/vobs/dev multitool: Warning: Although replica now preserves permissions, existing objects may still reflect previous non-preserving state. multitool: Warning: In a permissions-preserving replica, cleartool protect operations will fail on client machines running ClearCase versions associated with feature level 3 or lower. Updated replica information for "boston_hub".
On Windows, you can use the Properties Browser to change this property:
If you change the replica to permissions preserving or identities and permissions preserving, the appropriate warning is displayed (see the chreplica output above).
For restrictions, see the chreplica reference page.
If the import succeeds, you can use the protectvob command to undo the group changes you made.
For example, on UNIX, the following command finds all file and directory elements in /vobs/dev and executes the protect command:
cleartool find /vobs/dev -all -type fd –exec ’cleartool protect –chown vobowner –chgrp vobgrp $CLEARCASE_PN’
On Windows, the following command finds all file and directory elements in \dev and executes the protect command:
cleartool find \dev -all -type fd –exec "cleartool protect –chown vobowner –chgrp vobgrp %CLEARCASE_PN%"