- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE 3PAR StoreServ Storage
- >
- Remote copy slower from secondary to Primary
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
тАО03-11-2016 06:23 AM
тАО03-11-2016 06:23 AM
We had to failover to our DR site because of a power issue at the primary.
We have found that synchronisation is much slower in the reverse direction.
Any ideas what could be causing this?
Jeremy
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-12-2016 03:31 PM
тАО03-12-2016 03:31 PM
Re: Remote copy slower from secondary to Primary
Are the two StoreServs the same model and OS version?
Is one more heavily loaded than the other?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-14-2016 05:11 AM
тАО03-14-2016 05:11 AM
Re: Remote copy slower from secondary to Primary
Same model and OS.
Normally the target of the remote copy is doing nothing else while the source is our production system.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-14-2016 10:45 AM
тАО03-14-2016 10:45 AM
Re: Remote copy slower from secondary to Primary
>Normally the target of the remote copy is doing nothing else while the source is our production system.
That may explain why it is slower, too busy to write the data?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-16-2016 04:56 AM
тАО03-16-2016 04:56 AM
Re: Remote copy slower from secondary to Primary
Found the problem. It turns out that the default gateway wass missing from one of the replication ports. Must have gone missing when we had a power outage.
It's looking much better now.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-21-2016 07:27 AM
тАО03-21-2016 07:27 AM
Re: Remote copy slower from secondary to Primary
The relief was only temporary, it's back to being slow again.
The remote copy we have going from primary to secondary are working fine.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-16-2016 09:57 AM
тАО06-16-2016 09:57 AM
SolutionIt looks like we've finally fixed it though we still don't know why it was a problem in one direction and not the other.
The problem is that when heartbeats are missed the 3PAR resets the connections. The key was to stop the heartbeats from going missing.
We used setcopytarget tput to limit the bandwith to 40% of the link and setrcopytarget tunelinks to the same value with an appropriate latency. In our case 60. We tried 40 at first and it was a big improvement but we still had dropped heartbeats overnight.