Issues configuring robot and drives on Windows 2008 64-Bit

[Osoto_Gari]

Hello,

Working with a Windows 2008 64-Bit box for the first time as a media server in our DMZ.  Was able to install NBU 7.0.1 on the box, but can’t successfully configure drives or robot.  Drives are HP LTO5 in a Quantum i6000 Library.  Robotic control goes through Master Server on Solaris 10 and working without issue.  LTO5 drives zoned directly to HBA’s on new Window Box.  Additionally two other Solaris 10 media servers interface with Robotic control via master server.  New Windows Box being used for DMZ backups to replace a Windows 2003 box.  The windows 2003 box also seems to see the robot via the master without issues.

Master shows the Windows 2008 box as a media server and online; however when I try to use the GUI to add the robot and drives it never sees the robot and will not allow me to add it or the drives other than as stand alone.  As stand alone they show as down.

Windows 2008 box is in the DMZ, but have two-way access for ports 1556, 13782, 13701, 13711, 13724, 13723, 13721, 13720

Any suggestions GREATLY appreciated!

[RiaanBadenhorst]

Hi,

The vnetd and pbx ports should be sufficient for comms on the firewall. Did you verify that you can connect either way using bptestbpcd and telnet?

Did you add the media server to EMM using nbemmcmd? Can you run nbemmcmd -listhosts -verbose on the client successfully?

What you can do is just add the robot on the windows server manually using the GUI, then change the drives and add the windows hosts. Use the serial numbers to figure out which drive is which.

[Osoto_Gari]

Thank You Riann,

I have tested ports and they are open.  I tried using the GUI from both master and dmz media server side to add the robot with no success.  The robotic contorl is hosted on the master server.

[Marianne]

Verify correct hostname lookup between master and media server.

Do the following on master:

bpclntcmd -hn <media-server-name>
bpclntcmd ip <media-server-ip>

On media server:

bpclntcmd -hn <master-server-name>
bpclntcmd ip <master-server-ip>

Verify emm comms with media server. On master:

nbemmcmd -listhosts -verbose
nbemmcmd -getemmserver

Verify response from media server

[Osoto_Gari]

Thank you very much Marianne.

I checked from the master and dmz media server in question and the only thing I found is that on the master and other three media servers the machine flag has a lower case vowel in the middle 0xe4 is one; whereas the media server with issues shows only 0xf as machine flag. 

[Nathan_Kippen]

Make sure you've installed the correct drivers with the new windows box..  you should be able to see the robot and drives in the device manager.  If you can't see your devices locally netbackup wont be able to install/setup them up either.  On the new windows media server once "scan" is seeing the robot/drives with serial numbers etc then you should be able to run the NBU device configuration wizard.

[watsons]

First, make sure OS can detect the devices - otherwise Netbackup won't be able to detect it as well.

Then make sure device driver is installed, x64 should be from the hardware vendor.

If the above has been sorted and you still see problem, might want to check if there is any hidden device configured before:  http://www.symantec.com/docs/TECH93292

[Osoto_Gari]

Thank you for your help.  I did not see any ghost hardware on the system.

Windows Device Manager and scan both see the drives, but not the robot.  The robot is hosted by the master server so would I really need a driver other than the device mappings for it?

[Marianne]

You are correct - the media server does not need to see the robot. It needs to find the robot on the EMM server.

Please verify output of:

nbemmcmd -getemmserver

Run this on the master (which will connect to all media servers to obtain EMM server name).

If you don't mind, please post output of nbemmcmd -listhosts -verbose and nbemmcmd -getemmserver

There is more than just the machine flag that is important. Change hostnames if you don't want your hostname to be displayed. Call them master, media1, media2, etc. Please indicate which one is problematic media server.

[Osoto_Gari]

Thank You Marianne,

Per company rules I changed the server names and domain; hoever everything else is as it was displayed.  Media Server dmznb2 is the one with issues.

NBEMMCMD, Version:7.0.1
The following hosts were found:
masterserver
        MachineName = "masterserver"
        FQName = "masterserver.subdomain.domain.net"
        MachineDescription = ""
        MachineNbuType = server (6)
masterserver
        ClusterName = ""
        MachineName = "masterserver"
        FQName = "masterserver.subdomain.domain.net"
        GlobalDriveSeed = "VEND:#.:PROD:#.:IDX"
        LocalDriveSeed = ""
        MachineDescription = ""
        MachineFlags = 0xe6
        MachineNbuType = master (3)
        MachineState = active for tape and disk jobs (14)
        NetBackupVersion = 7.0.1.0 (701000)
        OperatingSystem = solaris (2)
        ScanAbility = 5
mediaserver2.subdomain.domain.net
        ClusterName = ""
        MachineName = "mediaserver2.subdomain.domain.net"
        FQName = "mediaserver2.subdomain.domain.net"
        LocalDriveSeed = "RN:POS"
        MachineDescription = ""
        MachineFlags = 0xe4
        MachineNbuType = media (1)
        MachineState = active for tape and disk jobs (14)
        MasterServerName = "masterserver"
        NetBackupVersion = 7.0.1.0 (701000)
        OperatingSystem = solaris (2)
        ScanAbility = 5
mediaserver1
        ClusterName = ""
        MachineName = "mediaserver1"
        FQName = "mediaserver1.subdomain.domain.net"
        LocalDriveSeed = ""
        MachineDescription = ""
        MachineFlags = 0xe4
        MachineNbuType = media (1)
        MachineState = active for tape and disk jobs (14)
        MasterServerName = "masterserver"
        NetBackupVersion = 7.0.1.0 (701000)
        OperatingSystem = solaris (2)
        ScanAbility = 5
dmzmedianb1
        ClusterName = ""
        MachineName = "dmzmedianb1"
        FQName = "dmzmedianb1.subdomain.domain.net"
        LocalDriveSeed = ""
        MachineDescription = ""
        MachineFlags = 0xa4
        MachineNbuType = media (1)
        MachineState = active for tape and disk jobs (14)
        MasterServerName = "masterserver"
        NetBackupVersion = 7.0.1.0 (701000)
        OperatingSystem = windows (11)
        ScanAbility = 5
dmzmedianb2
        ClusterName = ""
        MachineName = "dmzmedianb2"
        FQName = "dmzmedianb2.subdomain.domain.net"
        LocalDriveSeed = ""
        MachineDescription = ""
        MachineFlags = 0x4
        MachineNbuType = media (1)
        MachineState = active for disk jobs (12)
        MasterServerName = "masterserver"
        NetBackupVersion = 7.0.1.0 (701000)
        OperatingSystem = windows (11)
        ScanAbility = 5
Command completed successfully.

NBEMMCMD, Version:7.0.1
These hosts were found in this domain: mediaserver1, mediaserver2, masterserver, dmzmedianb1, dmzmedianb2

Checking with the host "mediaserver1"...
Checking with the host "mediaserver2"...
Checking with the host "masterserver"...
Checking with the host "dmzmedianb1"...
Checking with the host "dmzmedianb2"...

Server Type    Host Version        Host Name                     EMM Server

MEDIA          7.0     mediaserver1    masterserver

MEDIA          7.0                 mediaserver2    masterserver

MASTER         7.0                 masterserver                  masterserver

MEDIA          7.0                 dmzmedianb1                   masterserver

MEDIA          7.0                 dmzmedianb2                   masterserver

Command completed successfully.

[Marianne]

No comms problems...

Media server dmzmedianb2 : MachineState = active for disk jobs (12)

Have you added 'Library Based Tape Drive' license on the media server? If drives are shared you need Shared Storage Option license as well.

[Osoto_Gari]

Here is what the key shows ....

  file version    = 0x05000000
  time added      = 0x4dd942af 05/22/11 10:06:55
  hostname        = dmzmedianb2
  product ID      = 6 NetBackup Enterprise Server
  serial number   =
  key version     = 0x04050000
  count           = 0
  server platform = 2 Any Windows platform
  client platform = 0 Any platform
  server tier     = 10 NetBackup Enterprise Server
  client tier     = 0 No tier
  license type    = 1 Permanent
  Site ID         = 22 Unknown site: 22
  Feature ID      = 73 Open File Backup +
  Feature ID      = 71 Remote Client Support +
  Feature ID      = 70 Robotic Library Sharing Support +
  Feature ID      = 69 Remote Media Server Support +
  Feature ID      = 68 Microsoft RSM Robotic Libraries +
  Feature ID      = 67 ADIC DAS/SDLC Robotic Libraries +
  Feature ID      = 66 IBM ATL Robotic Libraries +
  Feature ID      = 65 Fujitsu LMF Robotic Libraries +
  Feature ID      = 64 StorageTek ACS Robotic Libraries +
  Feature ID      = 51 Snapshot Client <Core Frozen Image Services> +
  Feature ID      = 20 Base NetBackup +

I've checked Quantum's website for Scalar i6000 Windows drivers and there are none.  I did verify my HP LTO5 drivers on the box.

[Marianne]

Those are features enabled by the NetBackup Enterprise Server license key.

You need to add 'Library Based Tape Drives' license as well. If drives are shared, SSO license as well.

Use the same license keys for these 2 features that's on master or other media servers.

If robot control is on master, you don't need any robotic drivers on Windows media server.

[Osoto_Gari]

I updated the keys as well as a stop/restart of NetBackup on the media server.  I'm still at the same point.

I try to add from the wizard and it detects the tape drives, but not robot.  The drives come up in the wizard as limited via no known robot.

I manually add the robot and restart device daemons.  On the dmznb2 side it shows the correct robot type and enabled, but from the master server it shows not enabled, but only for the dmznb2 server?

[Marianne · Accepted solution]

I recently experienced a problem with a new media server that simply stayed 'Active for disk', even after devices were added successfully.

The following command (on the master) fixed the media server status:

nbemmcmd -updatehost -machinename <media-server> -machinestateop set_tape_active -machinetype media -masterserver <master>

[Osoto_Gari]

The command took and media server shows active for tape and disk, but it still shows robot as not enabled after delete, LTID restart,robot re-add, LTID restart

[Osoto_Gari]

It's very strange because we have the Quantum and two old Storage Tek 700e's all controlled by the master.  I get the same issues no matter which one I try and add to the media server.

[Nathan_Kippen]

When running the devize wizard you have to include the new windows media server and the master server (or server that can see the robot) in your selection for the wizard.  Device manager will not allow you to add tape drives if the wizard doesn't know who controls the robot.  The wizard makes queries to the robot to figure out the drive numbers etc...

[Marianne]

Great suggestion Nathan!

Please post output of 'scan' on master (robot control host) as well as new media server.

[Osoto_Gari]

Hello All,

I can't say with complete confidence that I truly know the solution, but I believe updating the license keys may have done it.

I tried testing each step of the way and that was the last thing I did before the drives configured correctly.

I actually did not know it at the time, but a contributing issue was that the patch panel my fiber was in had bad ports and the signal was intermittent.  I was able to get the drives to work correctly and consistently after re-routing the cables.

I greatly appreciate all of the assistance!