cancel
Showing results for 
Search instead for 
Did you mean: 

timed out waiting for media manager to mount volume

yngrblajay
Level 4

Backup job for the media server fails with the 52 error code, But the same media server successfully completes the backup for other clients.

It fails for self with either 52 or 40 error code.

1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

You need bptm log on the media server to troubleshoot status 52.
Also good to have VERBOSE entry in vm.conf on media server and robot control host (NBU needs to be restarted after entry has beed added).
With Verbose logging, Media Manager actions are logged to syslog (/var/adm/messages) - media server will log mount request, robot control host will log actual mount, etc.
Additional logging may be required if enough information cannot be retrieved from syslog.
See Verbose settings for logs in /usr/openv/volmgr/debug: in http://www.symantec.com/docs/TECH75805

What value is media mount timeout set to?

Status 40 is something different and needs to be looked at separately.

View solution in original post

5 REPLIES 5

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

You need bptm log on the media server to troubleshoot status 52.
Also good to have VERBOSE entry in vm.conf on media server and robot control host (NBU needs to be restarted after entry has beed added).
With Verbose logging, Media Manager actions are logged to syslog (/var/adm/messages) - media server will log mount request, robot control host will log actual mount, etc.
Additional logging may be required if enough information cannot be retrieved from syslog.
See Verbose settings for logs in /usr/openv/volmgr/debug: in http://www.symantec.com/docs/TECH75805

What value is media mount timeout set to?

Status 40 is something different and needs to be looked at separately.

Possible
Level 6
Accredited Certified

please help to show the job details...

show vmoprcmd -d and tpconfig -d outputs from media server.

might be the case tht they are different.

suggestion: please reconfigure the drives for that media server using dev config wizard.

thanks

 

huanglao2002
Level 6

Are you do some change about the clients or media server?

If ohter clients backup are ok,Pleae check the network connect.

1 check the hosts,the media server and the client have resolve for each other.

2 check the network connect

a) from the media server

bpclntcmd -h  "client name"

bptestbpcd -client 'client name"

b)from the client

bpclntcmd -h "media server"

bpclntcmd -pn

 

 

yngrblajay
Level 4

This was fixed by increasing the time out value and refreshed the netbackup services

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Seems my question on 6 July pointed you in the right direction?

What value is media mount timeout set to?

Please tell us what the value was and what you have changed it to.
I have always believed that this timeout should not be less than 20 minutes.