cancel
Showing results for 
Search instead for 
Did you mean: 

how to restore data from an netbackup kms encrypted tape

kamalbhuttoo
Level 4

hi,

Am trying to restore from a netabckup kms encrypted tape. I have already imported my key database from my main site to my remote site.

While listing the keys on the remote site, all the keys are being listed properly. Am getting an issue while importing the image from the tape:

Find logs below:

01/04/2016 19:58:54 - begin Import
01/04/2016 19:58:56 - Info bpbrm (pid=28377146) test1 is the host to restore to
01/04/2016 19:58:56 - Info bpbrm (pid=28377146) reading file list for client
01/04/2016 19:58:56 - Info bpbrm (pid=28377146) starting tar on client
01/04/2016 19:58:56 - Info tar (pid=23593086) Import started
01/04/2016 19:58:56 - Info bpbrm (pid=28377146) bptm pid: 8716426
01/04/2016 19:58:57 - Info bptm (pid=8716426) start
01/04/2016 19:58:57 - started process bptm (pid=8716426)
01/04/2016 19:58:57 - Info bptm (pid=8716426) reading backup image
01/04/2016 19:58:57 - Info bptm (pid=8716426) using 30 data buffers
01/04/2016 19:58:57 - Info bptm (pid=8716426) spawning a child process
01/04/2016 19:58:57 - Info bptm (pid=8716426) child pid: 18350222
01/04/2016 19:58:58 - requesting resource LTO402
01/04/2016 19:58:58 - Info bptm (pid=8716426) Waiting for mount of media id LTO402 (copy 1) on server nbusvr.
01/04/2016 19:58:58 - started process bptm (pid=8716426)
01/04/2016 19:58:58 - mounting LTO402
01/04/2016 19:58:58 - granted resource  LTO402
01/04/2016 19:58:58 - granted resource  VIOS.VTAPE.000
01/04/2016 19:58:59 - Info bptm (pid=8716426) INF - Waiting for mount of media id LTO402 on server nbusvr for reading.
01/04/2016 19:59:01 - mounted LTO402; mount time: 0:00:03
01/04/2016 19:59:01 - Info bptm (pid=8716426) LTO402
01/04/2016 19:59:02 - Info bptm (pid=8716426) INF - Waiting for positioning of media id LTO402 on server nbusvr for reading.
01/04/2016 19:59:02 - positioning LTO402 to file 1
01/04/2016 19:59:02 - positioned LTO402; position time: 0:00:00
01/04/2016 19:59:03 - begin reading
01/04/2016 19:59:03 - Error bpimport (pid=11796648) from host nbusvr, no data in archive
01/04/2016 19:59:03 - Error bpbrm (pid=28377146) from client nbusvr: no data in archive
01/04/2016 19:59:03 - Error bptm (pid=8716426) cannot read image from media id LTO402, drive index 0, The input or output media is write-protected.
01/04/2016 19:59:03 - Error bpimport (pid=11796648) Import of policy ENCR_FinAP, schedule full (f7029ap_1451311780) failed, tar had an unexpected error.
01/04/2016 19:59:03 - Info tar (pid=23593086) done. status: 6

01/04/2016 19:59:03 - Info bptm (pid=8716426) EXITING with status 85 <----------
01/04/2016 19:59:03 - Error bpimport (pid=11796648) Status = no images were successfully processed.
01/04/2016 19:59:04 - end Import; elapsed time 0:00:10
01/04/2016 19:59:04 - Info tar (pid=23593086) done. status: 85: media read error
no images were successfully processed  (191)

Is there any step for follow for the restore to be succesful

4 REPLIES 4

m_defender007
Level 3

Hi......

Best Information This website So You visit site and resolve your problems.

http://worldhistory.wiki/pages/Key_Management_for_NetBackup

 

Thanks

sdo
Moderator
Moderator
Partner    VIP    Certified

I think you're going to have to explain in detail the exact steps that you followed to import the KMS database.

PatS729
Level 5

I assume the KMS is configured correctly.

However, I do not see "SIZE DATA BUFFERS" used in import job. Can you check if you have this file in place

Windows: <install_path>\NetBackup\db\config\SIZE_DATA_BUFFERS
UNIX: /usr/openv/netbackup/db/config/SIZE_DATA_BUFFERS
 

Was the SIZE_DATA_BUFFERS file in place when the backup occurred? What was the value when backup occured ?

It is important to use same value for SIZE_DATA_BUFFERS for importing the tapes.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
I doubt that we will see an answer from the OP. Someone managed to dig up an unanswered post from Dec 2015. Weird that the timestamps in job details are later than the date of the post: 01/04/2016.