Let us know your exact motive. Are you looking for setting up RESTARTABLE copy of your R2 data ?
If yes, the Consistency should be enabled. Consistency basically means that write ordering and dependent writes are maintained when data is replicated. To put it in simpler words, assume that you encountered a Disk faliure on Source Symm. Due to this one of your R1 is WriteDisabled.
If the Consistency is enabled on the RA Group to which thisDevice belongs, then your replication will stop for all the devices in that RA Group. This will ensure that no new data is written on R2.
Internally, consistency is not as simple as I described. It is managed by the microcode itself.
There are couple of things you should keep in mind before you enable consistency:
1) Do you have multiple source Symms replicating to one or more targets?
2) Do you have a Composite group?
Write ordering and dependency write is taken care by SRDF. You dont need to enable consistency option to get write ordering/dependency writes. Consistency will help you in cases where you have multiple RA groups and if one link goes down, its going to suspend the other link also so the R2 site remains consistent. This is just one of the example. For more information please refer to the SRDF guide for more details.
I just want to modify Deepak's statement, "SRDF A is infact more useful than SRDF S if bandwidh is less". If you run the below command, it should tell you how much data you are behind the R1 and if r2 data is consistent or not. It does not require consistency to be enabled. I think many ppl in this thread have already discussed the use of consistency so i will not speak about it.
dell2850# symrdf -g test123 query -rdfa
.
.
.
.
Tracks not Committed to the R2 Side: 0 Time that R2 is behind R1 : 00:00:00 R2 Image Capture Time : N/A R2 Data is Consistent : Yes
PVB9369
12 Posts
1236
0
Posted August 29th, 2011 10:00
Hello iflaas,
My name is Paul and I work in Level 2 of Symmetrix hardware.Most of our customer due use consistency as they
need their R2 side to be consistent in case of a needed failover to bring their hosts and applications up on the
R2 (Remote) side.
Other customers use the remote side as just a backup so they don't have to be fully consistent all the time.
Some of the financial accounts need to always be consistent to be in compliance.
If you are in consistent mode you can drop out if you have un-protected disk drives and a drive drops ready.
Then you would need to do cleanup and re-start SRDF/A again.
It is really up to each individual account and what they are using SRDF/A for.
Please let me know if I can be of assistance with any other details.
Thank you,
Paul