My organization uses BRMS to perform our backup activities. Each week, on Saturday night, a full system save is completed, and then each weeknight, an incremental save is done. The incremental save is done prior to our batch. Our iSeries is housed at a data center, that manages the tapes, and also monitors our iSeries. In the event of a problem with a batch job, the datacenter personel, contact an oncall programmer from my company, who in turn deals with the issue.
Lately, we have been experiencing issues with the tapes that are used for our backups. At least once a week, our oncall staff are called, indicating that there is a problem with the backups, and every time, the problem is due to a bad tape. The solution is then to have the bad tape removed from the silo, and the backups are then restarted, resulting in a 90 minute delay (typically) to the overnight batch.
Is there a setting in BRMS, that can be changed, that would force the backup process to get a new tape, in the event that a bad one is encountered? I know of other backup products that offer this; does BRMS have this capability?
Free Guide: Managing storage for virtual environments
Complete a brief survey to get a complimentary 70-page whitepaper featuring the best methods and solutions for your virtual environment, as well as hypervisor-specific management advice from TechTarget experts. Don’t miss out on this exclusive content!