Re: HELP!!! Priv corrupt - events 9297 and 467

wow...you might want to start a weekly test of restoring a backup to the
RSG, just to make certain your backups are all usable...what a horrible
situation...or, in a case like this, where you have power issues, ensure
everyone's running in cached mode, so there's always a copy of the email on
the PC...my sympathies...

--
Susan Conkey [MVP]



"SusanV" <s@xxxxx> wrote in message
news:uBEyhFMzIHA.3496@xxxxxxxxxxxxxxxxxxxxxxx
The biggest is only 1.9 GB, and the priv is a little over 5 GB, lots of
space on this server, entire exchange db is 7 GB according to the store
startup event, so I'm not too concerned with losing SIS - it's more the
time involved in using Exmerge.

This has been a nightmare of a week, so many problems related to the power
failures, a UPS can only do so much when the power goes out for an hour
then up for 20 minutes then out again, lather, rinse, repeat.. We go
through this every summer, but this has been the worst as far as equipment
damage goes, it'll probably take me well into next week to get it all
straightened out - then I get to play catch-up on all the stuff I *should*
have done this week.

Thanks again, I really appreciate all the help you and Andy have given
today, I was about ready to slit my wrists <g>

HAGD,
SusanV


"Susan" <sconkey@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:OUUPN2LzIHA.2292@xxxxxxxxxxxxxxxxxxxxxxx
if you're going to just rename or delete the edb. and stm. files, you'll
end up with just a bunch of empty mailboxes...then you can use exmerge to
merge the data from those pst files back into the mailboxes...what's the
largest pst file? your database will most likely be much larger than it
was before, as SIS will be broken...and yes, dial-tone is the way to go,
when you have a good backup to restore from...

--
Susan Conkey [MVP]



"SusanV" <s@xxxxx> wrote in message
news:e$uoPyLzIHA.5816@xxxxxxxxxxxxxxxxxxxxxxx
I'm exmerging out now - thankfully there's only 34 mailboxes, and only a
few are big. Should be finished soon. While I've been waiting for this I
was looking at the dial tone method - neat trick if you have a good
backup.

When I move all the files out of mdbdata and restart the services, will
the mailboxes be available to exmerge in or will I have to touch each
one? If so, will sending a global email do the trick or will I have to
use OWA or somesuch? It's been so long since I was Exchange-based that
I've forgotten so much stuff.... very frustrating day.

Thanks again for all your suggestions,
SusanV

"Susan" <sconkey@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:esFqokLzIHA.1768@xxxxxxxxxxxxxxxxxxxxxxx
maybe...looks like you might be running out of options...

--
Susan Conkey [MVP]



"SusanV" <s@xxxxx> wrote in message
news:ecZcgbKzIHA.2292@xxxxxxxxxxxxxxxxxxxxxxx
Nope, the restore to the recovery group failed:
Unable to restore Exchange data to LSGSBS\Microsoft Information
Store\First Storage Group,
check the application event log for more information

Looks like maybe Exmerge is the way to go?

Applog:
Event Type: Error
Event Source: ESE
Event Category: Logging/Recovery
Event ID: 619
Date: 6/12/2008
Time: 12:05:55 PM
User: N/A
Computer: LSGSBS
Description:
Information Store (1528) Recovery Storage Group: Attempted to attach
database 'C:\Program Files\Exchsrvr\Recovery Storage Group\Mailbox
Store (LSGSBS).edb' but it is a database restored from a backup set on
which hard recovery was not started or did not complete successfully.

For more information, click
http://www.microsoft.com/contentredirect.asp.
=========================
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9519
Date: 6/12/2008
Time: 12:05:55 PM
User: N/A
Computer: LSGSBS
Description:
Error 0xfffffde0 starting database "Recovery Storage Group\Mailbox
Store (LSGSBS)" on the Microsoft Exchange Information Store.

For more information, click
http://www.microsoft.com/contentredirect.asp.
Data:
0000: 46 61 69 6c 65 64 20 74 Failed t
0008: 6f 20 61 74 74 61 63 68 o attach
0010: 20 74 6f 20 4a 65 74 20 to Jet
0018: 44 42 00 DB.
============================
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9518
Date: 6/12/2008
Time: 12:05:55 PM
User: N/A
Computer: LSGSBS
Description:
Error 0xfffffde0 starting Storage Group
/DC=local/DC=lightshipgroup/CN=Configuration/CN=Services/CN=Microsoft
Exchange/CN=LIGHTSHIPGROUP/CN=Administrative Groups/CN=first
administrative
group/CN=Servers/CN=LSGSBS/CN=InformationStore/CN=Recovery Storage
Group on the Microsoft Exchange Information Store.
MDB failed to start.

For more information, click
http://www.microsoft.com/contentredirect.asp.
============================

"Susan" <sconkey@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:O4MJYQKzIHA.5472@xxxxxxxxxxxxxxxxxxxxxxx
yes, a restore is the best way to go on something like this...and if
you got a good backup, that's a good sign...

--
Susan Conkey [MVP]



"SusanV" <s@xxxxx> wrote in message
news:uA31BKKzIHA.4772@xxxxxxxxxxxxxxxxxxxxxxx
I just ran a backup of the first storage group, ran without errors.

Now I'm going to try restoring from Monday to a RSG, see how that
goes.

Thanks again for your help.


"Susan" <sconkey@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:eYhRrGKzIHA.1772@xxxxxxxxxxxxxxxxxxxxxxx
that would be correct...how many mailboxes are we talking about,
here? what happens if you try to do a backup now? does it fail?
if you try to restore Monday's backup to an RSG, does it work?

--
Susan Conkey [MVP]



"SusanV" <s@xxxxx> wrote in message
news:OWh129JzIHA.4772@xxxxxxxxxxxxxxxxxxxxxxx
Hi Susan,
Backup failed last night, and I'm not sure when this issue
started, so Monday night's backup may be corrupt also. The only
known good backup I have is from Friday, and since Monday's was
succesful the logs from tjhe weekend are gone, correct?

SusanV

"Susan" <sconkey@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23iDTNtJzIHA.2208@xxxxxxxxxxxxxxxxxxxxxxx
the recommendation in a case of serious corruption is to restore
from backup...that would probably be your best bet...

--
Susan Conkey [MVP]



"SusanV" <s@xxxxx> wrote in message
news:u3AkdnJzIHA.2220@xxxxxxxxxxxxxxxxxxxxxxx
SBS2003 R2, SP1, Exchange is SP2 (version 6.5.7638.1)

After a series of power failures where the UPS was unable to
recharge enough to bring the server down gracefully after
powering back up, I am getting EventID 9297 and 467 (full errors
pasted below) in the Application log every few minutes. The
store mounts OK but users keep getting Exchange is unavailable
every few minutes. Searching the web, I found very little on
these errors,.

I dismounted the private store, backed it up, and ran eseutil:
C:\Program Files\Exchsrvr\bin> eseutil /d
c:\progra~1\exchsrvr\mdbdata\priv1.edb
results:
Operation terminated with error -338 (JET_errBadParentPageLink,
Database corrupted) after 1308.32 seconds.

Then ran isinteg:
C:\Program Files\Exchsrvr\bin>isinteg -s lsgsbs -fix -verbose -l
C:\isinteg.pri -test alltests
Results:
. . . . . SUMMARY . . . . .
Total number of tests : 21
Total number of warnings : 7
Total number of errors : 0
Total number of fixes : 1991
Total time : 0h:7m:33s

Reran isinteg, no errors warnings or fixes. Reran eseutil /g,
says database is still corrupt. The store will still mount, and
mail is still accessible, but I'm still getting the errors.
Currently I have the store dismounted to keep users out.

I thought to create a new store and move the mailboxes, but
after creating a new storage group, I cannot add a new mailbox
store, error says "This storage group already contains the
maximum number of stores allowed" - I assume this to be an SBS
limitation?

So now what??? Any ideas before I pull out the plastic and call
MS???

ANY help would be appreciated!!!
SusanV

App log data:
===================================
Event Type: Error
Event Source: ESE
Event Category: Database Corruption
Event ID: 467
Date: 6/12/2008
Time: 9:45:58 AM
User: N/A
Computer: LSGSBS
Description:
Information Store (1528) First Storage Group: Database
C:\Program Files\Exchsrvr\mdbdata\priv1.edb: Index
FidDeleteTimeIndex of table IndexAge is corrupted (0).

For more information, click
http://www.microsoft.com/contentredirect.asp.
===================================
Event Type: Error
Event Source: MSExchangeIS Mailbox Store
Event Category: Background Cleanup
Event ID: 9792
Date: 6/12/2008
Time: 9:45:59 AM
User: N/A
Computer: LSGSBS
Description:
Cleanup of the DeliveredTo table for database 'First Storage
Group\Mailbox Store (LSGSBS)' failed with error -1017. 4 entries
were purged before the failure was encountered.

For more information, click
http://www.microsoft.com/contentredirect.asp.
===================================























.

Relevant Pages

  • RE: Exchange 2003 & NTBackup Restore problems
    ... Have you considered just mounting an empty store instead of deleting the ... Did you do a FULL backup today?????? ... > can have clean accounts. ... Prepared to perform a restore, from the clean backup, to clean up the ...
    (microsoft.public.exchange.admin)
  • Re: Exchange 2003 & NTBackup Restore problems
    ... > have you tried simply dismounting the mailbox store and deleting the ... > remove all mailbox data from the accounts. ... > time than restoring from backup. ... Prepared to perform a restore, from the clean backup, to clean up the ...
    (microsoft.public.exchange.admin)
  • Re: Exchange database restore question - tg
    ... "The Exchange Information Store automatically redirects all restore ... operations to the Recovery Storage Group (if a Recovery Storage Group ... by NT Backup and my restore be pushed to the RSG? ...
    (microsoft.public.exchange.admin)
  • Re: Unable to restore single Exchange 2003 database
    ... I deleted the Exchange Storage Group and reran the restore from NT Backup ... The attempt to log on to the Microsoft Exchange Server computer has failed. ...
    (microsoft.public.exchange.admin)
  • Re: Can not restore Exchange Storage Group
    ... When I originally created the backup set, ... re-opened it and found that NTBackup only seems to store the storage group ... I restore to the same Exchange organization and server name ... I assume you are restoring to the same Exchange org and same server name? ...
    (microsoft.public.exchange.admin)