ILCattivo
ADSM.ORG Senior Member
I am fairly new to the realms of DRM and have previously used the del volhist type=dbs cmd to remove older TSM db backups.
Now I have inherited a few TSM Servers running DRM (7.1.5) and have found both the ExpireDBbackupdays setting and del volhist type=db? applied. IBM do not recommend both to be used at the same time and I have seen this first hand recently when Tape volumes disappear off the radar. So, I wanted to gauge how best to configure a TSM server where the following DB backups are taking place under a DRM environment.
backup db type=dbs devcl=<FileClass>
backup db type=FULL devcl=<LTOClass>
q drmstat...
DB backup Series Expiration days: 3
Now, I understand that DRM should take care of those db backups sent to a Tape file Class. (no probs there) So how does one manage the dbs ones sent to tape without using the 'del volhist type=dbs' cmd, which if set incorrectly can remove volume history from the DB?
Thanks
Now I have inherited a few TSM Servers running DRM (7.1.5) and have found both the ExpireDBbackupdays setting and del volhist type=db? applied. IBM do not recommend both to be used at the same time and I have seen this first hand recently when Tape volumes disappear off the radar. So, I wanted to gauge how best to configure a TSM server where the following DB backups are taking place under a DRM environment.
backup db type=dbs devcl=<FileClass>
backup db type=FULL devcl=<LTOClass>
q drmstat...
DB backup Series Expiration days: 3
Now, I understand that DRM should take care of those db backups sent to a Tape file Class. (no probs there) So how does one manage the dbs ones sent to tape without using the 'del volhist type=dbs' cmd, which if set incorrectly can remove volume history from the DB?
Thanks