EXIT STATUS 96 (unable to allocate new media for backup)

[BackupSysAdmin]

Still learning Netbackup. Came in this morning I saw several failed backups with Exit Status 96.  Results for the vxlogview is list below.  Would I need to just replace those tapes?, Any advise would be greatly appreciated.

4/29/2012 16:10:00.035 [RecoverableJob::writeBooleans] (ID:0000000003EB3828) flags=263(../RecoverableJob.cpp:101)
4/29/2012 16:10:00.035 V-116-215 [BaseJob::run] jobid=56370 submitted to nbjm for processing
4/29/2012 16:10:00.066 [RecoverableJob::writeBooleans] (ID:0000000003EB3828) flags=263(../RecoverableJob.cpp:101)
4/29/2012 16:10:00.066 [JobInstance::state] (0000000003B9E250) state=0(../JobInstance.cpp:311)
4/29/2012 16:10:00.066 V-117-56 [BackupJob::sendRequestToRB] requesting resources from RB for backup job (jobid=56370)
4/29/2012 16:10:00.066 V-118-227 [ResBroker_i::requestResources] received resource request ID {660BD955-2147-4495-BB7A-4B796C4E0EDA}, priority 0, secondary priority 26288, description THE_BACKUP_JOB-56370-{660BD955-2147-4495-BB7A-4B796C4E0EDA}
4/29/2012 16:10:00.066 [ResBroker_i::requestResources] RequestSeq:
Request=0 provider=MPXProvider resourcename=MpxRequest-56370 MPXGroupRequest maxmpx=1
    SubRequest=0 provider=DriveOperationProvider resourcename=jfsca0008-hcart-robot-tld-0 userSequence=0 RB::StorageUnitRequest { StorageUnitRequest { storageUnit=jfsca0008-hcart-robot-tld-0 mediaPool=MONTHLY_FULLS retentionLevel=8 mustUseLocalMediaServer=no failOnError=no mpxRequired=no mustBeNdmp=no getMaxFreeSpace=no minFreeSpaceKBytes=218593591 usageType=1 client=jfscem003 shareGroup=*ANY* } }
Request=1 provider=NamedResourceProvider resourcename=jfsca0008.NBU_CLIENT.MAXJOBS.jfscem003 CountedResourceRequest { max=99 }
Request=2 provider=NamedResourceProvider resourcename=jfsca0008.NBU_POLICY.MAXJOBS.JFSC-MANAGEMENT_SERVERS CountedResourceRequest { max=2147483647 }
4/29/2012 16:10:00.097 V-118-226 [ResBroker_i::evaluateOne] Evaluating request ID {660BD955-2147-4495-BB7A-4B796C4E0EDA}
4/29/2012 16:10:00.097 V-118-146 [ProviderManager::allocate] NamedResourceProvider returned Allocation Granted for request ID {660BD955-2147-4495-BB7A-4B796C4E0EDA}
4/29/2012 16:10:00.097 V-118-146 [ProviderManager::allocate] MPXProvider returned Resource is currently in use for request ID {660BD955-2147-4495-BB7A-4B796C4E0EDA}
4/29/2012 16:10:00.097 [Error] V-118-171 request ID {660BD955-2147-4495-BB7A-4B796C4E0EDA} failed with status 1 (Resource is currently in use); releasing 2 allocated resources
4/29/2012 16:10:00.097 [ResBroker_i::holdOne] tracking error status (RBErrorInfo: errorStatus=2005001 retryClass="RB Defined Retry" retryReason=25 retryText="AWAITING_RESOURCE 1335730200 jfsca0008-hcart-robot-tld-0 EMM_STATUS 2005001" retryResource=jfsca0008-hcart-robot-tld-0)
4/29/2012 16:10:56.711 V-118-226 [ResBroker_i::evaluateOne] Evaluating request ID {660BD955-2147-4495-BB7A-4B796C4E0EDA}
4/29/2012 16:10:56.711 V-118-146 [ProviderManager::allocate] NamedResourceProvider returned Allocation Granted for request ID {660BD955-2147-4495-BB7A-4B796C4E0EDA}
4/29/2012 16:10:56.711 V-118-146 [ProviderManager::allocate] MPXProvider returned Resource is currently in use for request ID {660BD955-2147-4495-BB7A-4B796C4E0EDA}
4/29/2012 16:10:56.711 [Error] V-118-171 request ID {660BD955-2147-4495-BB7A-4B796C4E0EDA} failed with status 1 (Resource is currently in use); releasing 2 allocated resources
4/29/2012 16:11:19.269 V-118-226 [ResBroker_i::evaluateOne] Evaluating request ID {660BD955-2147-4495-BB7A-4B796C4E0EDA}
4/29/2012 16:11:19.269 V-118-146 [ProviderManager::allocate] NamedResourceProvider returned Allocation Granted for request ID {660BD955-2147-4495-BB7A-4B796C4E0EDA}
4/29/2012 16:11:19.269 V-118-146 [ProviderManager::allocate] MPXProvider returned Resource is currently in use for request ID {660BD955-2147-4495-BB7A-4B796C4E0EDA}
4/29/2012 16:11:19.269 [Error] V-118-171 request ID {660BD955-2147-4495-BB7A-4B796C4E0EDA} failed with status 1 (Resource is currently in use); releasing 2 allocated resources
4/29/2012 16:11:19.300 V-118-226 [ResBroker_i::evaluateOne] Evaluating request ID {660BD955-2147-4495-BB7A-4B796C4E0EDA}
4/29/2012 16:11:19.300 V-118-146 [ProviderManager::allocate] NamedResourceProvider returned Allocation Granted for request ID {660BD955-2147-4495-BB7A-4B796C4E0EDA}
4/29/2012 16:11:19.300 V-118-146 [ProviderManager::allocate] MPXProvider returned Resource is currently in use for request ID {660BD955-2147-4495-BB7A-4B796C4E0EDA}
4/29/2012 16:11:19.300 [Error] V-118-171 request ID {660BD955-2147-4495-BB7A-4B796C4E0EDA} failed with status 1 (Resource is currently in use); releasing 2 allocated resources
4/29/2012 16:12:39.782 V-118-226 [ResBroker_i::evaluateOne] Evaluating request ID {660BD955-2147-4495-BB7A-4B796C4E0EDA}
4/29/2012 16:12:39.782 V-118-146 [ProviderManager::allocate] NamedResourceProvider returned Allocation Granted for request ID {660BD955-2147-4495-BB7A-4B796C4E0EDA}
4/29/2012 16:12:39.782 V-118-146 [ProviderManager::allocate] MPXProvider returned Resource is currently in use for request ID {660BD955-2147-4495-BB7A-4B796C4E0EDA}
4/29/2012 16:12:39.782 [Error] V-118-171 request ID {660BD955-2147-4495-BB7A-4B796C4E0EDA} failed with status 1 (Resource is currently in use); releasing 2 allocated resources
4/29/2012 16:17:39.807 V-118-226 [ResBroker_i::evaluateOne] Evaluating request ID {660BD955-2147-4495-BB7A-4B796C4E0EDA}
4/29/2012 16:17:39.807 V-118-146 [ProviderManager::allocate] NamedResourceProvider returned Allocation Granted for request ID {660BD955-2147-4495-BB7A-4B796C4E0EDA}
4/29/2012 16:17:39.807 V-118-146 [ProviderManager::allocate] MPXProvider returned Resource is currently in use for request ID {660BD955-2147-4495-BB7A-4B796C4E0EDA}
4/29/2012 16:17:39.807 [Error] V-118-171 request ID {660BD955-2147-4495-BB7A-4B796C4E0EDA} failed with status 1 (Resource is currently in use); releasing 2 allocated resources
4/29/2012 16:18:07.497 [allocateTwin] INITIATING:
4/29/2012 16:18:07.497 [allocateTwin] masterServer = jfsca0008, client = jfscem003, jobType = 1, capabilityFlags = 0, fatPipePreference = 0, statusOnly = 0, numberOfCopies = 1, kbytesNeeded = 218593591
4/29/2012 16:18:07.497 [allocateTwin] Twin_Record: STUIdentifier = jfsca0008-hcart-robot-tld-0, STUIdentifierType = 1, PoolName = MONTHLY_FULLS, MediaSharingGroup = *ANY*, RetentionLevel = 8, RequiredMediaServer = , PreferredMediaServer = , RequiredDiskVolumeMediaId = , RequiredStorageUnitName = , GetMaxFreeSpaceSTU = 0, CkptRestart = 0, CkptRestartSTUType = 0, CkptRestartSTUSubType = -1, CkptRestartSTUName = , CkptRestartMediaServer = , CkptRestartDiskGroupName = , CkptRestartDiskGroupServerType = , MpxEnabled = 0, MustUseLocalMediaServer = 0
4/29/2012 16:18:07.497 V-118-226 [ResBroker_i::evaluateOne] Evaluating request ID {660BD955-2147-4495-BB7A-4B796C4E0EDA}
4/29/2012 16:18:07.497 V-118-146 [ProviderManager::allocate] NamedResourceProvider returned Allocation Granted for request ID {660BD955-2147-4495-BB7A-4B796C4E0EDA}
4/29/2012 16:18:07.544 [BackupJob::ERMEvent] (0000000003B9E250) initial resource request failed, copy#=-1, EMM status=No media is available, NBU status=96(../BackupJob.cpp:333)
4/29/2012 16:18:07.544 [allocateTwin] EXIT INFO:
4/29/2012 16:18:07.544 [allocateTwin] EXIT STATUS = 2005000 (EMM_ERROR_MDS_MediaUnavailable, No media is available)

4/29/2012 16:18:07.544 V-118-201 [EMMAccess::allocateTwin] request to allocate STU (Master Server jfsca0008, Client jfscem003, Job Type 1, STU jfsca0008-hcart-robot-tld-0, STU Type 1, Media Pool MONTHLY_FULLS, Retention Level 8, Capabilities 0, Fibre Transport Preference 0) returned 2005000
4/29/2012 16:18:07.544 V-118-146 [ProviderManager::allocate] MPXProvider returned Not Enough Valid Resources for request ID {660BD955-2147-4495-BB7A-4B796C4E0EDA}
4/29/2012 16:18:07.544 [Error] V-118-171 request ID {660BD955-2147-4495-BB7A-4B796C4E0EDA} failed with status 0 (Not Enough Valid Resources); releasing 2 allocated resources
4/29/2012 16:18:07.544 [ResBroker_i::evaluateOne] resource request fails, requestId={660BD955-2147-4495-BB7A-4B796C4E0EDA}, userId=jobid=56370, status=2005000, birthTime=1335730200, timeToFirstEval=0 sec, timeToSuccessOrFailure=487 sec, numberOfTimesEvaluated=7
4/29/2012 16:18:07.544 V-118-108 [ResBroker_i::failOne] failing resource request ID {660BD955-2147-4495-BB7A-4B796C4E0EDA}, status 2005000
4/29/2012 16:18:07.544 V-118-137 [EMMProvider::getDriveForWaitingRequest] allocation information for request ID {660BD955-2147-4495-BB7A-4B796C4E0EDA} is not found
4/29/2012 16:18:07.544 V-118-255 [CorbaCall_requestFailed::execute] sending failure of request to nbjm for request ID {660BD955-2147-4495-BB7A-4B796C4E0EDA}, error code 2005000, reason not enough valid resources
4/29/2012 16:18:07.560 V-116-216 [RecoverableJob::doJobCompletion] jobid=56370 completed with status 96
4/29/2012 16:18:07.560 [Error] V-117-131  NBU status: 96, EMM status: No media is available

4/29/2012 16:18:07.560 [JobInstance::state] (0000000003B9E250) state=1(../JobInstance.cpp:311)
4/29/2012 16:18:07.560 [JobInstance::state] (0000000003B9E250) state=1(../JobInstance.cpp:311)
4/29/2012 16:18:07.560 [BackupJob::sendNotifications] (0000000003B9E250) disable resume=false, brm started=false(../BackupJob.cpp:2079)
4/29/2012 16:18:07.560 V-117-239 [BackupJob::terminateThisJob] terminated job, jobid=56370, status=96
4/29/2012 16:18:07.560 [BackupJob::~BackupJob] (dump Backup Job):
**************************
*BackupJob               *
(jobid=56370 jobtype=0)
**************************
isStdBackup       = true
backupType        = 0
subtype           = 0
mpxid             = {00000000-0000-0000-0000-000000000000}
maxmpx            = 1
Birthtime         = 0
backupid          =
Active pid        = 0
Job Count         = 1
IPaddr            = 0
currentThrottle   = -1
estimatedSize     = 218593591
estimatedFileCount= 60864
suspendable       = 0
progressLogTimerID= -1
localBackup       = 0
policy            = JFSC-MANAGEMENT_SERVERS
Num copies        = 1
Include_file#     = 5
resourceCount     = 1
Stu               = jfsca0008-hcart-robot-tld-0
Pool              = MONTHLY_FULLS
Retention         = 8
UseLocal          = false
(../BackupJob.cpp:289)
4/29/2012 16:18:07.591 V-116-222 [RecoverableJob::registerForRetryTime] retry of jobid=56370 schedule for 4/29/2012 4:28:07 PM
4/29/2012 16:18:07.591 [Info] V-116-14 CLIENT jfscem003  POLICY JFSC-MANAGEMENT_SERVERS  SCHED Management_Monthly  EXIT STATUS 96 (unable to allocate new media for backup, storage unit has none available)
4/29/2012 16:18:07.607 [Error] V-116-85 backup of client jfscem003 exited with status 96 (unable to allocate new media for backup, storage unit has none available)
4/29/2012 16:18:07.622 [RecoverableJob::writeBooleans] (ID:0000000003EB3828) flags=263(../RecoverableJob.cpp:101)
4/29/2012 16:28:07.001 [RecoverableJob::writeBooleans] (ID:0000000003EB3828) flags=263(../RecoverableJob.cpp:101)
4/29/2012 16:28:07.001 V-116-215 [RecoverableJob::run_SUBMIT_RETRY] jobid=56370 submitted to nbjm for processing
4/29/2012 16:28:07.048 [RecoverableJob::writeBooleans] (ID:0000000003EB3828) flags=263(../RecoverableJob.cpp:101)
4/29/2012 16:28:07.048 [JobInstance::state] (0000000003B9BA10) state=0(../JobInstance.cpp:311)
4/29/2012 16:28:07.048 V-117-56 [BackupJob::sendRequestToRB] requesting resources from RB for backup job (jobid=56370)
4/29/2012 16:28:07.048 V-118-227 [ResBroker_i::requestResources] received resource request ID {90FFB4A3-406D-49C1-9990-D9F132DC3930}, priority 0, secondary priority 26288, description THE_BACKUP_JOB-56370-{90FFB4A3-406D-49C1-9990-D9F132DC3930}
4/29/2012 16:28:07.048 [ResBroker_i::requestResources] RequestSeq:
Request=0 provider=MPXProvider resourcename=MpxRequest-56370 MPXGroupRequest maxmpx=1
    SubRequest=0 provider=DriveOperationProvider resourcename=jfsca0008-hcart-robot-tld-0 userSequence=0 RB::StorageUnitRequest { StorageUnitRequest { storageUnit=jfsca0008-hcart-robot-tld-0 mediaPool=MONTHLY_FULLS retentionLevel=8 mustUseLocalMediaServer=no failOnError=no mpxRequired=no mustBeNdmp=no getMaxFreeSpace=no minFreeSpaceKBytes=218593591 usageType=1 client=jfscem003 shareGroup=*ANY* } }
Request=1 provider=NamedResourceProvider resourcename=jfsca0008.NBU_CLIENT.MAXJOBS.jfscem003 CountedResourceRequest { max=99 }
Request=2 provider=NamedResourceProvider resourcename=jfsca0008.NBU_POLICY.MAXJOBS.JFSC-MANAGEMENT_SERVERS CountedResourceRequest { max=2147483647 }
4/29/2012 16:28:07.064 V-118-226 [ResBroker_i::evaluateOne] Evaluating request ID {90FFB4A3-406D-49C1-9990-D9F132DC3930}
4/29/2012 16:28:07.064 V-118-146 [ProviderManager::allocate] NamedResourceProvider returned Allocation Granted for request ID {90FFB4A3-406D-49C1-9990-D9F132DC3930}
4/29/2012 16:28:07.064 V-118-146 [ProviderManager::allocate] MPXProvider returned Resource is currently in use for request ID {90FFB4A3-406D-49C1-9990-D9F132DC3930}
4/29/2012 16:28:07.064 [Error] V-118-171 request ID {90FFB4A3-406D-49C1-9990-D9F132DC3930} failed with status 1 (Resource is currently in use); releasing 2 allocated resources
4/29/2012 16:28:07.064 [ResBroker_i::holdOne] tracking error status (RBErrorInfo: errorStatus=2005001 retryClass="RB Defined Retry" retryReason=25 retryText="AWAITING_RESOURCE 1335731287 jfsca0008-hcart-robot-tld-0 EMM_STATUS 2005001" retryResource=jfsca0008-hcart-robot-tld-0)
4/29/2012 16:30:56.701 V-118-226 [ResBroker_i::evaluateOne] Evaluating request ID {90FFB4A3-406D-49C1-9990-D9F132DC3930}
4/29/2012 16:30:56.701 V-118-146 [ProviderManager::allocate] NamedResourceProvider returned Allocation Granted for request ID {90FFB4A3-406D-49C1-9990-D9F132DC3930}
4/29/2012 16:30:56.701 V-118-146 [ProviderManager::allocate] MPXProvider returned Resource is currently in use for request ID {90FFB4A3-406D-49C1-9990-D9F132DC3930}
4/29/2012 16:30:56.701 [Error] V-118-171 request ID {90FFB4A3-406D-49C1-9990-D9F132DC3930} failed with status 1 (Resource is currently in use); releasing 2 allocated resources
4/29/2012 16:32:39.882 V-118-226 [ResBroker_i::evaluateOne] Evaluating request ID {90FFB4A3-406D-49C1-9990-D9F132DC3930}
4/29/2012 16:32:39.882 V-118-146 [ProviderManager::allocate] NamedResourceProvider returned Allocation Granted for request ID {90FFB4A3-406D-49C1-9990-D9F132DC3930}
4/29/2012 16:32:39.882 V-118-146 [ProviderManager::allocate] MPXProvider returned Resource is currently in use for request ID {90FFB4A3-406D-49C1-9990-D9F132DC3930}
4/29/2012 16:32:39.882 [Error] V-118-171 request ID {90FFB4A3-406D-49C1-9990-D9F132DC3930} failed with status 1 (Resource is currently in use); releasing 2 allocated resources
4/29/2012 16:32:57.978 [allocateTwin] INITIATING:
4/29/2012 16:32:57.978 [allocateTwin] masterServer = jfsca0008, client = jfscem003, jobType = 1, capabilityFlags = 0, fatPipePreference = 0, statusOnly = 0, numberOfCopies = 1, kbytesNeeded = 218593591
4/29/2012 16:32:57.978 [allocateTwin] Twin_Record: STUIdentifier = jfsca0008-hcart-robot-tld-0, STUIdentifierType = 1, PoolName = MONTHLY_FULLS, MediaSharingGroup = *ANY*, RetentionLevel = 8, RequiredMediaServer = , PreferredMediaServer = , RequiredDiskVolumeMediaId = , RequiredStorageUnitName = , GetMaxFreeSpaceSTU = 0, CkptRestart = 0, CkptRestartSTUType = 0, CkptRestartSTUSubType = -1, CkptRestartSTUName = , CkptRestartMediaServer = , CkptRestartDiskGroupName = , CkptRestartDiskGroupServerType = , MpxEnabled = 0, MustUseLocalMediaServer = 0
4/29/2012 16:32:57.978 V-118-226 [ResBroker_i::evaluateOne] Evaluating request ID {90FFB4A3-406D-49C1-9990-D9F132DC3930}
4/29/2012 16:32:57.978 V-118-146 [ProviderManager::allocate] NamedResourceProvider returned Allocation Granted for request ID {90FFB4A3-406D-49C1-9990-D9F132DC3930}
4/29/2012 16:32:58.025 [allocateTwin] EXIT INFO:
4/29/2012 16:32:58.025 [allocateTwin] EXIT STATUS = 2005000 (EMM_ERROR_MDS_MediaUnavailable, No media is available)

4/29/2012 16:32:58.025 V-118-201 [EMMAccess::allocateTwin] request to allocate STU (Master Server jfsca0008, Client jfscem003, Job Type 1, STU jfsca0008-hcart-robot-tld-0, STU Type 1, Media Pool MONTHLY_FULLS, Retention Level 8, Capabilities 0, Fibre Transport Preference 0) returned 2005000
4/29/2012 16:32:58.025 V-118-146 [ProviderManager::allocate] MPXProvider returned Not Enough Valid Resources for request ID {90FFB4A3-406D-49C1-9990-D9F132DC3930}
4/29/2012 16:32:58.025 [Error] V-118-171 request ID {90FFB4A3-406D-49C1-9990-D9F132DC3930} failed with status 0 (Not Enough Valid Resources); releasing 2 allocated resources
4/29/2012 16:32:58.025 [ResBroker_i::evaluateOne] resource request fails, requestId={90FFB4A3-406D-49C1-9990-D9F132DC3930}, userId=jobid=56370, status=2005000, birthTime=1335731287, timeToFirstEval=0 sec, timeToSuccessOrFailure=291 sec, numberOfTimesEvaluated=4
4/29/2012 16:32:58.025 V-118-108 [ResBroker_i::failOne] failing resource request ID {90FFB4A3-406D-49C1-9990-D9F132DC3930}, status 2005000
4/29/2012 16:32:58.041 [BackupJob::ERMEvent] (0000000003B9BA10) initial resource request failed, copy#=-1, EMM status=No media is available, NBU status=96(../BackupJob.cpp:333)
4/29/2012 16:32:58.041 [Error] V-117-131  NBU status: 96, EMM status: No media is available

4/29/2012 16:32:58.041 [JobInstance::state] (0000000003B9BA10) state=1(../JobInstance.cpp:311)
4/29/2012 16:32:58.041 [JobInstance::state] (0000000003B9BA10) state=1(../JobInstance.cpp:311)
4/29/2012 16:32:58.041 [BackupJob::sendNotifications] (0000000003B9BA10) disable resume=false, brm started=false(../BackupJob.cpp:2079)
4/29/2012 16:32:58.041 V-117-239 [BackupJob::terminateThisJob] terminated job, jobid=56370, status=96
4/29/2012 16:32:58.041 [BackupJob::~BackupJob] (dump Backup Job):
**************************
*BackupJob               *
(jobid=56370 jobtype=0)
**************************
isStdBackup       = true
backupType        = 0
subtype           = 0
mpxid             = {00000000-0000-0000-0000-000000000000}
maxmpx            = 1
Birthtime         = 0
backupid          =
Active pid        = 0
Job Count         = 1
IPaddr            = 0
currentThrottle   = -1
estimatedSize     = 218593591
estimatedFileCount= 60864
suspendable       = 0
progressLogTimerID= -1
localBackup       = 0
policy            = JFSC-MANAGEMENT_SERVERS
Num copies        = 1
Include_file#     = 5
resourceCount     = 1
Stu               = jfsca0008-hcart-robot-tld-0
Pool              = MONTHLY_FULLS
Retention         = 8
UseLocal          = false
(../BackupJob.cpp:289)
4/29/2012 16:32:58.041 V-118-137 [EMMProvider::getDriveForWaitingRequest] allocation information for request ID {90FFB4A3-406D-49C1-9990-D9F132DC3930} is not found
4/29/2012 16:32:58.041 V-118-255 [CorbaCall_requestFailed::execute] sending failure of request to nbjm for request ID {90FFB4A3-406D-49C1-9990-D9F132DC3930}, error code 2005000, reason not enough valid resources
4/29/2012 16:32:58.056 V-116-216 [RecoverableJob::doJobCompletion] jobid=56370 completed with status 96
4/29/2012 16:32:58.056 V-116-221 [RecoverableJob::run_PROCESS_STATUS] retry of jobid=56370 exceeds failure history, ending retries
4/29/2012 16:32:58.056 [RecoverableJob::writeBooleans] (ID:0000000003EB3828) flags=263(../RecoverableJob.cpp:101)
4/29/2012 16:32:58.056 [PemTask::taskComplete] (ID:0000000003EB3828) Active subtask count=0(../PemTask.cpp:527)
4/29/2012 16:32:58.056 [Info] V-116-14 CLIENT jfscem003  POLICY JFSC-MANAGEMENT_SERVERS  SCHED Management_Monthly  EXIT STATUS 96 (unable to allocate new media for backup, storage unit has none available)
4/29/2012 16:32:58.072 [Error] V-116-85 backup of client jfscem003 exited with status 96 (unable to allocate new media for backup, storage unit has none available)

[Will_Restore]

Recommended Action:

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 and Linux, this script is in:

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

On Windows, the script is in:

install_path\NetBackup\bin\goodies\available_media.cmd

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 theEMMdatabase 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 and Linux) 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 and Linux, 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.

[Marianne · Accepted solution]

Have a look at this troubleshooting wizard for status 96:

http://www.symantec.com/business/support/index?page=answers&type=wizard&wizardid=NBU090&wizardstepid=1A&question_box=status+code+96

Please work through it step-by-step and let us know...