Just wondering if there are some tweaks to get our replication speeds up. We have three Quest Rapid Recovery servers doing our backups. One main backup, one offsite replicated backup, and the last one we unplug to use as an offline replication backup which we plug back in once a week to update then unplug it when it is finished. I want to speed up the replication of our offline backup. It seems we have a major disk queue issue on our main core backup server and it spikes to well over 100 while performing replications. CPU is struggling as well. Network link is full 10Gb but never goes above 1.5Gb/sec.
Main Core:
Target replication core:(no bottlenecks it seems)
Is our new server seriously not fast enough to just transfer data? I know quest uses a database but really why is it so demanding? Main Core server was setup initially as RAID6, but I read since I am using insanely large 12TB disks that RAID6 is not recommended anymore and changed to RAID10. We have more than enough space so the penalty for raid 10 was not a problem. I do remember this issue was still there with RAID6 but I did not take benchmarks to see which one was better.
Anyhow, just curious if there is anything I can do to help or do I just have to roll with it as is (cannot buy more upgrades, server was already $20k).
Thanks!
-Tim
Check these out, looks like your Disk Cache Policy maybe part of the issue
support.quest.com/.../high-paged-pool-ram-utilization-on-systems-running-appassure-or-rapid-recovery
support.quest.com/.../dell-perc-controller-cache-settings-for-improved-disk-performance
Disabled disk cache policy on Main Core. Target core was already disabled. Disk queue still insanely high. CPU unchanged. This is for writes anyways isn't it? The main core should be doing mostly reads when it is transferring to the target.
As for paged pool, I don't think that is an issue. Main server is at 1.4GB paged pool usage. Total server memory is 74/128. Mainly due to increased deduplication recommended settings.
It was just a shot in the dark as you mentioned
Disck Cache Policy Enabled
And I saw PERC Controller
If you get anything else from Quest, I would be interested. Trying to troubleshoot performance issues with RR is a nightmare since they don't really log anything and support simply tells you to use other tools to troubleshoot their application.
The only message I have ever seen that shows you are having disk IO issues but not what to do, looks like
performance: on volume 1, during the last 600s, 3 IO operations exceeded 30000ms threshold, their total duration is 361s, the longest operation took 138s.
No worries. I appreciate any suggestions. Maybe a representative will chime in. I have never seen anything use the disk like this.