• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

High load every night/day during fullbackup

MislavO

Regular Pleskian
Hello.

On one of the servers there is like 1.8-2TB used in /var/ partion and I have problem during the backup. Backup usually takes 12-14 hours to complete and during that time load doesn't go below 8-10 (or even 15-20).

Server spec:
Intel® Core™ i7-2600 Quadcore (Hyper-Threading Technology)
RAM 32 GB DDR3 RAM
Hard disks 2 x 3 TB SATA 6 Gb/s HDD (7200 rpm (Software-RAID 1)

using plesk 11.0.9 on Debian 6.0.7

In plesk Backup manager under the tools & settings, backup is scheduled as "Server configuration and content -> all configuration and content" (there is more then 500 domains together with the subdomains).

After backup is over, load goes down to 2-3 and it's like that whole day.

Did anyone had problem like this? How did you "fix" it? Is there a way to reduce server load during the load? Is "nice" included in plesk daily scheduled backup?
 
Hm, I didn't found this one, I only found your post where you replied with "noatime" suggestion and http://kb.parallels.com/en/115056 (although this one is not for dedicated).

How is this script really working? I didn't found answers in KB or in that topic you've linked.

1) Backup is being archived to /var/lib/psa/dumps as I can see. Is this backup directory excluded(ignored) from script backup or as said on #42, I still have to delete everything before running the script?
2)
Not only server level backup can be exported, but also client or domain level as:
./fullbackup.php -e /var/lib/psa/dumps/clients/<client>/domains/<domain>/domain_backup_info.xml <output_file>

What is ment by "server level backup", httpdocs and configuration files or? Does this backup script only backup content under /var/www/vhosts/*/httpdocs or also /var/www/vhosts/*/ - before httpdocs you can put subdomains and other domains as well (basically the whole subscription). Script is calling plesk current file for backup/restore in bin folder, so I guess whole subscriptions are covered completely?

Can I still use parameter -b -o <output_dir> together with this -e /var/lib/psa/dumps/clients/<client>/etc./etc. ?
3) I guess with parameter mentioned on 2) -e, complete structure with clients/domain is almost the same as now is? Everything is sorted out in folders/clients/resellers + database from the same are also there?
4) How does this really improve backup? Is this one running with command "nice" priority or I have to set that?

I will have to test this out this evening.
 
Back
Top