Getting mismatched errors for all the tapes when doing a robot inventory on the media server

Issue


Getting mismatched errors for all the tapes when doing a robot inventory on the media server.

Solution


Robot inventory should be done on the server which is the volDB host. If the volDB host is the master server (normally, this is the case), then a robot inventory should be done on the master server, not the media server.  If the media server is used, it will give mismatched errors for all the tapes and update the volume information to the media server volume database.


To determine which server is the volDB host, run the tpconfig -d command from the master/media server.

Currently defined robotics are:
TLD(0)     robot host = nbusun02, volume database host = nbusun01


In this case:
Master server is nbusun01
Media server is nbusun02
Robot host is nbusun02
Volume Database host is nbusun01

NOTE: This is a test scenario.

On the media server, nbusun02, check the size of the volDB. By default, VERITAS NetBackup will create one that will be 8bytes in size.

nbusun02# ls -l /usr/openv/volmgr/database/volDB
-rw-------   1 root     other       8 Mar 15 16:26 volDB

Run the tpconfig -d command to check the volDB host

Index  DriveName              DrivePath                Type   Multihost  Status
*****     ********                   *********                    ****     *********    ******
 0   Drive0                 /dev/rmt/0cbn                   dlt         No        UP
      TLD(0) Definition      DRIVE=1
  1   Drive1                 /dev/rmt/1cbn                  dlt         No        UP
      TLD(0) Definition      DRIVE=2
  2   Drive2                 /dev/rmt/2cbn                  dlt         No        UP
      TLD(0) Definition      DRIVE=3
  3   Drive3                 /dev/rmt/3cbn                  dlt         No        UP
      TLD(0) Definition      DRIVE=4

Currently defined robotics are:
TLD(0)     robotic path = /dev/sg/c0t0l0, volume database host = nbusun01

volDB host is the master server, nbusun01

If robot inventory is run on nbusun02, you will get the following:

--------------------------------------------------------------------
03/29/2002 11:00:15
Robot: TLD(0) on nbusun02
Operation: Compare Robot Contents
Volume Database Host: nbusun02
--------------------------------------------------------------------

      Robot Contents                                         Volume Configuration
Slot      Tape  Barcode                        Media ID     Barcode       Mismatch Detected
====      ===================      =================  =================
 1        Yes  DGD516                                                                 Yes
 2        Yes  DGD239                                                                 Yes
 3        Yes  CLN465                                                                  Yes
 4        Yes  DGD222                                                                 Yes
 5        Yes  DGD226                                                                 Yes
 6        Yes  DGD221                                                                 Yes
 7        Yes  DG004C                                                                 Yes
 8        Yes  QYH661                                                                 Yes
 9        Yes  DGD223                                                                 Yes
10        Yes  DGD225                                                                 Yes
11        Yes  DGD505                                                                 Yes
12        Yes  DGD224                                                                 Yes
13        Yes  PCD619                                                                  Yes
14        Yes  DGD252                                                                 Yes
15        Yes  DGD232                                                                 Yes
16        Yes  DGD248                                                                 Yes

--------------------------------------------------------------------

--------------------------------------------------------------------
03/29/2002 11:01:10
Robot: TLD(0) on nbusun02
Operation: Preview of Inventory and Update
Volume Database Host: nbusun02
--------------------------------------------------------------------
Generating list of recommended changes ...

Proposed Change(s) to Update the Volume Configuration
=====================================================
Logically add new media DGD516 (barcode DGD516) to robot slot 1.
Logically add new media DGD239 (barcode DGD239) to robot slot 2.
Logically add new media CLN465 (barcode CLN465) to robot slot 3.
Logically add new media DGD222 (barcode DGD222) to robot slot 4.
Logically add new media DGD226 (barcode DGD226) to robot slot 5.
Logically add new media DGD221 (barcode DGD221) to robot slot 6.
Logically add new media DG004C (barcode DG004C) to robot slot 7.
Logically add new media QYH661 (barcode QYH661) to robot slot 8.
Logically add new media DGD223 (barcode DGD223) to robot slot 9.
Logically add new media DGD225 (barcode DGD225) to robot slot 10.
Logically add new media DGD505 (barcode DGD505) to robot slot 11.
Logically add new media DGD224 (barcode DGD224) to robot slot 12.
Logically add new media PCD619 (barcode PCD619) to robot slot 13.
Logically add new media DGD252 (barcode DGD252) to robot slot 14.
Logically add new media DGD232 (barcode DGD232) to robot slot 15.
Logically add new media DGD248 (barcode DGD248) to robot slot 16.

--------------------------------------------------------------------

--------------------------------------------------------------------
03/29/2002 11:01:56
Robot: TLD(0) on nbusun02
Operation: Inventory and Update
Volume Database Host: nbusun02
--------------------------------------------------------------------
Generating list of recommended changes ...

Proposed Change(s) to Update the Volume Configuration
=====================================================
Logically add new media DGD516 (barcode DGD516) to robot slot 1.
Logically add new media DGD239 (barcode DGD239) to robot slot 2.
Logically add new media CLN465 (barcode CLN465) to robot slot 3.
Logically add new media DGD222 (barcode DGD222) to robot slot 4.
Logically add new media DGD226 (barcode DGD226) to robot slot 5.
Logically add new media DGD221 (barcode DGD221) to robot slot 6.

Logically add new media DG004C (barcode DG004C) to robot slot 7.
Logically add new media QYH661 (barcode QYH661) to robot slot 8.
Logically add new media DGD223 (barcode DGD223) to robot slot 9.
Logically add new media DGD225 (barcode DGD225) to robot slot 10.
Logically add new media DGD505 (barcode DGD505) to robot slot 11.
Logically add new media DGD224 (barcode DGD224) to robot slot 12.
Logically add new media PCD619 (barcode PCD619) to robot slot 13.
Logically add new media DGD252 (barcode DGD252) to robot slot 14.
Logically add new media DGD232 (barcode DGD232) to robot slot 15.
Logically add new media DGD248 (barcode DGD248) to robot slot 16.
Updating volume configuration ...

Processing new media added to the robotic library by logically
adding media with new media IDs as follows...
      Media ID      Slot
      ========      ====
       DGD516         1
       DGD239         2
       CLN465          3
       DGD222         4
       DGD226         5
       DGD221         6
       DG004C         7
       QYH661         8
       DGD223         9
       DGD225        10
       DGD505        11
       DGD224        12
       PCD619         13
       DGD252           14
       DGD232         15
       DGD248         16


Volume configuration successfully updated.


--------------------------------------------------------------------

Now, check the size of the volDB on nbusun02 and that it has updated the volume information locally, although the volDB host is nbusun01.


nbusun02# ls -l /usr/openv/volmgr/database/volDB
-rw-------   1 root     other       9544 Mar 29 11:02 volDB


NOTE: In practice, always check which server is the volDB host before doing a robot inventory to avoid volDB being updated on other servers instead.