- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Re: EVA4400 & CA
HPE EVA Storage
1748181
Members
3370
Online
108759
Solutions
Forums
Categories
Company
Local Language
юдл
back
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
юдл
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
тАО04-25-2011 05:25 AM
тАО04-25-2011 05:25 AM
I am looking for clarification on something that recently happened with my EVA that has me really confused. It has to do with CA and Failover. I just upgraded to unlimited CA on my 2 EVA4400's and noticed that I had the source and destination reversed on a replication that I had setup a few weeks ago. I needed to test out my DR plans, so I verified that both the source and destination were presented to the (in this case) windows cluster nodes.
To failover the volume, I followed these steps,
1) Stopped the disk cluster resource and then name resource in Windows Cluster Manager
2) On the destination EVA, I failed-over the volume.
3) I then opened Disk Manager and rescanned the disks, expecting to find a new volume to assign it the same drive letter
The thing is, I didn`t see a new volume. I restarted the disk resource and then the name resource and everything came up fine.
The confusion I have is that I fully expected Windows to see the source volume of the replication pair to be new and unknown, as it comes from a different array. But it didn`t and I would like to know if anyone knows why.
This is an entirely welcome behaviour, albeit unexpected.
I suspect it might be from the MPIO driver, but I`m not sure.
Is this something I can depend upon when developing my DR procedures?
To failover the volume, I followed these steps,
1) Stopped the disk cluster resource and then name resource in Windows Cluster Manager
2) On the destination EVA, I failed-over the volume.
3) I then opened Disk Manager and rescanned the disks, expecting to find a new volume to assign it the same drive letter
The thing is, I didn`t see a new volume. I restarted the disk resource and then the name resource and everything came up fine.
The confusion I have is that I fully expected Windows to see the source volume of the replication pair to be new and unknown, as it comes from a different array. But it didn`t and I would like to know if anyone knows why.
This is an entirely welcome behaviour, albeit unexpected.
I suspect it might be from the MPIO driver, but I`m not sure.
Is this something I can depend upon when developing my DR procedures?
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-25-2011 05:28 PM
тАО04-25-2011 05:28 PM
Solution
It depends on how the Windows cluster was created. If the DR nodes are aware of primary cluster then the disk signatures are verified and will not be treated as new volumes. I have seen some setup where DR cluster is not configured correctly and their DR process has to write new disk signatures at DR clusters before they can use the replica disks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-26-2011 04:53 AM
тАО04-26-2011 04:53 AM
Re: EVA4400 & CA
Actually, your response makes quite a bit of sense. I never considered the disk signature. I'm going to test this on a MSSQL cluster and see if I can replicate the situation.
Thank you for the reply.
Thank you for the reply.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-26-2011 04:55 AM
тАО04-26-2011 04:55 AM
Re: EVA4400 & CA
Answer provided points me in the right direction.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP