mkreplicationpolicy

Use the mkreplicationpolicy command to create a replication policy.

Syntax

Creating a HA replication policy

Read syntax diagramSkip visual syntax diagram mkreplicationpolicy -name replication_policy_name -topology 2-site-ha -snapshotsyesno -location1systemlocation1_system_namelocation1_system_id -location1iogrp location1_iogrp_id -location2systemlocation2_system_namelocation2_system_id -location2iogrp location2_iogrp_id

Creating a DR replication policy inside a partition

Read syntax diagramSkip visual syntax diagram mkreplicationpolicy -name replication_policy_name-topologyasync-drrpoalertrpo_alert -partitionpartition_namepartition_idpartition_uuid

Creating a DR replication policy outside a partition

Read syntax diagramSkip visual syntax diagram mkreplicationpolicy -name replication_policy_name -topology 2-site-async-dr -rpoalert rpo_alert -location1systemlocation1_system_namelocation1_system_id -location1iogrp location1_iogrp_id -location2systemlocation2_system_namelocation2_system_id -location2iogrp location2_iogrp_id
A new replication policy can only be created when all the systems that are specified by the policy are online and connected.

Parameters

-name replication_policy_name
(Optional) Specifies the name of the policy.
Note: If a replication policy with the same name exists on the remote system, the command fails. Specify a unique name and rerun the command.
-topology 2-site-async-dr | 2-site-ha | async-dr
(Mandatory) Specifies the topology of the policy.
2-site-async-dr: 2-site asynchronous disaster recovery
  • This type of policy is used with volume groups that are not in a storage partition.
  • The -location parameters are used to specify the systems and the I/O groups in those systems that are used for replication.
  • The -rpoalert parameter must be specified for this type of policy.
  • This type of policy can be used for 2-site replication only.
async-dr: asynchronous disaster recovery
  • This type of policy is used with volume groups that are in a storage partition.
  • The storage partitions are linked to define the systems that are used for disaster recovery replication. The -location parameters are not used.
  • The partition parameter must be used to specify the partition in which the replication policy is created.
  • The -rpoalert parameter must be specified for this type of policy.
  • This type of policy can be used for 2-site disaster recovery and 3-site (high availability with disaster recovery) configurations.
2-site-ha: High availability
  • This type of policy is used with storage partitions.
  • The -location parameters are used to specify the systems and the I/O groups in those systems that are used for replication.
  • This type of policy can be used for 2-site high availability and 3-site (high availability with disaster recovery) configurations.
-snapshots yes no
Specifies whether the snapshots created for volumes and volume groups associated with the policy will be replicated to the remote system or not. It is only allowed to be specified on replication policies with a topology of 2-site-ha.
-rpoalert rpo_alert
Specifies the recovery point objective (RPO) alert threshold in seconds. An alert will be logged if the recovery point exceeds this value.

The minimum value is 60 seconds (one minute) and the maximum value is 86400 seconds (1 day). The value must be a multiple of 60 seconds.

-partition partition_name | partition_id | partition_uuid
Specifies the partition in which this replication policy will be created. This parameter can only be specified for an async-dr topology.
-location1system location1_system_name | location1_system_id
Specifies the name or ID of the system in location 1 of the topology.
-location1iogrp location1_iogrp_id
Specifies the ID of the I/O group of the system in location 1 of the topology.
Note: The I/O group parameters accept only numeric ID.
-location2system location2_system_name | location2_system_id
Specifies the name or ID of the system in location 2 of the topology.
-location2iogrp location2_iogrp_id
Specifies the ID of the I/O group of the system in location 2 of the topology.
Note: The I/O group parameters accept only numeric ID.
Note: This command is available during the upgrade process.
When using the partition IP address to run this command, consider the following:
  • The user must identify objects using the name or UUID. Short IDs cannot be specified when using the partition IP address.
  • Only objects belonging to the partition can be created or acted upon. When creating new objects, the -partition parameter will be auto-populated for the partition. You cannot move items out of a partition when using the partition IP address.

An invocation example

The following example creates a replication policy for asynchronous replication:

mkreplicationpolicy -name bath_bristol_dr -topology 2-site-async-dr
                -location1system bath -location1iogrp 0 -location2system bristol -location2iogrp 0
                -rpoalert 60

The resulting output:

Replication policy, id [2], successfully created