Re: [Duplicity-talk] Mirroring then writing to multiple backup destinations?

[GDR!]

Hi,

Duplicity keeps a local cache of the metadata files. Before it uses that
cache, it connects to the backup destination and checks if there are any
differences. I've deleted duplicity files manually over FTP and it
picked up the changes (not that it's a good way of doing anything).

Also I'm unsure about this part because I couldn't find the appropriate
code, but duplicity keeps its cache in a directory named after a hash of
something, and I believe that something is a pair of (backed up
directory, remote resource URL). So if I'm right, there's a chance that
your 3 devices will have 3 different local cache directories.

In case you have any issues, you could just delete the cache directory
(~/.cache/duplicity by default) after it finishes working, or point it
to use non-permanent storage.

GDR!
http://gdr.name/

On 04.06.2014 06:48, Rubin Abdi wrote:
> The short question: Does Duplicity keep any sort of backup knowledge
> data not in the actual backup destination? Or does Duplicity figure out
> the state of the backup destination by looking at the actual destination
> each time?
> 
> Setup:
>  * Laptop with important data
>  * Home server with other important data inside of a large RAID6
>  * Backup-A USB drive, plugged into server
>  * Backup-B USB drive, kept offsite most of the time
> 
> When at home I would like to periodically backup my laptop to Backup-A
> plugged into my home server, most likely when I'm about to go to sleep
> and remember to plug my laptop into the wired local network, multiple
> times a week. On my server I want a cronjob to also periodically backup
> important data from the RAID into Backup-A.
> 
> I live in a disastrous city called San Francisco, where there's a high
> chance that tomorrow an earthquake will happen and swallow my flat into
> the ground or some unwelcome party going friend of a friend hipster may
> inadvertently spill cheap beer all over my server. And so I have
> Backup-B which I typically keep offsite across the bay, unplugged from
> any networks.
> 
> Once a month I would like to bring Backup-B back to my house and
> basically mirror all of Backup-A to it, completely so they're 1:1,
> backups for both laptop and server RAID. After that mirror/update is
> done I will go and take Backup-B back to its remote site across the vast
> distance that is the bay.
> 
> Two or three times a month I might find myself at the remote location
> where Backup-B is being stored along with my laptop and would like to
> update the laptop's portion of the backup. There is a good chance that
> between the time I last mirrored Backup-A to Backup-B, and now doing
> this offsite laptop to Backup-B, I've already made multiple backups to
> Backup-A.
> 
> So my longer question would be can Duplicity possibly get confused if I
> attempt a backup to a destination that has a state older than the
> previously destination it might have used the day before?
> 
> Thanks!
> 
> 
> 
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/duplicity-talk
> 


-- 
Kreślę się z rewerencją,
GDR!

0x4ED3D2B7.asc
Description: application/pgp-keys

signature.asc
Description: OpenPGP digital signature