EXIT_STATUS 35

[Jotaerre]

Hi there, i'm having this issue, but i do have available medias in the SCRATCH and BCV_VOB03 pools. And according to the media list i don't have any FROOZEN or SUSPENDED media.


vmdb_query_scratch_bypool2: unable to unpack string from server: volume does not exist in database (35)
01:28:29.519 [23799] <16> vmdb_query_scratch_bypool2: query_scratchbypool2 request status: volume does not exist in database (35)
01:28:29.548 [23799] <16> select_media: Media Manager volume pool BCV_VOB03 has no more unassigned media in robotic device TLD(0)
01:28:29.549 [23799] <2> bptm: EXITING with status 96 <----------

Does anyone experienced this?

REgards,

 

[PGPhantom]

unable to allocate new media for backup, storage unit has none available
The tape manager (bptm) could not allocate a new volume for backups. This indicates that the storage unit has no more volumes available in the volume pool for this backup. Note that NetBackup will not change storage units during the backup.

Try the following:

Check the NetBackup Problems report to determine the storage unit that is out of media.

1. If the storage unit is a robot and there are empty slots, add more volumes (remember to specify the correct volume pool).

* If there are no empty slots, move some media to nonrobotic and then add new volumes.

* If you are having difficulty keeping track of your available volumes, try the available_media script:

On UNIX, this script is in:

/usr/openv/netbackup/bin/goodies/available_media

On Windows, the script is in:

install_pathNetBackupbingoodiesavailable_media.cmd

This script lists all volumes in the Media Manager volume configuration, and augments that list with information on the volumes currently assigned to NetBackup.

2. Set up a scratch volume pool as a reserve of unassigned tapes. If NetBackup needs a new tape and no more tapes are available in the current volume pool, NetBackup moves a tape from the scratch pool into the volume pool that the backup is using.

3. If the storage unit and volume pool appear to have media, verify the following:

* Volume is not FROZEN or SUSPENDED.

Check for this condition by using the NetBackup Media List report. If the volume is frozen or suspended, use the bpmedia command to unfreeze or unsuspend it (if that is desired).

* Volume has not expired or exceeded its maximum number of mounts.

* Volume Database Host name for the device is correct.

If you change the Volume Database Host name, stop and restart the Media Manager device daemon, ltid, (if the server is UNIX) or the NetBackup Device Manager service (if the server is a Windows system).

* The correct host is specified for the storage unit in the NetBackup configuration.

The host connection should be the server (master or media) that has drives connected to it.

* The Media Manager volume configuration has media in the correct volume pool and unassigned or active media is available at the required retention level.

Use the NetBackup Media List report to show the retention levels, volume pools, and status (active and so on) for all volumes. Use the NetBackup Media Summary report to check for active volumes at the correct retention levels.

4. In some configurations, the NetBackup bptm process is rejected when requesting media from the vmd process (UNIX) or the NetBackup Volume Manager service (Windows) because that process or service cannot determine the name of the host that is making the request.

This can be due to incorrect network configuration involving:

* Multiple network interfaces

* /etc/resolv.conf on those UNIX systems that use it

* Running DNS and not having reverse addressing configured

5. Create bptm and vmd debug log directories and retry the operation.

6. Examine the bptm debug log to verify that bptm is connecting to the correct system. If an error is logged, examine the vmd log.

On UNIX, the vmd log is:

/usr/openv/volmgr/debug/daemon/log.xxxxxx

On Windows, the vmd log is:

install_pathVolmgrdebugdaemonxxxxxx.log

7. If this is a new storage unit, and this is the first attempt to use it, stop and restart NetBackup on the master server.

Note: The bptm debug logs (in verbose mode) usually show the NetBackup media selection process.

 

[creakyjoe]

(assuming you are on UNIX), sounds like you should introduce scripts that repopulate the scratch pool regularly. NBU (up to 4.5 anyway) happily pulls 'em from scratch, but doesn't moved expired tapes back, instead leaves them in existing pool, then when wants more scratch, more often than not pulls from scratch pool, not existing pool

Rich (wondering if this feature of NBU will ever be fully implemented)