Matthias G. Eckermann wrote:
1. Before using the first time: create the config: snapper -c BienersBtrfsBackup create-config /mounts/BienersBtrfsBackup
--- I rely on a ".snapperrc" -- a bit primitive, but easy to modify
more .snapperrc [/home] #excludes=space separated list of patterns to exclude #additive string excludes='.recycle/** Bliss/**' excludes="$excludes .snapdir/**" CPAN-ishtar-build-cache/**" excludes="$excludes /home/law/dup-tst-dir/** /home/law/font/[1-8]"
# age = age of snap in integer days w/midnight as cutoff expire='age>32 or' expire="$expire age>24 && day_of_year%8 or" expire="$expire age>16 && day_of_year%4 or" expire="$expire age>8 && day_of_year%2" expire_default='x' snap_needed='age>1 or' snap_needed="$snap_needed hour_age>8"
2. After every rsync run: snapper -c BienersBtrfsBackup create -d "Whatever you want to tell"
I run it off cron once a day
Bonuspoints for automounting and autorunning the whole thing and publishing the resulting framework:-)
--- Well, the scripts take care of the running and cron does the running. But publishing??... um.. I've only had it running for ~ a year or so, so I don't regard it as stable enough for a real release, I just recently re-merged a separate module (maintaining them separately was a headache), but it's about 2000 lines of perl script -- about 2/3rd's of that is devoted to error checking, checkpointing, and recovery from failures -- and it still tends to break on suse-upgrades as some of the utils switch output or locations. I've thought about "releasing it" [sic] in the form of a git project "in progress" (though I don't work on it much these days -- unless something breaks... then have to figure out why and implement new error handling routines...though I get lazy at times and just rerun it -- and it usually will fix itself due to the checkpointing stuff. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org