Error trying to restore with : tar received an invalid archive

[toshiaki_yamagu]

Hi,

I am trying to do a restore on netbackup 7.1 with tapes used on our old master server (6.5) and everytime I receive a message that tar received an invalid archive.

02:30:30 27/11/2012: Restore Started

02:30:55 (578.xxx) Restore job id 578 will require 1 image.
02:30:55 (578.xxx) Media id FDU434 is needed for the restore.
02:30:55 (578.xxx) Media id 292DL4 is needed for the restore.

02:31:31 (578.001) Restoring from image created 23/06/2012 18:10:33
02:31:36 (578.001) INF - If Media id 292DL4 is not in a robotic library administrative interaction may be required to satisfy this mount request.
02:31:40 (578.001) INF - Waiting for mount of media id 292DL4 on server CPS1MSBKP01 for reading.
02:32:29 (578.001) INF - Waiting for positioning of media id 292DL4 on server CPS1MSBKP01 for reading.
02:33:05 (578.001) INF - Beginning restore from server CPS1MSBKP01 to client CPS1MSFS01.
02:33:24 (578.001) (578.001) FTL - tar received an invalid archive
02:33:24 (578.001) (578.001) INF - TAR EXITING WITH STATUS = 13
02:33:24 (578.001) (578.001) INF - TAR RESTORED 0 OF 1 FILES SUCCESSFULLY
02:33:24 (578.001) (578.001) INF - TAR KEPT 0 EXISTING FILES
02:33:24 (578.001) (578.001) INF - TAR PARTIALLY RESTORED 0 FILES

02:33:24 (578.001) Status of restore from image created 23/06/2012 18:10:33 = file read failed

02:33:31 (578.xxx) INF - Status = the restore failed to recover the requested files.
 

All backups done on the new master server 7.1 works fine, restore works fine. But we dont have the version 6.5 anymore, and there are some backups made in the beggining of this year that need to be restored... I have imported the tapes to the new library, even with the successfull import, still can´t get the restore to work.

Master server is running on Windows 2008 and the client is also Windows 2008. Master and Media server are the same server.

Can someone help me with this issue? Is there a compatibility problem with the version 6.5 with the 7.1?

Thank you in advance!

[revarooo]

Let's see the tar log from the client that you are trying to restore to, let's see if there are any errors.

[toshiaki_yamagu]

to enable the log I need to create a directory or so? I don´t remember now...

[toshiaki_yamagu]

I also have this log from the activity monitor

27/11/2012 02:30:39 - begin Restore
27/11/2012 02:30:55 - 1 images required
27/11/2012 02:30:55 - media FDU434 required
27/11/2012 02:30:55 - media 292DL4 required
27/11/2012 02:31:29 - restoring image BRSAODATA02_1340485833
27/11/2012 02:31:36 - requesting resource 292DL4
27/11/2012 02:31:36 - granted resource 292DL4
27/11/2012 02:31:36 - granted resource IBM.ULT3580-TD4.001
27/11/2012 02:31:37 - connecting
27/11/2012 02:31:38 - started process bptm (5192)
27/11/2012 02:31:38 - mounting 292DL4
27/11/2012 02:31:45 - connected; connect time: 00:00:08
27/11/2012 02:32:27 - mounted; mount time: 00:00:49
27/11/2012 02:32:29 - positioning 292DL4 to file 71
27/11/2012 02:33:03 - positioned 292DL4; position time: 00:00:34
27/11/2012 02:33:03 - begin reading
27/11/2012 02:33:22 - Critical bpbrm(pid=5236) from client CPS1MSFS01: FTL - tar received an invalid archive   
27/11/2012 02:33:22 - end reading; read time: 00:00:19
27/11/2012 02:33:24 - restored image BRSAODATA02_1340485833 - (file read failed(13)); restore time 00:01:55
27/11/2012 02:33:27 - Warning bprd(pid=6000) Restore must be resumed prior to first image expiration on INFINITY      
27/11/2012 02:33:29 - end Restore; elapsed time: 00:02:50
the restore failed to recover the requested files(5)

[revarooo]

Login to the client then cd to where netbackup is installed, usually c:\program files\veritas\netbackup\

cd logs

mkdir tar

increase logging of that client vis Java Console -> Host Properties -> Client -> Logging

reproduce the issue and post the tar log generated on the client

[Marianne]

We often see this error when trying to restore encrypted backups to a new environment.

Can you confirm if encryption was used in 6.5 environment?
Also what type of data you are restoring and what restore options were selected? 
Especially w.r.t. Restore without access control attributes...
If you are trying to restore WITH access control attributes, are you restoring within the same or different domain?
Domain user attributes will only have permissions in same domain.
tar log should give us some idea.

Please ensure that all of these log folders exist:

Master: bprd  (restart NBU after creating this folder)

Media server: bptm and bpbrm

Client: tar and bpcd

As a start, please upload tar log as File attachment . If we need more logs, we will ask for it.

[toshiaki_yamagu]

I got the log... and I believe i know what is going on now.  The previous version of netbackup was probably ina unix/linux environment... its trying to rename the file from a unix sintax. I dont know what environment was.. we got this client to manage and the previous one was on another country.

[Marianne]

The initial Unix paths are normal (NBU for Windows was ported from Unix).

Here we see that the path is corrected to Windows path: 

10:01:40.861 AM: [6592.4596] <4> tar_process_restore_args: INF - changed name of file: /usr/openv/netbackup/.rename.6108 to file: C:\Program Files\Veritas\NetBackup\logs\ALTPATH\.rename.6108

This is your problem:

10:03:09.826 AM: [6592.4596] <32> Encryptor::setDecryptionInfo[2](): FTL - InvalidStateException: Errors in initialisation stage.

Seems original backup was encrypted.

No way to restore without original encryption key.

[toshiaki_yamagu]

Thank you Marianne.

For this encryption key, can I get this from the people who did this original backup or it can only be done on their side, using their master server?

[toshiaki_yamagu]

In time.. we have the encrytion key already. we have use this kb

http://www.symantec.com/business/support/index?page=content&id=TECH56707

the encryption key is here

C:\Program Files\VERITAS\NetBackup\var\keyfile.dat on our master server

[Marianne · Accepted solution]

The keyfile must be obtained from the original client and copied/restored to the destination client.

See http://www.symantec.com/docs/TECH56759