• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Issue Backup causes websites unreachable

arjanvr

New Pleskian
Hello,

Whenever i run my daily backup for a single site, its a decent large wordpress site so the backup with mail is 30GB, it takes down the website while it is making the backup for server hours making the site unavailable.

I tried running the backup with low intensity at the lowest possible settings, i tried running the backup uncompressed so it would not have to tar it. Also no improvment.

The server is a 4 core vps with 8GB of ram.
When the server is running without backup it runs perfectly fine.

top - 19:02:05 up 2 days, 10:17, 1 user, load average: 0,42, 0,76, 0,72
Tasks: 73 total, 1 running, 72 sleeping, 0 stopped, 0 zombie
%Cpu(s): 0,1 us, 0,2 sy, 0,0 ni, 99,7 id, 0,0 wa, 0,0 hi, 0,0 si, 0,0 st
MiB Mem : 8192,0 total, 5073,4 free, 2397,3 used, 721,2 buff/cache
MiB Swap: 0,0 total, 0,0 free, 0,0 used. 5657,5 avail Mem

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
710 apache 20 0 2508632 17392 6628 S 0,3 0,2 2:12.77 httpd
1 root 20 0 242548 8388 5736 S 0,0 0,1 1:44.11 systemd
119 root 20 0 390656 218620 192888 S 0,0 2,6 7:49.57 systemd+
125 root 20 0 97280 4084 2944 S 0,0 0,0 0:00.70 systemd+
137 dbus 20 0 54248 2156 1376 S 0,0 0,0 0:55.01 dbus-da+
141 root 20 0 86144 4604 3488 S 0,0 0,1 0:25.93 systemd+
142 root 20 0 497736 18304 5608 S 0,0 0,2 0:03.31 firewal+
145 root 20 0 58292 600 0 S 0,0 0,0 0:00.00 saslaut+
146 root 20 0 58292 624 0 S 0,0 0,0 0:00.00 saslaut+
152 psaadm 20 0 1462592 7344 0 S 0,0 0,1 0:24.17 plesk-t+
529 root 20 0 522968 30796 23732 S 0,0 0,4 17:21.90 php-fpm
530 root 20 0 268644 5660 3256 S 0,0 0,1 0:39.43 httpd
534 root 20 0 413656 23140 17912 S 0,0 0,3 0:24.77 sw-engi+
537 amavis 20 0 1288148 705260 1376 S 0,0 8,4 0:37.40 clamd
538 root 20 0 76508 4864 3948 S 0,0 0,1 0:01.62 sshd
541 root 20 0 48856 2272 1700 S 0,0 0,0 0:21.63 xinetd
543 postfix 20 0 461160 6196 3992 S 0,0 0,1 1:44.72 psa-pc-+

When i run the backup the load averages spike up to around 7.00 to 14.00.
I would assume a 4 core 8GB vps (at strato) would be sufficient to make a backup in plesk.
Am i overlooking something that can fix this issue as several hours of downtime to make a daily backup is just too much.
 
Just a quick question: Did you disable the option "Suspend domains until backup task is completed" from the Scheduled Backup Settings?

As described here:
 
Back
Top