So Greg:
You went from one instance of STORE.EXE to three instances of STORE.EXE
and you now have your mail going to 3 physical drive sets and have three
separate physical drive sets for your TL's?
John H. Matteson, Jr.
Systems Administrator/ITT Systems
FOB Orgun-E
Afghanistan
DSN - 318 431 8000
VoSIP - (308) 431 - 0000
Iridium - 717.633.3823
"A man who thinks of himself as belonging to a particular national group in
America has not yet become an American. And the man who goes among you to trade
upon your nationality is no worthy son to live under the Stars and Stripes."
Woodrow Wilson
-----Original Message-----
From: Greg Mulholland [mailto:[EMAIL PROTECTED]
Sent: Saturday, January 05, 2008 1:58 AM
To: MS-Exchange Admin Issues
Subject: RE: ISINTEG question.
I'd agree with that
I recently had an issue with a corrupt database, albeit a very small part,
possibly one mailbox. The error in the backup was The 'Microsoft Information
Store' returned 'Error returned from an ESE function call (d).' from a call to
'HrESEBackupRead()' . There was a temptation for a second to run eseutil and
isinteg on the database for a fix but certainly everything ide been taught and
read was that these tools (isinteg particularly) can be abrasive to the
database and potentially cause more issues. In my situation I was without a
decent backup for a while as well.
I set about moving databases to new stores. It also gave me a chance to break
apart the stores in to more meaningful and manageable blocks and also re-define
my logs and databases drives a little better since build. I have now have 3
storage groups with a private store in each for my 3 clear different user
levels. In the process I managed to find a mailbox that had a few corrupted
items which I have re-created (mail gets pst'd after every year, so she has a
copy at home anyway) I could have run isinteg on the remaining mailbox in the
default store but wth its only one mailbox!!
I am now happy to report that the backups of each store are going swimmingly.
Thanks Michael for your help..
-----Original Message-----
From: Michael B. Smith [mailto:[EMAIL PROTECTED]
Sent: Friday, 4 January 2008 11:17 PM
To: MS-Exchange Admin Issues
Subject: RE: ISINTEG question.
Eseutil's /p option (repair) followed by isinteg. But it should really be
considered a "method of last resort".
Regards,
Michael B. Smith
MCSE/Exchange MVP
http://TheEssentialExchange.com
-----Original Message-----
From: HELP_PC [mailto:[EMAIL PROTECTED]
Sent: Friday, January 04, 2008 12:31 AM
To: MS-Exchange Admin Issues
Subject: R: ISINTEG question.
Practically there is no real option to get a Exchange database repaired ? No
Ese no isinteg so what ?
GuidoElia
HELPPC
-----Messaggio originale-----
Da: Michael B. Smith [mailto:[EMAIL PROTECTED]
Inviato: giovedì 3 gennaio 2008 19.16
A: MS-Exchange Admin Issues
Oggetto: RE: ISINTEG question.
Urg. Non-trivial to explain.
I tried to find a public document that describes some of what isinteg does on a
technical level, but couldn't.
Historically, isinteg was a debugging tool for PSS. It allowed them to scan a
store and in the case of corruption, basically get rid of the offending piece
of the store. This followed the "I'd rather have part of my store than none of
it" philosophy. After a while, it made it into the standard release.
Then, it was used primarily for patching stores that were reloaded from backup.
Today, the primary use for isinteg is to fix-up a database after it has been
repaired.
ESEutil is not Exchange aware. Difficult to believe, huh? But eseutil just
treats an Exchange store as any ESE database. And therefore its operations are
generic in nature.
It's up to isinteg to make sure that a given database is ready to be used by
Exchange. It understand the various tables and specific B+trees and the
consistency stuff and the split factors and the duplicate roots and the long
value blobs, etc. etc.
Under many situations isinteg can cause secondary indexes to be eliminated.
It can cause both table splits and table merges that Exchange will undo the
next-time it accesses a particular folder (because the Exchange store itself is
load-sensitive - but isinteg cannot be).
So...detuned. You'll have to regenerate secondary indexes (which Outlook calls
Views). And your table structure may no longer be optimal under load, which
Exchange will have to adjust in the future.
I don't think that there are any current recommendations from Microsoft to run
isinteg EXCEPT after a repair (or upon the recommendation of a PSS engineer).
In fact, a quick scan of the knowledge base reveals that there are, in fact,
problems with running isinteg on production databases - up to and including
Exchange 2007! (Fixed in update rollup 3.)
Regards,
Michael B. Smith
MCSE/Exchange MVP
http://TheEssentialExchange.com
-----Original Message-----
From: Tom Strader [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 03, 2008 7:18 AM
To: MS-Exchange Admin Issues
Subject: RE: ISINTEG question.
Michael,
I guess the term "detuned" is in question.
By running isinteg, how does it "detune" the indexes?? By what means are the
indexes kept "intune"?
I'm curious also.
Thanks,
Tom
-----Original Message-----
From: Matteson, John H Jr USA Mr USA 25th SigBN (ITT) [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 03, 2008 6:59 AM
To: MS-Exchange Admin Issues
Subject: ISINTEG question.
You can run isinteg on a dismounted database - pretty much ANY dismounted
database - and it will give you warnings. This is because isinteg is a utility
and not a database engine itself. You can tell isinteg to fix those warnings,
and run it multiple times until there aren't any more warnings, and you've just
detuned your indexes.
===================
Michael:
Can you explain your statement about detuning indexes when running
isinteg with the FIX option?
Thanks.
John H. Matteson, Jr.
Systems Administrator/ITT Systems
FOB Orgun-E
Afghanistan
DSN - 318 431 8000
VoSIP - (308) 431 - 0000
Iridium - 717.633.3823
"A man who thinks of himself as belonging to a particular national group in
America has not yet become an American. And the man who goes among you to trade
upon your nationality is no worthy son to live under the Stars and Stripes."
Woodrow Wilson
~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~
~ http://www.sunbeltsoftware.com/Ninja ~
~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~
~ http://www.sunbeltsoftware.com/Ninja ~
~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~
~ http://www.sunbeltsoftware.com/Ninja ~
~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~
~ http://www.sunbeltsoftware.com/Ninja ~
~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~
~ http://www.sunbeltsoftware.com/Ninja ~
~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~
~ http://www.sunbeltsoftware.com/Ninja ~
~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~
~ http://www.sunbeltsoftware.com/Ninja ~
