One way would be to move the nodes to another domain with unlimited retention, and then rename them node_archive. You would then need to recreate then nodes in the current domain for backups to continue.
This will cause the data to be backed up again for all nodes, but at least it will only be one copy. Another solution is to backup the stgpool to another backup stgpool, then keep it along with a copy of the TSM database. You would need to setup a separate TSM instance if they are actively restoring the data. Don't envy your situation. It would be best if you could get your lawyers to agree on what data needs to be retained rather than everything. This is where e-discovery and content management really starts saving people money. It's too late in your case, but it makes a great argument for the future. Good Luck, Gary Bowers Itrus Technologies On Aug 18, 2009, at 2:29 PM, Bill Boyer wrote:
History.have a client backing up with a 30-day retention policy (vere=nolimit rete=30) and last week they came as requested that the retention be change to No Limit across the board. Keep everything. Lawyers involved. Now they feel that the resource requirements for doing that for an indefinite period are more than they want to take on. So they asked that the retention be set back to 30-days , but..and here's the fun part.they want to tapes with the oldest backup data to be kept. You can see they have to concept of TSM and are thinking of keeping the oldest full backup tapes around so they could be re-cataloged if a restore is needed. So my problem/question is how do I accomplish the same thing? Was thinking EXPORT NODES, but what date range to use. Backupsets (no, I'm not 6.1! J) isn't what I want either. Any suggestions? Bill Boyer "He who laughs last probably made a back-up." Murphy's law of computing