Jeff Kosowsky writes:
> Actually, after doing some subsequent incrementals, I believe it is a
> 'bug' and not a feature.
Yes, definitely a bug. Here's a patch, which will shortly
be in CVS.
Craig
--- bin/BackupPC_dump.orig 2008-12-29 02:09:04.643105800 -0800
+++ bin/BackupPC_dump 2008-12-2
Jeffrey J. Kosowsky wrote at about 13:26:47 -0500 on Friday, December 12, 2008:
> I did the first backup on a new machine but aborted it part way
> through because I had the excludes wrong. It was recorded as a partial
> level 0 backup.
>
> I then ran BackupPC_dump from the command line using
Jeffrey J. Kosowsky wrote at about 13:26:47 -0500 on Friday, December 12, 2008:
> I did the first backup on a new machine but aborted it part way
> through because I had the excludes wrong. It was recorded as a partial
> level 0 backup.
>
> I then ran BackupPC_dump from the command line using
Just wanted to post up a "me too!"
I started to hand-edit the file just to make it read correctly, but it
may not be such a big deal.
Jeffrey J. Kosowsky wrote:
> I did the first backup on a new machine but aborted it part way
> through because I had the excludes wrong. It was recorded as a par
I did the first backup on a new machine but aborted it part way
through because I had the excludes wrong. It was recorded as a partial
level 0 backup.
I then ran BackupPC_dump from the command line using '-i'
(incremental) which completed without errors
The partial backup was (appropriately) repla
