Restore failing with error 830 (drives unavailable or down) & 5

[Shrikant68]

Environment: - Solaris10 with Netbackup 6.5.5

Backed up Environment: - a 3 tier architecture, 1 Master Server with 2 media servers connected to 2 tape libraries.

Restoring in to single Sun server (same version solaris & netbackup) acting as master/media server connected to a IBM Standalone LTO3 tape drive.

Catalog restored successfully;
Deleted all devices before trying to restore data (hosts/storage units/robots/drives etc)
Configured storage unit/drive, updated new volume and tested backup successfully;

However while trying to restore data from the tapes those were backed up in the 3 tier env. failing with with following error

Error: bptm NBJM returned an extended error status; drives unavailable or down (830)
           the restore failed to recover the requested files (5)

Error nbjm (pid=xxxx) NBU status:830, EMM status; No drives are available

Any idea how to go about it?

Thanks in advance for your suggestions.
 

[Marianne]

What is the density (drive type) of the tape drive?
What is the density of the media?

If there is a mismatch, NetBackup will not mount the tape, even if the hardware is compatible.
The media type and drive type must be the same. If the media is hcart2, ensure the drive type is hcart2 as well.

[Shrikant68]

Is that a bug of Netbackup 6.5.5?   We use to do this exercise successfully with Netbackup 5.1 with Solaris-9.

This is for DR purposes, so the hardware resources available are limited and I need to verify the data restoration successfully.

The Stnadalone drive is a IBM.ULT3580-TD3.000 hcart3  type whereas the tape is LTO2 type, which is working fine when I try to take backup;
While updating the media (manually) I tried adding the volume as both hcart2 & hcart3 type. There is no difference in the error messages;

if you look in to the whole error while restoration (as below)..... drives unavailable or down, then how come Netbackup is taking backup?


05/06/2010 17:17:23 - begin Restore
05/06/2010 17:17:35 - number of images required: 1
05/06/2010 17:17:35 - media needed: JFM386
05/06/2010 17:17:41 - restoring from image xxxxxxx_1271593296
05/06/2010 17:17:43 - connecting
05/06/2010 17:17:44 - connected; connect time: 0:00:00
05/06/2010 17:17:46 - Error bptm (pid=7801) NBJM returned an extended error status: drive(s) unavailable or down (830)
05/06/2010 17:17:44 - requesting resource JFM386
05/06/2010 17:17:45 - Error nbjm (pid=7552) NBU status: 830, EMM status: No drives are available
05/06/2010 17:17:45 - Error nbjm (pid=7552) NBU status: 830, EMM status: No drives are available
05/06/2010 17:18:02 - restored from image xxxxxx_1271593296; restore time: 0:00:21
05/06/2010 17:18:02 - end Restore; elapsed time 0:00:39
the restore failed to recover the requested files (5)

Is there any solutions under this kind of circumstances?

Thanks once again.

[Marianne]

Netbackup has worked like this for as long as I've known it (since 3.1.1).
Densities must match in mediaDB, volDB as well as devices. The logic is still the same post 6.x.
Media density that was written at the time of the backup would have been restored with the catalog recovery. If that density was hcart2, you need to change the drive density to hcart2. Drive density must match media density.
Please post output of the following:

bpmedialist -l -m JFM386
vmquery -m JFM386
nbemmcmd -listmedia -m JFM386
tpconfig -l

[Nicolai]

I my previous DR test I found this article very userfull. I know the catalog restore succeded, but I think you need to do a partial restore, this way you avoid overwriting the device configuration of the DR system.

How to create a blank NetBackup NBDB database for the recovery of the NetBackup NBDB database from a...

Have you added FORCE_RESTORE_MEIDA_SERVER  to bp.conf as you are missing the orginal media servers, the document below mention this ?

Disaster recovery using partial catalog recovery in NetBackup  

Catalog recovery procedure: an example of disaster recovery
 

[Shrikant68]

bpmedialist -l -m JFM386
JFM386 *NULL* 1 14 1271579059 1271605311 1279640511 0 377064288 25 25 5 12 0 8 1024 0 5222289 0 0 0 0 0 0 0


nbemmcmd -listmedia -mediaid JFM386
NBEMMCMD, Version:6.5.5
====================================================================
Media GUID:                     94fb6480-f9ac-11dd-8000-ab2a3319964a
Media ID:                       JFM386
Partner:                        -
Media Type:                     HCART2
Volume Group:                   000_00001_TLD
Application:                    Netbackup
Media Flags:                    1
Description:                    ---
Barcode:                        JFM386L2
Partner Barcode:                --------
Last Write Host:                XXXXXXXXXX
Created:                        03/19/2008 11:19
Time Assigned:                  04/18/2010 01:24
First Mount:                    03/22/2008 13:38
Last Mount:                     04/18/2010 08:42
Volume Expiration:              -
Data Expiration:                07/20/2010 08:41
Last Written:                   04/18/2010 08:41
Last Read:                      -
Robot Type:                     NONE
Robot Control Host:             -
Robot Number:                   -
Slot:                           -
Side/Face:                      -
Cleanings Remaining:            -
Number of Mounts:               32
Maximum Mounts Allowed:         0
Media Status:                   FULL
Kilobytes:                      377064288
Images:                         25
Valid Images:                   25
Retention Period:               5
Number of Restores:             0
Optical Header Size Bytes:      1024
Optical Sector Size Bytes:      0
Optical Partition Size Bytes:   0
Last Header Offset:             5222289
Adamm Guid:                     00000000-0000-0000-0000-000000000000
Rsm Guid:                       00000000-0000-0000-0000-000000000000
Origin Host:                    XXXXXXXXXXXXX
Master Host:                    XXXXXXXXXXXXXX
Server Group:                   NO_SHARING_GROUP
Upgrade Conflicts Flag:
Pool Number:                    12
Volume Pool:                    Unix
Previous Pool Name:             Scratch
Vault Flags:                    -
Vault Container:                -
Vault Name:                     -
Vault Slot:                     -
Session ID:                     284
Date Vaulted:                   -
Return Date:                    -
====================================================================
Command completed successfully.

 
vmquery -m JFM386
================================================================================
media ID:              JFM386
media type:            1/2" cartridge tape 2 (14)
barcode:               JFM386L2
media description:     ---
volume pool:           Unix (12)
robot type:            NONE - Not Robotic (0)
volume group:          000_00001_TLD
vault name:            ---
vault sent date:       ---
vault return date:     ---
vault slot:            ---
vault session id:      284
vault container id:    -
created:               Wed Mar 19 11:19:49 2008
assigned:              Sun Apr 18 01:24:19 2010
last mounted:          Sun Apr 18 08:42:47 2010
first mount:           Sat Mar 22 13:38:39 2008
expiration date:       ---
number of mounts:      32
max mounts allowed:    ---
status:                0x0
================================================================================

 
tpconfig -l

Device Robot Drive       Robot                    Drive                Device         Second
Type     Num Index  Type DrNum Status  Comment    Name                 Path           Device Path
drive      -    0 hcart3    -      UP  -          IBM.ULT3580-TD3.000  /dev/rmt/0cbn
 
 

[Shrikant68]

Thanks!

I could able to restore the complete catalog successfully after adding FORCE_RESTORE_MEIDA_SERVER  in to bp.conf  (though there was error 5 initially).
Usually if the drive is not availble due to some reason (or drive path mismatch) Netbackup 6.5.5 throws 830 error.
I am able to take backup successfully in this test DR environment using hcart2 tapes with hcart3 type drives.
I do not understand why does Netbackup do not recognise the same configuration while restoring? I am trying to restore the data in to the same system which is acting as master/media server.  Thanks in advance for your suggestions!

05/06/2010 17:17:23 - begin Restore
05/06/2010 17:17:35 - number of images required: 1
05/06/2010 17:17:35 - media needed: JFM386
05/06/2010 17:17:41 - restoring from image xxxxxx_1271593296
05/06/2010 17:17:43 - connecting
05/06/2010 17:17:44 - connected; connect time: 0:00:00
05/06/2010 17:17:46 - Error bptm (pid=7801) NBJM returned an extended error status: drive(s) unavailable or down (830)
05/06/2010 17:17:44 - requesting resource JFM386
05/06/2010 17:17:45 - Error nbjm (pid=7552) NBU status: 830, EMM status: No drives are available
05/06/2010 17:17:45 - Error nbjm (pid=7552) NBU status: 830, EMM status: No drives are available
05/06/2010 17:18:02 - restored from image xxxxxx_1271593296; restore time: 0:00:21
05/06/2010 17:18:02 - end Restore; elapsed time 0:00:39
the restore failed to recover the requested files (5)

[Rakesh_Khandelw]

Sine you have mentioned about using standalone drive, I hope you have followed the process on how to use standalone drives and media.. If not then following links may be useful..

How to re-introduce Tape / Media used prior with NetBackup without changing the Media ID when a barcode reader is not available or disabled within the Robotic Library  http://support.veritas.com/docs/323404

How to perform Media Management with standalone Drives in NetBackup 5.x and 6.x. http://support.veritas.com/docs/296268

[Marianne · Accepted solution]

JFM386 *NULL* 1 14
media type:            1/2" cartridge tape 2 (14)
Media Type:                     HCART2
drive      -    0 hcart3

NetBackup will only load hcart2 tapes in hcart2 tape drives.
PLEASE change the drive type to hcart2

[Shrikant68]

Thanks Marianne! 
change in the drive type resolved the issue.

Once again thanks to all for your valuable time / suggestions and support.

Cheers!

[Andy_Welburn]

This will enable any other users with the same issue to go direct to resolution, as well as giving Marianne the kudos she deserves!

***EDIT***
Done!