Timothy J. Massey wrote: > Hello! > > I had a series of new hosts that were put in place in the last few days. > All of them had been pinged enough that they were postponed to the > blackout period for the first time today, which is set to the default > (07:00-19:30). I had started the backups manually in the past, which > meant that their last backup was now over 1 day old, but not yet started > because of the blackout period. > > However, I just rebooted the server. All of the computers that were > being held because of the blackout period just started.
Further details: Not all of the hosts that might have started actually started. In fact, only three did start. Two that might have started (their last backup was > 1.0 days) did not start. They also did not start at the next wakeup time, either: they seem to be respecting the blackout period. I don't know if there is a difference between the hosts that caused some to start and others to not, or if there was a 4th job that might have been running and did not show up in the list of active jobs (e.g. some pool maintenance job, etc.) or had exited before I noticed that prevented more hosts from starting because MaxBackups is set to 4. There really is *no* difference between the hosts: in fact, every one of the hosts use virtually the same configuration file. They all use rsyncd with identical user ID and passwords: only the names or numbers of the shares might differ slightly between them. Tim Massey ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
