Operating System Software Owner manual

• The period can be set only for groups whose mode is asynchronous periodic (see
creatercopygroup).
• Do NOT use the reverse value of the <dr_operation> as part of the normal disaster
recovery process.
EXAMPLES
The following example sets the group policy for Group1:
# setrcopygroup pol auto_recover Group1
The following example reverses the current direction of secondary group Group1 on System2 (the
secondary system) so that I/O might be applied to the group after disaster recovery:
# setrcopygroup failover Group1.r121
The following example sets Group1 to be automatically synchronized every 30 minutes to System2:
# setrcopygroup period 30m System2 Group1
The following example reverses the current direction of all secondary groups that start with the
name testgroup so that I/O can be applied to the groups during disaster recovery:
# setrcopygroup failover -pat testgroup*
NOTES
• An earlier version of this command provided fail_wrt_on_err and no_fail_wrt_on_err
policies. These policies were deprecated in HP 3PAR InForm OS release 3.1.1.
• An earlier version of this command provided a target subcommand. This subcommand was
deprecated in InForm OS release 2.2.3.
• Reversing the direction of primary volumes will result in the loss of any data changed after
the group was stopped.
• There is no default resynchronization period. For groups whose mode is asynchronous periodic,
you must specify a resynchronization period using setrcopygroup period <value> or
resynchronizations will not automatically take place.
• The minimum interval for periodic resynchronizations is five minutes.
• If the mirror_config policy is set for this group's target and the group is a primary group,
then the setrcopygroup command will be mirrored to the target when the period and
pol subcommands are used.
• Use the -nosnap option when the primary system has failed or where the disks are ruined
or in an unknown state. For example, an uncontrolled shutdown can result in loss of data. If
you suspect that the primary volumes are not in a known good state, you should use this option
to force a FULL RESYNC when the primary system is restored.
• The -nosnap option can be used when making a secondary group take over as the primary
after a disaster takes down the primary (setrcopygroup failover -nosnap...). This
option indicates that no incremental resynchronization of the primary group is possible while
the primary system is coming back online. Without this option, a snapshot is taken when the
secondary system takes over as the primary. That snapshot is used to do an INCREMENTAL
synchronization of the primary after it is restored. This assumes that there was no loss of data
in the primary volumes when the primary system went down.
255