From: wb.kloke@gmail.com
To: 9fans <9fans@9fans.net>
Subject: [9fans] Re: Venti backups from unix
Date: Tue, 17 Dec 2024 11:53:12 -0500 [thread overview]
Message-ID: <17344543920.A102dDcb.377@composer.9fans.topicbox.com> (raw)
In-Reply-To: <AF21168D-47A9-4B59-819A-A13DCB939191@9srv.net>
[-- Attachment #1: Type: text/plain, Size: 2145 bytes --]
Using vac for Unix backup has some shortcomings.
I, too, used vbackup on FreeBSD (UFS2). Whether the different blocksize (on most disks: 32kB) to 8kB vac default may detrimental, is disputable. Now, I have moved to ZFS, and a different approach is needed. ZFS's own backup tools are useful only if the backup device is ZFS also. It is not known, wether a zfs-send stream would play nice with venti deduplication, and probably the send-stream files themselve are not very useful.
On a desktop system using a browser like chromium or firefox, we got a lot of files we simply don't want to backup. The browsers, and a lot of other desktop applications, scatter those files over several dot-named directories like .config, .local or .cache. Excluding dot-named files and directories from backup is a good idea, especially for .ssh, which contains secrets, which are not secret anymore, if backupped.
I find it clumsy to instruct vac to do it right by filenames only. Here is my current exclude file for my own user directory:
> exclude wb.vac
> include .*rc
> include .login
> include .profile
> include .xsession
> exclude .*
> exclude ....[gx]z
> exclude ....bz2
> exclude ....img
> exclude ....iso
> exclude ....zip
> exclude ....tar
> exclude ....t[bgx]z
> exclude ...octave-workspace
> exclude Downloads
A version usable for the /home directory would look like
> include */.*rc
> include */.login
> include */.profile
> include */.xsession
> exclude */.*
> exclude ....[gx]z
> exclude ....bz2
> exclude ....img
> exclude ....iso
> exclude ....zip
> exclude ....tar
> exclude ....t[bgx]z
> exclude ....tmp
> exclude .../temp.*
> exclude ...octave-workspace
I am not really happy with this version, too.
For files other than those in user directories, the restricted vac semantics (no file flags, eg.) will also limit the usefulness of plan9port vac as backup tool.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T5f59d7df5796d0cc-M68bafe46f0acf242efa628a0
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 3646 bytes --]
next prev parent reply other threads:[~2024-12-17 17:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-14 19:37 [9fans] " Anthony Sorace
2024-12-17 16:53 ` wb.kloke [this message]
2024-12-17 19:57 ` [9fans] " Alexander Schreiber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17344543920.A102dDcb.377@composer.9fans.topicbox.com \
--to=wb.kloke@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).