When the backup try to dump an account with a mysql of 1.8 giga of data it fails.
It's a problem of RAM (or some other hardware's component), or it's just a very bad idea to dump 1.8 giga of data?
The backup is automatic.... so i cannot select to don't dump the mysql.
When the backup try to dump an account with a mysql of 1.8 giga of data it fails.
It's a problem of RAM (or some other hardware's component), or it's just a very bad idea to dump 1.8 giga of data?
The backup is automatic.... so i cannot select to don't dump the mysql.
Do you have enough room on the HD? You can also increase "The load average above the number of cpus at which logs file processing should be suspended (default 0):" in Tweak Settings.
Do you have enough room on the HD? You can also increase "The load average above the number of cpus at which logs file processing should be suspended (default 0):" in Tweak Settings.
I have FTP backup to another server, and that server have enought space, also the HD on my server is almost empty. It's not a problem of space but of course of cpus / rams.
However i cannot understand the second hint that you give me, how can suspend log file processing can help to do not fail to dump the mysql of the account?
I have FTP backup to another server, and that server have enought space, also the HD on my server is almost empty. It's not a problem of space but of course of cpus / rams.
However i cannot understand the second hint that you give me, how can suspend log file processing can help to do not fail to dump the mysql of the account?