Status 84 occurring when running a backup to the newly created encrypted AdvancedDisk pool.

Article:TECH189776  |  Created: 2012-05-25  |  Updated: 2013-10-25  |  Article URL http://www.symantec.com/docs/TECH189776
Article Type
Technical Solution


Environment

Issue



When writing data to an encrypted AdvancedDisk pool the job may fail with the following:

Info bptm (pid=17306) EXITING with status 84


Error



From the Job details the following will be seen:

05/23/2012 10:00:03 - Info bpbrm (pid=17274) droid01 is the host to backup data from
05/23/2012 10:00:03 - Info bpbrm (pid=17274) reading file list from client
05/23/2012 10:00:03 - Info bpbrm (pid=17274) starting bpbkar on client
05/23/2012 10:00:03 - Info bpbkar (pid=14001) Backup started
05/23/2012 10:00:03 - Info bpbrm (pid=17274) bptm pid: 17306
05/23/2012 10:00:04 - Info bptm (pid=17306) start
05/23/2012 10:00:04 - Info bptm (pid=17306) using 262144 data buffer size
05/23/2012 10:00:04 - Info bptm (pid=17306) using 30 data buffers
05/23/2012 10:00:04 - Info bptm (pid=17306) start backup
05/23/2012 10:00:05 - Critical bptm (pid=17306) image open failed: error 2060022: software error
05/23/2012 10:00:05 - Info bptm (pid=17306) EXITING with status 84 <----------
05/23/2012 10:00:05 - Info bpbkar (pid=14001) done. status: 84: media write error
05/23/2012 10:10:05 - Info nbjm (pid=14152) starting backup job (jobid=66) for client droid01, policy droid01, schedule Full
05/23/2012 10:10:05 - Info nbjm (pid=14152) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=66, request id:{60BE9DAE-A4E9-11E1-A5FD-5C674D4C6C36})
05/23/2012 10:10:05 - requesting resource advdisk-STU
05/23/2012 10:10:05 - requesting resource batken.symantec.com.NBU_CLIENT.MAXJOBS.droid01
05/23/2012 10:10:05 - requesting resource batken.symantec.com.NBU_POLICY.MAXJOBS.droid01
05/23/2012 10:10:05 - granted resource  batken.symantec.com.NBU_CLIENT.MAXJOBS.droid01
05/23/2012 10:10:05 - granted resource  batken.symantec.com.NBU_POLICY.MAXJOBS.droid01
05/23/2012 10:10:05 - granted resource  MediaID=@aaaah;DiskVolume=/advdisk;DiskPool=advdisk-DP;Path=/advdisk;StorageServer=batken.symantec.com;MediaServer=batken.symantec.com
05/23/2012 10:10:05 - granted resource  advdisk-STU
05/23/2012 10:10:05 - estimated 0 kbytes needed
05/23/2012 10:10:05 - Info nbjm (pid=14152) started backup (backupid=droid01_1337785805) job for client droid01, policy droid01, schedule Full on storage unit advdisk-STU
05/23/2012 10:10:05 - started process bpbrm (pid=18342)
05/23/2012 10:10:06 - connecting
05/23/2012 10:10:06 - connected; connect time: 0:00:00
05/23/2012 10:10:08 - end writing
media write error  (84)

From bptm log

10:00:05.029 [17306] <16> 66:bptm:17306:batken.symantec.com: encrypt: OST_CRYPT_V1_init_encryption: kmsGetKeyAndKad() failed - unable to retrieve a key
10:00:05.029 [17306] <2> 66:bptm:17306:batken.symantec.com: encrypt: OST_CRYPT_V1_init_encryption: leaving, retval = 2060022
10:00:05.029 [17306] <16> 66:bptm:17306:batken.symantec.com: encrypt: Failed to initialize context crypt_version(13107), kms_version(16)
10:00:05.029 [17306] <16> 66:bptm:17306:batken.symantec.com: gateway: Failed to create image, return code = 2060022
10:00:05.029 [17306] <32> bp_sts_open_image: sts_create_image failed: error 2060022
....
10:00:05.031 [17306] <16> 66:bptm:17306:batken.symantec.com: encrypt: Failed to get image prop by name, error code = 2060013
10:00:05.031 [17306] <16> 66:bptm:17306:batken.symantec.com: gateway: Failed to get image prop by name, error code = 2060013
 


Cause



During the configuration of the Key Management Service (KMS) the short name for the storage server was using instead of the fully qualified host name.


Solution



When setting up the Key Management Service (KMS) make sure to use the fully qualified name for the storage server name.  If the configuration of KMS was completed without doing so the following command can be ran again to create the key group.

This can occur even if the storage server was created using the short name for the host.

UNIX - command resides in /usr/openv/netbackup/bin/admincmd
Windows - command resides in <install path>\program files\veritas\netbackup\bin\admincmd

nbkmsutil -createkg -kgname batken.symantec.com:advdisk
nbkmsutil -createkey -keyname dp_key -kgname batken.symantec.com:advdisk -activate

Also for the AdvancedDisk_crypt to be configured in NetBackup 7.5 the storage server has to be created using the command line.  This is a known issue and if will be resolved in a future release of NetBackup.

For more information on the configuration of AdvancedDisk and the encryption option please see the NetBackup 7.5 AdvancedDisk Storage Solution Guide.

Symantec NetBackup 7.5 AdvancedDisk Storage Solutions Guide Article:
Article URL http://www.symantec.com/docs/DOC5149 
 





Article URL http://www.symantec.com/docs/TECH189776


Terms of use for this information are found in Legal Notices