[OpenAFS] backup strategy

[nwf]

--+nBD6E3TurpgldQp
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Nov 12, 2014 at 11:18:54AM +0100, Harald Barth wrote:
>=20
> Do you have an existing backup system (for example for other stuff
> than AFS) and are you allowed to put data into that? In that case,
> what kind of system do you have?
>=20
> We do in effect (hiding all the gory stuff):
>=20
> ... Hilarious script ...
>  ... Hilarious script ...
>   ... Hilarious script ...
>     vos dump VOLUMENAME | tsmpipe /some-prefix/VOLUMENAME.DUMPLEVEL.DATE
>=20
> which makes "files" in TSM which in effect are volume dumps.

Belatedly chiming in with my own $0.02 from our cell.  We use a similar
strategy and the Venti CAS archival server from Plan 9 (as ported to *nix
userland) for backing store (being a CAS, it's all deduping, which is
wonderful).  We have found that passing the dumps through a ``rabin fingerp=
rint
splitter'' script helps immensely, as the dump data is not block-aligned
internal to the dump file.

Our setup is documented (mostly) at
https://www.acm.jhu.edu/~admins.pub/systems/afs-venti.html, and all the scr=
ipts
are available in /afs/acm.jhu.edu/readonly/group/admins.pub/scripts/chicago
(in particular, rabinsplit.c, dump-to-venti.sh, and dump-all-to-venti.sh).

Cheers,
--nwf;

--+nBD6E3TurpgldQp
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCgAGBQJUfBTJAAoJEDaV+jVGC2WDb8wIAKKLhaXPhnYK5mp8moivtxN0
1Ng23UgleSTDrvBIr+P0jORgd34+uuig56T1q1kGFnnlm2WZQd/ZOZjBxNI5Q4xa
pBRe9C3MacB2gnzD33nyAfZVcSjuFbBKdixqYzs0zJuBtX2LLXmX+K98W/6Eo+lb
/6HNE5BA9r7YQXrJ8fY4s4YOY9JJM60VCNG5m1yGPw6wwD8yacM/wremYAvd2g/k
Am9vOI+hNZRhFzFOX9oAk3hw2s0w2Tmhm2k8UyAzYCwVBu13tics86XzHtcvVIYw
njeD/EGeh8MSf/Gu6+0XXSwDRbEmLkwNFyTg2zNg7hk+R9zA1pQTQgdyjZfivaE=
=yUye
-----END PGP SIGNATURE-----

--+nBD6E3TurpgldQp--