- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- "Enhanced" Asynchronous Replication between EVA's
Operating System - OpenVMS
1748219
Members
4619
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
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
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
09-05-2007 02:06 AM
09-05-2007 02:06 AM
"Enhanced" Asynchronous Replication between EVA's
Hi Guys,
This is really a storage/SAN/DR question, however I am sneaking it in here based on the fact that I am replicating OpenVMS Data.
Basically, does anyone out there have any familiarity with this topic. We are researching the idea of using this product to replicate data asynchronously between the East Coast, and Reno Nevada. We are concerned about what happens when (or if) the inter-site link fails.
The general understanding is that at this point, the product starts logging (read 'caching') the IO (in a file) until the link is restored, at which time the software goes into a "fast-copy" (done in Synchronous Mode,) until the data is synched up again, and then reverts back to asynchronous replication again.
The problem is "What happens if the Log File is full, and the link is still down??"
Clearly, if your replicated data is for backup/Disaster Recovery, then you would want the software to abandon the attempts to replicate in favour of keeping your production systems running without degradation. And here is the crux of our problem, The product documentation hints or implies that the product will be well behaved, without actually, explicitly confirming the sequence of events.
Previous experiences (albeit with older VCS code) showed that when the link was lost, and the log filled, then local host IO to the local storage sub-system locked up.
Clearly this can be avoided if the log file is made sufficiently large (in the extreme case = the size of the DR group). Our question is simply - Is this the case??
We are not necessarily going to make our decision based on the answer, we are just trying to be aware of all of the implications before we configure and impliment this solution.
We would love to hear from anyone who has implemented "Enhanced Asynchronous Replication" and has any experiences with either testing its performance during simulated link outages, or real outages. Also anyone who is utilizing this with large log files (approaching DR set size)
thanks
Dave
This is really a storage/SAN/DR question, however I am sneaking it in here based on the fact that I am replicating OpenVMS Data.
Basically, does anyone out there have any familiarity with this topic. We are researching the idea of using this product to replicate data asynchronously between the East Coast, and Reno Nevada. We are concerned about what happens when (or if) the inter-site link fails.
The general understanding is that at this point, the product starts logging (read 'caching') the IO (in a file) until the link is restored, at which time the software goes into a "fast-copy" (done in Synchronous Mode,) until the data is synched up again, and then reverts back to asynchronous replication again.
The problem is "What happens if the Log File is full, and the link is still down??"
Clearly, if your replicated data is for backup/Disaster Recovery, then you would want the software to abandon the attempts to replicate in favour of keeping your production systems running without degradation. And here is the crux of our problem, The product documentation hints or implies that the product will be well behaved, without actually, explicitly confirming the sequence of events.
Previous experiences (albeit with older VCS code) showed that when the link was lost, and the log filled, then local host IO to the local storage sub-system locked up.
Clearly this can be avoided if the log file is made sufficiently large (in the extreme case = the size of the DR group). Our question is simply - Is this the case??
We are not necessarily going to make our decision based on the answer, we are just trying to be aware of all of the implications before we configure and impliment this solution.
We would love to hear from anyone who has implemented "Enhanced Asynchronous Replication" and has any experiences with either testing its performance during simulated link outages, or real outages. Also anyone who is utilizing this with large log files (approaching DR set size)
thanks
Dave
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