inventory update

Hello,

You would acomplish this with using vault. Issue is, if you are not using vault, then its on you to manage what tapes are outside of the robot and when they left. 

You can review the vault guide ,DOC5193, for more information on what vault does and how to use it.

Hi Symterry,

We are not using vault.

When you said "eject some media" I assume you physically removed them from the library, the inventory would show you a list of media "moving out" to standalone, together with those you inserted and "moving in". 

But if you miss the output of the inventory, I dont think there is any other file that keeps the activity - I would look through /usr/openv/netbackup/logs/admin/ logs.

Vault option would be the best to keep track of offsite tape list.

Ejected tapes will move into the --- volume group (yes, three dashes ...) Think that will be the easiest way to spot them. The volume group will only be created when media are ejected, if all the media are put back into the library, following an inventory, if empty, the --- volume group will be deleted.

In NetBackup GUI / Java Console, when you go to "MEDIA" tab you will see "Last Written" column.

The medias recently ejected must be having backup written recently on them.

As you have found, unless you are using vault, there is no NBU report that will give you this info.

I have in the past found this info in reqlib log on robot control host.
https://www-secure.symantec.com/connect/forums/netbackup-and-tape-movement-logging

Mark has been able to find it in EMM log:
https://www-secure.symantec.com/connect/forums/how-find-when-media-was-inserted-library

Hi Raj,

In Master server under this location , you can see the .txt files ,while will give you an idea what all were ejected.

/usr/openv/volmgr/misc

EJECT_0_1_0_0.txt
EJECT_0_1_0_0.txt.06Mar2013

 

 

Hi mph999,

Please elaborate, what will be the location for these temp. volume groups etc.

 

Hi NBU_nbu,

I am unable to find above mentioned file. PFB output

# pwd

/opt/openv/volmgr/misc
#
# ls -l
total 129
-rw-------   1 root     root        6372 Oct 14  2013 DqDriveState
-r--r--r--   1 root     bin          340 Feb  4  2011 README
-rw-------   1 root     root           0 Jul 17  2012 lmfcd.lock
-rw-rw-rw-   1 root     root       34788 Oct 22  2012 ltitables
drwxr-xr-x   2 root     bin            3 Jul 16  2012 robotic_db
-rw-------   1 root     root           0 Jul 17  2012 tl8cd.lock
-rw-------   1 root     root           0 Jul 16  2012 tld.lock.c0tw500104f000ae9638l0
-rw-------   1 root     root          17 Jun 11 16:00 tldcd.lock
-rw-------   1 root     root           0 Jul 17  2012 tlhcd.lock
-rw-------   1 root     root          16 Apr 17 13:15 vmd.lock
#

 

 

 

I wouldn't rely on anything in /opt/openv/volmgr/misc - that directory can 'safely' be deleted (it would recreate on restart of media manager services).

 

The attched picture below shows how to see the volume groups in the GUI

One day when you decide to have a look at my post dated 26 June, you may want to create debug log folders and restart ltid...

Media movement is for sure logged in reqlib when enabled.