Well Invalid tracks and tracks which exists in your R1 device waiting to be updated in R2 device. For example you have dev A as your R1 Device and Dev B as your R2 dev. You updated the R1 device with writes. Now these extra writes are the Invalid tracks present in your R1 that is they exist in your R1 device but not your R2 dev. This is a way enginuity knows which tracks to send to the R2 device. They only replicate the Invalid tracks from R1 to R2 so both the Devices are in sync.
Hi All, want to understand about source R1 invalid tracks and Target R2 invalid tracks it will be very help full if somebody explain this. I have attached the below output in txt for better reading. When I started SRDF -------------------       Source (R1) View                Target (R2) View    MODES --------------------------------    ------------------------ ----- ------------             ST                  LI      ST Standard      A                  N      A Logical      T  R1 Inv  R2 Inv  K      T  R1 Inv  R2 Inv      RDF Pair Device  Dev  E  Tracks  Tracks  S Dev  E  Tracks  Tracks MDAE  STATE -------------------------------- -- ------------------------ ----- ------------ N/A    244B RW      0  1054277 RW 028B NR      0  1054011 C.D.  SyncInProg N/A    2443 RW      0  1053378 RW 0293 NR      0  1053253 C.D.  SyncInProg N/A    243B RW      0  1053888 RW 02CB NR      0  506157 C.D.  SyncInProg N/A    2433 RW      0  1052837 RW 02D3 NR      0  1052658 C.D.  SyncInProg N/A    242B RW      0  1053013 RW 02DB NR      0  1052861 C.D.  SyncInProg N/A    2423 RW      0  1052743 RW 05CB NR      0  1052453 C.D.  SyncInProg After some time -------------------------       Source (R1) View                Target (R2) View    MODES --------------------------------    ------------------------ ----- ------------             ST                  LI      ST Standard      A                  N      A Logical      T  R1 Inv  R2 Inv  K      T  R1 Inv  R2 Inv      RDF Pair Device  Dev  E  Tracks  Tracks  S Dev  E  Tracks  Tracks MDAE  STATE -------------------------------- -- ------------------------ ----- ------------ N/A    244B RW      0      11 RW 028B NR      0        0 C.D.  SyncInProg N/A    2443 RW      0      27 RW 0293 NR      0        0 C.D.  SyncInProg N/A    243B RW      0      22 RW 02CB NR      0        0 C.D.  SyncInProg N/A    2433 RW      0      34 RW 02D3 NR      0        0 C.D.  SyncInProg N/A    242B RW      0      12 RW 02DB NR      0        0 C.D.  SyncInProg N/A    2423 RW      0      18 RW 05CB NR      0        0 C.D.  SyncInProg
want to understand about source R2 invalid tracks and Target R2 invalid tracks