Views:

Summary



Backup job returned an error code of 2354 and failed to find a free tape even though free volumes exist in the pool.

Symptoms



The following errors are shown:

xxx.xxx.xxx.xxx ssjobhnd Fri May 13 21:44:46 2005 SNBJH_3259J ===== Done tape [000483] of job 1116028800: 3250434 blocks [106510221312 bytes] rc=4 (tape is full) =====

xxx.xxx.xxx.xxx ssjobhnd Fri May 13 21:44:46 2005 SNBJH_3038E *** ssdatmgr returned error 2354 (reqid=60, function ID=145) ***

xxx.xxx.xxx.xxx ssevthnd Fri May 13 21:44:46 2005 SNBEHT4235E 1440: *** Failed to find a free tape in tape pool MONTHLY_POOL: return code = 2354 ***

xxx.xxx.xxx.xxx ssevthnd Fri May 13 21:44:46 2005 SNBEHT4236E 1440: *** Media bits for getfreetape query: EMPTY NEW APPENDABLE ***

xxx.xxx.xxx.xxx ssevthnd Fri May 13 21:44:46 2005 SNBEHT3057E 1440: *** Last message from DB: Could not reserve any media at device (Tape1) using the specified pattern. ***

xxx.xxx.xxx.xxx ssjobhnd Fri May 13 21:44:46 2005 SNBJH_3045E *** Task 3 of job 1116028800 for node node_SVR disk E: failed ***



Resolution



Generally, this issue occurs when one or both of the below conditions are encountered:

1. The pools used for the job do not have enough media in a valid status to support the demand for a volser. In this case:

  • Verify that the media pool has enough tapes available to meet the demand.
  • Set up an alternate pool so that if a low water mark is hit, it will begin pulling tapes from this pool. This requires that the alternative pool have EMPTY, NEW, or APPENDABLE tapes within it.

2. You have unintentionally created a backup job that uses different media pools so that some tasks go to one pool and the other remaining task go to another pool that does not have enough tapes. In this case, verify that all tasks are pointing to the same pool.