Oliver Freyd writes:
Last week I have changed the configuration to schedule my backups
from cron. As stated in some mails here on this list, I set
$Conf{FullPeriod} = -1;
so BackupPC does no backups on its own.
My crontab has these entries:
13 23 * * 5 backuppc /usr/local/BackupPC/bin/BackupPC_serverMesg \
backup all
# better would be something like "backup all incr"
13 23 * * 1-4 backuppc /usr/local/BackupPC/bin/BackupPC_serverMesg \
backup www www root 0
# more entries for each host to back up
well, the second entry really works, the incr backups get started.
Only the "backup all" does nothing.
I also tried it manually, same result.
I added logging output, the "BackupPC" script goes into QueueAllPCs(),
gets a list of my hosts correctly and puts them into the BgQueue,
but then nothing happens. And in the CGI user interface the queues are
all empty.
Sending the command "backup all" does exactly what a regular wakeup
does: queue all the PCs. Since $Conf{FullPeriod} = -1, no backups
will be done, since these are considered regularly scheduled backups.
I've seen in the code that the other backup command (with host parameter
etc.) uses the UserQueue, might that be the difference?
Yes. The second command will explicitly do an incremental backup
on host www. This will succeed, even with $Conf{FullPeriod} = -1.
I guess I should have been clearer about this: if you disable backups
using $Conf{FullPeriod} = -1 then you have to explicitly schedule
each host backup via cron.
Craig
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
