As per Primus solutions,In order to perform a clone on R2-side one full copy is needed before activating in a consistent mode for SRDF/A.Can this be incremental after this? or does this needs to be full copy every time? I am listing the commands also..let me know,if they are(not)going to work for R2 side.
Symclone -g <dgname> create -precopy -diff -rdf -tgt (For the initial establishment,or is the -copy -diff going to work also?) symclone -g <dgname> activate -consistent -rdf -tgt
let me say,I need to sync the clone day after with changed data,Can i issue, symclone -g <dgname> establish -consistent -rdf -tgt
Also,I am planning to use the -both_sides with the establish but it seems its giving me an error (not a valid option)
Unfortunatly I don't have experience with -both_sides option ... If possible I'll dig a little next week with this feature ..
Note that when you create session with -differential, the recrate will obviously be incremental. The pre-copy process doesn't force a full copy. Enabling pre-copy means you start copying tracks right after CREATING/RECREATING the pairs. Thus when you recreate sessions, you'll start copying changed tracks.
Please note that the procedure I gave you is what my beloved customer uses twice every day on 20 servers .. Thus I can tell you it works
We are doing the same thing, and to answer the one question that may have got lost (or glossed over) in the rest of the thread, if you are doing clones of an R2 the -precopy is definitely required. You need to have a script issue the precopy and scan the output of queries until the precopy completes one cycle before issuing the activate.
As Stefano pointed out, the precopy cycle after the initial activate is only an incremental update even though we talk about a "full cycle". The precopies after the first activate tend to be fairly fast... but that will depend a lot on your rate of change.
The command will return $? = 0 if all devices in pairfile (or if you prefer in your DG) already completed the precopy. Any other return code means at least a device is still precopying (poor wording but hope it's clear)
Oddly enough I suggested that the support team managing the clone process use "verify" to monitor progress, but they preferred to write a script that checked the output of a "query". I'm not sure if there was additional info they wanted to capture or what, but I had completely forgotten about using verify since my guys didn't want to use it.
It is actually another team that manages the clone process since it is part of a business process that has to tie into quiescing the database on the R1 side of the SRDF/A link. Storage is only responsible for making sure SRDF/A stays up.