many hosts not being backed up
On Tue, Mar 02, 2004 at 11:09:50PM -0800, Craig Barratt wrote:
"Christian G. Warden" writes:
I have BackupPC 2.0.2 configured with 26 hosts. All of them are always
online (no laptops). The first half, as listed in the hosts file, get
backed up regularly, while the second half do not. My WakeupSchedule is
[22,23,1,2,3,4], and the log shows that no backups start until 05:05
even though there are a number of hosts whose last backup is older than
IncrPeriod (0.97) as of 22:00. These hosts never get backed up on
BlackoutWeekDays, presumably because by the time the hosts before them
are finished, it is already past BlackoutHourBegin.
In summary, it appears that there is a bug in which hosts with backups
older than IncrPeriod do not get backed up during a Wakeup if there are
hosts before them whose last backup is newer than IncrPeriod.
Look at the main log file. Every night BackupPC_nightly runs. It
cleans the pool, and no backups are run while BackupPC_nightly is
running. So when it is queued (at 1am in your case), BackupPC waits
for all the in-progress backups to finish, then BackupPC_nightly is
started (it jumps ahead of any other queued backups). After it
finishes (perhaps at 5:05), others queued backups start. A litte
later BlackoutHourBegin causes the remaining backups to be skipped.
Thanks for the info, Craig. Looking at the log, BackupPC_nightly runs at
22:00 and doesn't finish until after 05:00. So, it seems that
BackupPC_nightly runs at the first hour in WakeupSchedule (22) rather than
the first hour of the day (1). I will try changing WakeupSchedule to
[8,22,23,1,2,3,4].
Unfortunately BackupPC doesn't prioritize hosts based on how old
the last backup was. So the pattern repeats each night.
Here are some suggestions:
- Increase $Conf{MaxBackups} so that more simulataneous backups
can run. This will only help if you are not cpu/disk limited
on the BackupPC server.
We currently have this set to 6. What are other people using?
- Improve the server cpu/disk speed. Some users have reported
significant improvements replacing ext3 with reiserfs.
BackupPC_nightly shouldn't take more than 15-30 minutes
to run (but it depends upon how big your pool is).
We seem to have a problem since BackupPC_nightly is taking more
than 7 hours. We've got a dual Xeon 2.66 and an ext3 filesystem on a
SATA RAID 10 array. Our cpool is about 330GB.
I'll look into moving to reiserfs when we add more disk space.
Thanks,
Christian
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
