- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Re: Link Speed for CA Replication With EVA 4400 An...
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
тАО01-17-2010 11:55 PM
тАО01-17-2010 11:55 PM
Link Speed for CA Replication With EVA 4400 And Question
thnx in ADV.
o.odeh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-18-2010 01:33 AM
тАО01-18-2010 01:33 AM
Re: Link Speed for CA Replication With EVA 4400 And Question
In a CA sync replication the source EVA waits for the acknowledge of the target EVA before continuing which leads to performance degradation of the production.
In an asynch replication you need to size a WriteHistoryLog which is a buffer for unsend IO's. You can size this up to 2TB but this data is unprotected when the EVA fails.
Also, when the WriteHistoryLog is completely full CA switches from Async to Sync replication to push all the data in the WriteHistoryLog over the link...
And that my friend is not a situation where you want to be in.
You can however set the WriteHistoryLog to a certainsize ex. 1GB and gradually extend this when needed. But, be aware that you can't decrease the size.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-18-2010 02:41 AM
тАО01-18-2010 02:41 AM
Re: Link Speed for CA Replication With EVA 4400 And Question
Watch out, as this is an internal virtual disk in VRAID-1, so it will take 4 TeraBytes...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-18-2010 02:10 PM
тАО01-18-2010 02:10 PM
Re: Link Speed for CA Replication With EVA 4400 And Question
we found the following message many time in event log:
"Excessive PING response time on the inter site link is preventing acceptable replication throughput: Reducing data exchange resources"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2010 02:39 AM
тАО01-19-2010 02:39 AM
Re: Link Speed for CA Replication With EVA 4400 And Question
If you are using MPX,depends on the firmware on the MPX,no of PING supported by the mpx were increased in the most recent firmware update.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2010 06:24 AM
тАО01-19-2010 06:24 AM
Re: Link Speed for CA Replication With EVA 4400 And Question
if we have low bandwidth between two site for ca replication also with Asynch
how this will be affected the source EVA 4400 and LUNs pathsc losted due to this performance issue.