yngrblajay
12 years agoLevel 4
timed out waiting for media manager to mount volume
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.
- 12 years ago
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/TECH75805What value is media mount timeout set to?
Status 40 is something different and needs to be looked at separately.