Re: crash during backup
From: Bill SG (don't)
Date: 10/21/04
- Previous message: ssaks: "Re: Can't do anything with corrupt priv1.edb"
- In reply to: Tyrone Cowart [MSFT]: "Re: crash during backup"
- Next in thread: Tyrone Cowart [MSFT]: "Re: crash during backup"
- Reply: Tyrone Cowart [MSFT]: "Re: crash during backup"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 21 Oct 2004 12:42:24 +0800
I don't know if this post will show up, since I am answering an old one. If
not, I'll repost it later.
I had been running the backup onto the C: drive of the exchange server. The
C: is also where priv1.edb and the log files are located. The backup would
crash the entire computer every time the backup file reach the approximate
size of the priv1.edb file.
Yesterday I got the idea to back up to another computer. The first time it
worked flawlessly. The backup finished without error. The log files were
removed. The priv1.edb did not increase in size, confirming that the data in
the logs was being put into it all along.
One thing that might be normal or might be odd. Today the new log files that
were created did not start over again at number 1. They are continuing from
the highest number that was there before the backup.
"Tyrone Cowart [MSFT]" <tyronec@online.microsoft.com> wrote in message
news:e4cGpCVsEHA.224@TK2MSFTNGP15.phx.gbl...
> If you dismount the stores or shutdown the Information Store in a graceful
> state then the transactions in memory should get committed to the
database.
> To check this run eseutil /mh <path to the database> |more. Look for the
> state of the database. If the database shows to be in a "Clean Shutdown"
> state then you can safely delete the log files.
>
> Circular logging is an option if you are concerned with disk space,
however,
> this will limit your recovery options. With circular logging enabled you
can
> only restore your last full backup and that is it. This means that if you
> crash on Friday and your last full backup was on Tuesday you would only
> recover up until Tuesday. with circular logging disabled you can restore
> from Tuesday's tape and replay the log files to the point of failure.
>
> Unfortunately the only way that I know to validate your backups is to
> restore it. If you have a recovery server and can test this then that
would
> be great.
>
>
> --
> Tyrone Cowart
> Microsoft
>
> "Please do not send email directly to this alias. This alias is for
> newsgroup purposes only."
> "This posting is provided "AS IS" with no warranties, and confers no
> rights."
> "Bill SG" <don't want any spam> wrote in message
> news:Or76MQNsEHA.3200@TK2MSFTNGP09.phx.gbl...
> > I see. The info in the log files is already in the main database. Is
there
> a
> > safe way to remove the log files besides backing up? There are taking up
> > 1.5GB now. I do have plenty of space for now (50GB), but would rather
have
> > backups as backups rather than as log files.
> >
> > How about using circular logging? Would that help me? Is it safe to
switch
> > it on now? Is it safe to switch back and forth?
> >
> > Is there a way to tell if the backups I've made are complete and
> uncorrupt?
> >
> > Thanks,
> >
> > Bill
> >
> >
> >
> > "Tyrone Cowart [MSFT]" <tyronec@online.microsoft.com> wrote in message
> > news:e0AFq7KsEHA.1032@TK2MSFTNGP10.phx.gbl...
> > > If this is happening then there is something going on at the kernel
> level.
> > > It is difficult for a user mode application to bring the kernel down,
> but
> > if
> > > you have no mouse and you can not bring up task manager then this is
> what
> > is
> > > happening. It may be necessary to take a user dump at the time to see
> what
> > > is actually happening.
> > > You may also want to verify that there is enough free disk space if
you
> > are
> > > backing up to a file on the disk.
> > >
> > > It is correct that the log files are for recovery purposes only. The
> > backup
> > > is not trying to commit these transactions to the database, but during
a
> > > full or incremental the backup does purge the log files.
> > >
> > >
> > >
> > > --
> > > Tyrone Cowart
> > > Microsoft
> > >
> > > "Please do not send email directly to this alias. This alias is for
> > > newsgroup purposes only."
> > > "This posting is provided "AS IS" with no warranties, and confers no
> > > rights."
> > > "Bill SG" <don't want any spam> wrote in message
> > > news:#FNRW#DsEHA.1232@TK2MSFTNGP11.phx.gbl...
> > > > Hi,
> > > >
> > > > I recently created a new Exchange 2000 server setup. I then copied a
> lot
> > > of
> > > > old data into users' mailboxes. I now have about 300 of those 5 MB
log
> > > > files. I know that backing up will put them into the database where
> they
> > > > belong. Problem is, when I use MS backup to do the backup, the
entire
> > > > computer crashes. The mouse won't move and CTRL-ALT-DEL won't work -
I
> > > have
> > > > to reset. The crash occurs after about 3 GB of data is backed up,
> which
> > is
> > > > the size of priv1.edb. So I guess the crash occurs when it is time
to
> > > start
> > > > posting the log files to the database.
> > > >
> > > > Is there any way I can solve this?
> > > >
> > > > Thanks,
> > > >
> > > > Bill
> > > >
> > > >
> > >
> > >
> >
> >
>
>
- Previous message: ssaks: "Re: Can't do anything with corrupt priv1.edb"
- In reply to: Tyrone Cowart [MSFT]: "Re: crash during backup"
- Next in thread: Tyrone Cowart [MSFT]: "Re: crash during backup"
- Reply: Tyrone Cowart [MSFT]: "Re: crash during backup"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
