cancel
Showing results for 
Search instead for 
Did you mean: 

Netbackup6.0MP3 Vault Catalog Fails with error 43

michael_kaishar
Level 3
Here's the failure:
12/1/2006 11:44:27 AM - requesting resource backup-03-hcart3-robot-tld-0
12/1/2006 11:44:27 AM - requesting resource backup-03.NBU_CLIENT.MAXJOBS.backup-03
12/1/2006 11:44:27 AM - requesting resource backup-03.NBU_POLICY.MAXJOBS.Vault-Catalog-6wk-Retention
12/1/2006 11:44:27 AM - granted resource backup-03.NBU_CLIENT.MAXJOBS.backup-03
12/1/2006 11:44:27 AM - granted resource backup-03.NBU_POLICY.MAXJOBS.Vault-Catalog-6wk-Retention
12/1/2006 11:44:27 AM - granted resource 1256L3
12/1/2006 11:44:27 AM - granted resource HP.ULTRIUM3-SCSI.000
12/1/2006 11:44:27 AM - granted resource backup-03-hcart3-robot-tld-0
12/1/2006 11:44:27 AM - started process bpbrm (7988)
12/1/2006 11:44:28 AM - connecting
12/1/2006 11:44:28 AM - connected; connect time: 00:00:00
12/1/2006 11:44:32 AM - mounted
12/1/2006 11:44:32 AM - positioning 1256L3 to file 2
12/1/2006 11:44:34 AM - begin writing
12/1/2006 11:44:34 AM - positioned 1256L3; position time: 00:00:02
12/1/2006 11:47:13 AM - Error bpbrm(pid=7988) db_FLISTsend failed: unexpected message received (43)
12/1/2006 11:47:42 AM - end writing; write time: 00:03:08
unexpected message received(43)

The Vault Duplication works fine but when it gets to running a catalog backup it bombs out.

Thanks
6 REPLIES 6

zippy
Level 6
check out this link

http://seer.support.veritas.com/docs/263235.htm

zippy
Level 6
It looks to me that your system could use a Veritas patch.

zippy
Level 6
http://seer.support.veritas.com/docs/285941.htm

michael_kaishar
Level 3
Hi

Thanks for your response.

This is a windows 2003 master server. And the vaulting used to work until I made some changes to the name of the policy. The problem is intermittent. Rebooting the server fixes the problem and I re-run the catalog vaulting. This is a weird issue. I keep getting status error 43 with more than just these backups. I get them with sql backups and regular windows backups. And again very intermittent.

Stumpr2
Level 6
What did the documentation that James gave you links to say? Have you followed any of their advise?

michael_kaishar
Level 3
I have followed the advice but none of them worked.

So I decided to make some changes to my backup policies.

I have also staggered my backups jobs. Instead of having 38 servers in one policy and having them kick off at the same time, I have split up the jobs into 5 different policies kicking off in 30 minutes increments. I have also split off the vaulting of the catalogs to daily, weekly, monthly and end of year.

I am in the process of working with the network group to make changes to our NICs. Our NICs are teamed and therefore we need to take a look at how our switches are configured. But all in all by splitting the jobs I was able to get successful backups.

Thanks for following up.