Removing volume/media in netbackup

[kilafish]

Hi,

I am trying to remove a volume from netbackup. It is complaining with an error saying "unable to allocate new media for backup, storage unit has none avaiable".

What has happened it that there is a volume assigned in netbackup where there is no physical tape. When I try to delete it to complains "Could not delete {label}. It is assigned.

My question is, how can I work around this? How can I de-assign it, so it can be deleted?

Thanks.

 

[Apricot]

Check the Enterprise NetBackup Problems report to determine
the storage unit that is out of media. If the storage unit
is a robotic device and there are empty slots, add more
media and enter them in the volume configuration,
remembering to specify the correct volume pool. If there
are no empty slots, consider moving some media offline and
entering new media in their place.

If you are having difficulty keeping track of your available media, you may want
to try the following script:

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

This script provides a convenient way for an administrator to list ALL Enterprise
NetBackup volumes in the volume configuration, and augment that list with
information on the volumes currently assigned to Enterprise NetBackup.

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

1. Media is not FROZEN or SUSPENDED.

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

#/usr/openv/netbackup/bin/admincmd/bpmedia -ev <mediaid> unfreeze

-or-

#/usr/openv/netbackup/bin/admincmd/bpmedia -ev <mediaid> unsuspend

If the tape is in DBbackup state, you should relabel the tape.

2. If the available_media script informs that the tape is ok and available, check the retension policy of the backup by running the following command:

#/usr/openv/netbackup/bin/goodies/bpmedialist

search for the media-id that is having the problem:

id rl images allocated last updated den kbytes restores
vimages expiration last read <---------------------->
--------------------------------------------------------------------------------
A00001 0 6 04/02/99 13:55 04/07/99 09:16 4mm 243434 1
6 04/14/99 09:16 04/07/99 10:04 available

The rl field indicates that the retension level is 0.

To list out all the attributes for the class that is backing up to the tape in
question, run:

#/usr/openv/netbackup/bin/admincmd/bpcllist <classname> -U

If the retention levels differ then you may want to label a new tape for that pool or add the following entry in the bp.conf file:

ALLOW_MULTIPLE_RETENTIONS_PER_MEDIA

This entry will allow NBU to write to tapes that *may* contain old NBU client data. Unless this entry is present, each tape can contain backups of only a SINGLE retention level.

3. Media has not expired or exceeded its maximum number of mounts.

4. Volume Database Host name for the devices are correct.

If you change the Volume Database Host name, stop and restart the Media Manager device daemon, ltid.

5. Host connection for the storage unit is correct (use the storage-unit-management options in the Enterprise NetBackup administration interface).

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

6. The volume configuration has media in the correct volume pool and you have available unassigned media or active media at the required retention level.

The Enterprise NetBackup Media List report shows the retention levels, volume pools, and status (active and so on) for all media ID's. The Enterprise NetBackup Media Summary provides a quick check for active media at the correct retention levels.

7. In some configurations (most often when using DNS or when multiple network interfaces are configured on a system), the Enterprise NetBackup bptm process
may be rejected when requesting media from the vmd process because vmd cannot determine the name of the host that is making the request.

Examine the bptm activity log to verify that bptm is connecting to the correct system. If an error is logged, you may need to examine the vmd log.

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

Problems such as this are frequently 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

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

 

[Apricot]

Check the Enterprise NetBackup Problems report to determine
the storage unit that is out of media. If the storage unit
is a robotic device and there are empty slots, add more
media and enter them in the volume configuration,
remembering to specify the correct volume pool. If there
are no empty slots, consider moving some media offline and
entering new media in their place.

If you are having difficulty keeping track of your available media, you may want
to try the following script:

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

This script provides a convenient way for an administrator to list ALL Enterprise
NetBackup volumes in the volume configuration, and augment that list with
information on the volumes currently assigned to Enterprise NetBackup.

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

1. Media is not FROZEN or SUSPENDED.

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

#/usr/openv/netbackup/bin/admincmd/bpmedia -ev <mediaid> unfreeze

-or-

#/usr/openv/netbackup/bin/admincmd/bpmedia -ev <mediaid> unsuspend

If the tape is in DBbackup state, you should relabel the tape.

2. If the available_media script informs that the tape is ok and available, check the retension policy of the backup by running the following command:

#/usr/openv/netbackup/bin/goodies/bpmedialist

search for the media-id that is having the problem:

id rl images allocated last updated den kbytes restores
vimages expiration last read <---------------------->
--------------------------------------------------------------------------------
A00001 0 6 04/02/99 13:55 04/07/99 09:16 4mm 243434 1
6 04/14/99 09:16 04/07/99 10:04 available

The rl field indicates that the retension level is 0.

To list out all the attributes for the class that is backing up to the tape in
question, run:

#/usr/openv/netbackup/bin/admincmd/bpcllist <classname> -U

If the retention levels differ then you may want to label a new tape for that pool or add the following entry in the bp.conf file:

ALLOW_MULTIPLE_RETENTIONS_PER_MEDIA

This entry will allow NBU to write to tapes that *may* contain old NBU client data. Unless this entry is present, each tape can contain backups of only a SINGLE retention level.

3. Media has not expired or exceeded its maximum number of mounts.

4. Volume Database Host name for the devices are correct.

If you change the Volume Database Host name, stop and restart the Media Manager device daemon, ltid.

5. Host connection for the storage unit is correct (use the storage-unit-management options in the Enterprise NetBackup administration interface).

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

6. The volume configuration has media in the correct volume pool and you have available unassigned media or active media at the required retention level.

The Enterprise NetBackup Media List report shows the retention levels, volume pools, and status (active and so on) for all media ID's. The Enterprise NetBackup Media Summary provides a quick check for active media at the correct retention levels.

7. In some configurations (most often when using DNS or when multiple network interfaces are configured on a system), the Enterprise NetBackup bptm process
may be rejected when requesting media from the vmd process because vmd cannot determine the name of the host that is making the request.

Examine the bptm activity log to verify that bptm is connecting to the correct system. If an error is logged, you may need to examine the vmd log.

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

Problems such as this are frequently 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

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