• State Not Answered
  • Locked Locked
  • Replies 15 replies
  • Subscribers 29 subscribers
  • Views 15278 views
  • Users 0 members are here
Options
Related
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

network.systex
over 6 years ago

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
  • 0 over 6 years ago
    I believe we are in the same boat. Quest state that the known issue related to exports being slow on a fragmented repository has been fixed in version 6.1.2. If it has I'm glad I never tried earlier versions. This is in fact in the known issues of the release notes of 6.1.2, apparently it should be in the fixed issues list.

    What I do know is when we were on 5.4.3 we were able to export/update 50 machines by 6AM every day and now we generally update about 10 over the entire 24 hours and are just getting further and further behind.

    Like you, likely we will be going elsewhere as we can't survive like this for long.
Reply
  • 0 over 6 years ago
    I believe we are in the same boat. Quest state that the known issue related to exports being slow on a fragmented repository has been fixed in version 6.1.2. If it has I'm glad I never tried earlier versions. This is in fact in the known issues of the release notes of 6.1.2, apparently it should be in the fixed issues list.

    What I do know is when we were on 5.4.3 we were able to export/update 50 machines by 6AM every day and now we generally update about 10 over the entire 24 hours and are just getting further and further behind.

    Like you, likely we will be going elsewhere as we can't survive like this for long.
Children
No Data