cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted

Restarting Media server management failed

The system failed to restart the media manager when add the drive, as I can see the robot and drive on the nbu admin console, but inventory the robot not to start the deamon, add the drive wizard but still to not able to start up.  Please advice 

9 Replies
Highlighted

Re: Restarting Media server management failed

Hey

Please provide output from bpps from media and master... and vmps

Highlighted

Re: Restarting Media server management failed

@Home_224 

Please show us what exactly is running on the media server :
bpps -x

You need to confirm that PBX and vmd is running as a minimum.

If ltid (and other media manager processes) are not running, please do this: 

Start ltid from cmd in verbose mode:
ltid -v

Check running processes again with bpps -x. 

You should see MM processes such as:
vmd
ltid
avrd
tldcd (if robot control host)
tldd (for robot-control tape drive(s) )

If not, or if processes start and then terminate, check /var/adm/messages for errors. 

Please show us output of commands and errors in messages file. 

Highlighted

Re: Restarting Media server management failed

@Marianne 

Please see the output message as follows:

bpps -x
NB Processes
------------
root 28133 11489 0 18:15:17 ? 0:00 /usr/openv/netbackup/bin/bpdbm
root 11489 1 0 Mar 17 ? 0:00 /usr/openv/netbackup/bin/bpdbm
root 11493 1 0 Mar 17 ? 0:09 /usr/openv/netbackup/bin/nbjm
root 11513 11512 0 Mar 17 ? 0:02 /usr/openv/netbackup/bin/nbproxy dblib nbpem
root 11487 1 0 Mar 17 ? 0:01 /usr/openv/netbackup/bin/bpcompat d
root 11511 11510 0 Mar 17 ? 0:00 /usr/openv/netbackup/bin/nbproxy dblib nbpem_email
root 11512 11498 0 Mar 17 ? 0:00 sh -c "/usr/openv/netbackup/bin/n bproxy" dblib nbpem
root 11504 11493 0 Mar 17 ? 0:00 sh -c "/usr/openv/netbackup/bin/n bproxy" dblib nbjm
root 11537 1 0 Mar 17 ? 0:00 /usr/openv/netbackup/bin/bmrd
root 11463 1 0 Mar 17 ? 0:40 /usr/openv/netbackup/bin/nbemm
root 11515 1 0 Mar 17 ? 0:09 /usr/openv/netbackup/bin/nbsl
root 11547 1 0 Mar 17 ? 0:01 /usr/openv/netbackup/bin/nbsvcmon
root 21784 1 0 17:50:01 ? 0:00 /usr/openv/netbackup/bin/bpjava-s usvc root -1 -1 C /usr/openv/java/auth.conf 1
root 11460 1 0 Mar 17 ? 0:00 /usr/openv/netbackup/bin/nbnos
root 11510 11498 0 Mar 17 ? 0:00 sh -c "/usr/openv/netbackup/bin/n bproxy" dblib nbpem_email
root 21834 21784 0 17:50:01 ? 0:00 /usr/openv/netbackup/bin/bpjava-s usvc root -1 -1 C /usr/openv/java/auth.conf 1
root 11505 11504 0 Mar 17 ? 0:00 /usr/openv/netbackup/bin/nbproxy dblib nbjm
root 22764 21784 0 17:50:14 ? 0:00 /usr/openv/netbackup/bin/bpjava-s usvc root -1 -1 C /usr/openv/java/auth.conf 1
root 11507 11506 0 Mar 17 ? 0:00 /usr/openv/netbackup/bin/nbproxy dblib nbjm_genjob
root 11498 1 0 Mar 17 ? 0:03 /usr/openv/netbackup/bin/nbpem
root 11466 1 0 Mar 17 ? 0:18 /usr/openv/netbackup/bin/nbrb
root 11506 11493 0 Mar 17 ? 0:00 sh -c "/usr/openv/netbackup/bin/n bproxy" dblib nbjm_genjob
root 11481 1 0 Mar 17 ? 0:01 /usr/openv/netbackup/bin/bprd
root 11457 1 0 Mar 17 ? 5:29 /usr/openv/db//bin/NB_dbsrv @/usr /openv/var/global/server.conf @/usr/openv/var/
root 22394 21784 0 17:50:02 ? 0:00 /usr/openv/netbackup/bin/bpjava-s usvc root -1 -1 C /usr/openv/java/auth.conf 1
root 11491 11489 0 Mar 17 ? 0:00 /usr/openv/netbackup/bin/bpjobd


MM Processes
------------
root 11478 1 0 Mar 17 ? 0:10 vmd


Shared VERITAS Processes
------------------------
root 115 1 0 Dec 09 ? 2:23 /opt/VRTSpbx/bin/pbx_exchange

I can see the vmd and pbx_exchange daemeon running 

--------------------------------------------------------------------------

ltid -v
No Entries in the Drive Database
TLDCD: No robots are configured

Mar 20 18:13:54 devuarbak01 ntpdate[191]: [ID 398266 daemon.notice] waiting 300 seconds before trying again
Mar 20 18:16:27 devuarbak01 vmd[28286]: [ID 152614 daemon.error] terminating - another daemon already exists (89)
Mar 20 18:16:30 devuarbak01 tldcd[28290]: [ID 572907 daemon.notice] Skipping TLD(0), it's controlled by another host (devuarbak01)
Mar 20 18:16:30 devuarbak01 tldcd[28290]: [ID 632197 daemon.error] No robots are configured - Operation not supported
Mar 20 18:16:30 devuarbak01 tldcd[28290]: [ID 147959 daemon.error] Daemon has terminated abnormally

Thanks,

 

 

 

Highlighted

Re: Restarting Media server management failed

You can see what the issue is: 

No Entries in the Drive Database
TLDCD: No robots are configured

Skipping TLD(0), it's controlled by another host (devuarbak01)

Is there another robot that you are trying to add on this master server?
Or are you trying to reconfigure the robot on media server devuarbak01? 

Please check bpps -x output on devuarbak01. 

If all seems okay on media server, ensure that devuarbak01 is selected as Device Host in Inventory screen.

Highlighted

Re: Restarting Media server management failed

@Marianne 

I check the tpconfig -l which is no robot, but able to see the tape drive when run scan command.

I select the correct one (TLD0) on the inventory robot. I try to reconfigure the robot and tape drive to resume as nomral operation for testing backup. 

 

 

Highlighted

Re: Restarting Media server management failed

@Home_224 

It seems that the robot is physically connected to media server devuarbak01.
Can you check?
Or ask someone onsite to check and confirm? 

How many tape drives in the robot? 
Is it shared between media server and master server?
Or dedicated drive(s) for master and media server?

If the robot is attached to the media server, and configured in NBU as being attached to the media server, why are you trying to reconfigure the robot?

Highlighted

Re: Restarting Media server management failed

If the robot is attached to the media server, and configured in NBU as being attached to the media server, why are you trying to reconfigure the robot?

As I mention that I cannot see the robot by run command tpconfig -d , so I try to delete the robot on the console and reconfigure again. 

I can see two robots on the NBU console, and want to delete the device host imduarbak01 but not work 

delete robot.PNG

Highlighted

Re: Restarting Media server management failed

I use the device wizard to rescan the robot and 2 drives , but still get the problem when inventory robot cannot connect to obotic software daemon (42)Restart media manager daemon problem(AR).PNGinventory-issue.PNG

 

Highlighted

Re: Restarting Media server management failed

I thought this looked familiar .... same master server as 6 months ago where you were unable to delete devices.

https://vox.veritas.com/t5/NetBackup/Invalid-drive-index-when-delete-the-tape-drive/m-p/871473

I do not see a solution on your current, unsupported NBU version.

As per @mph999 back then:

Problem here is that you are looking at manual SQL commands, and this is not really something for a forum, + these usually go via Engineering as it they can be destructive.