HPE GreenLake Administration
- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Re: RSM - Automated failover
HPE EVA Storage
1833300
Members
3062
Online
110051
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
Forums
Discussions
Discussions
Discussions
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
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
05-28-2007 02:30 AM
05-28-2007 02:30 AM
RSM - Automated failover
Hi,
Can somebody help to configure Replication Solution Manager. So that if the source fails automatically the clients should attach to DR.
Currently we are doing this manually. We have one eva at source and one at DR. the server connected to source and destination have the same application. each client is having two shortcut icon of the application one pointing to source and another to dr. once the source fail, users will use the second shortcut to use their application. Can we automate this using RSM, like which can be done through Storage mirroring.
Can somebody help to configure Replication Solution Manager. So that if the source fails automatically the clients should attach to DR.
Currently we are doing this manually. We have one eva at source and one at DR. the server connected to source and destination have the same application. each client is having two shortcut icon of the application one pointing to source and another to dr. once the source fail, users will use the second shortcut to use their application. Can we automate this using RSM, like which can be done through Storage mirroring.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2007 02:40 AM
05-28-2007 02:40 AM
Re: RSM - Automated failover
I think that you need "HP StorageWorks Cluster Extension EVA" http://h18006.www1.hp.com/products/storage/software/ceeva/index.html
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2007 02:49 AM
05-28-2007 02:49 AM
Re: RSM - Automated failover
Hi,
Thanks for the reply. The one you have suggested is for having a Cluster kind of solution. Can we achieve this without cluster using RSM.
Thanks for the reply. The one you have suggested is for having a Cluster kind of solution. Can we achieve this without cluster using RSM.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-29-2007 02:38 AM
05-29-2007 02:38 AM
Re: RSM - Automated failover
While I'm guessing it is possible using the command line interface, the key here is being able to determine if the triggering event actually happened or not.
I believe you would need (to develop) some sort of out-of-band mechanism to accurately determine why the dr site no longer hears the source site: Looking just from within the network, there is no difference at the dr site between "The source site was hit by a tornado (initiate failover)" and "Someone kicked the router power cable (wait a little for it to come back)".
Both are communications failures. Both result in transmission timeouts. How does a program at the dr site tell them apart?
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
I believe you would need (to develop) some sort of out-of-band mechanism to accurately determine why the dr site no longer hears the source site: Looking just from within the network, there is no difference at the dr site between "The source site was hit by a tornado (initiate failover)" and "Someone kicked the router power cable (wait a little for it to come back)".
Both are communications failures. Both result in transmission timeouts. How does a program at the dr site tell them apart?
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
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP