7.4 Changing Ownership Preservation

Any subset of replicas in a VOB family can be ownership-preserving. Within this group 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 group has no immediate effect on the replica's objects. However, future changes to object permissions are propagated among all of the ownership-preserving replicas in the VOB family.

NOTE: On UNIX, maintaining ownership preservation across 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 be ownership-preserving. You can maintain ownership preservation on a subset of replicas in the same domain. In a mixed environment, you cannot maintain ownership preservation on the entire set of replicas. For more information, see Element Ownership and Ownership Preservation.

The most common change is to convert a replica from ownership-preserving to non-ownership-preserving. For example, if a replica was created incorrectly as ownership-preserving, you may need to change it. You can change a replica from non-ownership-preserving to ownership-preserving. The replica will receive future changes to ownership information, but the original ownership information is not restored.

To change a replica's ownership-preserving property:

  1. At the master replica, change the replica property.

  2. On UNIX or Windows, you can use the chreplica command to change this property:

    On Windows, you can use the Properties Browser to change this property:

    1. Display properties of the replica. See Displaying Properties of a Replica.

    2. To change from non-preserving to preserving, select the Ownership-preserving check box. To change from preserving to non-preserving, clear the Ownership-preserving check box.

    3. Click OK or Apply.

    See the chreplica reference page for restrictions.

  3. If the changed replica is not self-mastering, export an update packet from the master replica to the changed replica.

  4. At the changed replica, import the update packet. If the import fails because the VOB group lists are different, use the cleartool protectvob command to change the group list for the importing VOB replica, and then try the import again.

  5. If the import succeeds, you can use the protectvob command to delete the group you added.

  6. (If the replica was changed to non-ownership-preserving) At the changed replica, use the cleartool protect command to change the ownership of all elements in the replica to the VOB owner at your site.

  7. cleartool protect -chown vobowner -chgrp vobgrp -recurse /vobs/dev