Forum Discussion

6 Replies

  • This is probably more of a library question than a NetBackup question - almost!

    If they are being added to existing libraries then the engineer will need to power cycle the libraries so you will have an effect

    If it is a new library then you can get away with it to a certain amount but in general NetBackup likes to re-start the device manager service when adding drives - so that can also cause disruption

    Windows also sometimes likes a reboot to detect new hardware but you may get away with a scan for new hardware

    Hope this helps - best done at a quiet time when at least the device manager service can be restarted

  • Once properly zoned with media servers you will be able to access the tape drives from OS.

    Once detected by OS install the drivers and use Device Configuration Wizard to confgure drives.

  • You never mentioned OS on the media servers?

    'Will the os be interrupted in order for the drives to be configured?'

    Windows - yes.

    Unix/Linux - probably not, depending on platform... Please ensure that persistent binding is done at OS level before you start configuring NBU.

    When you start configuring devices in NBU, I suggest you go for a phased approach - something like 5 media servers at a time? Remember that media server device management services need to be restarted, so no backups can run on chosen media servers while adding devices

  • What kind of direction u r looking for? Want to know what is the way to technically do it? Architectural opinions? Imapact in the environment? Please give us some more data
  • If you are adding the drives to Solaris, you may need to rebuild the sg driver ...

    http://www.symantec.com/docs/TECH10725

    No matter what operating system, the /usr/openv/volmgr/bin/scan command must show the devices before you even think about NetBackup.  If the devices are not visibale in scan, NetBackup will not see them.

    Martin