Certain TimeFinder copy operations are not allowed on devices that are SRDF protected, as these operations can conflict with each other. The availability of some actions depends on the current state of SRDF pairs. Refer to your product guide for details about supported features.
The following table provides a description the various SRDF pair states.
Table 1. SRDF pair states
State
Description
ActiveActive
The R1 and the R2 are currently in the default SRDF/Metro configuration which uses a Witness array:
There are no invalid tracks between the two pairs.
The R1 and the R2 are Ready (RW) to the hosts.
ActiveBias
The R1 and the R2 are currently in an SRDF/Metro configuration using bias:
The user could have specified “use bias” during the establish/restore action or the Witness array is not available.
There are no invalid tracks between the two pairs.
The R1 and the R2 are Ready (RW) to the hosts.
Consistent
The R2 mirrors of SRDF/A devices are in a Consistent state. Consistent state signifies the normal state of operation for device pairs operating in asynchronous mode.
Failed Over
The R1 is currently Not Ready or write disabled and operations have been failed over to the R2.
Invalid
The default state when no other SRDF state applies. The combination of R1, R2, and SRDF link states and statuses do not match any other pair state. This state may occur if there is a problem at the disk director level.
Mixed
A composite device group SRDF pair state. There exists different SRDF pair states within a device group.
Partitioned
Solutions Enabler is currently unable to communicate through the corresponding SRDF path to the remote array. Partitioned may apply to devices within an RA group.
For example, if Solutions Enabler is unable to communicate to a remote array via an RA group, devices in that RA group will be marked as being in the Partitioned state.
R1 Updated
The R1 is currently Not Ready or write disabled to the host, there are no local invalid tracks on the R1 side, and the link is Ready or write disabled.
R1 UpdInProg
The R1 is currently Not Ready or write disabled to the host, there are invalid local (R1) tracks on the source side, and the link is Ready or write disabled.
Split
The R1 and the R2 are currently Ready to their hosts, but the link is Not Ready or write disabled.
Suspended
The SRDF links have been suspended and are Not Ready or write disabled. If the R1 is Ready while the links are suspended, any I/O will accumulate as invalid tracks owed to the R2.
Synchronized
The R1 and the R2 are currently in a Synchronized state. The same content exists on the R2 as the R1. There are no invalid tracks between the two pairs.
SyncInProg
A synchronization is currently in progress between the R1 and the R2. There are existing invalid tracks between the two pairs and the logical link between both sides of an SRDF pair is up.
Transmit Idle
The SRDF/A session cannot push data in the transmit cycle across the link because the link is down.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\