synchronous

Specifies the mode of replication. This attribute can be set to the following values:

synchronous=off for asynchronous mode of replication.

synchronous=override for synchronous override mode of replication.

Set synchronous=fail for synchronous mode of replication.

srlprot

Enables or disables log protection. The data volumes must have a DCM log for srlprot to be set to DCM or AutoDCM. This attribute can be set to the following values:

srlprot=autodcm enables log protection. The DCM logs are used to synchronize the data when the Replicator Log overflows, even when the Primary and Secondary are connected.

srlprot=dcm enables log protection. The DCM logs are used to synchronize the data if the Replicator Log overflows, when the Primary and Secondary are disconnected.

srlprot=override enables log protection. If the Secondary is still connected and the Replicator Log is about to overflow then the writes are stalled until a predetermined amount of space, that is, 5% or 20 MB (whichever is lesser) becomes available in the Replicator Log. The log protection is automatically disabled if the Secondary becomes inactive due to a disconnection or administrative action, and Replicator Log will overflow.

srlprot=fail enables log protection. If the log is about to overflow the writes are stalled until a predetermined amount of space, that is, 5% or 20 MB (whichever is lesser) becomes available in the Replicator Log. If the connection between Primary and Secondary RVG is broken, then, any new writes to the Primary RVG are failed.

srlprot=off disables log protection.

latencyprot

Enables or disables latency protection. This attribute can be set to the following values:

latencyprot=off disables latency protection.

latencyprot=override enables latency protection. However, latency protection is automatically disabled if the RLINK becomes inactive due to a disconnection or administrative action.

latencyprot=fail enables latency protection.

See Latency protection - latencyprot attribute.

latency_high_mark

Specifies the maximum number of outstanding requests that are allowed when latency protection is enabled.

latency_low_mark

Specifies a value such that when the writes are stalled, the number of outstanding requests must drop to this value before latency protection can be disabled.

pri_host

Name or IP address of the Primary host. This can be used to set or modify a specific IP for replication if the host has multiple IP addresses.

sec_host

Name or IP address of the Secondary host. This can be used to set or modify a specific IP for replication if the host has multiple IP addresses.

packet_size

Specifies the size of packets in which data can be sent through the network during replication.

If you specify a value smaller than 1100 bytes then it is automatically rounded off to 1100 bytes. Similarly, if you specify a value greater than 64400, it is automatically rounded off to 64400 bytes.

Within the range of 1100 to 1400 bytes you can choose to specify any value in multiples of four. If the value you specify is not a multiple of four it is automatically rounded off to the next higher value that is a multiple of four.

From 1400 onwards any packet size that you specify is rounded off to the next multiple of 1400.

bandwidth_limit

Specifies a value that can be used to control the bandwidth that Volume Replicator needs to use for replication. If this attribute is not specified Volume Replicator uses the entire available bandwidth for replication. To disable bandwidth throttling, set this attribute to none. Note that the specified bandwidth value must be at least 1 Mbps (Megabits per second). You can specify the value in units of Kbps, Mbps, Gbps, or bps. The default is Kbps. If no value is specified then bandwidth throttling is disabled.

protocol

Specifies the protocol to be used for replication between the Primary and Secondary. Specify TCP or UDP.

If the setup includes a Bunker Secondary and replication is over IP, the protocol can be set to UDP or TCP. The default is UDP.

If the storage at the Bunker Secondary is directly accessible from the Primary, for example, DAS or SAN, use the STORAGE protocol, otherwise use TCP/IP or UDP/IP

compression

Specifies whether compression is enabled or disabled and takes the value of true and false respectively.