Media Manager error 109, pool does not exist in pool database

[makhs]

Hi all,

all my backups are suddenly failling with similar messages like the one below.

Error bptm (pid=3191) Media Manager error 109, pool does not exist in pool database, host=ferrisbkup
Error bptm (pid=3191) Media Manager volume pool PDMB2B has no more unassigned media in robotic device TLD(1)

what does it mean?

I have verified that all volumes pools have available media and that none of them are frozen or full.

[Rakesh_Khandelw]

The Policy Volume Pool: setting in the NetBackup (tm) Policy Attributes is case sensitive. If the volume pool name specifically named in the backup policy or schedule does not exactly match a volume pool defined on the NetBackup master server, then the backups will fail with a status code of 96 even though there are available tapes in the scratch pool.

Check this out -
http://support.veritas.com/docs/276495

[Stumpr2]

let's look at the definitions.

Please run this command

windows command prompt

$INSTALL_DIR\Volmgr\bin\vmpool -listall -bx

UNIX shell

/usr/openv/volmgr/bin/vmpool -listall -bx

[makhs]

Hi Stumpr,

the backup policies which are failing all use volume pools from this media server.  (shown here)

[stmfx11(root)]$ /usr/openv/volmgr/bin/vmpool -listall -bx
pool                   index   host             user             group            description
---------------------------------------------------------------------------------------------
None                     0     ANYHOST          ANY              NONE             the None pool (for anyone)
NetBackup                1     ANYHOST          root (0)         NONE             the NetBackup pool
DataStore                2     ANYHOST          root (0)         NONE             the DataStore pool
sapPRD                   3     ANYHOST          ANY              NONE             ----
sapPBW                   4     ANYHOST          ANY              NONE             ----
msapPBW                  5     ANYHOST          ANY              NONE             Monthly
msapPRD                  6     ANYHOST          ANY              NONE             Monthly
sapPRD_adhoc             7     ANYHOST          ANY              NONE             ----
LTO2adhoc                8     ANYHOST          ANY              NONE             ----
PDMB2B                   9     ANYHOST          ANY              NONE             (WM/WIN/B2B)PROD
emergency               10     ANYHOST          ANY              NONE             scratch_pool
m.PDMB2B                11     ANYHOST          ANY              NONE             ----
sanbkup                 12     ANYHOST          ANY              NONE             ----
carp_finalbackup        13     ANYHOST          ANY              NONE             ----
CIM_Windows             14     ANYHOST          ANY              NONE             ----
m.CIM_Windows           15     ANYHOST          ANY              NONE             ----
carp_QA2                16     ANYHOST          ANY              NONE             ----
AIX_Adhoc               17     ANYHOST          ANY              NONE             ----
carp_QA2_daily          18     ANYHOST          ANY              NONE             ----
AIX_daily               19     ANYHOST          ANY              NONE             ----
AIX_monthly             20     ANYHOST          ANY              NONE             ----
sgsapjv                 21     ANYHOST          ANY              NONE             ......
m.sgsapjv               22     ANYHOST          ANY              NONE             ------
sapTBW_adhoc            23     ANYHOST          ANY              NONE             ----
stmes02                 24     ANYHOST          ANY              NONE             daily volume pool for Stmes02
mstmes02                25     ANYHOST          ANY              NONE             monthly vol pool for stmes02
testing                 26     ANYHOST          ANY              NONE             ----
test-lto1               27     ANYHOST          ANY              NONE             ----

[makhs]

Hi ,

this problem started after we reconfigured the tape device path on the media server due to SAN fabric migration.

I notice that the volume database host has been changed for the media server (it is now pointing the the master server instead).  Could this be the cause?

Before:

[stmfx11(root)]$ cat tpconfig.-d.201107
Index DriveName              DrivePath                Type    Shared   Status
***** *********              **********               ****    ******   ******
  1   HPUltrium2-SCSI0       /dev/rmt/c12t0d0BESTnb   hcart2   No       UP
        TLD(1) Definition       DRIVE=3
  2   HPUltrium2-SCSI1       /dev/rmt/c12t0d1BESTnb   hcart2   No       UP
        TLD(1) Definition       DRIVE=4
  3   HPUltrium2-SCSI2       /dev/rmt/c13t0d1BESTnb   hcart2   No       UP
        TLD(1) Definition       DRIVE=1
  4   HPUltrium2-SCSI3       /dev/rmt/c13t0d2BESTnb   hcart2   No       UP
        TLD(1) Definition       DRIVE=2

Currently defined robotics are:
  TLD(1)     robotic path = /dev/rac/c13t0d0,
             volume database host = stmes11bkup

Now:

[stmfx11(root)]$ tpconfig -d
Index DriveName              DrivePath                Type    Shared   Status
***** *********              **********               ****    ******   ******
  0   D1                     /dev/rmt/c38t0d0BESTnb   hcart2   No       UP
        TLD(1) Definition       DRIVE=1
  1   D2                     /dev/rmt/c38t0d1BESTnb   hcart2   No       UP
        TLD(1) Definition       DRIVE=2
  2   D3                     /dev/rmt/c37t0d1BESTnb   hcart2   No       UP
        TLD(1) Definition       DRIVE=3
  3   D4                     /dev/rmt/c37t0d2BESTnb   hcart2   No       UP
        TLD(1) Definition       DRIVE=4

Currently defined robotics are:
  TLD(1)     robotic path = /dev/rac/c37t0d0,
             volume database host = ferrisbkup

[Stumpr2]

You should not change the volume database host.

Are any of the existing pools designated as a "scratch pool"?

# vmpool -listscratch
Scratch Pools
=============
Scratch