ahh. that is a slight problem. The only way that I know how (with my puny brain) is by restoring and old TSM DB backup that was done before the del filespace command was run. What you might do is stop the current TSM server and then start a 2nd instance that uses different database and recovery log volumes (essentially creating a 2nd TSM server instance on the same physical server).
You could at this point do an export of that node's filespace, then stop the 2nd instance, start the original. then import the filespace to the original. This is a high
level description with some minor details omitted.
anyone else got any ideas?
