Retention class collisions

A retention class collision occurs when these events occur in the order shown:

1.Different changes are made to the same retention class on each of the two systems involved in a replication link.

2.The changed retention class on one of the systems is replicated to the other system.

If a collision occurs when a change to a retention class is replicated from one system (system A) involved in a replication link to the other system (system B) involved in the link:

If the last change to the retention class on system A is more recent than the last change to the class on system B and:

oThe value of the class on system A is greater than the value of the class on system B, HCP changes the value of the class on system B to the value of the class on system A

oThe value of the class on system A is less than the value of the class on system B and:

System B is in enterprise mode, HCP changes the value of the class on system B to the value of the class on system A

Note: An exception to this rule is when the value of the class on system A is -2 (Initial Unspecified) and the value of the class on system B is not 0 (Deletion Allowed). In this case, the value of the class on system B does not change.

System B is in compliance mode, HCP does not change the value of the class on system B

If the last change to the retention class on system B is more recent than the last change to the class on system A, HCP does not change the value of the class on system B

Note: A retention class value of -1 (Deletion Prohibited) is greater than a value that’s a specific duration. A retention class value of 0 (Deletion Allowed) or -2 (Initial Unspecified) is less than a value that’s a specific duration.

Trademark and LegalDisclaimer

© 2016 Hitachi Data Systems Corporation. All rights reserved.