Re: [Duplicity-talk] Multiple backends (for instance local/network + S3)

[Olivier Berger]

Le lundi 15 mars 2010 à 00:08 +0100, Simon Ruderich a écrit :
> On Sun, Mar 14, 2010 at 10:09:17PM +0100, Olivier Berger wrote:
> > Hi.
> >
> > I'm looking for examples on how to use duplicity both with some "local"
> > targets (maybe on local network) and remote like S3.
> >
> > I'm thinking about saving some of the processing power if the same
> > backup files can be sent to several backends at once instead of having
> > to recompute them for different backends.
> >
> > Am I missing some obvious guidelines/options/tools ?
> >
> > Thanks in advance.
> 
> A simple solution for that would be to just make the backup to a
> local directory and then use ftp/ssh/whatever to upload the files
> to multiple locations.

I wonder if it would then be possible to restore from S3... probably...
but this seems quite obvious, yes... maybe having to fiddle with the
archive dir or archive name somehow...

But in general, my idea would be that it is integrated into duplicity,
and is run from the source side (not the "local" target's side) so that
in case of unreachability of one of the backends, duplicity would manage
this automatically, for instance. Also there wouldn't be problems like
sync to S3 started while a backup is still in progress on duplicity
side, etc.

A use case would be that whenever at "home" you backup to both
"local" (LAN) and cloud (S3), and whenever on the go, you still backup
to the cloud.

If the sync is done on the local dest host (in case of LAN backups),
then S3 would be updated only when you've cehcked-in back home firs.

Does it make sense ?

Thanks in advance.

Best regards,
-- 
Olivier BERGER <address@hidden>
http://www-public.it-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8
Ingénieur Recherche - Dept INF
Institut TELECOM, SudParis (http://www.it-sudparis.eu/), Evry (France)