Torsdag 8. mars 2012 14:13:38 skrev Petter Reinholdtsen : > [Klaus Ade Johnstad] > > > Having slbackup in cron.daily will cause the backup to start at > > about 06:25 in the morning, which, on a busy fileserver, will > > probably not be finished in time for when then the masses of users > > starts logging in at around 07:30, causing the fileserver to crawl, > > isn't that correct? > > Could be. I have not seen that problem on any server yet, so I do > not know how likely it is to happen in real life. Did you see it? > How much data was being backed up in that case? > > > Didn't slbackup use to run from /etc/cron.d/slbackup at 01:00? > > No idea. > -- > Happy hacking > Petter Reinholdtsen This is from a reallife skolelinux fileserver, a few thousand users, but still not that uncommon, it takes most days more than 1 hour to complete the backup, which is why I have it started at 22:00. mars 03 22:02:03 - Starting backup of client localhost mars 03 22:02:03 - Trying to remove backups older than 365 days: mars 03 22:02:03 - No increments older than Fri Mar 4 22:02:03 2011 found, exiting. mars 03 22:02:03 - Removing backups older than 365 days succeeded! mars 03 23:24:30 - --------------[ Session statistics ]-------------- StartTime 1330808523.00 (Sat Mar 3 22:02:03 2012) EndTime 1330813469.52 (Sat Mar 3 23:24:29 2012) ElapsedTime 4946.52 (1 hour 22 minutes 26.52 seconds) SourceFiles 6069773 SourceFileSize 186835321588 (174 GB) MirrorFiles 6069775 MirrorFileSize 186835258947 (174 GB) NewFiles 2 NewFileSize 8304 (8.11 KB) DeletedFiles 4 DeletedFileSize 16608 (16.2 KB) ChangedFiles 121 ChangedSourceSize 13728246 (13.1 MB) ChangedMirrorSize 13657301 (13.0 MB) IncrementFiles 139 IncrementFileSize 663591 (648 KB) TotalDestinationSizeChange 726232 (709 KB) Errors 0 -------------------------------------------------- mars 03 23:24:30 - Successfully finished backing up client localhost -- Klaus Ade 67E61D18B2C44F8A3DA35C6D849F9F5F 26FA477D
Attachment:
signature.asc
Description: This is a digitally signed message part.