Re: [Duplicity-talk] SVN Backup?

[cwood]

Quoting Kenneth Loafman <address@hidden>:

> address@hidden wrote:
> > I need to backup an svn repository.  The correct way, apparently, is to
> > use 'svnadmin hotcopy' to create a copy of the repository so that the
> > backup is clean (e.g. nobody made changes to the repository while the
> > copy was happening).
> >
> > However, each night when it creates a copy of the repository, it now has
> > new time stamps on the files.  Chances are that very little changed.
> >
> > In testing it, it appears that duplicity ignores the file date
> > differences.  Generally, what rules does duplicity (librsync?) use for
> > knowing when a file is different?
>
> Duplicity uses librsync to store only delta's of the files that have
> changed.  In your case, all files have changed some, at least the time
> and date.  All that would be stored is the new time and date plus any
> modifications that have been made.  It would be a very minimal set of
> data, but could be reduced even more if the time and date were not
> changed during every backup.

That makes sense and definitely should save some space.

If I lose the machine that I am backing up, what keys/info do I need  
to store separately from the machine to make sure that I can restore  
my backups?

Right now I have:
gnupgp key passwd
a gnupgp key (an 8 char key of some sort)
my Amazon s3 key/id and secret

Since I haven't used gnupgp before, I'm not sure if it is storing  
something in a keyring somewhere that I need as well.

C.