cancel
Showing results for 
Search instead for 
Did you mean: 

Netbackup 7.6 data restore problem

Tanveer_Ahmad
Level 4

from last couple of day I have problem restore data when ever I try to restore following error is appear

connecting
2/2/2015 11:56:12 AM - Info bpbrm(pid=2560) start tar32 on client        
2/2/2015 11:56:12 AM - mounted
2/2/2015 11:56:12 AM - Info bptm(pid=6848) A00024           
2/2/2015 11:56:12 AM - Info bptm(pid=6848) INF - Waiting for positioning of media id A00024 on server desnet-vmh07.descon.com for reading.
2/2/2015 11:56:12 AM - positioning A00024 to file 30
2/2/2015 11:56:15 AM - Info tar32(pid=0) done. status: 181: tar received an invalid argument    
2/2/2015 11:56:15 AM - Info bpbrm(pid=6312) child done, status 181        
2/2/2015 11:56:15 AM - Info bpbrm(pid=6312) sending message to media manager: STOP RESTORE desnet-srv02_1422756926    
2/2/2015 11:56:27 AM - positioned A00024; position time: 0:00:15
2/2/2015 11:57:07 AM - begin reading
2/2/2015 11:57:13 AM - Info bpbrm(pid=6312) media manager for backup id desnet-srv02_1422756926 exited with status 150: termination requested by administrator
2/2/2015 11:57:13 AM - restored image desnet-srv02_1422756926 - (tar received an invalid argument(181)); restore time 0:01:01
2/2/2015 11:57:13 AM - Warning bprd(pid=5920) Restore must be resumed prior to first image expiration on INFINITY     
2/2/2015 11:57:13 AM - end Restore; elapsed time: 0:03:26
Restore error(2850)

 

 

 

1 ACCEPTED SOLUTION

Accepted Solutions

revarooo
Level 6
Employee

Seems there is an issue with tar reading the data.

Can you enable the tar log on the client and restart the restore, when it errors, upload the tar file.

View solution in original post

5 REPLIES 5

revarooo
Level 6
Employee

Seems there is an issue with tar reading the data.

Can you enable the tar log on the client and restart the restore, when it errors, upload the tar file.

Nicolai
Moderator
Moderator
Partner    VIP   

Please state Netbackup version and the OS involved on master/media and client

Some general advice regarding status code 181

http://www.symantec.com/docs/TECH200064

http://www.symantec.com/docs/HOWTO104101

Also check client Netbackup version is not higher than master server version.

 

Marianne
Level 6
Partner    VIP    Accredited Certified

Tell us more about the restore job:

NBU version and OS on source client?

NBU version and OS on destination client?

Type of restore - filesystem or db?

Was source data encrypted? What kind of encryption?
If NBU encryption on client, have you added encryption keys on the destination client?

Tanveer_Ahmad
Level 4

I am using Netbackup 7.6.0.1 windows Server 2012 as a master server it is also media server as well. My client have Windows 2003 64bit. File which I try to restore is SQL database file. File is first backup on client machine by SQL maintenance plan then backup on Tape (LTO5). I have one standalone drive (LTO5) and one Tandberg Storageloader. Tape cartridge which I try to restore is written by using standalone dive. There is no data encryption on server and client.

 

Marianne
Level 6
Partner    VIP    Accredited Certified

Standalone tape drive is always a nightmare to manage....

Have you put a sticker on each tape with media id?
Are you 100% sure that the tape loaded for restore is indeed the correct media id?
Media id on sticker and internal label must be the same.

Ensure than bptm log folder exists on NBU server under ...netbackup\logs and that VERBOSE entry is in ...volmgr\vm.conf. 
Restart NBU Device Manager service after VERBOSE entry is added to vm.conf.

Device errors will be logged to bptm log and Event Viewer System and Application logs.

Try to run a verify on media id A00024.
Post the results.