From owner-freebsd-current@FreeBSD.ORG Tue Jun 29 21:34:33 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D82BF16A4CE for ; Tue, 29 Jun 2004 21:34:33 +0000 (GMT) Received: from mail010.syd.optusnet.com.au (mail010.syd.optusnet.com.au [211.29.132.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id D978B43D49 for ; Tue, 29 Jun 2004 21:34:32 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) i5TLXWB14143; Wed, 30 Jun 2004 07:33:33 +1000 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])i5TLXWVd067860; Wed, 30 Jun 2004 07:33:32 +1000 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost)i5TLXWTE067859; Wed, 30 Jun 2004 07:33:32 +1000 (EST) (envelope-from pjeremy) Date: Wed, 30 Jun 2004 07:33:32 +1000 From: Peter Jeremy To: Dan Nelson Message-ID: <20040629213331.GT1596@cirb503493.alcatel.com.au> References: <1088385053.18392.3.camel@newton.aipo.gov.au> <20040628192527.1C2755C29@techpc04.okladot.state.ok.us> <20040629075138.GB74930@atrbg11.informatik.tu-muenchen.de> <20040629143101.GC81324@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040629143101.GC81324@dan.emsphone.com> User-Agent: Mutt/1.4.2i cc: freebsd-current@freebsd.org Subject: Re: Q's about IBM TSM (was Re: HEADSUP: ibcs2 and svr4 compat headed for history) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jun 2004 21:34:34 -0000 On Tue, 2004-Jun-29 09:31:01 -0500, Dan Nelson wrote: >Casually mention that Veritas NetBackup supports FreeBSD and you were >wondering what the migration path might be :) I'd suggest that's a fairly empty threat. We migrated from TSM to NetBackup at work about 2 years ago and I think TSM was vastly better. We had major problems getting NetBackup working - though I'm not sure how much of that was caused by poor internal planning and implementation decisions. NetBackup administration is also atrocious. Note that NetBackup's security model seems to be fairly poor (the NetBackup daemon must be started from inetd as root and has no obvious security). -- Peter Jeremy