h8mmer
ADSM.ORG Member
I completed a DRM procedure on a windows (W2K std server) TSM (5.2.2) environment recently for a customer using a DB backup from two weeks previously which was the date of their last DBB.
As they assured me they had not backed anything up to their primary tape pools (no diskpools in use) since the last DBB I did not run the "destroy primary tape vols" as part of the DRM procedure as all their volumes were still sat in the library.
It now turns out they did continue to backup ordinary filesystems after the last DBB (for about a week) until their TSM environment went kaput.
Now they are in a situation where their DB and volhist is out of sync and they cannot checkin tapes or run backups.
Is there anyway to solve this issue w/o having to re-perform the DRM procedure and this time delting the primary tape pool??
As they assured me they had not backed anything up to their primary tape pools (no diskpools in use) since the last DBB I did not run the "destroy primary tape vols" as part of the DRM procedure as all their volumes were still sat in the library.
It now turns out they did continue to backup ordinary filesystems after the last DBB (for about a week) until their TSM environment went kaput.
Now they are in a situation where their DB and volhist is out of sync and they cannot checkin tapes or run backups.
Is there anyway to solve this issue w/o having to re-perform the DRM procedure and this time delting the primary tape pool??