Video Screencast Help
Scheduled Maintenance: Symantec Connect is scheduled to be down Saturday, April 19 from 10am to 2pm Pacific Standard Time (GMT: 5pm to 9pm) for server migration and upgrades.
Please accept our apologies in advance for any inconvenience this might cause.

Eject & insert new media

Created: 25 Oct 2011 • Updated: 01 Nov 2011 | 13 comments
This issue has been solved. See solution.

Hey folks, This should be straight-forward, but would seem to be lost on me.  I am quite new, and yes, I have been looking through both A) the manuals, and B) the forums.  Ok, that being said, I have the following:

Windows 2008

Netbackup 6.5.4 (No, the support license was never renewed, so I cannot go to version 7.0 not to mention the cost to renew (expired june this year) is more than purchasing a complete BE solution, Ugh)

Now the challenge for me, there was no off-siting of media.  So I created a volume pool (several, actually), added tapes to those pools from the existing NetBackup pool, created schedules for backups to occur so I could off-site the tapes (I set retention to infinity).

Once a set was created that I wished to off-site, I then went to the manual, went to the section Injecting and ejecting volumes, and got stumped.  Ejecting was not an issue.  The robot moved the requested tapes to the CAP (MAP, which ever it was called), I opened the CAP, removed the tapes, INSERTED new black tapes (with brand new barcodes on the tapes), and that's where I was stopped.

The Volume pool still has the pulled tapes referenced in there.  Ok, so I try to delete the tape references, No go. "Cannot delete assigned volume INC263(92)" (INC263 happens to be the name of the tape).

Ok, maybe I should Expire the tape references with the GUI.  Select "Expiration date" of yesterday (it defaults to 24 hours before).  Seems to work just fine.  Nex,t maybe I should move the tape references to a different media pool, like "None" or "Netbackup". Failed: "Change pool of INC263 failed (91)".

So, I am currently stuck.  My intention is of course, eject the tapes (completed), move the brand new tapes into the previous slots.  The only other thing I see so far is to DeAssign the volume, but that pretty much says "Danger, Wil Robinson!".

I did reference this link: http://www.symantec.com/connect/forums/fairly-new-trying-learn-quickly-about-loading-cap, but that primarily talks about ejecting (which I have done), and references the manuals (which I have been combing through).

Thanks folks,

James

Comments 13 CommentsJump to latest comment

wr's picture

Ejecting tapes changes Volume Group and not Volume Pool.  Think of it this way - VG is physical location; VP is logical usage.  

 

Ok, maybe I should Expire the tape references with the GUI.

You just removed catalog information so it does not know what/where to restore the data on those tapes.  You'd have to do two-phase Import now to rebuild the catalog.

 

...move the brand new tapes into the previous slots. 

Action, Inventory Robot, Update Volume Configuration, Empty media access port

Will Restore -- where there is a Will there is a way

Andy Welburn's picture

If all you want to do is eject then that's all you do - eject. The media will still appear in the volume pool as they still have images on, they are just not in the library.

If you expire the media then you are removing all reference to any backup images on said media - you will have to look at importing if you ever need to restore from them (& hope that they haven't been overwritten in the meantime).

Tapes cannot be moved from one volume pool to another whilst they are assigned (i.e. have images on) & the expiration you set I think will be the physical expiration of the media (effectively a "sell-by" date after which they are deemed not suitable for backups)

Mark_Solutions's picture

James

When you do the eject the last thing you get is a pop up box with an OK on it. Dont click OK until you have removed the tapes and closed the door again as it will cause the volume update to fail.

So remove the tapes and click OK.

Now add the next batch of tapes, run the inventory with the "empty media access port" selected and this will bring in the new tapes and update the volume configuration - job done.

If you still do it the way you have been then afterwards just select to inventory the robot using the update volume configuration but not loading the tapes and it will update the robot contents for you.

Hope this helps

PS If you maintenance only ran out in June I am sure you could get a competitive renewal rather than having to buy it all again - if you are UK based then drop me a line

Authorised Symantec Consultant

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

TandyBrands's picture

First off, thanks to everyone answering so quckly.

Ok, so several things I did wrong from all of the input.  I should not Expire the media. I should not click OK before replacing the CAP/MAP (did that wrong as well). It was not clear on this point . I should NOT insert new tapes in, but instead do an inventory after removing the previous tapes, or can I "kill two birds with one stone" so to speak by removing the media and inserting new tapes when I pull the previous ones?

Mark, thanks for the offer about renewal, but I'm in the US.  Further, what was originally purchased was totally incorrect on a multitude of different reasons (this was before I came on board). I have since had quoted the right and proper licensing, then had a BE solution quoted.  The BE solution turns out to be cheaper.

NB is a great enterprise solution, but way overkill for what we need here.  An SL-500 with 50 tapes & two drives.  We were guided to the NB solution because we have 2 drives  and BE dosn't support two drives (which I know was totally incorrect but again, before my time).

Anyhow, thanks folks...

James

Marianne's picture

Ejected tapes remain in the Volume database and in the designated pool. The location will just be NONE (non-robotic).

Tapes need to remain in the config - NBU records image location on each tape. If you SHOULD manage to delete tapes, NBU would have no idea where to find the data.

Please see info stored for media id INC263, no matter what the location:

Run on master from cmd (remember to Run as Administrator):

...\veritas\netbackup\bin\admincmd\nbemmcmd -listmedia -mediaid INC263.

 

To add new media, simply put media in the CAP, run Robot Inventory, select Update volume configuration and Update volume configuration.

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

TandyBrands's picture

BTW, I did the ...\veritas\netbackup\bin\admincmd\nbemmcmd -listmedia -mediaid INC263 , Now, what did that do for me again?

And is there a way to force the backup when it goes to the pool to use the remaining tapes in the pool first before using the new ones?  Do I need to freeze or suspend the new tapes until the existing ones get used?

Thanks,

James

TandyBrands's picture

OK, I did the following command as suggested: ...\veritas\netbackup\bin\admincmd\nbemmcmd -listmedia -mediaid INC263 And that produced a bit of information:

C:\Program Files\Veritas\NetBackup\bin\admincmd>nbemmcmd -listmedia -mediaid INC263
NBEMMCMD, Version:6.5.4
====================================================================
Media GUID:                     da295075-0276-4ff6-a69e-b898bc928bb2
Media ID:                       INC263
Partner:                        -
Media Type:                     HCART3
Volume Group:                   ---
Application:                    Netbackup
Media Flags:                    1
Description:                    Added by Media Manager
Barcode:                        INC263
Partner Barcode:                --------
Last Write Host:                tbbackup01
Created:                        10/04/2011 17:41
Time Assigned:                  10/07/2011 09:18
First Mount:                    10/07/2011 08:57
Last Mount:                     10/07/2011 10:52
Volume Expiration:              10/24/2012 08:48
Data Expiration:                INFINITY
Last Written:                   10/07/2011 10:51
Last Read:                      -
Robot Type:                     NONE
Robot Control Host:             -
Robot Number:                   -
Slot:                           -
Side/Face:                      -
Cleanings Remaining:            -
Number of Mounts:               3
Maximum Mounts Allowed:         0
Media Status:                   FULL
Kilobytes:                      545611663
Images:                         2
Valid Images:                   2
Retention Period:               9
Number of Restores:             0
Optical Header Size Bytes:      1024
Optical Sector Size Bytes:      0
Optical Partition Size Bytes:   0
Last Header Offset:             3049778
Adamm Guid:                     00000000-0000-0000-0000-000000000000
Rsm Guid:                       00000000-0000-0000-0000-000000000000
Origin Host:                    NONE
Master Host:                    tbbackup01
Server Group:                   NO_SHARING_GROUP
Upgrade Conflicts Flag:
Pool Number:                    6
Volume Pool:                    Offsite-EXCH
Previous Pool Name:             -
Vault Flags:                    -
Vault Container:                -
Vault Name:                     -
Vault Slot:                     -
Session ID:                     -
Date Vaulted:                   -
Return Date:                    -
====================================================================
Command completed successfully.

Also, is there a way to force the backups in the pool to use the old tapes first before using the new tapes?  Would I freeze or suspend the tape?
 

J.H Is gone's picture

1) when a tape is written to with a valid job - you will see in the the GUI that it has an assigned date and an expiration date.  So you were right to then eject these tapes to send off-site.  Have them come back AFTER they expire - you should not put them back into the lib until they are expired ( if un-expired the next backup will append to the tape - then those older images/backups expire - you would then have wasted tape at the beginning of the tape - so just make sure they are past the expiration date of the images before putting them back in). 

2) When you eject the tapes and take them out of the map - before the eject you will see in the GUI they have a slot number and a robot number.  Once they are ejected those will be a - or blank.  This means the tape is no longer in the library.  But the tape MUST still be reference in NB because it knows you have valid backups on the tape.  Think of the Media GUI as showing you all your tapes - the different columns show you where they are and when they were used and when the images on them will expire.  The ones with a slot number tells you how many are in the robot - this can be important so if  you sort by tapes that are in the robot you can verify that you have enough tapes for tonight's backups.

3) putting in new tapes - you might want to create a bar-code rule as to where the tapes go when you inject them - you can read the details on that in the manual and ask if you have questions on it.  When you have the tapes in the MAP ( and based on what robot you have you might have to tell the robot what lib..)  then go back to the GUI / Media and do the inject - based on which console you use you might be able to preview this - make sure the tapes come in with the correct media id and bar-code.  Once injected you should see these tapes on your media list.

FYI - on the sort  - if you hit Time Assigned twice, then Robot Control host twice - all the tapes IN the robot will be at the top, and the ones that have been written to will be at the very top.

I don't have to know how to spell....I work on Unix.
NetBackup 7.0.1 - AIX & Windows

SOLUTION
Mark_Solutions's picture

James

You can get away with the unload / load in one go - just run the inventory update selecting to "empty media access" and it should sort itself out.

If you are happy with the advice dont forget to close the thread - good luck with BE!

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

I see the following in the output:

Time Assigned: 10/07/2011 09:18
First Mount: 10/07/2011 08:57
Last Mount: 10/07/2011 10:52
Volume Expiration: 10/24/2012 08:48
Data Expiration: INFINITY
Last Written: 10/07/2011 10:51
Last Read: -
Robot Type: NONE

Number of Mounts: 3
Maximum Mounts Allowed: 0
Media Status: FULL
Kilobytes: 545611663

VOLUME EXPIRATION means the tape is old/faulty/can no longer be used. Is this what you want?
I guess not. Seem this has only be used/mounted 3 times: Number of Mounts: 3

Robot Type: NONE means you have successfully ejected the tape.

Data Expiration: INFINITY : Backup images will never expire.

Media Status: FULL  No more backups can be added to this tape.

 

"is there a way to force the backup when it goes to the pool to use the remaining tapes in the pool first before using the new ones?"

We will need more info  - please run the following from cmd and post output:

..\veritas\netbackup\bin\goodies\available_media

As long as media is in the robot,  in the correct volume pool, correct retention level, not FULL,FROZEN,SUSPENDED, etc... it will append to it.

Please also see if this info helps:

About selecting media in robots on Windows 
http://www.symantec.com/docs/HOWTO33982

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

TandyBrands's picture

C:\Program Files\Veritas\NetBackup\bin\goodies>available_media
media   media   robot   robot   robot   side/   ret    size     status
 ID     type    type      #     slot    face    level  KBytes
----------------------------------------------------------------------------
CatalogBackup pool

DataStore pool

NetBackup pool

FUL166  HCART3   TLD      0       25     -       1     79522945 ACTIVE
INC219  HCART3   TLD      0       21     -       3     361125274        ACTIVE
INC265  HCART3   TLD      0       22     -       1     304625928        ACTIVE
INC322  HCART3   TLD      0       36     -       3     264289   ACTIVE
000002  HCART3   TLD      0       34     -       -     -        AVAILABLE
000018  HCART3   TLD      0       14     -       -     -        AVAILABLE
000021  HCART3   TLD      0       30     -       -     -        AVAILABLE
000023  HCART3   TLD      0       2      -       -     -        AVAILABLE
000038  HCART3   TLD      0       12     -       -     -        AVAILABLE
ARL005  HCART3   TLD      0       28     -       -     -        AVAILABLE
FUL152  HCART3   TLD      0       44     -       -     -        AVAILABLE
INC201  HCART3   TLD      0       9      -       -     -        AVAILABLE
INC209  HCART3   TLD      0       8      -       -     -        AVAILABLE
INC210  HCART3   TLD      0       18     -       -     -        AVAILABLE
INC217  HCART3   TLD      0       13     -       -     -        AVAILABLE
INC222  HCART3   TLD      0       10     -       -     -        AVAILABLE
INC225  HCART3   TLD      0       39     -       -     -        AVAILABLE
INC254  HCART3   TLD      0       7      -       -     -        AVAILABLE
INC256  HCART3   TLD      0       5      -       -     -        AVAILABLE
INC259  HCART3   TLD      0       29     -       -     -        AVAILABLE
INC268  HCART3   TLD      0       38     -       -     -        AVAILABLE
INC270  HCART3   TLD      0       6      -       -     -        AVAILABLE
INC271  HCART3   TLD      0       26     -       -     -        AVAILABLE
INC274  HCART3   TLD      0       24     -       -     -        AVAILABLE
INC281  HCART3   TLD      0       33     -       -     -        AVAILABLE
INC289  HCART3   TLD      0       3      -       -     -        AVAILABLE
INC308  HCART3   TLD      0       45     -       -     -        AVAILABLE
INC320  HCART3   TLD      0       4      -       -     -        AVAILABLE
INC332  HCART3   TLD      0       17     -       -     -        AVAILABLE
INC333  HCART3   TLD      0       15     -       -     -        AVAILABLE
INC339  HCART3   TLD      0       35     -       -     -        AVAILABLE
INC340  HCART3   TLD      0       46     -       -     -        AVAILABLE
INC351  HCART3   TLD      0       23     -       -     -        AVAILABLE
INC354  HCART3   TLD      0       32     -       -     -        AVAILABLE
INC365  HCART3   TLD      0       37     -       -     -        AVAILABLE
000016  HCART3   TLD      0       16     -       3     543133139        FULL
ARL006  HCART3   TLD      0       19     -       3     535927115        FULL
INC238  HCART3   TLD      0       27     -       1     648580773        FULL
INC284  HCART3   TLD      0       11     -       3     564219590        FULL
INC294  HCART3   TLD      0       20     -       3     595869798        FULL
INC371  HCART3   TLD      0       31     -       3     627954146        FULL

None pool

CLNU02  HC3_CLN  TLD      0       1      -       -     -        AVAILABLE

Offsite-EXCH pool

INC318  HCART3   NONE     -       -      -       9     273112961        ACTIVE
000032  HCART3   TLD      0       43     -       -     -        AVAILABLE
INC296  HCART3   TLD      0       41     -       -     -        AVAILABLE
TBA040  HCART3   TLD      0       40     -       -     -        AVAILABLE
TBA042  HCART3   TLD      0       42     -       -     -        AVAILABLE
INC263  HCART3   NONE     -       -      -       9     545611663        FULL

Offsite-FILE-SQL pool

FUL151  HCART3   NONE     -       -      -       9     191864342        ACTIVE
FUL164  HCART3   TLD      0       47     -       -     -        AVAILABLE
TBA048  HCART3   TLD      0       48     -       -     -        AVAILABLE

 

Thanks folks.

Marianne's picture

I hope we have managed to answer your query?

As you can see from available_media output, your retention level 9 (Infinity) tapes have been ejected from the robot (Robot Type = NONE).
NBU knows about the data on them. If you ever need to restore data from these Infinity tapes, NBU will prompt you to put it back in the robot.

It seems you have also inserted new media in the robot and Inventory/updated NBU config successfully.

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

Omar Villa's picture

Is simple the tape is infinite will go back to its pool with put it back in. U need to expire the tape and later change the pool.

Omar Villa

Netbackup Expert

Twiter: @omarvillaNBU