how tu force using an old full tape

[Youssef_s]

Hi All,

i m new in Netbackup,

i have 45 slots, and 45 tapes. I need to use one of old tape in my Robots. how can i tell to NEtBackup to do that.

I tried before an import, but every time i got failure saying that the tape is unmountable.

(the version in 6.5)

Thanks,

[inn_kam]

in that old tape what data is there?

[inn_kam]

Step-by-step procedure on how to import NetBackup backup images via the NetBackup Administration Console GUI.

Article:TECH43584

|

Created: 2005-01-14

|

Updated: 2013-04-15

|

Article URL http://www.symantec.com/docs/TECH43584

[Marianne]

Full tape? As in FULL of valid, unexpired images?

When you say 'old' tapes - are these tapes that were written by older tape drives that have been replaced with new drives? (e.g. LTO3 tapes and now LTO4 drives)

Please bear in mind that although the media can be read or written by newer drives, NBU can ONLY mount tapes in drives if the densities/media type is the same.

So, hcart3 media can only be mounted in hcart3 drives.
hcart media can only be mounted in hcart drives.

Please show us output of the following for media that you want to reuse and drive config:

nbemmcmd -listmedia -mediaid <media-id>
(Command is in ...\veritas\netbackup\bin\admincmd)

tpconfig -l 
(Command is in ...\veritas\volmgr\bin)

[Youssef_s]

Hi All,

inn_kam : i have old Backup that i can recycle and overwrite.

Marianne :  

the result of the command is 

NBEMMCMD, Version:6.5.3.1

====================================================================

Media GUID:                     d42b90c9-6a5b-422d-9c08-8c4dadc8960a

Media ID:                       Q114L3                              

Partner:                        -                                   

Media Type:                     HCART3                              

Volume Group:                   000_00000_TLD                       

Application:                    Netbackup                           

Media Flags:                    1                                   

Description:                    Added by Media Manager              

Barcode:                        ATQ114L3                            

Partner Barcode:                --------                            

Last Write Host:                NONE                                

Created:                        02/15/2010 16:14                    

Time Assigned:                  -                                   

First Mount:                    06/10/2011 21:15                    

Last Mount:                     10/10/2013 20:09                    

Volume Expiration:              -                                   

Data Expiration:                -                                   

Last Written:                   -                                   

Last Read:                      -                                   

Robot Type:                     TLD                                 

Robot Control Host:             gingembre3                          

Robot Number:                   0                                   

Slot:                           48                                  

Side/Face:                      -                                   

Cleanings Remaining:            -                                   

Number of Mounts:               145                                 

Maximum Mounts Allowed:         0                                   

Media Status:                   ACTIVE                              

Kilobytes:                      0                                   

Images:                         0                                   

Valid Images:                   0                                   

Retention Period:               -                                   

Number of Restores:             0                                   

Optical Header Size Bytes:      0                                   

Optical Sector Size Bytes:      0                                   

Optical Partition Size Bytes:   0                                   

Last Header Offset:             0                                   

Adamm Guid:                     00000000-0000-0000-0000-000000000000

Rsm Guid:                       00000000-0000-0000-0000-000000000000

Origin Host:                    NONE                                

Master Host:                    gingembre3                          

Server Group:                                                       

Upgrade Conflicts Flag:                                             

Pool Number:                    2                                   

Volume Pool:                    DataStore                           

Previous Pool Name:             -                                   

Vault Flags:                    -                                   

Vault Container:                -                                   

Vault Name:                     -                                   

Vault Slot:                     -                                   

Session ID:                     -                                   

Date Vaulted:                   -                                   

Return Date:                    -                                   

====================================================================

Command completed successfully.

thanks to all of you

[Marianne]

We need to see 'tpconfig -l' output as well, please. See my previous post.

[Youssef_s]

Hi Marianne,

for tpconfig -l

Device Robot Drive       Robot                    Drive                   Device   

Type     Num Index  Type DrNum Status  Comment    Name                    Path     

robot      0    -    TLD    -       -  -          -                       {1,0,1,1}

  drive    -    0 hcart3    1      UP  -          gingembre3_lto3_drive0  {1,0,1,0}

  drive    -    1 hcart3    2      UP  -          gingembre3_lto3_drive1  {1,0,0,0}

Thnaks

Youssef

[Marianne]

The densities are fine. The media may be physically damaged. Use robtest command to manually mount and dismount tapes. Errors from the robot will tell us what is wrong when you try to mount.

[Youssef_s]

Thanks Marianne,

but while i have not real experience, i launch robtest, but i don't know the command line to mount/dsmount manually the tapes, if you can give it to me.

Thanks a lot 

Youssef

[Marianne]

See this TN:

Robtest commands that can be used to test the SCSI functionality of a robot

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

So, in short - when you run robtest command, select the robot.

s s      (to show all slots)

s d      (show drives)

m s48 d1  (move slot 48 to drive 1)

(does it mount? Any errors?  If no errors, you can unload and move tape back)

unload d1 
(wait for confirmation)

m d1 s48

quit

[Youssef_s]

Hi Marianne,

the result of moving tape from slot to drive :

m s48 d1

Initiating MOVE_MEDIUM from address 1048 to 1

move_medium failed

sense key = 0x3, asc = 0x30, ascq = 0x0, INCOMPATIBLE MEDIUM INSTALLED

Regards,

Youssef

[Marianne]

 INCOMPATIBLE MEDIUM INSTALLED

This is a message from the robot.

You need to eject the tape and physically inspect the media type printed on the tape and the label on the tape. 

Check with your tape library vendor about the media compatibility of this media with the drives in the robot.

Tape libraries such as STK is very specific about which tapes it will mount in drives.

[Youssef_s]

Hi Marianne,

while launching unload d1 :

unload d1

Opening {1,0,1,0}, on the local host, please wait...

Tape {1,0,1,0} has not become ready.

Thanks for your help

[Youssef_s]

Hi Marianne,

but the probleme that the Backup works before with tose media

Any change in Robot or Medias  :(

Thank you

Youssef

[Marianne]

You need to eject the tape to see what is wrong with it. 

I cannot tell you why the robot (NOT NBU) is refusing to mount the tape.
Maybe the target on the slot came loose, may the barcode got damaged somehow.

Please examine the slot where the tape is and then take the tape out and see if you can see anything wrong.

[mph999]

INCOMATIBLE MEDIUM INSTALLED There is absolutely nothing that can be done in NBU to fix this. The problem is with the library/ drive. It may have been working before, it is not working now, that does not make it NBUs fault. At some point when anything breaks, it was working previously - that does not shift the blame into anither area. There is one way only to fix this : Example the tape as suggested by Marianne, and if no issue can be seen, you will need to call the hardware vendor. Martin