Temposs wrote:
> I'm also getting a manifest mismatch when I break off a backup(hard shut
> down on computer, etc), and then try to start it again. It was off by
> one, e.g. 3293 on the local manifest and 3292 on the remote manifest. I
> tried deleting the last entry on the local manifest, but it doesn't
> change the result.
If you stop duplicity there will be no remote manifest unless its the
one from a previous backup. The manifest and sigtar files are not sent
to the remote until the backup is complete. Prior to that, they will be
named with a *.part.* in their name, uncompressed and not encrypted.
Some log info, as much as you can, would be helpful.
Temposs wrote:
> I'm also getting a manifest mismatch when I break off a backup(hard shut
> down on computer, etc), and then try to start it again. It was off by
> one, e.g. 3293 on the local manifest and 3292 on the remote manifest. I
> tried deleting the last entry on the local manifest, but it doesn't
> change the result.
If you stop duplicity there will be no remote manifest unless its the
one from a previous backup. The manifest and sigtar files are not sent
to the remote until the backup is complete. Prior to that, they will be
named with a *.part.* in their name, uncompressed and not encrypted.
Some log info, as much as you can, would be helpful.
...Ken