Veritas NetBackup.

[prev] [thread] [next] [lurker] [Date index for 2006/11/27]

From: David Mackintosh
Subject: Veritas NetBackup.
Date: 16:27 on 27 Nov 2006
So as a consultant who gets to go different places to do different
things, I have managed to get exposed to both Veritas NetBackup and
Bakbone NetVault.  

The latter will undoubtedly be the subject of a later email; today
I'm being hindered by the former.

See, in order to change the media in the robot for NetBackup, one
must go to the robot, remove the media to be removed, and then add
the media to be added.

Oh wait no, there's another step: you must MANUALLY TELL THE SOFTWARE
THAT THE CONTENTS OF THE ROBOT HAVE CHANGED.

Oh wait no, there's another step: you must MANUALLY TELL THE SOFTWARE
THAT THE CHANGES ARE TO BE REFLECTED IN THE SOFTWARE'S IDEA OF WHAT
IS IN THE ROBOT.

Because, you know, there are many reasons why you'd want the
software's idea of what is in the robot to be inconsistant with what
is _actually_ in the robot.  Like for example... um wait no, I can't
think of any.  

If you miss the last two steps, the software will try to load the
media it thinks is wants, and then go and sulk because it isn't
there.  

And if you have changed the tape you have been saving your backup
databases on, you must manually go and tell the software to use a
different tape (ie the tape which is _actually_ there) instead of the
old tape (which is, you know, now gone).  If you miss _this_ step,
NetBackup will refuse to do _anything_.  Including complain that
there's something wrong, and you won't find out until the next week
when you go to rotate out the weekly backups which never happened
because NetBackup couldn't find a tape to dump its databases to.

Say what you want about NetVault (and believe me I will), but it gets
all this RIGHT.  Which is stunning when you consider how much else
NetFault gets WRONG.

_HATE._

-- 
 /\oo/\
/ /()\ \ David Mackintosh | 
         dave@xxxxxx.xxx  | http://www.xdroop.com

Generated at 16:01 on 28 Nov 2006 by mariachi 0.52