Remote Copy group policies

Auto failover

The auto failover policy, with HPE Quorum Witness, enables an automatic failover on a Remote Copy group. If the primary storage system fails, the group fails over to the secondary storage system automatically.

Starting in HPE Primera OS 4.2, the auto failover policy also enables Remote Copy group failover strategies for RAID set failure or metadata corruption of a primary volume in the group. To enable this functionality, the auto failover and the path management policies are required.

The auto failover policy is not enabled by default. When not enabled, if a disaster occurs, the Remote Copy group does not fail over and must be recovered manually.

This policy is required for an automatic transparent failover (ATF) Peer Persistence configuration.

Auto recover

When enabled, if a Remote Copy link goes down, the Remote Copy group is restarted automatically after the links recover.

If you enable the auto recover policy when the links are down and the group is stopped, the group does not automatically restart when the links recover. However, if auto recover is set and the links fail, and then you disable the policy, the Remote Copy group does not restart automatically after the links recover.

The auto recover policy is not enabled by default. When not enabled, you must restart the Remote Copy group manually after the links recover.

Auto synchronize

If a failover occurs and the auto synchronize policy is enabled, all virtual volumes in the Remote Copy group are automatically synchronized. Synchronization occurs after system recovery completes and the Remote Copy links recover. In synchronous long distance (SLD) and three data center Peer Persistence (3DC PP) configurations, this policy can be set on the Remote Copy group synchronous targets only.

NOTE:

In SLD configurations, to perform a failover to the synchronous target, the SLD group must be stopped on all targets, or started on all targets. To perform a failover to the periodic target, the SLD group must be stopped on all targets.

In 3DC PP configurations, the target links must be down to perform a failover to the synchronous target. To perform a failover to the periodic target, the groups on the periodic target must be stopped. The links can be up or down.

The auto synchronize policy is not enabled by default. When not enabled, you must manually synchronize the Remote Copy group after the system recovery completes and after the links recover.

Mirror

The mirror policy automatically applies actions and settings to the Remote Copy group at the source and target storage systems simultaneously. For example, if you start or stop a Remote Copy group, the group starts or stops on the source and target systems simultaneously. You can start or stop the Remote Copy group even if the target storage system is disconnected from HPE SSMC.

The mirror policy option is automatically enabled when you create a Remote Copy configuration.

Over period alert

If periodic synchronization does not complete within the specified synchronization period, the over period alert policy generates alerts.

The over period alert policy is enabled by default for periodic Remote Copy groups. This policy applies to periodic mode only.

Path management

The path management policy sets the Asymmetric Logical Unit Access (ALUA) path from the host to the primary Remote Copy group to active. The path to the secondary Remote Copy group is set to standby.

If path management is not enabled, ALUA behavior is not enabled for volumes in the Remote Copy group. The Target Port Group state of the volumes is active (default).

This policy is required for Peer Persistence configurations and is applied only to the synchronous groups in a Peer Persistence or 3DC PP configuration.

Multi-target Peer Persistence

The multi-target Peer Persistence policy enables the primary Remote Copy groups to update the secondary groups synchronously with a Peer Persistence target and periodically to a tertiary site. The policy must be set on all group targets in a 3DC PP configuration.

This policy is required for 3DC PP configurations.