Unix client Restore fails
Updated: 16 Oct 2010 | 6 comments
Our environment is NetBackup 6.5.4 installed on Windows Standard Server 2003 SP2 32bit attached to an HP dual drive LTO1 tape library
Our Unix support team requested a policy to backup a number of folder paths on an existing Linux2.6.9-67.ELsmp client. A Full backup ends with:-
>>
Status: the requested operation was successfully completed(0) Current kilobytes written: 5948640 Current files written: 1333.
<<
However the detailed status for a subsequent Full Restore to an alternate folder on the Windows backup server itself looks like this:-
>>
09:04:39 13/04/2010: Restore Started
09:04:40 (53925.xxx) Restore job id 53925 will require 1 image.
09:04:40 (53925.xxx) Media id XXXXXX is needed for the restore.
09:04:40 (53925.xxx) Media id XXXXXX is needed for the restore.
09:04:43 (53925.001) Restoring from image created 13/04/2010 08:55:25
09:04:44 (53925.001) INF - If Media id XXXXXX is not in a robotic library administrative interaction may be required to satisfy this mount request.
09:04:46 (53925.001) INF - Waiting for mount of media id XXXXXX on server servername for reading.
09:04:46 (53925.001) INF - TAR STARTED
09:05:23 (53925.001) INF - Waiting for positioning of media id XXXXXX on server servername for reading.
09:06:09 (53925.001) INF - Beginning restore from server servername to client servername.
09:06:10 (53925.001) TAR - netapps:\folder1\folder2\.snapshot\epos_backup\gen_q1\bol_epos_wells_01\
09:06:10 (53925.001) MNR - The file was renamed to the following:
09:06:10 (53925.001) UTF - D:\unix_epos_restored\netapps\folder1\folder2\.snapshot\epos_backup\gen_q1\bol_epos_wells_01\
09:06:10 (53925.001) TAR - netapps:\folder1\folder2\.snapshot\epos_backup\gen_q1\bol_epos_wells_01\BRITGOLD\
09:06:10 (53925.001) MNR - The file was renamed to the following:
09:06:10 (53925.001) UTF - D:\unix_epos_restored\netapps\folder1\folder2\.snapshot\epos_backup\gen_q1\bol_epos_wells_01\BRITGOLD\
09:06:10 (53925.001) TAR - netapps:\folder1\folder2\.snapshot\epos_backup\gen_q1\bol_epos_wells_01\BRITGOLD\pns_register.db
09:06:10 (53925.001) MNR - The file was renamed to the following:
09:06:10 (53925.001) UTF - D:\unix_epos_restored\netapps\folder1\folder2\.snapshot\epos_backup\gen_q1\bol_epos_wells_01\BRITGOLD\pns_register.db
09:06:10 (53925.001) TAR - netapps:\folder1\folder2\.snapshot\epos_backup\gen_q1\bol_epos_wells_01\BRITGOLD\wells\
09:06:10 (53925.001) MNR - The file was renamed to the following:
09:06:10 (53925.001) UTF - D:\unix_epos_restored\netapps\folder1\folder2\.snapshot\epos_backup\gen_q1\bol_epos_wells_01\BRITGOLD\wells\
09:06:10 (53925.001) TAR - netapps:\folder1\folder2\.snapshot\epos_backup\gen_q1\bol_epos_wells_01\BRITGOLD\wells\ow.interp_list
09:06:10 (53925.001) MNR - The file was renamed to the following:
09:06:10 (53925.001) UTF - D:\unix_epos_restored\netapps\folder1\folder2\.snapshot\epos_backup\gen_q1\bol_epos_wells_01\BRITGOLD\wells\ow.interp_list
09:06:10 (53925.001) FTL - tar received an invalid archive
09:06:10 (53925.001) INF - TAR EXITING WITH STATUS = 13
09:06:10 (53925.001) INF - TAR RESTORED 5 OF 6 FILES SUCCESSFULLY
09:06:10 (53925.001) INF - TAR KEPT 0 EXISTING FILES
09:06:10 (53925.001) INF - TAR PARTIALLY RESTORED 0 FILES
09:06:11 (53925.001) Status of restore from image created 13/04/2010 08:55:25 = file read failed
09:04:44 (53925.001) INF - If Media id XXXXXX is not in a robotic library administrative interaction may be required to satisfy this mount request.
09:04:46 (53925.001) INF - Waiting for mount of media id XXXXXX on server servername for reading.
09:04:46 (53925.001) INF - TAR STARTED
09:05:23 (53925.001) INF - Waiting for positioning of media id XXXXXX on server servername for reading.
09:06:09 (53925.001) INF - Beginning restore from server servername to client servername.
09:06:10 (53925.001) TAR - netapps:\folder1\folder2\.snapshot\epos_backup\gen_q1\bol_epos_wells_01\
09:06:10 (53925.001) MNR - The file was renamed to the following:
09:06:10 (53925.001) UTF - D:\unix_epos_restored\netapps\folder1\folder2\.snapshot\epos_backup\gen_q1\bol_epos_wells_01\
09:06:10 (53925.001) TAR - netapps:\folder1\folder2\.snapshot\epos_backup\gen_q1\bol_epos_wells_01\BRITGOLD\
09:06:10 (53925.001) MNR - The file was renamed to the following:
09:06:10 (53925.001) UTF - D:\unix_epos_restored\netapps\folder1\folder2\.snapshot\epos_backup\gen_q1\bol_epos_wells_01\BRITGOLD\
09:06:10 (53925.001) TAR - netapps:\folder1\folder2\.snapshot\epos_backup\gen_q1\bol_epos_wells_01\BRITGOLD\pns_register.db
09:06:10 (53925.001) MNR - The file was renamed to the following:
09:06:10 (53925.001) UTF - D:\unix_epos_restored\netapps\folder1\folder2\.snapshot\epos_backup\gen_q1\bol_epos_wells_01\BRITGOLD\pns_register.db
09:06:10 (53925.001) TAR - netapps:\folder1\folder2\.snapshot\epos_backup\gen_q1\bol_epos_wells_01\BRITGOLD\wells\
09:06:10 (53925.001) MNR - The file was renamed to the following:
09:06:10 (53925.001) UTF - D:\unix_epos_restored\netapps\folder1\folder2\.snapshot\epos_backup\gen_q1\bol_epos_wells_01\BRITGOLD\wells\
09:06:10 (53925.001) TAR - netapps:\folder1\folder2\.snapshot\epos_backup\gen_q1\bol_epos_wells_01\BRITGOLD\wells\ow.interp_list
09:06:10 (53925.001) MNR - The file was renamed to the following:
09:06:10 (53925.001) UTF - D:\unix_epos_restored\netapps\folder1\folder2\.snapshot\epos_backup\gen_q1\bol_epos_wells_01\BRITGOLD\wells\ow.interp_list
09:06:10 (53925.001) FTL - tar received an invalid archive
09:06:10 (53925.001) INF - TAR EXITING WITH STATUS = 13
09:06:10 (53925.001) INF - TAR RESTORED 5 OF 6 FILES SUCCESSFULLY
09:06:10 (53925.001) INF - TAR KEPT 0 EXISTING FILES
09:06:10 (53925.001) INF - TAR PARTIALLY RESTORED 0 FILES
09:06:11 (53925.001) Status of restore from image created 13/04/2010 08:55:25 = file read failed
09:06:11 (53925.001) The following files/folders were not restored:
09:06:11 (53925.001) UTF - /folder1/folder2/folder3/.snapshot/epos_backup/gen_q1/bol_epos_wells_01/BRITGOLD/wells/uk16!26-b39z.well
09:06:11 (53925.001) UTF - /folder1/folder2/folder3/.snapshot/epos_backup/gen_q1/bol_epos_wells_01/BRITGOLD/wells/uk16!26-b40.well
09:06:11 (53925.001) UTF - /folder1/folder2/folder3/.snapshot/epos_backup/gen_q1/bol_epos_wells_01/BRITGOLD/wells/uk16!26-b40z.well
09:06:11 (53925.001) UTF - /folder1/folder2/folder3/.snapshot/epos_backup/gen_q1/bol_epos_wells_01/BRITGOLD/wells/uk16!26-b41.well
09:06:11 (53925.001) UTF - /folder1/folder2/folder3/.snapshot/epos_backup/gen_q1/bol_epos_wells_01/BRITGOLD/wells/uk16!26-b41z.well
09:06:11 (53925.001) UTF - /folder1/folder2/folder3/.snapshot/epos_backup/gen_q1/bol_epos_wells_01/BRITGOLD/wells/uk16!26-b42.well
09:06:11 (53925.001) UTF - /folder1/folder2/folder3/.snapshot/epos_backup/gen_q1/bol_epos_wells_01/BRITGOLD/wells/uk16!26-b43.well
09:06:11 (53925.001) UTF - /folder1/folder2/folder3/.snapshot/epos_backup/gen_q1/bol_epos_wells_01/BRITGOLD/wells/uk16!26-b44.well
09:06:11 (53925.001) UTF - /folder1/folder2/folder3/.snapshot/epos_backup/gen_q1/bol_epos_wells_01/BRITGOLD/wells/uk16!27-1.well
09:06:11 (53925.001) UTF - /folder1/folder2/folder3/.snapshot/epos_backup/gen_q1/bol_epos_wells_01/BRITGOLD/wells/uk16!27-1a.well
09:06:11 (53925.001) Suspending the display of 1045 additional messages for this image.
09:06:11 (53925.001) UTF - /folder1/folder2/folder3/.snapshot/epos_backup/gen_q1/bol_epos_wells_01/BRITGOLD/wells/uk16!26-b39z.well
09:06:11 (53925.001) UTF - /folder1/folder2/folder3/.snapshot/epos_backup/gen_q1/bol_epos_wells_01/BRITGOLD/wells/uk16!26-b40.well
09:06:11 (53925.001) UTF - /folder1/folder2/folder3/.snapshot/epos_backup/gen_q1/bol_epos_wells_01/BRITGOLD/wells/uk16!26-b40z.well
09:06:11 (53925.001) UTF - /folder1/folder2/folder3/.snapshot/epos_backup/gen_q1/bol_epos_wells_01/BRITGOLD/wells/uk16!26-b41.well
09:06:11 (53925.001) UTF - /folder1/folder2/folder3/.snapshot/epos_backup/gen_q1/bol_epos_wells_01/BRITGOLD/wells/uk16!26-b41z.well
09:06:11 (53925.001) UTF - /folder1/folder2/folder3/.snapshot/epos_backup/gen_q1/bol_epos_wells_01/BRITGOLD/wells/uk16!26-b42.well
09:06:11 (53925.001) UTF - /folder1/folder2/folder3/.snapshot/epos_backup/gen_q1/bol_epos_wells_01/BRITGOLD/wells/uk16!26-b43.well
09:06:11 (53925.001) UTF - /folder1/folder2/folder3/.snapshot/epos_backup/gen_q1/bol_epos_wells_01/BRITGOLD/wells/uk16!26-b44.well
09:06:11 (53925.001) UTF - /folder1/folder2/folder3/.snapshot/epos_backup/gen_q1/bol_epos_wells_01/BRITGOLD/wells/uk16!27-1.well
09:06:11 (53925.001) UTF - /folder1/folder2/folder3/.snapshot/epos_backup/gen_q1/bol_epos_wells_01/BRITGOLD/wells/uk16!27-1a.well
09:06:11 (53925.001) Suspending the display of 1045 additional messages for this image.
09:06:11 (53925.xxx) INF - Status = the restore failed to recover the requested files.
<<
The value of the successfully restored files & folders is less than 20KB.
<<
The value of the successfully restored files & folders is less than 20KB.
We've been through the Full Backup/Restore process several time using different media & this is one Policy/Client of around 70 clients in a several policies which otherwise complete successfully.
Has anyone else experienced similar issues ?
Thansk for any input anyone can offer.
Discussion Filed Under:
Comments
Unix to Windows restore ? I
Unix to Windows restore ? I did not imagine that it was possible...
Don't loose more time, restore to a unix/linux server.
it's impossible
You can't recover unix files on Windows platform
There are restrictions even between Unix/Linux platforms as well
Use target platform for recovery
All depends on the files
Most UNIX files are just txt files. (windows to UNIX not so easy, UNIX to windows - some times).
I would check to see if you can restore the files to the UNIX server (say to a different dir) if that restore works then I would say the "format" of the files is not windows compatible.
I don't have to know how to spell....I work on Unix.
NetBackup 7.0.1 - AIX & Windows
Thanks for your replies
Thanks all for your replies.
You've confirmed my suspicions that I don't have enough of a clue about Unix and its mysterious ways.
I'll enlist the assistance of our Unix support team to test a restore to a Unix device.
It wont work..
which is a shame because it can be useful. I had a need to transfer some files under Linux (vmware server vmdk files) onto a windows server (so I could run a esx converter which is only on windows) and I couldnt. Reverted to scp. So youre right not to spend any more time trying!
You can go and check in your
You can go and check in your /usr/openv/netbackup/logs/user_ops/<user-nam>/logs
there will be file called jbp**** ..check time stamp u will be able to see exact error
Would you like to reply?
Login or Register to post your comment.