Just break the SRDF cleanly.  Tracks will build however they will be destaged to disk so when the site is back online you can resume the sync.  Data will be re-read from disk and transferred back over the link to the target.  Let the data synchronize for a while and when it is nearing sync you can then enable SRDF/A.  It will then take a bit longer to get to a consistent state.  If you have several RDF groups you can either bring them all online or bring them up in whatever priority you want; if you have a more important group bring that online first etc.
All:  We have a VMAX in our primary site and a DMX "target" array in our DR site with asynch SRDF/A running continuously from VMAX -> DMX.  We have to shut down the DR site for 23 hours (estimated) to upgrade the UPS system in the DR site, and they can't do it (for some reason) one "half" at a time.  They have to shut down the entire site.  That's (in roughly this order):  Applications, Servers, Storage, LAN, WAN.  Then start them up again in reverse order.  So, my question is, what do I do with our SRDF?  Ideally I DON'T want to do a full establish when we get back up.  I'd like to be able to do a "resume".  We have in the past had to suspend our SRDF and then resume it for up to 10 hours for various little problems like they replaced the WAN router in DR or something like that; and it resumed just fine.  I'm not asking for the command syntax.  I know that (I think.).  Here's what I'm really asking about: 1.  I'm pretty sure that I have to suspend the SRDF (symrdf -g rdfgXX -rdfg XX suspend -force -noprompt) before the outage. 2.  The VMAX (source) will then "accumulate" changes that it would otherwise be sending "down the line" to the DMX (target). 3.  Is there some point at which the accumulated changes will reach a point where they fill up the "holding area", and the SRDF will be "broken" and I'll have to do a full establish on "restart". 4.  Can I do anythingn to make the "holding area" bigger?  Can I do anything to prevent a "full establish" on restart.  Here's another issue: 1.  We had a case last year where just one of our "rdfg"s went "interrupted".  We're not sure why. 2.  The result was that an Oracle Application crashed. 3.  In "Root Cause Analysis" EMC stated that SRDF "caches" changes, and the "holding area" (that's my word - I forget what they called it) filled up. 4.  When the holding area filled up, the VMAX refused write requests from the Application, and the application crashed. 5.  I'm embarrased to say that I don't remember how we fixed this problem - I think that we had to do a full establish of the SRDF rdfg.  This is a long question.  I'd appreciate your advice on this.      Stuart
We are shutting down our DR Site for 23 hours. How do I handle our SRDF?