Hi All
I have to disagree about some things here, (not all). I run a large TSM
site, Three TSM server's in production all Microsoft NT server clients
etc, I like TSM, but we have removed TSM exchange backups to a product
called Galaxy(Comvault), you should look at what it can do, and yes I
know of some Microsoft offices using it too. The product supports both
message level and db level backups and restores and has work very well,
even during the migration from 5.5 to 2000. The speed in not to bad,
maybe two hours for an incremental backup of messages on a 30 GB Db.
The first capture I think was 7-8 hours. We run full DB backups as well
each night as well. Its used daily here and there has been no problems
for the last 10 months with regard to exchange service packs etc. I
guess if there's a market for a product you have to supply it, and
that's what others have done.
That's all, But I must also say the TSM exchange connect agent works
well, and we have used it many times for DB restores.
Anthony.
-----Original Message-----
From: Mark Stapleton [mailto:stapleto AT BERBEE DOT COM]
Sent: Thursday, 22 November 2001 7:23 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Dumb Exchange question
On Tue, 20 Nov 2001 13:31:44 -0500, it was written:
> We will be upgrading to the new TDP for Exchange 2.2 from
version
>1.1 some time after the first of the year and we are wondering if the
newer
>version supports individual mailbox recovery. I know the 1.1 version
didn't
>easily support mailbox recovery, you had to build a new Exchange box,
dump
>an entire database restore to it and then export the mailbox back to
the
>production system.
> Do will still need to jump through all the same hoops again to
>restore a mailbox in version 2.2??
Tivoli refuses to use non-Microsoft-standard APIs to do TSM work...for
which I am eternally grateful. Using such non-standard stuff is what
gets Legato, Veritas, and ArcServe in such hot water when an MS
service pack or hot fix is applied.
MS Exchange APIs do *not* support individual mailbox ("brick-level")
restores. What non-TSM backup apps use to get around this is (usually)
the Exchange messaging API, which was *not* built for backups/restores
and which are incredibly slow and buggy when used for such.
--
Mark Stapleton (stapleton AT berbee DOT com)
Mark Stapleton (stapleton AT berbee DOT com)
Notice:
The information contained in this e-mail message and any attached files may
be confidential information, and may also be the subject of legal
professional privilege. If you are not the intended recipient any use,
disclosure or copying of this e-mail is unauthorised. If you have received
this e-mail in error, please notify the sender immediately by reply e-mail
and delete all copies of this transmission together with any attachments.
|
