[OpenAFS] Current OpenAFS Backup Recommendations

Holger Rauch holger.rauch@empic.de
Mon, 28 Dec 2009 11:41:34 +0100


--5mCyUwZo2JvN/JJP
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi Dan!

Thanks a lot for your reply.

On Mon, 28 Dec 2009, Dan Pritts wrote:

> [...]=20
> It is disk-based, no tape support at all.  You could use a standard
> tape backup program to back up backuppc4afs's backup store.
>=20
> You may see mention elsewhere that using tape to backup a backuppc data
> store is untenable; this is true due to non-afs backuppc's extensive
> use of hard links as a poor-man's dedup. =20
>=20
> backuppc4afs does not do the hardlink bit, since it does individual vos
> dumps and the expectation is that no two vos dumps will ever be identical.

Thanks for elaborating. What would then be the best solution to write
backuppc4afs's backup store to tape (taking into account that I have a
HP StorageWorks 1/8 G2 autoloader equipped with two Ultrium 920/960
tape drives for LTO3 tapes)?

By "best" I mean that it should be capable of handling the following

- Daily differential backups
- one weekly full backup performed on weekends
- should be easily manageable (to set a few basic parameters at the
  beginning of a script or in a dedicated config file is OK but having
  to change some lengthy script somewhere in the middle isn't)
- (if available) some ncurses or web based interface would be a plus
- should automatically detect when to change tapes and should initiate
  the tape change, so that no manual intervention is necessary
- should ideally be open source or at least freely usable

I'm thinking about using Bacula in order to write disk based backups
to tape(s). Any comments/other suggestions provided that I'd follow
the backuppc4afs path?

Thanks in advance & kind regards,

       Holger
      =20
--5mCyUwZo2JvN/JJP
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAks4i14ACgkQbiVtWpZdKQLDNACeJzK1h8Nmry2Pp3btALM00koq
bHcAni3IbC/0jDBOdvD4cZei4s1mryUS
=t/Wg
-----END PGP SIGNATURE-----

--5mCyUwZo2JvN/JJP--