- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- EVA 6000 to 8100 migration and Windows Cluster
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
Forums
Discussions
Discussions
Discussions
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
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
07-08-2008 06:16 AM
07-08-2008 06:16 AM
In my mind, the process would be:-
Create new groups/LUN's etc. on EVA 8100
Configure CA to replicate the data across
Take all cluster resources offline, and move them to one of the nodes, shutting down the other 3 nodes;
Shut down the fourth node, and let CA finish replicating so data is consistent;
Unpresent the old LUN's, and present the new ones, to all cluster nodes;
Boot up the cluster node again that has all the resources currently on it;
Use Microsoft Cluster Recovery Tool or dumpcfg.exe, to change the disk signatures on the new disks to match the old ones;
Rename drive letters where necessary;
Bring the resources online;
Move the resources back to their original nodes;
What do you think? Any suggestions/corrections would be really appreciated!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-09-2008 06:51 AM
07-09-2008 06:51 AM
Re: EVA 6000 to 8100 migration and Windows Cluster
1. the DR secondary luns will be created/ allocated automaticaly
2. after the CA replication ended stop the io on the cluster nodes (shutdown)
3. failover to the new eva, it mutualy swaps the roles of the primary/secondary.
4. you neednot do anything with the disk signatures because those are real clones
5. so the only thing is to power on the hosts and they will get the vdisks from the new eva
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-09-2008 06:56 AM
07-09-2008 06:56 AM
Re: EVA 6000 to 8100 migration and Windows Cluster
Thanks very much for your reply. Are you 100% sure about this? Have you done Windows Cluster migrations between EVA's before? It just sounds too good to be true! :)
All the other posts i've been reading seem to indicate that the signatures will definitely change....?
many thanks,
Raymond
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-09-2008 07:03 AM
07-09-2008 07:03 AM
Re: EVA 6000 to 8100 migration and Windows Cluster
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-09-2008 07:10 AM
07-09-2008 07:10 AM
Re: EVA 6000 to 8100 migration and Windows Cluster
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-09-2008 07:24 AM
07-09-2008 07:24 AM
Solutionthe strongest of the CA is in a synchronous replication, which warranties the 2 continuous identical clones (disk signatures included). I will show it in your example:
1. you will install the CA on the 6000 as a source DR vdisk member. It will automaticaly creates the destination replicated vdisks on the EVA 8100. When the copy is fully finished, EVA 6000 is still the primary mirror with vdisks with readwrite access and the EVA 8100 is still the secondary mirror with vdisks with readonly access. At that time you should zone (on the SAN level) and then create the 4 node cluster host group on the EVA 8100 and present the new readonly vdisks which will not be visible.
Then you will go down with the cluster (as you have written) and then you will do the failover, which will only swaps the roles of the primary (6000) and secondary (8100) and after the failover the eva 8100 will become the primary storage (RW vdisks) and the EVA 6000 will become the secondary storage (RO vdisks) and thats it. You only need to power on the cluster and it will access the new disks without any problems
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-10-2008 02:57 AM
07-10-2008 02:57 AM
Re: EVA 6000 to 8100 migration and Windows Cluster
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-05-2008 11:18 PM
08-05-2008 11:18 PM
Re: EVA 6000 to 8100 migration and Windows Cluster
Just some feedback - thanks your suggestions were spot on. The process was really straighforward - take everything offline, power down the 4 servers in the cluster, unpresent old disks, present new disks, power back up. Two physical disk resources failed, but then promptly new hardware was found, and I could bring them online again. There were no issues with disk signatures - so there was no need to run the Cluster Recovery Tool etc.
thanks
Ray