I have a situation where I basically have two volumes with certain save sets on them that (due to company policy) necessitate the erasure of both tapes. However, there are many save sets on these tapes that are not in violation of policy and I'd really like to avoid erasing these permanently.
My thoughts on this are to identify all ssid's on each volume (done), identify the actual "policy-violating" save set ssid's (done), then I'm thinking I can perhaps clone the "good" save sets over to a new tape(s) (probably into a new pool created for this purpose). After that I could do something like delete the ssid's from the original volumes, then erase those offending volumes. I'm guessing that next, I could relabel the now "good" erased tapes and put them back into my backup pool. However, I will also need to stage/clone/??? the save sets I cloned to the new pool, back to my backup pool. Hopefully, once all is said and done, the only clients affected in any way would be the clients to which those offending save sets actually belonged. All other save sets from those two volumes would now be browseable and restoreable.
I could really use some advice on how to actually do this, if it's possible at all. What command syntax should I use? Should the new pool be another backup pool, or a clone pool? What have I missed?
I know I'm asking alot, so thanks in advance.
- Ravashaak
My thoughts on this are to identify all ssid's on each volume (done), identify the actual "policy-violating" save set ssid's (done), then I'm thinking I can perhaps clone the "good" save sets over to a new tape(s) (probably into a new pool created for this purpose). After that I could do something like delete the ssid's from the original volumes, then erase those offending volumes. I'm guessing that next, I could relabel the now "good" erased tapes and put them back into my backup pool. However, I will also need to stage/clone/??? the save sets I cloned to the new pool, back to my backup pool. Hopefully, once all is said and done, the only clients affected in any way would be the clients to which those offending save sets actually belonged. All other save sets from those two volumes would now be browseable and restoreable.
I could really use some advice on how to actually do this, if it's possible at all. What command syntax should I use? Should the new pool be another backup pool, or a clone pool? What have I missed?
I know I'm asking alot, so thanks in advance.
- Ravashaak