NetBackup status code: 10 (Separate media server and client)
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.bank.com;MediaServer=media01.bank.com
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)
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
