Hi, I am doing some c$ share lock-down in Windows Group Policy at present and backup failures are expected for primary backup attempts and for catch-ups on any failures. No problem there. What _wasn't_ expected was that with the failed hosts that are getting retried at each wake-up all the other hosts (ie. currently up-to-date) are getting extra backups. This is clearly undesirable as it rolls out my older states unnecessarily and runs my DumpPostShareCmd notifiers causing spam.
Any suggestions for what bits of the BackupPC configuration I can set to prevent this whilst ensuring the normal backups keep working? Aside from lengthening the wake-up intervals, I would have thought that only failed hosts would get retried whilst also picking up any hosts ready for new backup but as as for previously successful hosts getting retried within their retention periods I am not so comfortable with. - Do backups and retention check off each other? backup <-> retention ... versus ... retention<-backup dismissing backup<-retention - Can retention policies 'block' backup attempts? My schedule for all hosts: hourBegin 7 hourEnd 23 weekDays 1, 2, 3, 4, 5 hourBegin 7 hourEnd 21 weekDays 6, 7 Thanks -- Mark ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ BackupPC-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
