Orin, Del, I think you could accomplish this by exporting the backups for the node to a separate TSM server. The domain you export it into could have policy settings to effectively never expire anything, even the inactive copies that already exist. You can do this by having the default management class have no limit on versions and an infinite retention, and also make sure that the grace periods in the domain are set as high as possible.
We are not currently doing this, but are thinking about implementing something along these lines. ..Paul At 11:43 AM 11/16/2006, Del Hoobler wrote:
Orin, You can't freeze just "one" particular backup. Short term, you can solve this by creating a new NODENAME for your future Data Protection for Exchange backups. This will keep all of your current active backups "frozen". In the future, you should look into using Data Protection for Exchange COPY type backups, and bind the "COPY" backups to a different management class that solves your longer term "archival" needs. Thanks, Del ---------------------------------------------------- "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 11/16/2006 09:04:51 AM: > Yipes, we have pending litigation and an "E-discovery." > > I've been told to "freeze" our TDP for Exchange backups. How do you do > dat? The backups roll off. (Just keeping one backup may be good enough.) > > Regards, > Orin > > Orin Rehorst
-- Paul Zarnowski Ph: 607-255-4757 Manager, Storage Services Fx: 607-255-8521 719 Rhodes Hall, Ithaca, NY 14853-3801 Em: [EMAIL PROTECTED]