EVA 5000 Data Migration to EVA 8000 using CA

[Lyndon Handy]

Need to migrate all data from existing EVA 5000 to new EVA 8000, via Continuous Access EVA for phased cutover and speed.
Current state:
EVA 5000 at VCS 3.025
~12TB of useable data
EVA 8000 *new* at XCS v5 online, empty
CA or RSM not yet installed, have temp keys
Windows 2K3 and 2K environment, SP 4.0C (no patch)

Is CA supported in this manner? What minimum versions of VCS, Securepath, do I need to upgrade to?

Suggested game plan:
1) Zone fabric for new (EVA 8000's) SMA to manage both EVA's via CV 4.122. Install RSM 1.2 or CA 2.2 on new SMA
2) Patch Securepath on all windows platforms to SP 4.0C SP2-1 to prepare for VCS 3.028 upgrade
3) Upgrade VCS from 3.025 to 3.028 on EVA 5000
4) Establish DR groups and synchronize
5) Install MPIO FullFeature on servers (to be supported with EVA 8000), split mirrors and present new LUNs one-by-one and cutover to new LUNs on EVA 8000 and test
6) Repeat step 5 until all data has been migrated to EVa 8000, unpresent old LUNs, un-initialize EVA 5000 and redeploy

Q: Must we upgrade VCS to 4.001 to be able to safely replicate to the EVA 8000? Let me know if I have missed anything?

TIA!

[Steven Clementi · Accepted solution]

Lyndon:

If you are not having any problems with your Secure Path version at the moment, I probably would not worry about upgrading it as you will need to remove it once your done with the 5000. FF-MPIO works with Secure Path so there are no issues having them installed together.

As for your VCS, you should have no problem as well. Again, unless you plan on re-utilizing the 5000, you probably shouldn't bother upgrading it.

Current VCS is 3.028, or 4.001 for those that want Active/active controllers and other ported features.

Current XCS is 5.031 I believe. I might be off.

You probably want to upgrade the 8000 to the latest code before anything so you don't have to do it later.

To answer your question, no. I have successfully migrated data from a 5000 to a 6000 without even going to 3.028. I believe I was on 3.014 or 3.020.

If you want to upgrade the VCS on the 5000, then your gameplan looks ok. If you do the VCS, you should probably do the drive firmware as well, just to be on the safe side, but I think that is all un-necessary, unless you are going to continue to use the 5k or redeploy... in which case, you can probably do all those upgrades after you replicate the data to safe you some time.. and some potential for failure or unexpected events during unneeded upgrades.


Steven

[gurdeep_2]

I too did this same migration a few weeks ago.
I had EVA5000 controller version 3.025 and EVA8000 controller version 5.031
Command View 4.1.2.2 and continious access 2.2
one glitch I ran into was, after presenting the virtual disks to the servers, there is a "Write Protect" switch that is set to "Yes" which needs to be changed to "No" on the EVA8000.

I also had to rename disks from "Local Disks" in windows to "Data", etc. but only on a single occasion.

[Ivan Ferreira]

We did a migration from 5000 to 4000, basically will be the same to 8000. Attached are the requisites.

[Lyndon Handy]

This is all great feedback and thanks for your vote of confidence in the plan- 2 important questions to help finalize:

1) When the data has been migrated to the EVA 8000, we plan to use a portion of the EVA 5000 disks on the EVA 8000 for capacity. Assuming the disk firmware upgrade done as part of the VCS 3.028 firmware upgrade, Can we delete the FC disks from the disk group, then physically move the disks to the EVA 8000? Are there transportability risks? Will XCS recognize these as "new disks" with no data?
2) For CA, is it best to simply use the new RSM v2.0 to setup DR groups and suspend or split LUN synchronization, or simply the bare-bones CV 4.122 GUI to create and delete DR groups? Confused on CA version #'s versus RSM version 2.0.

thanks