Getting Started

Invalid tracks in SRDF pairs

Invalid tracks in SRDF configurations indicate that the data is not synchronized between the two devices in an SRDF pair. On both the source and target sides of an SRDF configuration, the Symmetrix array keeps an account of the tracks that are "owed" to the other side. The owed tracks are known as remote invalids. For example, consider the case of an R1 device whose logical connection to its R2 has been suspended. If both devices are made write-accessible, hosts on both sides of the SRDF links can write to their respective devices, creating R2 invalids on the R1 side and R1 invalids on the R2 side. Each invalid track represents a track of data that has changed since the two sides were split. To re-establish the logical links between the R1 and R2, the invalid tracks must be resolved. The resolution of invalid tracks depends on which control operation you perform. For instance, you can have remote invalids on both sides prior to an establish or a restore operation. If so, performing an establish operation indicates to SRDF that you want to copy the modified R1 tracks to the R2 side. In the process, any tracks that were modified on the R2 side are overwritten with data from corresponding tracks on the R1 side. Performing a restore operation indicates the oppositethat you want to copy modified R2 tracks to the R1 side. In the process, any tracks that were modified on the R1 side are overwritten with data from corresponding tracks on the R2 side.

SRDF device and link state combinations

When you invoke a control action on an SRDF pair, the SRDF pair state may be changed. This depends on whether the SRDF state of the source (R1) side, the SRDF links, or the SRDF state of the target (R2) side has changed. Additionally, the state of a device can change if its front-end or back-end Integrated Directors change in the SRDF links. Table 4 shows each SRDF pair state resulting from the combination of the states of the source and target devices and the SRDF links. It also shows the possible R1 or R2 invalid tracks for each SRDF pair state.
Table 4 Possible SRDF device and link state combinations (page 1 of 2) SRDF pair state Synchronized Failed Over R1 Updated R1 UpdInProg Split SyncInProg Suspended Partitioned3 Partitioned4 Source (R1) SRDF state Ready (RW) Not Ready or WD Not Ready or WD Not Ready or WD Ready (RW) Ready (RW) Any status2 Any status Not Available SRDF link state Ready (RW) Not Ready Ready (RW) or WD Ready (RW) or WD Not Ready or WD Ready (RW) Not Ready or WD Not Ready Not Ready Target (R2) SRDF state Not Ready or WD Ready (RW) Ready (RW) Ready (RW) Ready (RW) Not Ready or WD Not Ready or Write Disabled Not Available Any status R1 or R2 invalid tracks 0 01 >01 >0

Understanding SRDF pair states and links

27