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

On Thu, Jul 29, 2004 at 12:02:13PM +0100, David Brownlee wrote:
  | On Thu, 29 Jul 2004, Joel Rees wrote:
  |=20
  | >Not really a specifically netbsd question, but I I'd like to get a sur=
vey=20
  | >of what people here are currently using for backups, particularly in t=
he=20
  | >case where the customer wants to take periodic snapshots of the system=
=20
  | >instead of developing a proper backup strategy.
  | >
  | >(Customer wants to mount a large volume and do something like  cp -dpr=
 .)
  |=20
  | 	Look at sysutils/rdiff-backup. If you can live with python
  | 	installed it works like rsync with history. I'm using it in
  | 	several places to keep a remote backup plus history of various
  | 	machines onto certain servers. Works locally as well of course :)


I have used rsync & rdiff-backup extensively.

A problem with both is that they modify the atime of the "source" file
and don't have the ability to reset it back to what it was before
the program ran (c.f., the -t option to pax(1)). =20
This can cause problems if you use mbox-style mailboxes, as your
mail "biff" check (e.g, mutt's "new mail in folder" monitoring)
will be confused by this.

YMMV.

Cheers,
Luke.

--1lE8Wy7Exphh2Vpg
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (NetBSD)

iD8DBQFBCQkypBhtmn8zJHIRAr2QAJ9fAPC/ylQf396F2FNgGn6v84WZJwCgt8Bs
/ImpVk0/7A6BggArk+GFhYk=
=FoPa
-----END PGP SIGNATURE-----

--1lE8Wy7Exphh2Vpg--