When running a 'q libv' recently we noticed many Private DbBackup tapes listed, nearly half the library capacity.
The correct tapes are listed in the DR plan and are checked out and sent to vault, and they are retrieved from vault on schedule. It seems maybe they are not always going to scratch on checkin?
We use a scheduled 'prepare' for DR and a scheduled 'del volhist type=all' for general volumes. I confirmed the DR backup days setting is set to 3. My understanding from other posts here is that if you use the DRM system, expiration of DBB should be handled by that and not a 'del volhist type=dbb' type command.
I wanted to check with everyone here before I ran any hasty commands. I was planning to try a 'delete volhist type=dbbackup todate=today-3' and then checkout and back in the offending DbBackup tapes. I think something else might be going on, as it had been running file for quite some time.
Thanks!
The correct tapes are listed in the DR plan and are checked out and sent to vault, and they are retrieved from vault on schedule. It seems maybe they are not always going to scratch on checkin?
We use a scheduled 'prepare' for DR and a scheduled 'del volhist type=all' for general volumes. I confirmed the DR backup days setting is set to 3. My understanding from other posts here is that if you use the DRM system, expiration of DBB should be handled by that and not a 'del volhist type=dbb' type command.
I wanted to check with everyone here before I ran any hasty commands. I was planning to try a 'delete volhist type=dbbackup todate=today-3' and then checkout and back in the offending DbBackup tapes. I think something else might be going on, as it had been running file for quite some time.
Thanks!