SRDF query

Hi Sushma,

Please consider moving this question as-is (no need to recreate) to the proper forum for maximum visibility.  Questions written to the users' own "Discussions" space don't get the same amount of attention and questions can go unanswered for a long time.

You can do so by selecting "Move" under ACTIONS along the upper-right.  Then search for and select: "Symmetrix Support Forum" which would be the most relevant for this question.

Thanks Fenglin

If the RDF links are suspended while the R1 devices are in operation, The R1 invalid tracks counter will increment.

If the R2 devices are updated locally, R2 invalid track counter will increment.

If the link is not operational, the remote query will not be able to determine the number of invalid tracks at the remote end. In this case a local query on the R1 and a local query on the R2 will provide an accurate account of invalid tracks at each site.

When an SRDF Establish (for example) is run, one of the steps involved is the "mark and merge". This is where SRDF figures out which tracks have been updated on each site. The number of invalid tracks will go up on each side if there have been updates to both the R1 and the R2. This can be seen by running a query after the establish is done.

Thanks for the reply.

Need few more clarifications.

If the RDF links are suspended while R1 devices are in operation, R2 invalid tracks column is getting incremented, indicates that changes in R1 side that needs to be sent to R2 side.

When the links are suspended, still R2 devices will be WD to its host, so R2 devices cannot take any updates from its host.

Only when the replication is split R2 will be RW to host.

Just want to know In which scenario, R1 invalid tracks column in R1 side and R2 invalid tracks column in R2 side will be incremented in SRDF query oputput..

Even the link suspended the R2 devices will be WD to the host.
When split operation performed then R2  will be RW to the host

R2 invalid track column will increase at R1 side when the SRDF link is in suspend/split state ,which says these are the tracks that has not yet written to R2 device.

When link get ready this invalid tracks will be flood to R2.

Similarly when the link is in split state,and R2 device is being accessed by host .

Then if you run SRDF query at R2 site, it will show you the R1 invalid tracks which says these are the tracks which are modified at R2 .

Thanks Mahesh.

I understand what is R2 invalids in R1 and R1 invalids in R2.

I want to know what is R1 invalids in R1 and R2 invalids in R2.

in what scenario R1 invalids on R1 accumulates?

I am sorry if the question is confusing

These numbers will accumulate in one off the following scenarios..

You have suspended the links and no data is replicating from R1 to R2, Writes are still going from R1 to R2 so R1 owes tracks to R2, you will have R1 invalids that will get copied when you resume your links.

You Have split the links, you are now running on your R1 but perhaps have mounted the R2 for a test, you may see invalids on both sides..  When you do establish a track compare is done and the tracks are copied from R1 to R2.

You have Failed over to the R2 and are up on your R2 volume, R2 may have invalids owing to R1, in this instance you may need to do R1 update to copy tracks in reverse direction from normal operation getting ready for a failback.

Hope this Helps, the RDF product guide will have more information

Thanks Paul