Perfect...Thanks.
The only bad thing is gonig to be copying the 2.5 tb of data from lto to 3590,
WEW..
Thanks,
Jason
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Bill Smoldt
Sent: Tuesday, August 17, 2004 10:51 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Exchange TDP question - HELP
Ah, I think I understand more about this, now.
If you put the old Exchange nodes in their own domain, you can set up the
copygroup to have nolimit versions and retainonly so that the old ones won't
expire.
It sounds as though you're going to continue to send the data to the outside
company, so as long as you send a database with each batch of tapes, you
don't have to worry about expiring the old data from your current database
if you convince them to use a dated database restore.
Bill Smoldt
STORServer, Inc.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Cain, Jason (Corporate)
Sent: Tuesday, August 17, 2004 9:01 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Exchange TDP question - HELP
We just send the media to them, and I know it sounds strange, but it is
there responsibility to restore the data. I am assuming they use Tivoli.
This is for legal reasons...
The problem I am having is this.
The media goes to LTO tape with over 2.5 tb of data.
I need to stop backups for the current Exchange nodes, move the data to a
EXCHANGE ONLY pool with 3590 media only. Then create new nodes going
forward. I know how to rename the nodes and define stgpools, but is this
the right way. Is it possible to STOP expiration for these Exchange nodes
only after I rename them?
Jason
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Bill Smoldt
Sent: Tuesday, August 17, 2004 9:49 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Exchange TDP question - HELP
Jason,
I don't know enough of your constraints or requirements to make a qualified
recommendation. However, faced with a similar situation my preference was
to create a second copy storage pool, backup the existing required data to
that new copypool, and save an extra bi-weekly (expiration period divided by
2 for redundancy) copy of the database backup.
Restore of the Exchange data required a TSM database restore to a new TSM
server and then TDP restores to a new Exchange server (both can be on the
same standalone system if you're running TSM on Windows). By not performing
reclamation on the new copypool, you can keep adding new data to the pool.
By keeping an extra copy of the database tapes with known dates, you can
restore the Exchange database from the date you need, even though the data
gets expired in the current active database. This allows you to continue
normal operations and still get to the old data.
Do "they" need you to deliver the tapes to "them" or are you going to keep
them and perform restores? If the former, do "they" have TSM restore
capabilities? Are you under some legal requirements for producing the data?
Is this a one time thing or do you have to continue this procedure?
There are many ways to accomplish this.
Bill Smoldt
STORServer, Inc.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Cain, Jason (Corporate)
Sent: Tuesday, August 17, 2004 8:33 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Exchange TDP question - HELP
Is there a way to archive everything that has already been backed up to a
new media type, and how. We currently backup our Exchange servers to LTO
tape and now for legal purposes they need all of our Email data. They need
it on 3590 tape, and we must keep all of the data going back from today and
start new backups.
If I move the data, how can I tell TSM from stop expiring on the Exchange
nodes only.
Any suggestions.....
Jason
|
