Netbackup not recognizing a tape for restore

[bfogliano]

I need a bit of help please- I am trying to do a restore and Netbackup will not recognize two of the tapes for the job.  I have confirmed that they are in the robot by looking at the list of tapes in the robot but the only difference between these two tapes and the rest of the tapes in the robot is that next to the data expiration date there is no time listed as with the other tapes.  This really is the only difference I notice and every time I run the restore it keeps putting the job into a pending state looking for these tapes any ideas?

Thanks

Brandon

[Marianne]

Please explain what you mean by 'not recognize'?

What are the media-id's that the restore is looking for?

What are the media-id's and barcodes that is displayed in the Media GUI?

[bfogliano]

What I mean is that the tape is in the robot but the program appears to not see that it is there because it continues to ask for the tapes though they are present.  The media ID's are 000021 and 000043, I hope that is what you meant by the ID's. 

Thanks

Brandon

[Marianne]

Does NetBackup know that the tapes are in the robot? Did you run Inventory to update NBU robot contents?

Can you see these media's in the Media section of the GUI with it's slot # in the robot?
Did NBU perhaps add it as a new media-id (e.g. 0021L3)?

Please provide output of:

nbemmcmd -listmedia -mediaid 000021

That will tell us where NBU believes the tape is and what the status is.

[Yasuhisa_Ishika]

I understand you can see these two media in [Media and Device Management]-[Media], but you can not see any time and date in expiration date column. Right?

This means NetBackup recognize these media, but there are no data on them. All data recorded have been already expired. You should check what data you write, when data is written, and retention period of data.

[bfogliano]

Thats the confusing part the expiration date is there for the data expiration but the time is not next to the date like it is with every other tape in the robot.

[bfogliano]

I can see the tapes in the GUI and yes the 000021 tape is there it has a data expiration date next to it but there is no time next to the date that is the difference between that tape and the rest in the machine.

[Marianne]

Please post output of nbemmcmd command as per my previous post.

Unix path: /usr/openv/netbackup/bin/admincmd

Windows path: <install-path>\veritas\netbackup\bin\admincmd

[bfogliano]

Ok here is the output you asked for I hope this helps

F:\Program Files\Veritas\NetBackup\bin\admincmd>nbemmcmd -listmedia -mediaid 000
021
NBEMMCMD, Version:7.0.1
====================================================================
Media GUID:                     978ab706-1e31-4606-bc17-b7b36575fdc2
Media ID:                       000021
Partner:                        -
Media Type:                     HCART3
Volume Group:                   000_00000_TLD
Application:                    Netbackup
Media Flags:                    1
Description:                    LTO3 - Scratch pool
Barcode:                        000021
Partner Barcode:                --------
Last Write Host:                srlb1tbx02
Created:                        04/09/2007 19:11
Time Assigned:                  01/21/2012 12:01
First Mount:                    04/10/2007 09:53
Last Mount:                     01/22/2012 00:45
Volume Expiration:              -
Data Expiration:                01/21/2013 00:00
Last Written:                   01/22/2012 00:00
Last Read:                      -
Robot Type:                     TLD
Robot Control Host:             srla4tbx01
Robot Number:                   0
Slot:                           42
Side/Face:                      -
Cleanings Remaining:            -
Number of Mounts:               59
Maximum Mounts Allowed:         0
Media Status:                   FULL MPX
Kilobytes:                      825683473
Images:                         434
Valid Images:                   434
Retention Period:               8
Number of Restores:             0
Optical Header Size Bytes:      1024
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:                    srla4tbx01
Server Group:                   NO_SHARING_GROUP
Upgrade Conflicts Flag:
Pool Number:                    5
Volume Pool:                    Windows
Previous Pool Name:             Scratch
Vault Flags:                    -
Vault Container:                -
Vault Name:                     Weekly_offsite
Vault Slot:                     -
Session ID:                     386
Date Vaulted:                   02/07/2012 10:58
Return Date:                    -
====================================================================
Command completed successfully.

[Marianne]

I still don't understand what you mean by 'Netbackup will not recognize two of the tapes'.

Media-id is in:
Robot Number:                   0
Slot:                           42

Last Written:                   01/22/2012 00:00

Data will expire 365 days later :

Data Expiration:                01/21/2013 00:00

There is no hardware expiration date on the tape (which is normal):

Volume Expiration:              -

Everything seems fine to me....

[bfogliano]

I know we thought the same thing, that's why we are so confused, as I said though the only thing that looks odd is the time is not next to the data expiration date like with the other tapes in the GUI, do you think that could be an issue at all?

[Marianne]

There is no time because expiration time is midnight exactly:  00:00. To the second 365 days after it was last used for backup.

Last Written:                   01/22/2012 00:00

Data Expiration:                01/21/2013 00:00

(You will notice that 1 year retention is 365 days - it does not automatically adjust to 366 days when it is a leap year.)

I don't see any 'issue' at all.

Are you getting an error when you start the restore?

[Kernel_Panic]

Hi Marianne,

One quick question, what about the date vaulted? could it be possible that he is using vault and Netbackup generate a pending request because the tape is not back on the production environment for Netbackup?

On the other hand if the BAR tell him about those 3 tapes, maybe the pending request is being generated because of a density issue or something like that. Could it be this way?

Thanks for your reply.

[Marianne]

Vaulting will not prevent restores.

The tape is currently in the robot - restore should work. Or at least start and mount the tape on media server (srlb1tbx02).

We need more info - was the restore attempted? Did it go through or fail? If failed, what error? (other that status 5...)

*** EDIT ***

Just read opening post again - seems Pending request is generated.

The backup was done by media server srlb1tbx02.

Restore will by default be assigned to this media server (unless Media Host Override was done)

Please show us output of the following on media server srlb1tbx02:

....\volmgr\bin\tpconfig -l

....\volmgr\bin\vmoprcmd -d

Above output will show us drive density on media server and if suitable drive is available in robot 0.

[bfogliano]

Ok well I'm glad about the time I had a feeling that may be the reason, the restore does start, it lists the media needed, it starts to restore the image and then in the details screen it hangs at this point:

2/8/2012 11:40:48 AM - connected; connect time: 00:00:06
2/8/2012 11:41:44 AM - awaiting resource 000021 A pending request has been generated for this resource request.
  Operator action may be required. Pending Action: All drives down.,
  Media ID: 000021, Barcode: 000021, Density: hcart3, Access Mode: Read,
  Action Drive Name: N/A, Action Media Server: N/A, Robot Number: 0, Robot Type: TLD,
  Volume Group: 000_00000_TLD, Action Acs: N/A, Action Lsm: N/A

I hope this helps.

[Marianne]

Please post output of commands requested above:

Please show us output of the following on media server srlb1tbx02:

....\volmgr\bin\tpconfig -l
....\volmgr\bin\vmoprcmd -d

This seems to be be the problem:

Operator action may be required. Pending Action: All drives down.,
  Media ID: 000021, Barcode: 000021, Density: hcart3, Access Mode: Read,