Our restores run just slightly slower than the backups, definately not
double the time, on our RS/6000 (3466 Netstor).  We have had some problems
with restores, though not really the connect agent's fault.

Recently we had to do a series of restores, and after each one we had to run
ESEUTIL on the IS before it would start.  The closest we could come in
determining the problem was that the server we were restoring to was at the
same level of Exchange, but not the same level of NT, as the server we had
taken the backup from.  As that server was in use by other apps it was
impossible to correct, so each restore took about one working day due to the
length of time it takes to run the utility.  There is some MS doc that
indicates that the server you are restoring to should be at the same release
of both NT and Exchange.  We have since set up a server dedicated to
Exchange restores, and insured that it was at the appropriate levels...still
had trouble, but different errors.  I have been too busy with other things
to really investigate these errors, but our past experience has been that we
can recover, it just might take some time.

> -----Original Message-----
> From: Nathan King [SMTP:nathan.king AT USAA DOT COM]
> Sent: Friday, July 23, 1999 8:08 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: Recovery of Exchange - was: backing up Exchange
>
> John,
>
> I have yet to encounter a problem restoring an Exchange Database with the
> Adsm Connect Agent.
> Let me take that back.. we have had problems but not related to the
> Connect
> Agent and I've restored well over 50 Exchange databases so far - either
> for
> the purpose of mailbox restore or for loss of server.
>
> I'm still trying to work out however why our recoveries take much longer
> than the backup.
>
> When backing up straight to tape we reach about 30Gb/hr, however restore
> is
> about 15Gb/hr.
> That's a pefectly acceptable restore rate but I'm curious as to the
> dramatic
> loss of speed.
>
> I understand that you are going to loose some speed because you are
> writing
> data rather than reading it.
> Our Exchange Servers also have write cacheing disabled to improve
> reliability - this also slows down a restore - enabling write cacheing
> boosted the restore up to almost 18Gb/hr.
>
> I still can't believe that restores are giving half the throughput of the
> backup. I've a feeling it's a network tuning parameter on our Rs/6000.
> Anyone any ideas?
>
> Nathan
>
>
>
>         -----Original Message-----
>         From:   Talafous, John G. [SMTP:Talafous AT TIMKEN DOT COM]
>         Sent:   Friday, July 23, 1999 6:54 AM
>         To:     ADSM-L AT VM.MARIST DOT EDU
>         Subject:        Recovery of Exchange - was: backing up Exchange
>
>         It's nice to see success stories regarding backup of Exchange with
> the
>         Connect Agent.
>         Does anyone wish to share success stories on the recovery process?
> How easy
>         is
>         it?  Hardware considerations? Any gotchas?
>
>         John G. Talafous                         Sr. Tech. Prog/Anal
>         The Timken Company                 Phone: (330)-471-3390
>         P.O. Box 6927                           Fax  : (330)-471-4034
>         1835 Dueber Ave. S.W.
>         Canton, Ohio USA  44706-0927
>         talafous AT timken DOT com     http://www.timken.com/