Orin

There are a number of different ways of achieving this and the best
method will probably depend on your environment. It may be that a
combination of methods may suit for you.

You can generate a backupset of the active data using the command
'generate backupset'.
For further info, do 'help generate backupset' or take a look at the
server reference manual. The main benefit is that it is stored and
managed as a single object.
You may wish to use this method to get a 'snapshot' of the baclient data
for the exchange server. It saves on objects in the DB.

Backupsets don't work for TDP data, therefore I would create a new node.
Give it a recognisable name, something like

Exchsvr_Litigation_15Nov06

Change the TDP nodename in the dsm.opt file to this temp nodename and
perform a manual backup of the exchange db. This does assume that you
have a window big enough in the evening to run a manual before the
scheduled or that you can run a manual full during the day.

Providing that you do not backup to this node again, the backup will
always be active and never expire. If you are really concerned about
expiration, set the retention values that you associate to the new node
to no limit.

You may also want to take the precaution of marking the tape(s) that the
data is written to as read-only and also setting the read-only switch
physically on the tapes.

Leigh


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Orin Rehorst
Sent: 16 November 2006 14:05
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [SPAM: 4.000] [ADSM-L] Litigation!

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