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.

 

I expect (but admit that I do not know it for sure) that those warnings are
what are being reported by GoExchange.

 

Db integrity is checked 100% with every single online backup that you take.
100%. You can't back up a corrupted database with online backup. It aborts.

 

And in Exchange 2007 sp1, it's regularly checked on an ongoing basis.

 

In my Exchange 5.0 to 5.5 migration, I had a call that lasted for 32 hours
with Microsoft. They stuck with me all the way. When I had a RAID-5 failure
with a bad backup tape on SBS-2000 (and Exchange 5.5 had a custom version in
SBS 2000), I had as many as eight engineers working with me to make that
right. It took 3 days. And cost me - you guessed it - about $250. 

 

Yes, sometimes frontline support can be idiots - but I've never had MSFT
fail me in a critical support situation.

 

Regards,

 

Michael B. Smith

MCSE/Exchange MVP

http://TheEssentialExchange.com

 

From: Tom Strader [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, January 02, 2008 5:24 PM
To: MS-Exchange Admin Issues
Subject: RE: Email de-duplicator?

 

 

According to the logs it creates, it is still finding errors and fixing
them. If someone can show me why we shouldn't use the program and still
maintain DB integrity, I'm open to any suggestions for saving money and 

downtime.

 

The article Webster sent was eye-opening to say the least.

 

..and they say you can't teach an old dog new tricks.

 

 

  _____  

From: William Lefkovics [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, January 02, 2008 5:16 PM
To: MS-Exchange Admin Issues
Subject: RE: Email de-duplicator?

 

I have never heard of Microsoft failing so badly. They would work with you
until the problem was solved.

Even the notion of GoExchange solving something that Microsoft couldn't is
completely ludicrous. 

 

>> it works for us, that's all I know.

 

Really?  What is the ongoing need it is filling, besides creating
unnecessary downtime?

 

 

From: Tom Strader [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, January 02, 2008 1:38 PM
To: MS-Exchange Admin Issues
Subject: RE: Email de-duplicator?

 

 

Good comments there and it makes sense, but when I took over at the PAC,
their Exchange 5.5 server was getting corrupted at least once a week. We
called Mickeysoft and they couldn't figure out the problem. Everything was
setup properly, up to date etc.

 

GoExchange was purchased and installed. It fixed the problems and the
databases have never had a problem since. We are at Exchange 2K3 SP2 now and
still use the program.

 

It made a difference for us where Microsoft couldn't. Their response was
restore from backup. At that time, the PAC was using demo backup software to
backup about 200 Gigs of data. Needless to say, I insisted on better
software and hardware to take care of this.

 

Knowing what I know now, after having to restore the DB several times using
the Eseutil and Isinteg utils for several weeks prior to upgrading the
backup situation and reading this article, I probably would not renew the
software.

 

However, for what it's worth, it works for us, that's all I know.

 

Tom

 

  _____  

From: Webster [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, January 02, 2008 4:03 PM
To: MS-Exchange Admin Issues
Subject: RE: Email de-duplicator?

 

 

 

From: Tom Strader [mailto:[EMAIL PROTECTED] 
To: MS-Exchange Admin Issues
Subject: RE: Email de-duplicator?

 

Whatcha got against GoExchange?

 

http://www.themssforum.com/ExchangeAdmin/GoExchange/

 

Read Ben Winzenz's 2nd response.

 

Webster

 

 

 

 

 

 

 

 

 

 


~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~
~             http://www.sunbeltsoftware.com/Ninja                ~

Reply via email to