Unable to see images after 1st & 2nd phase import completed for Restores frm LTO3 tapes

[imashu]

Hi,

We have LTO5 tape drives in our environment and need to import data from few LTO3 media's.

We have successfully completed the 1st phase import and also imported the required images in 2nd phase import. But now i am unable to see images for the required dates in Backup Archive and Restore Window.

All imports were successfull but don't know why the images are not showing in BAR gui.

This is very critical please help!!

[Marianne]

Please show us the log from the phase 2 import.

This log will show us client name (correct spelling/case) and date of backup.

This information is important when browsing for backups.

Hopefully the log will also tell us backup type (Standard, MS-Windows, etc).

[mph999]

The most common cause of this is incorrect date range.

Just to eliminate this, try puting a larger date range in, do the images then appear.

Martin

[imashu]

Hello Marianne,

Thanks for your reply. Please find the 1st and 2nd phase import logs for 1 LTO3 media's for 1 policy.

We need to restore from five(5) LTO3 media's.

Phase 1::

Import phase 1 started Mon 15 Apr 2013 11:39:10 AM BST
11:39:10 INF - Create DB information for media id BLS112.
11:39:11 INF - Initiation of bptm process to phase 1 import media id BLS112 was successful.
11:39:11 INF - Waiting for mount of media id BLS112 on server BUK003BKUP001P for reading.
 
11:39:59 INF - Recreating image information for client bze1ub03, policy Bel_BCV_BO_R12_excludeUO05, and schedule Weekly_Full, done on 04/07/2013 02:41:50.
11:40:00 INF - Recreating copy 1, fragment 9 information for image.
 
11:40:51 INF - Found existing image information for client bze1ub03, policy Bel_BCV_BO_R12_excludeUO05, and schedule Weekly_Full, done on 04/07/2013 02:41:50.
11:40:51 INF - Recreating copy 1, fragment 10 information for image.
 
11:41:15 INF - Found existing image information for client bze1ub03, policy Bel_BCV_BO_R12_excludeUO05, and schedule Weekly_Full, done on 04/07/2013 02:41:50.
11:41:15 INF - Recreating copy 1, fragment 11 information for image.
 
11:41:49 INF - Found existing image information for client bze1ub03, policy Bel_BCV_BO_R12_excludeUO05, and schedule Weekly_Full, done on 04/07/2013 02:41:50.
11:41:49 INF - Recreating copy 1, fragment 12 information for image.
 
11:42:44 INF - Recreating image information for client bze1ub03, policy Bel_BCV_BO_R12_excludeUO05, and schedule Weekly_Full, done on 04/14/2013 01:08:52.
11:42:44 INF - Recreating copy 1, fragment 1 information for image.
 
11:43:25 INF - Found existing image information for client bze1ub03, policy Bel_BCV_BO_R12_excludeUO05, and schedule Weekly_Full, done on 04/14/2013 01:08:52.
11:43:25 INF - Recreating copy 1, fragment 2 information for image.
 
11:43:54 INF - Found existing image information for client bze1ub03, policy Bel_BCV_BO_R12_excludeUO05, and schedule Weekly_Full, done on 04/14/2013 01:08:52.
11:43:54 INF - Recreating copy 1, fragment 3 information for image.
 
11:45:01 INF - Found existing image information for client bze1ub03, policy Bel_BCV_BO_R12_excludeUO05, and schedule Weekly_Full, done on 04/14/2013 01:08:52.
11:45:01 INF - Recreating copy 1, fragment 4 information for image.
 
11:46:35 INF - Found existing image information for client bze1ub03, policy Bel_BCV_BO_R12_excludeUO05, and schedule Weekly_Full, done on 04/14/2013 01:08:52.
11:46:35 INF - Recreating copy 1, fragment 5 information for image.
 
11:48:11 INF - Found existing image information for client bze1ub03, policy Bel_BCV_BO_R12_excludeUO05, and schedule Weekly_Full, done on 04/14/2013 01:08:52.
11:48:11 INF - Recreating copy 1, fragment 6 information for image.
 
11:49:55 INF - Recreating image information for client bze1ub03, policy Bel_BCV_BO_R12_excludeUO05, and schedule Weekly_Full, done on 04/14/2013 02:35:53.
11:49:55 INF - Recreating copy 1, fragment 1 information for image.
 
11:50:19 INF - Found existing image information for client bze1ub03, policy Bel_BCV_BO_R12_excludeUO05, and schedule Weekly_Full, done on 04/14/2013 02:35:53.
11:50:19 INF - Recreating copy 1, fragment 2 information for image.
 
11:50:43 INF - Found existing image information for client bze1ub03, policy Bel_BCV_BO_R12_excludeUO05, and schedule Weekly_Full, done on 04/14/2013 02:35:53.
11:50:43 INF - Recreating copy 1, fragment 3 information for image.
 
11:51:21 INF - Found existing image information for client bze1ub03, policy Bel_BCV_BO_R12_excludeUO05, and schedule Weekly_Full, done on 04/14/2013 02:35:53.
11:51:21 INF - Recreating copy 1, fragment 4 information for image.
 
11:52:11 INF - Found existing image information for client bze1ub03, policy Bel_BCV_BO_R12_excludeUO05, and schedule Weekly_Full, done on 04/14/2013 02:35:53.
11:52:11 INF - Recreating copy 1, fragment 5 information for image.
 
11:52:49 INF - Found existing image information for client bze1ub03, policy Bel_BCV_BO_R12_excludeUO05, and schedule Weekly_Full, done on 04/14/2013 02:35:53.
11:52:49 INF - Recreating copy 1, fragment 6 information for image.
 
11:53:02 INF - Found existing image information for client bze1ub03, policy Bel_BCV_BO_R12_excludeUO05, and schedule Weekly_Full, done on 04/14/2013 02:35:53.
11:53:02 INF - Recreating copy 1, fragment 7 information for image.
 
11:53:27 INF - Found existing image information for client bze1ub03, policy Bel_BCV_BO_R12_excludeUO05, and schedule Weekly_Full, done on 04/14/2013 02:35:53.
11:53:27 INF - Recreating copy 1, fragment 8 information for image.
 
11:54:23 INF - Creation of database information for import of media id BLS112 complete.
 

Phase 2:

Import phase 2 started Mon 15 Apr 2013 12:38:58 PM BST
12:38:58 INF - Importing policy Bel_BCV_BO_R12_excludeUO05, schedule Weekly_Full (bze1ub03_1365903353), media id BLS112, created on 04/14/2013 02:35:53.
12:38:59 INF - If Media id BLS112 is not in a robotic library administrative interaction may be required to satisfy this mount request.
12:38:59 INF - Waiting for mount of media id BLS112 on server BUK003BKUP001P for reading.
12:39:48 INF - Waiting for positioning of media id BLS112 on server BUK003BKUP001P for reading.
12:41:04 INF - Beginning import on server BUK003BKUP001P of client bze1ub03.
14:25:42 INF - If Media id BOE078 is not in a robotic library administrative interaction may be required to satisfy this mount request.
14:26:39 INF - Waiting for mount of media id BOE078 on server BUK003BKUP001P for reading.
14:27:28 INF - Waiting for positioning of media id BOE078 on server BUK003BKUP001P for reading.
14:27:28 INF - Continuing import on server BUK003BKUP001P of client bze1ub03.
14:45:11 INF - Import of policy Bel_BCV_BO_R12_excludeUO05, schedule Weekly_Full (bze1ub03_1365903353) was successfully completed.
 
14:45:11 INF - Imported 1 of 1 images successfully.

 -------------------------------------------------------------------------------------------------------------------------------

The policy is standard and these are database backup's. Does this has something to do if the media is Write-Protected before being inserted into the library.

Please help as we need to resolve this asap please.

[imashu]

Hello Martin,

I tried putting a very large date range of 1 year still no luck.

[Marianne · Accepted solution]

The policy is standard and these are database backup's.

Sorry, I don't understand - database backup with policy type of Standard?

There is no problem with write-protected tapes - NBU can read from them.

When we browse for backups, we are only looking at NBU catalog entries on the master, not the tapes.

Please show us output of the following on the master server:

bpimagelist -client bze1ub03 -t 0 -d 04/01/2013 -U

[imashu]

Hi Marianne,

Basically we have Standard policy type for these backups in the original policy.

Please find the output from master;

This gives no entity found,

[Marianne]

Please do the following on the master server -

cd /usr/openv/netbackup/db/images/bze1ub03

ls -l

(There should be a directory called 1365000000, right?)

cd 1365000000

ls -l 

Please show us output of last 'ls -l' as well as output of:
bpimagelist -backupid bze1ub03_1365903353 -L 

[imashu]

Hello Marianne,

I am able to see the images now but now while running the restores we are getting the below error;

04/16/2013 18:04:31 - begin Restore
04/16/2013 18:09:33 - media needed: BLS476
04/16/2013 18:09:33 - restoring from image bze1ub03_1365912125
04/16/2013 18:09:33 - Info bprd (pid=9110) Restoring from copy 1 of image created Sun Apr 14 05:02:05 2013
04/16/2013 18:14:34 - Info bpbrm (pid=10495) connect failed STATUS (18) CONNECT_FAILED
04/16/2013 18:14:34 - Info bpbrm (pid=10495)  status: FAILED, (44) CONNECT_TIMEOUT; system: (115) Operation now in progress; FROM 0.0.0.0 TO 10.25.208.52 10.25.208.52 bpcd VIA pbx
04/16/2013 18:14:34 - Info bpbrm (pid=10495)  status: FAILED, (44) CONNECT_TIMEOUT; system: (115) Operation now in progress; FROM 0.0.0.0 TO 10.25.208.52 10.25.208.52 bpcd VIA vnetd
04/16/2013 18:14:34 - Info bpbrm (pid=10495)  status: FAILED, (44) CONNECT_TIMEOUT; system: (115) Operation now in progress; FROM 0.0.0.0 TO 10.25.208.52 10.25.208.52 bpcd
04/16/2013 18:14:34 - Error bpbrm (pid=10495) cannot connect to 10.25.208.52, Operation now in progress (115)
04/16/2013 18:14:34 - Info tar (pid=0) done. status: 58: can't connect to client
04/16/2013 18:14:34 - Error bpbrm (pid=10495) client restore EXIT STATUS 58: can't connect to client
04/16/2013 18:14:34 - restored from image bze1ub03_1365912125; restore time: 0:05:01
04/16/2013 18:14:34 - Warning bprd (pid=9110) Restore must be resumed prior to first image expiration on Sun 16 Jun 2013 12:50:46 PM BST
04/16/2013 18:14:34 - end Restore; elapsed time 0:10:03
Standard policy restore error  (2800)

Could you please suggest!!

[Marianne]

Please let us know what has chanced to enable browsing of imported images?

Was the last bpimagelist output the clue?
Different policy type perhaps? 

If so, it means we have solved your "Unable to see images" issue, right?

You will agree with us that the connection problem is now a different issue?

I have moved that question to a new discussion.

[imashu]

Hello Mariaane,

That seems to be a DNS issue as when i tried through IP, it worked :)