Date: Wed, 20 Feb 2002 22:01:32 -0500 From: Alan Clegg <alan@clegg.com> To: Noah Davidson <Noah@oopz.com> Cc: "FreeBSD-ISP List (E-mail)" <freebsd-isp@FreeBSD.ORG> Subject: Re: backups Message-ID: <20020220220132.C87710@shell.wetworks.org> In-Reply-To: <A6A82340FB3DB643A0678E3B10CD5AC102980D@xela.oopz.com>; from Noah@oopz.com on Wed, Feb 20, 2002 at 06:12:37PM -0800 References: <A6A82340FB3DB643A0678E3B10CD5AC102980D@xela.oopz.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--dkEUBIird37B8yKS
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Unless the network is lying to me again, Noah Davidson said:=20
> [...] We are interested in Veritas=
=20
> BackupExec products. We have used these before. [...]
I am currently forced to use BackupExec running on NT to bacup UNIX clients
(Solaris, Linux, and FreeBSD), and can tell you:
RUN AWAY!
We have actually seen the backup software cause corruption in files as
they are backed up. =20
I'd recommend that if you really want to use BackupExec, use dump to create
disk-based 'backup images' and either drop them to an NT filesystem for the
BackupExec suite to save, or aim BackupExec at a samba share... We are=20
using Amanda to backup to disk, then dropping those files to an NT box.
AlanC {details on why to not use BackupExec when backing up Rational's=20
ClearCase data on request}
--dkEUBIird37B8yKS
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (FreeBSD)
Comment: For info see http://www.gnupg.org
iD8DBQE8dGMMyJP8xSfQVdsRAraDAJ9oInwrswpQ/Z7EMlulkfJkeZtoKgCePar+
T4+O5Ms1+VVyV7EqBoGrk8E=
=BZfP
-----END PGP SIGNATURE-----
--dkEUBIird37B8yKS--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020220220132.C87710>