[H-SASIG] rdiff-image-cron /etc/rdiff-image/rdiff-image.conf FAILED!

[Raymond Smith]

On 2 February 2010 15:56, Russell Stuart <russell-humbug at stuart.id.au> wrote:
>> What I meant to say here was that if we prefixed with a
>> unique-to-(virtual)machine artifact then there would be no problem
>> with different instances of excalibur overwriting each other. We might
>> then dispense with the backup is stuffed check.
>
> There are a couple of issues with that.  Firstly, storing those unused
> backups on S3 forever more costs money.  Secondly it makes restoring
> even harder - how to you know which "artifact" is the most recent one?
> Restoring is difficult as it is - I had write a wrapper around because
> it appears everyone found too complex to do by hand.

If I understood your original statement, you added these checks
because there were two "excaliburs" backing up to S3 at the same time.
If we simply disambiguate between the excaliburs then we don't need
the check for this condition. We still need to delete the files though
and each "excalibur" can and should delete backup files it does not
need. If we still see undead files appearing then maybe some automated
reaper is required.

Cheers,

Raymond