Re: Exchange 2003

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: K.J.B. (blah_at_blah.com)
Date: 10/04/04 

Date: Mon, 4 Oct 2004 11:10:20 -0700

I moved my Database files to D:\Exchange Data

This Drive had/has nothing on it except the Folder Exchange Data.

I only moved the database.

Where are the transaction logs kept by default?

"Jaclynn Hiranaka [MSFT]" <jaclynnh@online.microsoft.com> wrote in message
news:O1i1twjqEHA.3980@TK2MSFTNGP12.phx.gbl...
> You said you lost a disk right? Where were your transaction log files?
> Were they on the disk that failed? Did you replace that disk and name it
> the same thing?
>
> Is your original transaction log and database path valid? If you bring up
> the properties of the store you are trying to restore and go to the
database
> tab does that location exist? If you bring up the properties of the
storage
> group the store is in is the transaction log file path valid? Does the
file
> structure exist there?
>
>
> --
> Hope that helps.
>
> -------------------------
> Jaclynn Hiranaka
> Enterprise Messaging Support
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> © 2004 Microsoft Corporation. All rights reserved.
>
>
> "K.J.B." <blah@blah.com> wrote in message
> news:OykYzrjqEHA.592@TK2MSFTNGP11.phx.gbl...
> > Now when I do a restore (I cleared out the D:\Exchange Data) I get an
> > error
> > message:
> >
> > Unable to create log Path. Check to make sure it is a valid path.
> >
> > Any ideas?
> >
> > K.J.B.
> >
> >
> >
> > "Jaclynn Hiranaka [MSFT]" <jaclynnh@online.microsoft.com> wrote in
message
> > news:usT3zXjqEHA.1988@TK2MSFTNGP09.phx.gbl...
> >> When you did the restore did you check the last restore set check box?
> >> Before you did the restore did you clean out the database and log file
> >> locations?
> >>
> >> What happens is in Exchange 200X a hard recovery (eseutil /cc) needs to
> >> be
> >> run to play in the log files to bring the stores to a consistent state
to
> > be
> >> able to mount them. If you check the 'Last restore set' check box then
> >> it
> >> is done for you automatically. You have to ensure that there are not
any
> >> extra log files in your transaction log file directory when you do the
> >> restore. The reason for this is that those log files most likely do
not
> > go
> >> a long with the databases you are restoring and therefore would fail to
> > play
> >> into those databases.
> >>
> >> What is the consistency of the databases? If you run an eseutil /mh
> > against
> >> the databases what does 'State' say? If consistent ensure that your
log
> >> file directory is clear and attempt to mount the store. If
inconsistent
> >> I
> >> would suggest re-restoring and ensuring that the 'Last Restore Set'
check
> >> box is checked.
> >>
> >> --
> >> Hope that helps.
> >>
> >> -------------------------
> >> Jaclynn Hiranaka
> >> Enterprise Messaging Support
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> >> © 2004 Microsoft Corporation. All rights reserved.
> >>
> >>
> >> "K.J.B." <blah@blah.com> wrote in message
> >> news:Otvh3OjqEHA.3172@TK2MSFTNGP10.phx.gbl...
> >> > Hi,
> >> >
> >> > I have a big problem. I recently install a Windows 2003 SBS Standard
> >> > Server.
> >> >
> >> > Users were able to use exchange and then my Exchange Data" drive
kicked
> >> > it!
> >> >
> >> > I was doing backups with NTBackup.exe.
> >> >
> >> > I restored from backup (I can see the files *.edb and *.stm) but when
I
> >> > goto
> >> > mount the store I get the following error message:
> >> >
> >> > An internal processing error has occured. Try restarting the
Exchange
> >> > System Manager or Information Store Service or Both.
> >> > ID # C1041124
> >> >
> >> > Exchange System Manager?
> >> >
> >> > Is there anyway to repair Exchange files?
> >> >
> >> > K.J.B.
> >> >
> >> >
> >> >
> >>
> >>
> >
> >
>
>

Relevant Pages

  • Re: Transaction log problems
    ... IF you have to shrink a database or file it ... sure that you get that database backup on tape or to another machine. ... > We are using SQL Server 2000 on Windows Server 2003 Standard Edition, ... > One of the databases has recently begun showing large growth of the> transaction log and it is causing us some problems. ...
    (microsoft.public.sqlserver.server)
  • RE: Backup in maintenance plan
    ... I selected "Back up the transaction log of the database as part of the ... To ensure an efficient and effective backup and recovery strategy for your ... The transaction log should not be backed up if the truncate log on ...
    (microsoft.public.sqlserver.programming)
  • Re: Restoring from non-truncated transaction log
    ... The transaction log is there to support transactional consistency as well ... as supporting "incremental" backup. ... A database backup contains both data pages as well as the necessary log records (from the ... When your restore a database backup, ...
    (microsoft.public.sqlserver.server)
  • Re: Large Transaction Log Backup after Database Backup
    ... script and see for yourself that the database backup doesn't truncate the ... ALTER DATABASE steve SET RECOVERY FULL ... But my understanding was that the transaction log was> truncated after a full database backup. ...
    (microsoft.public.sqlserver.server)
  • Re: Transaction Log Size
    ... Backup database does not empty the transaction log files. ... How to Shrink the SQL Server 7.0 Transaction Log ...
    (microsoft.public.sqlserver.server)