# bpdbm -ctime 1441252847
1441252847 = Thu Sep 03 06:00:47 2015

or use GNU awk

# echo 1441252847 | gawk '{ print strftime("%Y-%m-%d %H:%M:%S",$0) }'
2015-09-03 06:00:47

# bperror -S 96
unable to allocate new media for backup, storage unit has none available
The NetBackup Resource Broker (nbrb) did not allocate a new volume for backups. This error indicates that the storage unit has no more volumes available in the volume pool that is specified for this backup. Note that NetBackup does not change storage units during the backup.

# bperror -S 96 -r
unable to allocate new media for backup, storage unit has none available
The NetBackup Resource Broker (nbrb) did not allocate a new volume for backups. This error indicates that the storage unit has no more volumes available in the volume pool that is specified for this backup. Note that NetBackup does not change storage units during the backup.

Check the NetBackup Problems report to determine the storage unit that is out of media.
* If the storage unit is a robot with 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 have 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_path\NetBackup\bin\goodies\available_media.cm
d
This script lists all volumes in the volume configuration, and augments that list with information on the volumes currently assigned to NetBackup.
* Set up a scratch volume pool as a reserve of unassigned tapes. If NetBackup needs a new tape and none are available in the current volume pool, it does the following: Moves a tape from the scratch pool into the volume pool that the backup uses.
* 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 wanted).
* Volume has not expired or exceeded its maximum number of mounts.
* The EMM database host name for the device is correct.
If you change the EMM database host name, stop and restart the following: The Media Manager device daemon, ltid, (if the server is UNIX or Linux) 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) with drives connected to it.
* The Media and Device Management volume configuration has media in the correct volume pool. 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.
* The NetBackup bptm process is rejected when it requests media from the vmd process (UNIX) or the NetBackup Volume Manager service (Windows). The cause of this problem is that the process or service cannot determine the name of the host that makes the request.
This error can be due to an incorrect network configuration that involves the following:
* Multiple network interfaces
* /etc/resolv.conf on those UNIX or Linux systems that use it
* Running DNS with reverse addressing not configured
* Create bptm and vmd debug log directories and retry the operation.
* Examine the bptm debug log to verify that bptm connects 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_path\Volmgr\debug\daemon\xxxxxx.log
* If this storage unit is new and this attempt to use it is the first, stop and restart NetBackup on the master server.
Note
The mds unified logging files (OID 143) usually show the NetBackup media selection process.
More troubleshooting information in a wizard format is available for this status code.
http://www.symantec.com/business/support/index?StatusCode=96
Click here to view technical notes and other information in the Symantec Knowledge Base about this status code.

# bpexpdate -m L30000 -d 0 -force
Media L30000 is due to expire at 01/01/1970 01:00:00
Are you sure that the data on this media is not critical to
your business, and you are sure you want to delete L30000 y/n (n)?

lsof -n -P -p $(pgrep "bpbkar|bpfilter" | xargs | tr ' ' ',') | grep -v REG