Facebook
Twitter
S
swhelp
Guest
Plesk 8.2, Fedora 7.
When initiating a backup the CPUs in the server are pegged. The gzip process runs @ 99% and this continues thru the backup. The site backup footprint is nearly 3GB and grows everyday.
Is there a way to nice the backup? Can I just tar & gz the site contents and not rely on Plesk backup? I cannot afford to lose the horsepower, even @ 4:00am.
Any thoughts?
Also, on one scheduled backup did not complete and Plesk was caught in a loop, it's only to retain 2 backups but made 14 of them in attempts to complete. This eventually brought the server down and 100% outage.
When initiating a backup the CPUs in the server are pegged. The gzip process runs @ 99% and this continues thru the backup. The site backup footprint is nearly 3GB and grows everyday.
Is there a way to nice the backup? Can I just tar & gz the site contents and not rely on Plesk backup? I cannot afford to lose the horsepower, even @ 4:00am.
Any thoughts?
Also, on one scheduled backup did not complete and Plesk was caught in a loop, it's only to retain 2 backups but made 14 of them in attempts to complete. This eventually brought the server down and 100% outage.
