cancel
Showing results for 
Search instead for 
Did you mean: 

NetBackup status code: 10 (Separate media server and client)

perez_cmz
Level 6

I can't seem to run a backup on this W2012 vm (server568.bank.com); continously fails with error 10.

We have 4 other vm's built the same time, with the same OS, configurations, etc. No issues. We are attempting a MS-Windows type backup.

Media and master servers are Netbackup 7.5.0.5 running on RHEL 6.7. Netbackup client is 7.6.0.1

Client has been uninstalled and reinstalled, with reboots in between.

Below are the job details from the latest failure. Any help is greatly appreciated.

 

04/28/2016 09:32:49 - Info nbjm (pid=12280) starting backup job (jobid=243538682) for client server568.bank.com, policy WIN_backup_policy, schedule EOW_5W
04/28/2016 09:32:49 - Info nbjm (pid=12280) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=243538682, request id:{B394ECC2-0D45-11E6-BA2F-2805B60C8037})
04/28/2016 09:32:49 - requesting resource NYK_DD01
04/28/2016 09:32:49 - requesting resource master01.bank.com.NBU_CLIENT.MAXJOBS.server568.bank.com
04/28/2016 09:32:49 - requesting resource master01.bank.com.NBU_POLICY.MAXJOBS.WIN_backup_policy
04/28/2016 09:32:50 - granted resource  master01.bank.com.NBU_CLIENT.MAXJOBS.server568.bank.com
04/28/2016 09:32:50 - granted resource  master01.bank.com.NBU_POLICY.MAXJOBS.WIN_backup_policy
04/28/2016 09:32:50 - granted resource  MediaID=@aaade;DiskVolume=LSU01;DiskPool=NYK_DD01_NETBPNY1P01;Path=LSU01;StorageServer=NYK_DD01-ost....
04/28/2016 09:32:50 - granted resource  NYK_DD01
04/28/2016 09:32:50 - estimated 0 kbytes needed
04/28/2016 09:32:50 - Info nbjm (pid=12280) started backup (backupid=server568.bank.com_1461850370) job for client server568.bank.com, policy WIN_backup_policy, schedule EOW_5W on storage unit NYK_DD01
04/28/2016 09:32:52 - started process bpbrm (pid=17255)
04/28/2016 09:33:08 - Info bpbrm (pid=17255) server568.bank.com is the host to backup data from
04/28/2016 09:33:08 - Info bpbrm (pid=17255) reading file list from client
04/28/2016 09:33:08 - connecting
04/28/2016 09:33:18 - Info bpbrm (pid=17255) starting bpbkar on client
04/28/2016 09:33:18 - Info bpbkar (pid=1820) Backup started
04/28/2016 09:33:18 - Info bpbrm (pid=17255) bptm pid: 17289
04/28/2016 09:33:18 - Info bpbkar (pid=1820) change time comparison:<disabled>
04/28/2016 09:33:18 - Info bpbkar (pid=1820) archive bit processing:<enabled>
04/28/2016 09:33:18 - Info bptm (pid=17289) start
04/28/2016 09:33:18 - connected; connect time: 0:00:00
04/28/2016 09:33:21 - Info bptm (pid=17289) using 262144 data buffer size
04/28/2016 09:33:21 - Info bptm (pid=17289) setting receive network buffer to 262144 bytes
04/28/2016 09:33:21 - Info bptm (pid=17289) using 32 data buffers
04/28/2016 09:33:21 - Info bpbkar (pid=1820) not using change journal data for <C:\>: not enabled
04/28/2016 09:33:21 - Info bpbkar (pid=1820) not using change journal data for <D:\>: not enabled
04/28/2016 09:33:21 - Info bpbkar (pid=1820) not using change journal data for <E:\>: not enabled
04/28/2016 09:33:23 - Info bptm (pid=17289) start backup
04/28/2016 09:33:25 - Info bptm (pid=17289) backup child process is pid 17293
04/28/2016 09:33:25 - begin writing
04/28/2016 09:33:59 - Error bptm (pid=17289) media manager terminated by parent process
04/28/2016 09:34:09 - Error bpbrm (pid=17255) could not send server status message
04/28/2016 09:34:14 - Info bpbkar (pid=1820) done. status: 10: allocation failed
04/28/2016 09:34:14 - end writing; write time: 0:00:49
allocation failed  (10)
 

1 ACCEPTED SOLUTION

Accepted Solutions

perez_cmz
Level 6

So here it. I initially had encryption enabled on the client properties in nbu, the policy and the client itself.

During my troubleshooting, I uninstalled the agent/client from the client/server and reinstalled it.

Apparently, this removes the "keyfile.dat" file which is created with the bpkeyutil command. I never recreated it.

Once I recreated the passphrase, the backup job began to write.

This article helped   https://www.veritas.com/support/en_US/article.000087860

 

View solution in original post

7 REPLIES 7

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Media and master servers are Netbackup 7.5.0.5 running on RHEL 6.7. Netbackup client is 7.6.0.1

Not supported.

Client cannot be higher minor release (point version) than master and/or media server.
(Version support can be found in Release Notes for NBU 7.5 and 7.6.)

You need to upgrade the NBU servers or download NBU 7.5.0.6 (which was a full release for W2012).

Nicolai
Moderator
Moderator
Partner    VIP   

Allocation failed is a sign of memory issues. How much free memory does server568.bank.com have ?

How big is the swap file ? 

official recommendation for status 10: 

https://www.veritas.com/support/en_US/article.TECH57161

perez_cmz
Level 6

Understood, but I have several other servers/clients with the same exact configuration which are backing up successfully.

perez_cmz
Level 6

server568.bank.com is using 200mb out of the 8gb of RAM. I'm not sure how big the swap file is.

I've seen the tech article. This server is used as a file server, with not much else running on it. I've also restarted the server several times.

 

Michael_G_Ander
Level 6
Certified

Be aware that windows seem to use the swap file for some things even if there is memory free, where file caching seems to be one when scanning file systems.

Is there any errors/warnings in the event logs around the time the backup fails ?

The standard questions: Have you checked: 1) What has changed. 2) The manual 3) If there are any tech notes or VOX posts regarding the issue

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Please do not ignore version compatibility.

I have personally seen 2 identical media servers where one of them failed with status 10. 
It was something other than version compatibility, but proof that 'others that are working' is a bonus.

Install supported version on client or else upgrade master and media.

If the issue persists after compatibility has been addressed, let us dig deeper by going into logs... 
Status 10 is not always a problem with the client. I have seen this status code when users have manually 'fiddled' with the client's images folder on the master...

perez_cmz
Level 6

So here it. I initially had encryption enabled on the client properties in nbu, the policy and the client itself.

During my troubleshooting, I uninstalled the agent/client from the client/server and reinstalled it.

Apparently, this removes the "keyfile.dat" file which is created with the bpkeyutil command. I never recreated it.

Once I recreated the passphrase, the backup job began to write.

This article helped   https://www.veritas.com/support/en_US/article.000087860