Only user backups failing with 52.

[Venkatesh_K]

Hi All,

Only the user backups are failing with status code 52. Scheduled incremental and full backups are running fine. The user backups are either  hung for more then 5hr stating mounting media, and it fails with 52, "timed out waiting for media manager to mount volume".  i have 6 drives in the envornmrnt out of wich 4 are used by backup. NB version 5.0MP6

waiting for quick response.

Thanks,

Venkat

[Venkatesh_K]

Hi All,

Above mentioned user backups are oracle backups which are repository backups.

[Patrick_Whelan_]

When you say all user backups, do you mean for a particular client, policy or all? Are you using a firewall? Do you have different [V]LANs? What type of systems (Windoze? Solaris? other?)

Message Edited by Patrick Whelan on 12-05-2007 12:03 PM

Message Edited by Patrick Whelan on 12-05-2007 12:04 PM

[Stumpr2]

Check the reverse name lookup.

[Venkatesh_K]

Hi,

User backups are failing for more then one client.

But for a single policy, all the clients are under same policy.

Systems are Windows machines.

firewalls enabled.

why are the user backups(all are repository backups) failing when incementals and Full backups for the same clietns are running fine.?

[Patrick_Whelan_]

Are other user backups using other policies working? Can you temporarily put a failing client into a working policy and see it that works? Is the policy type set to windows not Standard? If you log on to one of the failing clients can you telnet master_server bpcd from that client? Have you tried the bpclntcmd -pn from the failing client.

I have seen this problem when the master or media server is on a different vlan from the client. The master initiated backup works because it can talk to both the media server and the client, whereas the client initiated backup fails because the client cannot talk to the master or more likely the media server.

Good luck, keep us posted.

[Amit_Bhardwaj]

check that all jobs failed with 52 are giving mounting problem for the same media ID ? i believ it happens if you have a problem with the specific media , in this case it shows positioning then must be failed with mounting media problem ,  if you find this is happening with the same one or two media ID for all failed jobs giving 52 , try suspending those media with bpmedia -suspend -m <media ID> and reconfirm the suspended media with bpmedialist -summary | grep SUSPENDED , then try re-executing the backup again , it should work .