Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 24 May 2007 18:10:18 +0200
From:      Roland Smith <rsmith@xs4all.nl>
To:        Jason Lixfeld <jason+lists.freebsd-questions@lixfeld.ca>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Backup advice
Message-ID:  <20070524161018.GC20309@slackbox.xs4all.nl>
In-Reply-To: <28E0DBBA-BB24-4D6B-AE65-07EB5254025C@lixfeld.ca>
References:  <28E0DBBA-BB24-4D6B-AE65-07EB5254025C@lixfeld.ca>

next in thread | previous in thread | raw e-mail | index | archive | help

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

On Wed, May 23, 2007 at 07:27:05PM -0400, Jason Lixfeld wrote:
>  So I feel a need to start backing up my servers.  To that end, I've deci=
ded=20
>  that it's easier for me to grab an external USB drive instead of a tape.=
  It=20

Buy at least two, and keep one off-site.

>  would seem dump/restore are the tools of choice.  My backup strategy is=
=20
>  pretty much "I don't want to be screwed if my RAID goes away".  That sai=
d I=20
>  have a few questions along those lines:
>=20
>  - Most articles I've read suggest a full backup, followed by incremental=
=20
>  backups.  Is there any real reason to adopt that format for a backup=20
>  strategy like mine, or is it reasonable to just do a dump 0 nightly?  I=
=20
>  think the only reason to do just one full backup per 'cycle' would be to=
=20
>  preserve system resources, as I'm sure it's fairly taxing on the system=
=20
>  during dump 0 times.

Depending on the size of your data, a level 0 dump could take a couple
of hours. Unless you have a terabyte raid array, in which case a single
USB disk probably won't cut it. :)

On the other hand, if your dataset changes rapidly you might not save
much with incremental dumps.

You can save time by setting the nodump flag on directories that contain
files that you don't really nead or can easily replace, such as
/usr/obj, /usr/ports/distfiles, /tmp et cetera.

>  - Can dump incrementally update an existing dump, or is the idea that a =
dump=20
>  is a closed file and nothing except restore should ever touch it?

You cannot update a dump file, AFAIK.

>  - How much does running a backup through gzip actually save?  Is taxing =
the=20
>  system to compress the dump and the extra time it takes actually worth i=
t,=20
>  assuming I have enough space on my backup drive to support a dump 0 or t=
wo?

It depends. On a normal filesystem you save about 50% with gzip. But if you=
 have
lots of (already compressed) audio and picture data there are almost no sav=
ings.
Compressing with gzip shouldn't tax the system too much, unless it's very
old. Using bzip2 usually isn't worth it. It takes much longer and maxes
out the CPU on my 2,4 GHz athlon64.

Do not forget the -L flag if you're dumping a live filesystem!

>  - Other folks dumping to a hard drive at night?  Care to share any of yo=
ur=20
>  experiences/rationale?

My desktop machine's file systems are backed up every week to a USB
drive, using gzipped dumps. Every month I start with a new level 0
dump. When I run out of space I delete the oldest set of dumps.

When I nuked my /usr parition by accident I was very happy to be able to
restore things with the tools in /rescue, without first having to
rebuild a lot of ports.

Roland
--=20
R.F.Smith                                   http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)

--s9fJI615cBHmzTOP
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.3 (FreeBSD)

iD8DBQFGVbjpEnfvsMMhpyURAn7nAJsHpZdHgw7GGNWIa+RL4UALT+g4UgCfeQpd
WxFqmEGujUHjumUBe+MDaPg=
=HAcl
-----END PGP SIGNATURE-----

--s9fJI615cBHmzTOP--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070524161018.GC20309>