Vasan wrote: > For the next backup, it always seems to check for any modifications > during the last 24 hours. If for example, the next days nightly job > takes only a minute to complete (8:01PM), then first it will check if > any backup has been done for the last 24 hours at 8:01PM itself. In > this scenario, it will come out that the backup has been done in the > last 24 hours since the last backup time was 8:03PM which is less > than 24 hours of the current time. Because of this, it skips this day > and goes on to the next day's backup. > > This is turning out to be an serious issue as this results in a loss > of one day's backup completely. Please throw some light on the > veracity of our observations and advice on how this issue can be > resolved. > Firstly, as someone else has already noted, it should just start the backup at the next 'wakeup' cycle, eg, 9pm or 8:30pm, depending on your config.
Secondly, from memory, the included documentation suggests setting the incremental backup period to 0.97 and the full to 6.97 to avoid this precise issue. Personally, I set the daily to 0.9 and the full to 6.9 ... Really, I could probably set this to 0.6 and 6.6 because I want the backups to run as soon as possible within my 12 hour backup period (the other 12 hours are blacked out). Regards, Adam -- Adam Goryachev Website Managers Ph: +61 2 8304 0000 [EMAIL PROTECTED] Fax: +61 2 8304 0001 www.websitemanagers.com.au ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ BackupPC-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
