Vasan writes:
> 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.
Provided you have a $Conf{WakeupSchedule} or blackout periods that force
the backup to around 8pm, instead of setting $Conf{FullPeriod} to 2.0,
set it to 1.5. Similarly for $Conf{IncrPeriod}.
This is why the default $Conf{IncrPeriod} is 0.97 and $Conf{FullPeriod}
is 6.97. 0.03 * 24 = 0.72hr, less than the 1 hour spacing in
$Conf{WakeupSchedule}.
Craig
-------------------------------------------------------------------------
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/
