From: Michael K. <mic...@ip...> - 2018-09-06 21:55:55
|
Thanks Lonnie Yes I certainly hear what you are saying and it does sort of defeat the store only once purpose of deduplication but does it break it? Effectively all I am doing is presenting a list of included files to tarsnap! Regards Michael Knill On 7/9/18, 4:49 am, "Lonnie Abelbeck" <li...@lo...> wrote: Hi Michael, > So I assume that I can just replace 2) with tarsnap No, that would somewhat defeat tarsnap's "Deduplication" http://www.tarsnap.com feature, which saves you money. I would replace all 1-3 steps with tarsnap. Each AstLinux box would have their own tarsnap.key . The web interface Network tab -> Tarsnap Backup: { Tarsnap Backup Options } defines the following variables -- BACKUP_KD_DEFAULTS BACKUP_KD_INCLUDE_DIRS BACKUP_KD_INCLUDE_FILES BACKUP_ASTURW_DEFAULTS BACKUP_ASTURW_INCLUDE_DIRS BACKUP_ASTURW_INCLUDE_FILES BACKUP_PRUNE_AGE_DAYS BACKUP_NOTIFY BACKUP_NOTIFY_FROM -- Files/Dirs automatically excluded via /etc/tarsnap.conf: -- exclude *.bak exclude *.db exclude *.mdb exclude *.sqlite3 exclude *.fossil exclude *.netset exclude *.rom exclude *.bin -- For most users the defaults just work, and possibly add a few tweaks. If you want *everything* (minus the excluded suffixes), disable both "Backup [kd] Defaults" and "Backup [asturw] Defaults:" and specify "*" for all four Backup [kd|asturw] Dirs/Files entries. Though I would doubt many users would do that. Be sure to perform some dry-run testing from the command line to help understand what is happening. -- tarsnap-backup --help -- > PS the doco mentions that I can edit /etc/tarsnap.conf. Does that mean that /mnt/kd/tarsnap.conf will take precedence or do I need to edit this file? It was intended that most users will never need to edit the /etc/tarsnap.conf file, and as such it is not linked to /mnt/kd/tarsnap.conf . Editing /etc/tarsnap.conf will use unionfs just as editing /etc/rc.modules does. Lonnie > On Sep 5, 2018, at 9:02 PM, Michael Knill <mic...@ip...> wrote: > > Hi Devs > > I have decided that I will be changing my current backup strategy to Tarsnap for the following reasons: > • I need to back up sensitive files securely > • I need to be performing daily backups as I suspect a few of my customers will be doing their own basic administration soon > • And it looks awesome from my preliminary tests > > My current backup strategy is as follows: > 1) Find all changed files with rsync by comparing files in /mnt/kd and /mnt/kd/.ref and using an excluded directory/file list. > 2) Use tar to back up all the resulting files on the Astlinux server > 3) Move the backup file to the management server via SCP > > So I assume that I can just replace 2) with tarsnap instead of tar and not do 3) but the problem is that I cant do this natively using the tarsnap-backup script. > Will I need to modify/recreate it or is there another way? > > PS the doco mentions that I can edit /etc/tarsnap.conf. Does that mean that /mnt/kd/tarsnap.conf will take precedence or do I need to edit this file? > > Thanks > > Regards > Michael Knill > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Astlinux-devel mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-devel |