Backup question: Uncompressed incremental vs compressed

[Bravo]

I have a server (dual xeon 2.4 with 1GB RAM) with 450 accounts. The customer accounts use close to 50GB and tarring and gziping all this data for backup takes forever and also increases server load.

Would it be better to do an incremental backup with no compression instead? Disk space on the b/u drive is not an issue.

 

[OCX]

you must have the same size backup drive to even do this uncompressed method

if you have 450clients an used 50gigs..better have 80gigs or more.because backup also backs up cpanel as well..


hope that made since..its still earily..lol

OCX

 

[Bravo]

Both drives, main and backup, are 200GB each, so space should not be a problem,.

 

[OCX]

then use what ever method of back up you like

 

[Jeff-C]

For the last few months I've been using the compressed tar backup method on a 2.8 Ghz server with two 80 GB drives. However, today I finally had to switch to the incremental method because doing the compressed backup simply created too high of a load during backup. Total data being backed up was around 10 GB, and doing this with the standard backup brought loads from 0.20 (15-minute) to over 40 which brought mysql to a virtual hault and made browsing sites on the server noticably too slow for the ~30 minutes that backup takes. Hopefully changing to incremental will provide a more graceful way to backup large accounts.

 

[OCX]

For the last few months I've been using the compressed tar backup method on a 2.8 Ghz server with two 80 GB drives. However, today I finally had to switch to the incremental method because doing the compressed backup simply created too high of a load during backup. Total data being backed up was around 10 GB, and doing this with the standard backup brought loads from 0.20 (15-minute) to over 40 which brought mysql to a virtual hault and made browsing sites on the server noticably too slow for the ~30 minutes that backup takes. Hopefully changing to incremental will provide a more graceful way to backup large accounts.

there is an option to stop backup process if server load is high

if you are only doing a weekly backup or a monthly backup would be good to
select a day that is normaly slow thus keepiing your server up to par any other time

i do monthly and weeklybackups..i leave the daily backups up to the customer

and i ask clients if they want me to backup there account or they can OPT not to have it backed up..which saves you some space..and resources during backup time.


just my 2cents

 

[Jeff-C]

there is an option to stop backup process if server load is high

1.) Is there a way to specify one load at which to stop log processing and another at which to stop backup? Currently I can only find one place to specify and it's for both. If I set it as low as I would like to for backup, I find that stats are sometimes not processed for the larger two accounts.
2.) How does the stop actually work? If the backup is copying files for a larger account to backup, can it stop copying if the load goes too high? Or if it's tarring, is there a way for it to stop or slowdown the gzip/tarring process if the load gets too high? Or does it only react after the current copy or tar/gzip operation is finished?

 

[OCX]

1.) Is there a way to specify one load at which to stop log processing and another at which to stop backup? Currently I can only find one place to specify and it's for both. If I set it as low as I would like to for backup, I find that stats are sometimes not processed for the larger two accounts.
2.) How does the stop actually work? If the backup is copying files for a larger account to backup, can it stop copying if the load goes too high? Or if it's tarring, is there a way for it to stop or slowdown the gzip/tarring process if the load gets too high? Or does it only react after the current copy or tar/gzip operation is finished?

from what i can tell it stops after it finishes the last then carrys on when server load is ok for it to continue

as for ther other question.im not sure..you prolly can check the scripting files for the backup processes then edit where necessary