[NTLUG:Discuss] Dirvish -vs- Duplicity

[Richard]

NTLUG had a presentation on the 'dirvish.org' project a while back.  I 
have enjoyed using dirvish to do backups but have always been at odds 
with the approach that the backup server must always pull a backup from 
the client.

So now I have an issue where I don't want to setup a dirvish server and 
have to maintain it. I just want to rent some storage space.    I want 
to push a backup from a client to an offsite server.  Furthermore I want 
the offsite backup to be encrypted.

Through a company that has disk space for rent, I learned of a project 
called 'duplicity'.  It appears that duplicity is a python wrapper 
around rsync ( and the librsync libraries) that is used to determine 
which files to backup into a destination that turns out to be an 
encrypted tar-formatted volume.

I'm still reading up on this, but I thought I'd share this solution and 
ask some questions to which I'm still looking for the answer.

Have any of ya'll used this?

Does duplicity manage deleting files out of  the destination's existing 
tar file backups as the files disappear from the source path?

Can duplicity handle multiple backup backup sets of the same data 
(version'ing ??)  similar to dirvish backup images?

-- 
Richard