Backup Central

Looking at the XferLog of a recent backup, I see it running the
PostDumpCmd twice (or two entries for it running once). Twice would make
sense, since that command is supposed to start a service, and the service
would already be up after the first attempt. It seems that the first
attempt timed out, and the seccond attempt failed.

Big deal. I can live with that. Only now the backup has "failed" and
backuppc threw the whole thing away. All files copied successfully, so
the only place I can possibly imagine it failing is that PostDumpCmd. I
definitely want to see something in the log, and perhaps an email sent to
me (a pager paged?) if this command fails. But I don't want the entire
backup thrown away and the command possibly STILL not succeeding as a
result.

Thoughts?


-------------------------------------------------------
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/

"David Masover" writes:

Looking at the XferLog of a recent backup, I see it running the
PostDumpCmd twice (or two entries for it running once). Twice would make
sense, since that command is supposed to start a service, and the service
would already be up after the first attempt. It seems that the first
attempt timed out, and the seccond attempt failed.

This shouldn't happen: PostDumpCmd should be run exactly once.
BackupPC_dump shouldn't re-run the command; it ignores the
exit status.

Big deal. I can live with that. Only now the backup has "failed" and
backuppc threw the whole thing away. All files copied successfully, so
the only place I can possibly imagine it failing is that PostDumpCmd. I
definitely want to see something in the log, and perhaps an email sent to
me (a pager paged?) if this command fails. But I don't want the entire
backup thrown away and the command possibly STILL not succeeding as a
result.

Again, the exit status is ignored. So the backup must be considered
failed due to some problem with the backup itself.

Looking in the XferLOG.bad file should provide clues to both issues.

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/