Video Screencast Help

Restore failing with system error occurred (130)

Created: 10 May 2013 | 5 comments
SaurabhHeda's picture

Hello,

Restore failing with system error occurred (130). Restore is failing only for 1 file.

Restore is failing for file file_path = /data004/orasvc01/ILMESNP/perfstat02.dbf 

But the restore for other files within the same path is working fine. We are facing the error code only for this particular file i.e perfstat02.dbf

Policy is standard. We are doing the cold database backup using standard policy.

in bprd logs found the below error code:

<16> add_to_restore_list: backup date of 1366773439 for /data004/orasvc01/ILMESNP/perfstat02.dbf  not found in image list

Also tried to perform the Media verify which compeleted successfully. Even tried to take the backup on different media but the restore fails with the same error code.

Master server version: 7.5 .0.4

Detailed job status:

04/30/2013 15:19:35 - begin Restore 
04/30/2013 15:19:37 - Warning bprd (pid=385208) Restore must be resumed prior to first image expiration on Fri May 10 08:55:18 IST 2013 
04/30/2013 15:19:40 - Warning bprd (pid=385208) Restore must be resumed prior to first image expiration on Fri May 10 08:55:18 IST 2013 
04/30/2013 15:19:40 - end Restore; elapsed time 0:00:05 
system error occurred (130) 
 
Attaching bprd logs with next post

Found the below technote:

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

But i dont think it is relevant

Please Help.

Operating Systems:

Comments 5 CommentsJump to latest comment

SaurabhHeda's picture

bprd logs

AttachmentSize
bprd.txt 44.09 KB

If this post answered your'e qustion -  Please mark as a solution.

Nicolai's picture

If you know the image id you can list what files are recorded in the backup:

See for example:

http://www.mass.dk/netbackup/quick-hints/64-bpflist.html

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.

Mark_Solutions's picture

I am guessing that it has a problem when cataloging this client - but dont know why

Does the same happen when you restore it to the original client? (but in an alternate location to be on the safe side!)

Probably need to see the image file itself - there was a similar issue with NDMP imports a while back but that is very different to this

Anything in the clients messages logs at the time of the backup or in the veritas servers messages at the time of the restore? - 130 is a system error which could indicate that more details do get logged somewhere

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

SaurabhHeda's picture
Hi Mark,
 
Did got any system errors during restore or backup. But the below lines in bpdbm are repeated for quite a time and then the process aborts.
 
Findings from bpdbm logs:
 
14:46:03.362 [225652] <2> getIDIRSTRUCT: ?
14:46:03.362 [225652] <2> lock_file_by_path: db_Imglock(9001000a0005850) READ in /usr/openv/netbackup/db/images/LGDAMESD01N/1366000000/LGDAMESD01N_FULL_1366686950_FULL.lck
14:46:03.362 [225652] <2> lock_file_by_path: Acquired db_Imglock(9001000a0005850) in /usr/openv/netbackup/db/images/LGDAMESD01N/1366000000/LGDAMESD01N_FULL_1366686950_FULL.lck
14:46:03.464 [225652] <2> vfm_extract_frag_info_VxFIv5: input_frag_id : []
14:46:03.464 [225652] <2> vfm_extract_frag_info_VxFIv5: Parse error; No fi_fim_name found
14:46:03.464 [225652] <2> strcmp_match_file_list: Entering
14:46:03.464 [225652] <2> strcmp_match_file_list: pattern:/data004/orasvc01/ILMESNP/perfstat02.dbf   level:1002  path_independent:0 fl_option:0x5800082
14:46:03.471 [225652] <2> ImageListFiles::executeQuery: selected 0 total_selected 15
14:46:03.471 [225652] <2> db_ImgUnlock: db_ImgUnlock(9001000a0005850) unlocked
14:46:03.471 [225652] <2> DBEnumerator::move_next: Got image LGDAMESD01N_1366686705
14:46:03.471 [225652] <2> CompositeCriterion::db_matches: got result of 2 after 2 out of 2 calls
14:46:03.471 [225652] <2> CompositeCriterion::db_matches: got result of 2 after 9 out of 9 calls
14:46:03.471 [225652] <2> CompositeCriterion::db_matches: got result of 2 after 2 out of 2 calls
14:46:03.471 [225652] <2> CompositeCriterion::db_matches: got result of 2 after 4 out of 4 calls
14:46:03.471 [225652] <2> DBEnumerator::move_next: New state: LOOPING_STATE
14:46:03.471 [225652] <2> DBFileMergeEnumerator::move_next: New state: LOOPING_ONLY_DB_STATE
14:46:03.471 [225652] <2> image_path_r: ?
14:46:03.471 [225652] <2> image_dir_name: ?

If this post answered your'e qustion -  Please mark as a solution.

Mark_Solutions's picture

I think you need to take a look at the image file to see if anything is obvious within it:

/usr/openv/netbackup/db/images/LGDAMESD01N/1366000000/LGDAMESD01N_FULL_1366686950_FULL

What O/S are you using and are the backups to tape, disk , de-dupe etc?

Juts wondering if something case sensitive has cropped up - though i doubt it as a verify works

Did you try it back to the original client?

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.