I'm using rsnapshot on all my production servers. I love it. For one client, I simply exported the rsnapshot dir with Samba as read-only, and they love it.

BackupPC seems pretty popular. It has a nice web interface. It's also based on rsync, and it also only stores the deltas (using hardlinks). But it stores the files in an open-yet-proprietary format. You are forced to use the web interface to retrieve files, which is not always handy in an emergency situation. On the plus side, BackupPC compresses the stored files, and it also caches the MD5s of the files (which is a big deal for network-based backups). I wish rsnapshot had those features.

   I'm curious if anyone has done these setups:

Q1: Has anyone used rsnapshot on a compressed filesystem? Something like compFUSEd, FuseCompress, or fuse-zip? If one of those fuse-based filesystems properly emulated hard links, then I could simply point rsnapshot to a compressed mountpoint to get compression like BackupPC...

Q2: Has anyone used the rsync option --checksum-seed with rsnapshot? (I.e., to cache checksums on the server, the way BackupPC does?)

If those two things worked, then I could slap a generic PHP "File Explorer" on my rsnapshot dir and have something that does everything BackupPC does, except with backups that appear as standard files on the filesystem (so I could do emergency restores using SSH).


--Derek

On 10/11/2009 08:28 AM, Mark Foster wrote:
William Kreuter wrote:
Thanks again to everyone who offered help with my
inquiries last month about off-the-shelf freeware
backup tools.  I settled on rsnapshot and have it
running now.

What's the easiest way to tell which files have been
written afresh on each new backup?  The target
volume for rsnapshot is, according to df, filling
slightly faster than I would have expected.

Billy
Bump the verbosity and the files backed up should appear in the
rsnapshot.log
Or you can run (something like) rsnapshot -t hourly
and find the backup set you are suspicious of , run the rsync command it
shows you (but possibly replace -q with -v and definitely -n) to get a
real-time explanation.

Reply via email to