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

[Raymond Smith]

On 2 February 2010 14:58, Russell Stuart <russell-humbug at stuart.id.au> wrote:
> On Tue, 2010-02-02 at 14:25 +1000, Raymond Smith wrote:
>> Would dropping files into different directories help? Maybe
>> one-directory per base-backup?
>
> I doubt it.  S3 states very clearly in their doco things like this can
> happen.  For example then say if you put a file up then, then
> immediately reconnect it is entirely possible it won't appear in the
> directory listing.  It is not an ACID database, and doesn't pretend to
> be one.

I suspect I am missing some context here.

When does your backup script delete files? Do deletes only happen with
each full backup or do they happen more often?

Also, any idea if S3 directory creation suffers from the same
eventual-consistency problem as files?

Another possibility would be including some prefix that we can rely on
to be unique to the machine -- IP address or MAC address maybe. The
"is backup stuffed" check could then limit itself to looking for files
with that prefix.

> So is it only the noisy emails.  There is a simple solution to them if
> it continues - just don't report files appearing out of thin air as
> evidence of someone else modifying the backups.  Check for file
> deletions and modifications only.

This would be a great improvement -- noisy system emails will end up
being treated just like spam.

Cheers,

Raymond