> From: Brad Beyenhof [mailto:[email protected]]
>
> At $PREVIOUSJOB, I wrote a Perl frontend for rdiff-backup that I kicked off
> nightly via cron to backup shared /home (NFS- and samba-mounted on
> clients) and a few other important data locations. It was a lifesaver when
> clobbered data needed restoring.
That sounds like a job better suited for rsnapshot. At least in a redhat
derivative system, it's as easy as this: Edit /etc/rsnapshot.conf to specify
the source & destination.
Copy the cron command from the man page "man rsnapshot"
>> Although I'm surprised it doesn't have any comment capability.
>
> I'm not sure exactly what you mean by this,
I mean, in a versioning system, you're going to specify comments with your
commits.
svn commit -m 'updated the ssl certs due to nearing expiration'
In rdiff-backup, you're actually performing a version operation (synonymous to
svn commit) but no comments.
Think about it like this: With git or svn, if you commit or push a new version
up to a server somewhere, you're storing the diffs with the previous version.
When you run a rdiff-backup, you're doing exactly the same thing. So the
statement "backup != versioning" has some truth in some situations, but it
doesn't correlate to any distinction between git/svn/rdiff-backup. Well ...
git and svn have some obvious features related to versioning (branch/tag,etc).
But that's really a complete tangent.
_______________________________________________
Tech mailing list
[email protected]
https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech
This list provided by the League of Professional System Administrators
http://lopsa.org/
