Backup disk space

[jpwdesigns]

I'm having trouble with 9.3 backups filling up my free diskspace.

When backing up it backs up each domain inside /var/lib/psa/dumps/clients/here... and then duplicates it in a tgz file here /var/lib/psa/dumps/here...

I have about 55% free of my had drive but because it stores the files twice the server disk space gets full 100% before the backup can finish. This obviously makes it impossible to backup using psabackup.

Why does it behave this way? Is there a way to initiate a server wide backup and not have my more than have free disk space used up?

Any suggestions are appreciated.

 

[IgorG]

By default, pleskbackup stores backups in Plesk backup repository located on the Plesk server (/var/lib/psa/dumps/ folder in Plesk for Linux/Unix and %plesk_dir%\Backup\ in Plesk for Windows).
Plesk is capable of exporting the created backup as a single file (.tar on Unix and .zip on Windows) in one of the following ways:

* to stdout
* to local file system
* to FTP server

For export backup as a single file you should use the --output-file option. After a backup is exported, pleskbackup removes it from the Plesk backup repository.
Path to Plesk backup repository can be changed here:

# cat /etc/psa/psa.conf | grep dumps
DUMP_D /var/lib/psa/dumps

Or use this workaround.

 

[jpwdesigns]

I cant see how that answer is a solution. It still will create at some point 2 copys of the domains. I already explained that above. Whether it creates the second copy as a single file or not doesn't seem to mater because it copies first everything in individual folders then will put it in one archive file for stdout. Am I missing something here?

J

 

[TobiI]

Same problem here. Furthermore, no way to exclude subdomains from backup

I have the same problem as explained by jpwdesigns. The filesystem of my virtual server is 30 GB large and is about 60% full using 2 subdomains. As soon as a backup is created, the filesystem fills up and the system chokes on large temporary files under /var/lib/psa/dumps/clients/<client>/domains/<domain>/phosting/subdomains/<subdomain>.

This is a real nuisance, seemingly I am not able to exclude subdomains from the scheduled backups.

 

[PeerR]

Same problem here.

I have a 120GB domain; only 40GB left space on the hard disk leaving be unable to back it up using Plesk Backup. Very frustrating.

Plesk need to create a solution whereby you can specify a segment size for the backup; e.g. 20GB.
So 20GB of your domain is first packed into an archive; then sent to the external FTP server; then deleted; and then the next 20GB is tarred up and so on.