Manage Learn to apply best practices and optimize your operations.

BRMS for our backups

We are currently using BRMS for our backups. When I have two full tape racks (20 tapes) BRMS looks for the oldest tape to use and not what is in the slots. There has been times when the backup fails just because it is looking for specific tapes. This might occur when I add new tapes into the inventory -- since they don't have an expiration date, BRMS wants them first.

I haven't had this problem. I set up a scratch pool of tapes and any tape that is available for use will be written on. This is described in the following excerpt taken from the BRMS Redbook:

* Scratch pool:

With a scratch pool, tapes are not allocated to specific sets. When a tape is required for output, any available scratch tape can be used. This requires that you keep an inventory of all tapes so that available tapes can be identified. The advantage is that tapes do not need to be allocated in advance. If the inventory is well managed, tape usage can be balanced rather than some tapes being used more than others. You can control the retention periods down to the file level on the tape. A scratch pool is easily managed by BRMS/400, which is the preferred option.

Do you have a scratch pool defined in BRMS or are you using tape sets? If you do have a scratch pool defined and you continue to have this problem, I would recommend that you contact IBM Support Line and report this as a bug.


Ask the Experts yourself: Our Backup & Recovery gurus are waiting to answer your questions.

Search400.com's targeted search engine: Get relevant information on backup & recovery.

Check out this Search400.com Featured Topic on backup & recovery.

Dig Deeper on Data backup, storage and retrieval on iSeries

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.