Rene,
Ahhh, ok. Now that's more reasonable.
Why then don't you perform a full every day ? Wouldn't that cut your log
time down to almost 0 ? Or is it a question of backup time ?
At the moment, I have a backup time of around 2 hours for 24GB of data,
which includes the NT system as well as the Exchange online stuff.
Have you thought about a Bare Metal / Intelligent Disaster Recovery solution
for your Exchange server ?
Mike
> -----Original Message-----
> From: Lambelet,Rene,VEVEY,FC-SIL/INF. [SMTP:[EMAIL PROTECTED]]
> Sent: â ðåáîáø 14 2000 15:02
> To: [EMAIL PROTECTED]
> Subject: Re: Your experience with Tivoli Data Protection for MS
> Exchange
>
> Mike,
>
> I have no work to do, Exchange does it automatically ! It just need
> time...
>
> Regards,
>
> René Lambelet
> Nestec S.A. / Informatique du Centre
> 55, av. Nestlé CH-1800 Vevey (Switzerland)
> *+41'21'924'35'43 7+41'21'924'28'88 * K1-117
> email [EMAIL PROTECTED]
> Visit our site: http://www.nestle.com
>
> This message is intended only for the use of the addressee and
> may contain information that is privileged and confidential.
>
>
>
> > -----Original Message-----
> > From: Mike Glassman - Admin [SMTP:[EMAIL PROTECTED]]
> > Sent: Tuesday, November 14, 2000 1:59 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: Your experience with Tivoli Data Protection for MS
> > Exchange
> >
> > Del,
> >
> > From what you say it seems it should be a rather forwards sort of
> > backup-while-active and as easy to restore.
> >
> > Yet in Rene's email of a short while ago today, it seems that he has to
> > work
> > rather hard once the restore has been done.
> >
> > I am very much questioning the need to drop BE and try the TSM Exchange
> > backup, as I have had extremely good results with BE, and the restore is
> > easy, fast and no need of manually applying logs to the database in
> order
> > to
> > get things in shape. A simple restore, reboot, and sometimes, but
> rarely,
> > an
> > ISINTEG.
> >
> > One other issue I like with BE today, is the ability to do a full
> restore
> > including OS and have everything work in the time it takes to restore +
> 1
> > hour.
> >
> > I am still not so hot on the TSM version of Intelligent Disaster
> Recovery,
> > or Bare Metal Restore as it's called here.
> >
> > Mike
> >
> > > -----Original Message-----
> > > From: Del Hoobler [SMTP:[EMAIL PROTECTED]]
> > > Sent: â ðåáîáø 14 2000 14:38
> > > To: [EMAIL PROTECTED]
> > > Subject: Re: Your experience with Tivoli Data Protection for MS
> > > Exchange
> > >
> > > Mike,
> > >
> > > >> Seems that a lot of you are happy with the exchange backup.
> > > >>
> > > >> So let me ask if I may :
> > > >>
> > > >> 1. Do you backup Exchange while active or do you shut down the
> > services
> > > >> prior to backup ?
> > >
> > > In order to use Tivoli Data Protection for Microsoft Exchange, your
> > > services must be running. It uses the Microsoft provided APIs that
> were
> > > built to run online backups. If you bring down the services and
> > > run a backup, you cannot use TDP for Exchange. You could use
> > > the standard backup archive client...BUT.... and this is a big BUT...
> > > ...you will not get online backup data integrity checking that is
> built
> > > into the Microsoft APIs and thus TDP for Exchange. When you use
> > > TDP for Exchange, every page of the database is read and check-summed
> > > to make sure it is consistent.
> > >
> > > >>
> > > >> 2. How many of you have had to restore your whole Exchange from
> > backup,
> > > and
> > > >> how long did it take, and did it work fully or were there any
> > glitches
> > > that
> > > >> had to be retouched to get it all running ?
> > >
> > > I want to answer part of this question...
> > > You should not have to "retouch" anything. Any if you do have to
> > > use ESEUTIL or whatever your favorite tool is... then we want
> > > to know about it because the APIs were built so that you do not
> > > have to do this.
> > >
> > > >>
> > > >> Thanks,
> > > >>
> > > >> Mike
> > >
> > >
> > > Del
> > >
> > > ----------------------------------------------------
> > >
> > > Del Hoobler
> > > IBM Corporation
> > > [EMAIL PROTECTED]