Media Server Can not Connect to Tape Library

Check for the Master server and media server hostname given correctly and able to resolve correctly.

Check for the permission and user account for the netbackup daemons. It should be Netbackup Administrator.

Also check for Event Viewer logs for any application/system errors.

--Praveen

What exactly are you trying to start? Request Service/daemon ONLY runs on a master server.

Please have a look at this TN to verify which services should be running on a windows media server:

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

Rather use cmd to start services on a windows media server : 'bpup -v' will start media services in correct order.

Please also give us more info for Media server 2:

Is this a new installation?

Does the master server 'know' about this media server? Check output of 'nbemmcmd -listhosts -verbose'

Can master server connect to media server 2? Check output of 'nbemmcmd -getemmserver'

Are you able to see the tapedrives and Medium changers in the computer management of Media server2. Check the physical connectivity of the tape library and Media server.

Hello Ram,

Yes, in Computer management I see tape driver and medium changers, all driver is OK.

Master server ping Media server ok.

Hello Marianne van den Berg,

Thank you for your answer,

Media Server 2 is new server, it is pmssfss12.

On Media Server 2:

- bpup -v

Starting services
> NetBackup Client Service
> NetBackup Client Service -- STARTED
> NetBackup SAN Client Fibre Transport Service
> NetBackup SAN Client Fibre Transport Service -- STARTED
> NetBackup Event Manager
> NetBackup Event Manager -- DISABLED
> NetBackup Volume Manager
> NetBackup Volume Manager -- STARTED
> NetBackup Device Manager
> NetBackup Device Manager -- STARTED
> NetBackup Remote Manager and Monitor Service
> NetBackup Remote Manager and Monitor Service -- STARTED
> postgresql-8.3
> postgresql-8.3 -- NOT STARTED
> NetBackup Deduplication Manager
> NetBackup Deduplication Manager -- NOT STARTED
> NetBackup Deduplication Engine
> NetBackup Deduplication Engine -- NOT STARTED
> NetBackup Compatibility Service
> NetBackup Compatibility Service -- STARTED
> NetBackup Request Daemon
> NetBackup Request Daemon -- NOT STARTED
> NetBackup Job Manager
> NetBackup Job Manager -- DISABLED
> NetBackup Policy Execution Manager
> NetBackup Policy Execution Manager -- DISABLED
> NetBackup Service Layer
> NetBackup Service Layer -- STARTED
> NetBackup Vault Manager
> NetBackup Vault Manager -- STARTED
> NetBackup Storage Lifecycle Manager
> NetBackup Storage Lifecycle Manager -- NOT STARTED
> NetBackup Service Monitor
> NetBackup Service Monitor -- STARTED
> NetBackup Bare Metal Restore Boot Server
> NetBackup Bare Metal Restore Boot Server -- STARTED
Start up of one or more services failed.

- nbemmcmd -getemmserver

C:\Program Files\Veritas\NetBackup\bin\admincmd>nbemmcmd -getemmserver
NBEMMCMD, Version:7.0
These hosts were found in this domain: pmssapp27, pmssdbs04, pmssfss12

Checking with the host "pmssapp27"...
Checking with the host "pmssdbs04"...
Checking with the host "pmssfss12"...

Server Type    Host Version        Host Name                     EMM Server

MASTER         ■       Üèσv        pmssapp27                     pmssapp27

MEDIA          ■       Üèσv        pmssdbs04                     pmssapp27

MEDIA          ■       Üèσv        pmssfss12                     pmssapp27

On Master server:

- nbemmcmd -listhosts -verbose

C:\Program Files\Veritas\NetBackup\bin\admincmd>nbemmcmd -listhosts -verbose
NBEMMCMD, Version:7.0
The following hosts were found:
pmssapp27
        MachineName = "pmssapp27"
        MachineDescription = ""
        MachineNbuType = server (6)
pmssapp27
        ClusterName = ""
        MachineName = "pmssapp27"
        GlobalDriveSeed = "VEND:#.:PROD:#.:IDX"
        LocalDriveSeed = ""
        MachineDescription = ""
        MachineFlags = 0x7
        MachineNbuType = master (3)
        MachineState = active for tape and disk jobs (14)
        NetBackupVersion = 7.0.0.0 (700000)
        OperatingSystem = windows (11)
        ScanAbility = 5
pmssvms01
        MachineName = "pmssvms01"
        MachineDescription = ""
        MachineNbuType = virtual_machine (10)
smssvms01
        MachineName = "smssvms01"
        MachineDescription = ""
        MachineNbuType = virtual_machine (10)
pmss
        MachineName = "pmss"
        MachineDescription = ""
        MachineNbuType = virtual_machine (10)
pesx04.prudential.com.vn
        MachineName = "pesx04.prudential.com.vn"
        MachineDescription = ""
        MachineNbuType = virtual_machine (10)
pmssdbs04
        ClusterName = ""
        MachineName = "pmssdbs04"
        LocalDriveSeed = ""
        MachineDescription = ""
        MachineFlags = 0x7
        MachineNbuType = media (1)
        MachineState = active for tape and disk jobs (14)
        MasterServerName = "pmssapp27"
        NetBackupVersion = 7.0.0.0 (700000)
        OperatingSystem = windows (11)
        ScanAbility = 5
pmssfss12
        ClusterName = ""
        MachineName = "pmssfss12"
        LocalDriveSeed = ""
        MachineDescription = ""
        MachineFlags = 0x5
        MachineNbuType = media (1)
        MachineState = not reachable by master (4)
        MasterServerName = "pmssapp27"
        NetBackupVersion = 7.0.0.0 (700000)
        OperatingSystem = windows (11)
        ScanAbility = 5
Command completed successfully.


Yes, we can, Master server can connect to media server.

Master can connect to tape library.

Media server 1 can connect to tape library.

As per your ouputs, Netbackup request daemon (bprd) is not starting in the media server and hence master server is unable to connect to media server.

pmssfss12
        ClusterName = ""
        MachineName = "pmssfss12"
        LocalDriveSeed = ""
        MachineDescription = ""
        MachineFlags = 0x5
        MachineNbuType = media (1)
        MachineState = not reachable by master (4)
        MasterServerName = "pmssapp27"
        NetBackupVersion = 7.0.0.0 (700000)
        OperatingSystem = windows (11)
        ScanAbility = 5

Please try starting the service using local admin account.

if the new media server is a windows 2008 box, you may need to open command prompt as "Run As Administrator" and then try to bring up the services by "bpup -f -v".

GUYS, please -  Request Service /Daemon DOES NOT run on a media server!!

Symantec Private Branch Exchange needs to be running as well as all the services as per TECH57458 listed above .

I do agree with Rizwan - this seems to be causing the problem(s):

MachineState = not reachable by master (4)

The only other time that I've seen this was in your other post when the production media servers were not available at your DR site: https://www-secure.symantec.com/connect/forums/delete-media-server-after-recovery-catalog#comment-5714601

Please check output of the following from master:

bptestbpcd -host pmssfss12 -verbose

Please also confirm that you have all necessarry license keys installed on the media server:

Enterprise Server (or Enterprise Client)
Robotic drive license
SSO (shared storage option - if drives are shared)
 

I apologise for the wrong info and appreciate Marianne highlighting it. In our production setup we dont have seperate media server, out of curiosity installed a test media server and found BPRD does not runs in media server.

C:\Program Files\Veritas\NetBackup\bin>bpps
* TSTBKP2
COMMAND           PID      LOAD             TIME   MEM
bpcompatd        2912        0.000%            0.062  9.3M
nbsvcmon         3836        0.000%            0.125   10M
bpinetd             3864        0.000%            0.093  4.4M
vmd                  3980        0.000%            0.187   10M
bpjava-msvc      4040        0.000%            0.031  3.4M
nbsl                 192          0.000%            0.156   17M
nbrmms            4072        0.000%            0.343   19M
bpps                 836         0.000%            0.031  2.1M

Symantec Private Branch Exchange will not be shown in bpps, you have check that in Services console.

As Marriane stated, check on bpcd test. Also you may check if telnet to media server on port 13782 works.

telnet pmssfss12 13782

Looks like pmssfss12 is locally dedined as Master server. Check in Registry for the Servers entry and see if the actual master server is listed on the top. if not put the master server on the top of the list.

This might happen if we give server name a media server name pmssfss12 during installation.

I hope Drives and Robot are visible at OS level on pmssfss12 ?

--Praveen