This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Virtual Standby to ESXI are slow

Appliance: DL4300

Software Version: RapidRecovery 6.1.2.115

ESXI Version: 6.0

ESXI Server Spec: Dell R730x, 24 15k SAS Drives in RAID 6 - Adaptive Read Ahead - Write Back, 64GB RAM, Dual Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHz

Problem: Exports from RR to ESXI run below 10MB/s on a 10Gb/s network. Many of our standby's are in the TB per day range, meaning most take approx 20-30 hours to complete. During this time backups of that agent do not take place, leaving the server vulnerable.

 

Troubleshooting taken with Support:

 - All software and hardware updates completed

 - Direct 10Gb/s fibre between Core and ESXI

 - Pausing all other tasks on the Core and restarting the server

 - Change RAID policy to Adaptive Read Ahead and Write Back

 

Performing an export of an agentless backup last night seemed to run in the 100MB/s+ range, however after checking the logs this morning it dropped back down to 18MB/s after an hour.

 

Any help is appreciated, and even a comment to say you are experiencing the same and info about your setup will assist.

 

James

Parents
  • i'd dream of speeds like 3-8 MB/s since the upgrade. I currently have a 3.6GB incremental update (yes 3.6 Gigabytes) that has been running for 5h13 minutes and estimates another 18 hours to complete.

    EDIT:

    I am however wondering if i'm also impacted by https://support.quest.com/appassure/kb/119686 since all my free memory has been consumed and allocated to standby.

    Am waiting for these exports to finish and some other jobs before I stop the core and change the registry entry, just takes a while to get to that situation.

Reply
  • i'd dream of speeds like 3-8 MB/s since the upgrade. I currently have a 3.6GB incremental update (yes 3.6 Gigabytes) that has been running for 5h13 minutes and estimates another 18 hours to complete.

    EDIT:

    I am however wondering if i'm also impacted by https://support.quest.com/appassure/kb/119686 since all my free memory has been consumed and allocated to standby.

    Am waiting for these exports to finish and some other jobs before I stop the core and change the registry entry, just takes a while to get to that situation.

Children
No Data