I have an issue with similar circumstances which may be the same bug. Using an IAM sub-key on a backup that is approximately 1GB in size, a backup is done hourly and a full backup is done daily.
Yesterday the backup stopped working. When looking at the log I noticed roughly 800 instances of:
NOTICE 1
. Deleting local /opt/cache/mysql/duplicity-inc.20120704T004130Z.to.20120704T014124Z.manifest (not authoritative at backend).
Subsequent runs required a decryption key (which is NOT present on my backup machine), I was able to resolve the problem by pulling the deleted cache files from S3, decrypting them on a secure machine and putting them back on the backup machine. This seemed to resolve the immediate problem, I will continue monitoring for the cache getting cleared.
I have an issue with similar circumstances which may be the same bug. Using an IAM sub-key on a backup that is approximately 1GB in size, a backup is done hourly and a full backup is done daily.
Yesterday the backup stopped working. When looking at the log I noticed roughly 800 instances of:
NOTICE 1 mysql/duplicity -inc.20120704T0 04130Z. to.20120704T014 124Z.manifest (not authoritative at backend).
. Deleting local /opt/cache/
Subsequent runs required a decryption key (which is NOT present on my backup machine), I was able to resolve the problem by pulling the deleted cache files from S3, decrypting them on a secure machine and putting them back on the backup machine. This seemed to resolve the immediate problem, I will continue monitoring for the cache getting cleared.