- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE 3PAR StoreServ Storage
- >
- Re: Another EVA to 3PAR Migration Question
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-05-2015 10:35 AM
тАО02-05-2015 10:35 AM
Another EVA to 3PAR Migration Question
I read the guide, but need to be sure of 2 issues.
EVA 4100 to 3PAR 7200. Only Window 2008R2 servers.
All the Zoning is done on the 3PAR switches, right?
The only zoning that is done on the EVA is to disconnect the Windows Host server (when asked).
The Windows Host server is NOT be Zoned (on the 3PAR) until asked to (not before hand), right?
Adding the DSM '3PARdataVV' is that done manually or does it get added automatically?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-05-2015 02:20 PM
тАО02-05-2015 02:20 PM
Re: Another EVA to 3PAR Migration Question
Basically, yes.
All the zoning is done, when asked on the switches. (There are no "3PAR switches".)
The '3PARdataVV' string can be manually added in Windows MPIO ahead of time, or once the Windows server is zoned to the 3PAR, it will show up in MPIO as a new potential device type. You click on it and add it.
Either way, when adding the '3PARdataVV' string, Windows will want to reboot.
Note: While I work for HP, all of my comments (whether noted or not), are my own and are not any official representation of the company.
----------
If my post was useful, click on my KUDOS! "White Star" !
Note: While I am an HPE Employee, all of my comments (whether noted or not), are my own and are not any official representation of the company
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-06-2015 02:38 AM
тАО02-06-2015 02:38 AM
Re: Another EVA to 3PAR Migration Question
Hello Mike,
As for SAN zonin you are right, just follow the manual and the migration interface indications.
Just in case you are dealing with windoes 2008 clusters.
This is what I have done on the windows server, and it worked flawlessly.
STOP (not pause) all the EVA volume replication, valid for servers and clusters, this is not supported (however, it will warn you with an error message )
If the Host is a cluster member, you have to release all the SCSI on the cluster volumes, before the migration.
The Windows 2008 cluster must be disabled and all the cluster applications must be STOPPED on all the cluster nodes.
1. Configure from control panel Windows 2008 Microsoft MPIO DSM add 3PARdataVV as device HW ID
2. Just to be on the safe side, on Clusters, I setted to Manual the cluster service, in that way they will not start at the required MPIO change reboot. They can be started after the migration manually (then set them automatic again).
3. Shutdown Host, after the migration in started you can reboot the servers/clusters
Regards
Sergio
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-06-2015 06:07 AM
тАО02-06-2015 06:07 AM
Re: Another EVA to 3PAR Migration Question
Thanks Sheldon & Sergio,
Sheldon when you say there are no "3PAR switches". To be clear I'm running 2 independent SAN's. The EVA & 3PAR share nothing. So the Zoning is done on the 3PAR side only. I'm bring 3 fibre cables from the EVA to the 3PAR. 2 cables are from the EVA controllers & 1 from the CV server. I'm zoning them on the 3PAR side.
Sergio, I'm NOT using Clustering, but I am using Replication. When you say to 'stop & not pause', the choices are 'resume & suspend'. Do you mean 'suspend' or should I remove replication completely?
Thanks,
Mike
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-06-2015 06:15 AM
тАО02-06-2015 06:15 AM
Re: Another EVA to 3PAR Migration Question
Mike,
Sorry I should have said "Stop and Remove", even if suspended, the migration interface will intercept the volume replication relationship, and not allow you to continue.
It is up to you if you want to leave the replicated volumes in a consistent state, in this case you probably have to do something before stopping the replica.
Regards
Sergio