I was getting sick and tired of the Perl implementations, hence rdup-tr and now rdup-up. With rdup-up you can update a directory tree with an rdup archive. So right now there are three programs that make up the rdup-suite.

• rdup - this creates a file list (possible with file content rdup -c)
• rdup-tr - transform an rdup list to an archive (possible rdup -c)
• rdup-up - update the filesystem

The only Perl program left is rdup-s3 for uploading an archive to Amazon's S3 service. I'm not sure how to deal with this situation. Maybe I will fold the rdup-utilities back into the main rdup archive again. Or create a contrib/ directory where these will live? Don't know yet.

One things that will not come back is rdup-simple, or at least not in the form it was. The main reason for this is that you are so flexible with rdup, rdup-tr and rdup-up that an extra script is an overkill, IMO.

Again a few examples

A compressed dump of /bin to /vol/backup

rdup /dev/null /bin | rdup-tr -Pgzip,-c,-f |\
rdup-up -v /vol/backup

Or, you want to go remote?

rdup /dev/null /bin | rdup-tr -Pgzip,-c,-f \
-Popenssl,enc,-e,-des-cbc,-k,mysecret | \
ssh -C user@remotehost rdup-up /vol/backup/myhost/today/

Then, don't forget the encryption. Restoring is actually reversing the command line:

rdup /dev/null /vol/backup/myhost/today | \
rdup-tr -Popenssl,enc,-e,-des-cbc,-k,mysecret \
-Pgzip,-c,-f |\
ssh -C user@myhost rdup-up /bin