Backup Performance Issue (gzipping on a NFS partition)
Hello everybody,
i'm experimenting a performance issue on my Backup Server due to the way cpanel makes backup.
THE LANDSCAPE:
WHAT CPANEL DO DURING A BACKUP:
This affect the performance on the internal network smoothly in case of 1 server, but with 20 server you are gonna to kill the performance of every NFS mounts by filling up all the bandwith connections.
THE AWKARD TEMPORARY SOLUTION:
The awkard solution is to make the local backup on a different dir "/backup_tmp" and place the NFS backup dir on the alternate destination settings. Which means that i cannot use the new restore system AT ALL.
I think cPanel should make the whole "backup process" in a local tmp dirs and after move to the default local backup directory (which is the one used for restoring backup).
In order to fix there are two possibilities:
- use a tmp directory to backup till the gzip compression (avoid compression on a NFS network)
- or give the possibility to add local restore directory in order to see the backup on alternative destination
Thanks,
Massimiliano Cuttini
Hello everybody,
i'm experimenting a performance issue on my Backup Server due to the way cpanel makes backup.
THE LANDSCAPE:
- On my network I have a local backup server which I use to store backups of all my cpanel server (about 20).
- The speed of the internal Network is 1Gb LAN ethernet on a dedicated netcard.
- Every cPanel Server have a NFS mount on "/backup" which is a dir created on the backup server
WHAT CPANEL DO DURING A BACKUP:
- Start making a copy of the account within "/backup/day/username/" which mean:
-> SEND DATA TO THE BACKUP SERVER - gZip/pigZip the whole content of the directory created "/backup/day/username" which mean:
<- READ IN STREAMING SINGLE FILE FROM THE BACKUP SERVER
<-> PERFORM THE COMPRESSION DURING THE STREAMING
-> WRITE THE FINAL GZIP FILE TO THE BACKUP SERVER
This affect the performance on the internal network smoothly in case of 1 server, but with 20 server you are gonna to kill the performance of every NFS mounts by filling up all the bandwith connections.
THE AWKARD TEMPORARY SOLUTION:
The awkard solution is to make the local backup on a different dir "/backup_tmp" and place the NFS backup dir on the alternate destination settings. Which means that i cannot use the new restore system AT ALL.
I think cPanel should make the whole "backup process" in a local tmp dirs and after move to the default local backup directory (which is the one used for restoring backup).
In order to fix there are two possibilities:
- use a tmp directory to backup till the gzip compression (avoid compression on a NFS network)
- or give the possibility to add local restore directory in order to see the backup on alternative destination
Thanks,
Massimiliano Cuttini
Last edited: