#135 PR `merged`: Extend Relax-and-Recover to use duplicity and duply as backup methods¶

thumm opened issue at 2012-07-26 10:07:¶

Duplicity is a backup tool that supports encrypted incremental backup to local or remote storage. Duply as a shell frontend to duplicity simplifies backup tasks.

This patchset adds two additional backup targets to ReaR to use duplicity and duply while recovering a system.

jhoekx commented at 2012-07-26 10:19:¶

Ok, looks simple and good!

One question:
is it necessary to have two separate methods? As far as I could see the code in DUPLICITY is a subset of DUPLY, the only difference being the additional binary? Can't you merge them into one and copy duply only when it's on the system.

Something like this:

REQUIRED_PROGS=(
"${REQUIRED_PROGS[@]}"
gpg
duplicity
python2.6
)
PROGS=(
"${PROGS[@]}"
duply
)

That would mean you need at least duplicity and duply will be copied when available.

thumm commented at 2012-07-26 10:54:¶

Beside the binaries duply needs the files in the directories
/etc/duply
/root/.duply
to be part of the recovery image. Is it possible to extend COPY_AS_IS
with paths which do not exist? If this is the case it's not necessaray
to have two separate methods.

jhoekx commented at 2012-07-26 10:59:¶

Yes, COPY_AS_IS does (or should) not complain when listed files are missing. For example, I have no /etc/termcap and I can still make a backup.

thumm commented at 2012-07-26 12:16:¶

Ok, pull request is updated

jhoekx commented at 2012-07-26 12:32:¶

Good.

Another question: what is build-stamp? You remove it in the makefile, but I have never seen it...

thumm commented at 2012-07-26 12:55:¶

The file is generated if you build a debian package with the make target deb
make deb

I use this target because I always install rear on a server as a debian
package.

jhoekx commented at 2012-07-26 12:59:¶

Ok, merged. Thanks!

[Export of Github issue for rear/rear.]

#135 PR merged: Extend Relax-and-Recover to use duplicity and duply as backup methods¶