MS-Windows policy restore error(2808)- Duplicate copy

[Being_human]

Hi

I am restoring a data from from duplicate copy (I amde it primary) . The data is bit older taken on 2011 . Phase1 and phase 2 import done. Did duplicate of data and made that as primary.

When I tried to restore the data from duplicate copy ( local disk) getting error MS-Windows policy restore error(2808).

So kindly suggest what needs to eb done

[Marianne]

We need details of the restore job.

Are you restoring to same or different client? To same or different location?

Please post all text in Job details and client bpcd and tar logs.
Please post logs as .txt files.

[Being_human]

w

HI,

I am trying to restore the data of a client that is decommisoned . So I am restoring the data in the master server.

The duplicate data is available in the master server disk storage .

TAR LOGS:

3:27:25.900 PM: [16708.17588] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: Active Directory Application Mode
3:27:29.925 PM: [16708.14716] <16> tar_tfi:rocessException:
An Exception of type [InvalidStateException] has occured at:
  Module: @(#) $Source: src/ncf/tfi/lib/Encryptor.cpp,v $ $Revision: 1.41 $ , Function: Encryptor::setDecryptionInfo[2](), Line: 768
  Module: @(#) $Source: src/ncf/tfi/lib/UnpackerTAR.cpp,v $ $Revision: 1.144 $ , Function: UnpackerTAR::startObject(), Line: 351
  Unable to find the decryption key in the file

3:27:29.925 PM: [16708.14716] <2> tar_base::V_vTarMsgW: FTL - tar had an unexpected error
3:27:29.925 PM: [16708.14716] <2> tar_base::backup_finish: TAR - restore:                     0 files
3:27:29.925 PM: [16708.14716] <2> tar_base::backup_finish: TAR - restore:          file data:          0 bytes
3:27:29.925 PM: [16708.14716] <2> tar_base::backup_finish: TAR - restore:         image data:       1536 bytes
3:27:29.925 PM: [16708.14716] <2> tar_base::backup_finish: TAR - restore:       elapsed time:          1 secs         1536 bps
3:27:29.925 PM: [16708.14716] <8> tar_restore:rocessStateEOT: WRN - processStateEOT before keepalive
3:27:29.925 PM: [16708.12648] <4> tar_base::keepaliveThread: INF - keepalive thread terminating (reason: WAIT_OBJECT_0)
3:27:29.925 PM: [16708.14716] <4> tar_base::stopKeepaliveThread: INF - keepalive thread has exited. (reason: WAIT_OBJECT_0)
3:27:29.925 PM: [16708.14716] <8> T_tar_rename::BMRApply: Cleaning up the BMR IDRInProgress and IDRSystemData config entries.
3:27:29.925 PM: [16708.14716] <2> tar_base::V_Close: closing...
3:27:29.925 PM: [16708.14716] <8> T_tar_rename::BMRApply: Cleaning up the BMR IDRInProgress and IDRSystemData config entries.
3:27:29.925 PM: [16708.17588] <2> ov_log::V_GlobalLog: INF - BEDS_Term(): enter - InitFlags:0x00000001
3:27:29.925 PM: [16708.14716] <8> T_tar_rename::BMRApply: Cleaning up the BMR IDRInProgress and IDRSystemData config entries.
3:27:29.925 PM: [16708.14716] <8> T_tar_rename::BMRApply: Cleaning up the BMR IDRInProgress and IDRSystemData config entries.
3:27:29.925 PM: [16708.14716] <4> OVStopCmd: INF - EXIT - status = 0
3:27:30.939 PM: [16708.14716] <4> OVShutdown: INF - Finished process
3:27:30.939 PM: [16708.14716] <4> WinMain: INF - Exiting C:\Program Files\Veritas\NetBackup\bin\tar32.exe
3:27:32.967 PM: [16708.14716] <4> ov_log:VClose: INF - Closing log file: C:\Program Files\Veritas\NetBackup\logs\TAR\011018.LOG

[Marianne]

Hi @Being_human

I am battling to understand the reference in the log to :

BMR IDRInProgress and IDRSystemData config entries.

BMR = Bare Metal Restore
IDR = Intelligent Disaster Recovery

IDR is very old and replaced by BMR in NBU 6.0.
Both of them meant for full system recovery.

You will agree that this type of backup cannot be restored to the master server?

Maybe I am still getting it wrong...
Can you please take screenshots of the entire browse and data selection for restore up to the last screen where you select 'start restore' ? 

**** EDIT ****

I have just noticed the following in the tar log:

Unable to find the decryption key in the file.

So, the original backup was encrypted?

Restore is not possible without the encryption key.