- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Re: Replication performance EVA 8000
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-12-2009 08:01 AM
тАО01-12-2009 08:01 AM
Replication performance EVA 8000
After it started I received 1 "Excessive Vdisk response time at the DR Destination has been detected". I also received some "Copy resources on the inter site link have been reduced" errors and a couple of messages about alarm level reached on the disk group. Apart from this things seemed to progress OK if slowly.
A couple of hours later severe reduction in performance was reported on at least one system using the destination EVA as its primary disk. This was using another disk group on this EVA.
As soon as I removed this member from the replication disk group (leaving the destination vdisk in place) the issues disappeared.
Is this likely to be caused by
1) The disk group on the destination EVA was too full
2) The writes to this disk group were overwhelming the controller
3) something else
Any help appreciated
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-12-2009 08:51 AM
тАО01-12-2009 08:51 AM
Re: Replication performance EVA 8000
2) If the replication is synchronous, slowness on the target EVA can affect the source EVA too
3) Could be that after trying to replicate a the changes to a 1 TB vdisk you're over the capacity of the link
4) This can be analyzed if you capture some performance data with EVAperf
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-12-2009 09:21 AM
тАО01-12-2009 09:21 AM
Re: Replication performance EVA 8000
It was synchronous replication, but the target EVA showed all the performace hit. Is this possibly as it was writing when the other EVA was just reading? It was just doing the initial copy at this stage, it only got to about 35% of the initial copy.
The link was probably using a lot of bandwidth but the performance problems on our systems were unrelated to that. They were definitely disk related
I might try and recreate and run evaperf.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-12-2009 11:52 AM
тАО01-12-2009 11:52 AM
Re: Replication performance EVA 8000
If you put a virtual disk from FATA into a Data Replication Group (DRG) with FC, you can slow down the FC I/Os, because the write ordering is preserved in the DRG and thus limited by the FATA I/O capability.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-12-2009 12:39 PM
тАО01-12-2009 12:39 PM
Re: Replication performance EVA 8000
Where should I start for a little more reading, the EVA best practices white papers maybe?
Should FC and FATA be always separate in DR. Is it OK to have a FC vdisk replicate to a FATA vdisk, for example in a DR group with no other members.
The DR group I added to in the case above already had a FC vdisk replicating to a FATA vdisk.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-13-2009 10:33 AM
тАО01-13-2009 10:33 AM
Re: Replication performance EVA 8000
I am afraid this is not described in the product documentation.
One of the problem is that people beleive that FATA disks are just 'slower drives with a FC interface' which can be used if a server 'is not deemed that important'. I've been discussing this a few times with customers now.
Quite a number of years ago I've talked to an engineer who did disk drive qualification on the EVA. He told me that the FATA disks (at that time) were quite robust. It appears that the situation has changed.
In the mean time, HP explicitly discourages the use of FATA disks for the CA-EVA Write History Log (WHL) - CV-EVA was recoded. And writes in the EVA specifications:
""FATA drives are designed for lower duty cycle applications such as near on-line data replication for back-up. These drives should not be used as a replacement for EVA high performance, standard duty cycle, Fibre Channel drives. Doing so could shorten the life of the drive.""
> Is it OK to have a FC vdisk replicate to a FATA vdisk
What is the argument to have FATA at the destination? No high I/O requirements? What is supposed to happen if the source goes down and you have to fail over?
> The DR group I added to in the case above already had
> a FC vdisk replicating to a FATA vdisk.
Did you ever check the timing on that configuration? Maybe it was operating just before 'falling over the edge'.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-03-2009 02:56 AM
тАО03-03-2009 02:56 AM
Re: Replication performance EVA 8000
1/ CA FC to FC - very good no degredation of EVA performance
2/ CA FC to FATA - reasonable rates some degredation of performance
2/ CA FATA to FATA - forget it (20MB/s)
I am trying to migrate two disk groups on a 2c12d EVA8100 (FATA) to a single disk group on a 2C18D EVA8000 (FATA) and it manages 1TB in 16 hours. I have 78TB to copy !
I am only using CA to migrate a CDR network data copy from FC to FATA in two stages.
I have some spare 146GB FC disks which I could install in a new extra group for WHL - will this help - should I do it at source or destination or both, how many disks would I need to make it get used (8,16,24...)?
I lost a disk on the destination EVA disk group(88x1TB FATA). I replaced it and levelling is taking 24hrs to do 4% (25 days to complete. I have the latest disk code (HP05) and using XCS6200.
Any help appreciated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-26-2010 03:17 AM
тАО04-26-2010 03:17 AM
Re: Replication performance EVA 8000
I have put this down mainly to not enough spare capacity in disk group.