MSEO restoration -LTO 4 tapes getting error in LTO5 drives

[Nicenavin]

Hi Friends,

Currently we are taking the backup with MSEO option with following details:

OS: Sun Solaris 5

MSEO : 6.1.3

NBU: 7.1.0.4  

Role: (Master and media server)

Tape library: SL500

Drives: LTO-4 & LTO -3

We have installed MSEO in another Solaris Media server, it has LTO 5drives and enabled  them as MSEO drives.

 And Started the restore  with LTO -3 and 4 Tapes.

1. We are able to restore data from LTO -3 tapes. ( Both MSEO and NON-MSEO data)
2. Also able to restore the NON MSEO data from LTO-4 tape
3. However, not able to restore MSEO data from LTO-4 tapes. The following error reported;

“tpperror: Robotic operation failed”

After confirmed that the drives are working fine. Again tried the restore , still it’s failing with above error.

Friend,

Do you have any idea to resolve this issue?

Awaiting your suggestions and thoughts………

NiceN…

[Mark_Solutions]

Could we see a bptm log for when this error ocurrs - also the full restore job log

You also need to check the barcode labels on the tapes and how the library is configured

Many will not allow the wrong tape to go into a drive - so a tape with L5 on the end will not be mounted into an LTO4 drive

You are backing up on LTO5 drives so you need to know which bar code labels are in use and what the library classes its drives as

Quite often it is the library itself that causes this - the event and reason should be logged on the library web gui

[Nicenavin]

Hi Mark,

below is the log:

12/16/2013 08:40:29 - begin Restore
12/16/2013 08:40:32 - media needed: CO5976
12/16/2013 08:40:32 - restoring from image orlsxbk01_1382068814
12/16/2013 08:40:32 - Info bpbrm (pid=11557) dosxbkocnp01 is the host to restore to
12/16/2013 08:40:33 - Info bpbrm (pid=11557) reading file list from client
12/16/2013 08:40:34 - Info bpbrm (pid=11557) connecting to bprd to get file list
12/16/2013 08:40:34 - connecting
12/16/2013 08:40:34 - Info bpbrm (pid=11557) starting bptm
12/16/2013 08:40:34 - Info tar (pid=11561) Restore started
12/16/2013 08:40:34 - connected; connect time: 0:00:00
12/16/2013 08:40:34 - Info bpbrm (pid=11557) bptm pid: 11562
12/16/2013 08:40:35 - Info bptm (pid=11562) start
12/16/2013 08:40:35 - started process bptm (pid=11562)
12/16/2013 08:40:36 - Info bpdm (pid=11562) reading backup image
12/16/2013 08:40:36 - Info bptm (pid=11562) using 30 data buffers
12/16/2013 08:40:38 - Info bptm (pid=11562) Waiting for mount of media id CO5976 (copy 1) on server dosxbkocnp01.
12/16/2013 08:40:38 - started process bptm (pid=11562)
12/16/2013 08:40:38 - mounting CO5976
12/16/2013 08:40:38 - requesting resource CO5976
12/16/2013 08:40:39 - Info bptm (pid=11562) INF - Waiting for mount of media id CO5976 on server dosxbkocnp01 for reading.
12/16/2013 08:40:39 - granted resource  CO5976
12/16/2013 08:40:39 - granted resource  HP.ULTRIUM5-SCSI.007
12/16/2013 08:41:26 - mounted CO5976; mount time: 0:00:48
12/16/2013 08:41:26 - Info bptm (pid=11562) CO5976
12/16/2013 08:41:27 - Info bptm (pid=11562) INF - Waiting for positioning of media id CO5976 on server dosxbkocnp01 for reading.
12/16/2013 08:41:27 - positioning CO5976 to file 29
12/16/2013 08:41:56 - positioned CO5976; position time: 0:00:29
12/16/2013 08:41:57 - begin reading
12/16/2013 08:46:57 - Error bpbrm (pid=11557) socket read failed: errno = 62 - Timer expired
12/16/2013 08:46:57 - Error bptm (pid=11562) cannot read image from media id CO5976, drive index 5, Device busy
12/16/2013 08:46:59 - Error bptm (pid=11562) media manager terminated by parent process
12/16/2013 08:47:30 - Info tar (pid=11561) done. status: 13: file read failed
12/16/2013 08:47:30 - Error bpbrm (pid=11557) client restore EXIT STATUS 13: file read failed
12/16/2013 08:47:31 - end Restore; elapsed time 0:07:02
the requested operation was successfully completed  (0)

[mph999]

That doesn't look like a robot error - the tape made it into the drive as it was mounted and positioned. Can you get the MSEO log for this same date as the above bptm log - /var/log/meso.log I think .... If not, shouldn't be too hard to search for it as it's called mseo.log. Could you do this test - create a new volume pool - test Move a LTO4 tape into the test pool Create a policy that backs up to the volume pool test Run a none mseo backup - confirm the restore works (save the bptm log) Expire the tape Run a mseo backup to the same tape - just copy a mseo policy if required and change the volume pool See if the restore works - save the bptm and mseo log To move the tape into a voume pool, right click the tape and select change - the pool can be selected in the popup window.

[Nicenavin]

Hi mph999,

I will try as you advised. However how can i restore the previous mseo data from the tape?

[Marianne]

Similar 'Device Busy' errors with MSEO in these TN's:

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

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

The troubleshooting and steps to solve will hopefully fix your issue as well.

[Nicenavin]

Thanks Marianne, i will try the same....

[Nicenavin]

Hi All,

Thanks for you suggestions.

We have removed the mseo and ran the backup as NON MSEO and the started the restore.

Restore job has 11 streams and 5 streams completed successfully without any error.

I will update, once all the streams get completed.

[Nicenavin · Accepted solution]

After removed the MSEO ( 6.1.3), the resore jobs were completed successfully.