We have a DMX4 in CA and another in TX. SRDF/A is running from CA to TX. We will be upgrading from 5772 to 5773. We will upgrade the TX (DR) array one night and the CA (Prod) array the next night.
We replicate about 400 mainframe volumes along with a handfull of Windows volumes and Unisys volumes. What happens to SRDF/A during the Enginuity upgrade? Does it just keep running? Any issues to be concerned with?
The 5772 to 5773 Enginuity Upgrade with SRDF/A is supported but from a "best practice" if possible we would recommend having SRDF/A in a suspended mode.
I have another EMC guy telling me to put the RDF groups into adaptive copy disk mode rather than suspending. Last time we did an Enginuity upgrade we were not running SRDF in production but had some testing going on. If I remember correctly the upgrade actually stopped SRDF. When I came in the next morning all groups were in suspeneded mode and I neede to resume them all.
The open systems SRDF is managed with SE symrdf commands (symrdf -g winGroup suspend). But the Mainframe SRDF we manage by submitting MVS jobs that do things like pend_drops etc.
Ok I spoke to Tech support and Adaptive Copy would at least keep the data moving. My recommendation of Suspended mode cam from my PSE days many years ago!
We have done multiple code upgrades with DMX arrays running SRDF/A (mainframe and open systems). We no longer even take the devices out of SRDF/A mode it runs right through no problem.
Have you ever upgraded out of family from 5772 to 5773 with SRDF/A running. I'm hoping I can leave all SRDF running without changes during the upgrade. Also our mainframe will be kicking off batch Time Finder jobs to do Establish, Split etc during the upgrade. Hopefully these will run fine during the upgrade.
SSRDude
44 Posts
855
0
Posted March 9th, 2011 10:00
The 5772 to 5773 Enginuity Upgrade with SRDF/A is supported but from a "best practice" if possible we would recommend having SRDF/A in a suspended mode.
Gary Bastarache