ISINTEG switches in Exchange 5.5

[LokiX]

I am in a desperate hunt for a way to run isinteg just against the calendar. I am aware that the switches exist but i don?t know them. Thanks for the help

 

[mikecel79]

Originally posted by: LokiX
I am in a desperate hunt for a way to run isinteg just against the calendar. I am aware that the switches exist but i don?t know them. Thanks for the help

Why are you running it against just the calendar? Are you having problems with your calendar in user's mailboxes? HAve you checked your Free/Busy Connector?

 

[spyordie007]

AFAIK it's run against an entire database (so not just the calendar). KB article about using it

 

[LokiX]

We have somewhere around an 80gb database and not enough time to run it against the whole thing. i have been told that there is a way to brake it down and just run it against all or parts of the database. i am not the Exchange Admin but my boss wants me to do the leg work on this utility since our Exchange Admin is inept.

 

[mikecel79]

Originally posted by: LokiX
We have somewhere around an 80gb database and not enough time to run it against the whole thing. i have been told that there is a way to brake it down and just run it against all or parts of the database. i am not the Exchange Admin but my boss wants me to do the leg work on this utility since our Exchange Admin is inept.

Do you know the repercusions of using ISINTEG? It's a very dangerous utility and 80GB of email is a LOT of email to lose. You have to run it against the whole database. You can't just run it against one part of it because then it would be out of synch with everything else. Everything in the Exchange database is closely related to each other, and running ISINTEG against just a part (which I'm about 95% sure is NOT possible is just going to make a mess of the database. Normally ISINTEG is only to be run when recommended from PSS or after an offline restore. This isn't something you just run on a schedule.

If you are having a problem with your Exchange server and you think you may have DB corruption get on the phone and call PSS ASAP. They can help you out. The $300 call is more than worth it, than risk losing 80GB of email.

BTW 80GB is probably close to the limit that you should let an Exchange 5.5 server grow too. Often it's recommended to split the store at 50GB on an Exchange 5.5 server.

 

[spyordie007]

The $300 call is more than worth it, than risk losing 80GB of email.

Agreed.

 

[LokiX]

i agree with you guys completly. I am not the one doing the work thank goodness. just doing someresearch. Thanks for the help.