Video Screencast Help

Automount tape in standalone drive

Created: 19 Dec 2011 • Updated: 26 Mar 2012 | 26 comments
This issue has been solved. See solution.

I got a standalone tapedrive in my test environment.

When I change the tape to the weekly one it wont mount it automatically.

In the Device Monitor it waites for me to assign the media.

But that happens when the Policy starts, which is at 01:00 am.

How could I automate this?

Comments 26 CommentsJump to latest comment

Marianne's picture

So, if I understand correctly - you have inserted a tape in the drive but NBU is not recognising it?

Is this a new tape (never used before) or a previously used tape that you want to append to or overwrite?
If new - have you added the Media ID in the Media section of the GUI, add it to the correct pool and label it (bplabel)?

Is Device Monitor promting for another media-id than the one that you have inserted? To prevent NBU from prompting for previously used media, you can suspend media when ejecting it.

Next time you change a tape, please verify that NBU is recognising the media and reading the internal label:

Unix: /usr/openv/volmgr/bin/vmoprcmd -d
Windows: <install-path>\veritas\volmgr\bin\vmoprcmd -d

It is important to understand how NBU is using/selecting media in Standalone drives:

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

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Mark_Solutions's picture

If the tape has been used before it will have a physical header written to the tape which NetBackup should recognise when it is inserted.

If you have not used the tape before (brand new) then just label it first.

If you run the bplabel command from a command line you will see it appears to hang.

If you go to the admin console under Device Monitor you will see a pending request at the bottom of the screen. Drag this and drop it onto the tape drive.

This will label the tape physically with its Media ID and the bplabel command will complete.

Do this for all new tapes.

Once a tape has been used once it should show up automatically next time it is inserted

Dont forget to give it a couple of minutes after inserting a tape for NetBackup to read it and do a refresh in activity monitor to see if it has been picked up.

Hope this helps

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

rsm.gbg's picture

To me it seems it wont try to read the tape when I insert a new (previously used) tape

If I insert a tape say the Daily tape and I do refresh on the standalone tape in the Device Monitor it waits and thinks abit and then it display the previous tape not the new tape.

Next day (because the backups failed) I got status 96 on the policies because it couldn't find any media.

If I just do a restart job it will tell me there is a pending action.I just go to the device Monitor and refresh and do Assign Request and the backup starts just fine.

btw, the standalone tape drive sits on a media server not on the master.

When running the command below, it is LTD002 in the drive,

I used that tape yesterday just fine (LTD002).

ipndadm1 % /usr/openv/volmgr/bin/vmoprcmd -d

                                PENDING REQUESTS

                                     <NONE>

                                  DRIVE STATUS

Drv Type   Control  User      Label  RecMID  ExtMID  Ready   Wr.Enbl.  ReqId
  0 hcart    AVR               Yes   LTW001           Yes     Yes        0

                             ADDITIONAL DRIVE STATUS

Drv DriveName            Shared    Assigned        Comment
  0 HP.ULTRIUM4-SCSI.000  No       -
ipndadm1 %

 

Marianne's picture

Nope - not LTD002 in the drive.

The header on the tape (internal label) that is currently in the drive is LTW001.

Do you manually label new tapes before using it? Do you also write this media-id on the paper-label on the tape?

Best to insert all your used tapes one-by-one in the drive, check what the internal label is (using vmoprcmd) and check that the external label matches the internal label.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

rsm.gbg's picture

Same thing happened,

Backups didn't start the LTD002 IS in the drive.

If I do restart job on the nightly failed ones I just go to the device Monitor and refresh and do Assign Request and the backup starts just fine.

This tape is written to and labeled correctly, it was used on Monday.

So, if I change tape, Netbackup should read the label and if it is valid it should assign it?

For some reason that doesn't seem to happen here.

/usr/openv/volmgr/bin/vmoprcmd -d
will not tell me what tape is in the drive

I will do some more testing today, when backup finishes.

Mark_Solutions's picture

Hi

Just a thought - what O/S is the media server that this drive is attached to?

I am assuming it is a Unix O/S from your command line but if that is just run from the Master and the Media Server is actually Windows ensure that removable storage service is stopped and disabled otherwise Windows will be interferring with the drive.

Other than that i can aonly assume you have a settiong or a touch file in place somewhere causing this - media unmount delay or something on the Master or Media Server media section under Host Properties

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

Marianne's picture

You have not mentioned you OS or NBU version?

It seems that you might have discovered a bug in AVRD (the process that reads and reports the internal label).

 

Sounds similar to this problem: https://www-secure.symantec.com/connect/forums/loa...

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Mark_Solutions's picture

There was a similar bug that was fixed way back in V6.0 MP5, that actually had a registry workaround so dont know if it is worth trying it:

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

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

rsm.gbg's picture

Some more tests...

All Solaris 10, running NBU 7.1.0.2

It seems that if I put in a new tape and label it, say LTD003, I can see that tape and vmoprcmd reports correct label.

If I then change tape to say LTW001 it correctly changes the tape displayed in Device Manager.

If I change back to the LTD003 tape, it doesn't change.

If I run a backup on LTD003 I have to do the assign request in the Device Manager.

After this the tape gets correctly assign automatically.

To me it seems that I have to start a real backup on the tape before it could mount it automatically.
Label it is not enough.

If this is a bug or feature i don't know.

Mark_Solutions's picture

I dont think we have covered what type of tape drive you have

Is it LTO or (S)DLT?

I do know that some SDLT4 drives had a firmware issue where tapes had to be labelled twice before they could be used by NetBackup

This was fixed by a firmware update

What ever your drive it is may be worth checking that it has the latest firmware installed

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

SOLUTION
rsm.gbg's picture

SUN half height LTO 4 tape drive, 1RU

HP Ultrium4 drive inside.

rsm.gbg's picture

Trying to get help from Oracle to get the correct firmware.

Or for that matter figure out the current firmware.

Marianne's picture

To see current firmware level, run one of the following commands (in /usr/openv/volmgr/bin)

'scan -tape'    
Firmware version will be in 'Inquiry' and 'Product Rev' fields.

'tpautoconf -t'
the 2nd field is the firmware version

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

rsm.gbg's picture

Merry Christmas everyone
Hope you had a good time with family and friends.

Here is the firmware W51D

Just need to get the correct patch from Oracle and update if needed.
Got a case with Oracle to locate the correct patch/firmware.

************************************************************
*********************** SDT_TAPE    ************************
************************************************************
------------------------------------------------------------
Device Name  : "/dev/rmt/0cbn"
Passthru Name: "/dev/sg/c1t0l0"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "HP      Ultrium 4-SCSI  W51D"
Vendor ID  : "HP      "
Product ID : "Ultrium 4-SCSI  "
Product Rev: "W51D"
Serial Number: "HU1046DJCE"
WWN          : ""
WWN Id Type  : 0
Device Identifier: ""
Device Type    : SDT_TAPE
NetBackup Drive Type: 3
Removable      : Yes
Device Supports: SCSI-5
Flags : 0x0
Reason: 0x0
 

Marianne's picture

Your firmware seems newer than the versions listed in the NetBackup 7 Hardware Compatibility List (HCL):    http://www.symantec.com/docs/TECH76495

The following statement on p. 123 seems like a good idea to open a support call with Symantec and your hardware vendor:

3. The firmware versions listed below represent the firmware that has been tested. Firmware versions that are newer than what is listed are also supported. This means that if a newer firmware version is causing a problem, Symantec will work with the hardware vendor to resolve the problem. Symantec and most hardware vendors listed are members of TSANet.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Marianne's picture

Have you tried yet to get support calls logged with Symantec and your tape vendor?

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

mph999's picture

Just for info ...

I had a simalr case to this recently - NBU unable to mount the tape, but os was able to run mt commands / tar to the tape just fine ...

It really did look like some NBU issue.

Turned out, it was the firmware on the HBA - so you might want to start there, as I see you are doing ...

I'll see if I can reproduce the issue ....

Martin

 

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
mph999's picture

Well I'm going to stick my neck out here and suggest this is more likely to be outside NetBackup, or, at least be a combination of config/ events.

I've tested on a Soalris 10 / NBU 7.1.0.2    -  and I cannot reproduce the issue.  Therefore, I am reasonably confident in saying, this isn't going to be entirely down to NetBackup, after all, I am using exactly the same version as you, and it works fine, so there has to be something else contributing to the issue on your server.

Note.  Had to turn my drive into standalone, so I made it non-robotic, created a new STU and moved the media to standalone.

I loaded a tape into the drive, waited a while and then checked it was visible in Device Monitor and vmoprcmd.

I then changed the tape multiple times, and after a short delay each time (normal), the new media was shown  in vmoprcmd and the Device Monitor.

I did notice that when I removed the tape, the Device Monitor needed to be refreshed for the media id to be removed.  However, if a tape was put into the empty drive, or, the tapes were swapped, the GUI updated, even without manually refreshing.

Regards,

Martin

 

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
Amaan's picture

It is probably from the host properties.
Can you please check on your media servers host properties if "Enable Standalone Drive Extension" is unchecked. It is under media section of media server host properties. If it is unchecked this is the root cause of the issue.
Check it (i ment enable it) this should let your jobs mount tapes automatically.

You can find it from nbemmcmd command as well. Run nbemmcmd -getsettings -h media.servername
Check the command syntax it may be incorrect. If the similar comand gives you that Enable Standalone drive extension is no change it to yes from command line or GUI.

rsm.gbg's picture

Hi,

Sorry for the long delay I have been busy with production issues....
Still same issue.

Had a go at this again, it seems I have the latest fw from Sun.I will patch to 7.0.1.3 today.
Hostproperties are ok.
It is a SCSI drive so no HBA.
 

 

- Roland

Marianne's picture

SCSI tape will be connected to SCSI HBA on the server. A whole lot of different things to look at - type of HBA - SE, LVD, HVD?  Type of device - SE, LVD, HVD? Cable length? SCSI bus terminated?

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

rsm.gbg's picture

Hi,

All SCSI 320 LVD, bus terminated correctly.

Just upgraded to a new firmware W62D, well see if that helps.

- Roland

rsm.gbg's picture

I can see the tape in the Device Monitor after just changing tape, it didn't do that before without some sort of manual intervention.

We'll see tonight if it will start backing up or wait for someone to assign the tape.

rsm.gbg's picture

It worked!

I'll change the tape again today and see if it works tomorrow.

Changes:

1. Upgraded to 7.1.0.3 that alone didn't solve the problem.

2. New LTO4 drive Firmware to W62D

Marianne's picture

I think we can all agree that the firmware upgrade fixed the problem. There is nothing in 7.1.0.3 that addresses this kind of issue.

Mark_Solution was first to suggest firmware on 23 December last year:

What ever your drive it is may be worth checking that it has the latest firmware installed.

Please mark his post as Solution!

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

rsm.gbg's picture

Hi,

I marked that as a solution, but at that time (23 dec) there was no new firmware.

This firmware is from 12 Feb.

Thanks for all your help guys and girls.

- Roland