VSACIT
asked on
S - ISINTEG vs. ESEUTIL
Hello,
I have been searching on the web to find a good doc to give me details on these two Exchange DB clean up programs. It seems that most docs state that the ISINTEG is for scanning, while the ESEUTIL is actually for repairs.
While I know that Exchange does it's own online defrag, this tech support person I was speaking to was telling me how I should be running these utils consistently to clean up the database. I found this weird because I have not seen any errors in my event viewer concerning the DB. I get nice messages like :
The database "First Storage Group\Mailbox Store (Server Name)" has 131 megabytes of free space after online defragmentation has terminated.
Does anyone know of a nice doc that would explain these two utilities cleanly to me ? Perhaps also let me know if it is required that I run these constantly or just wait for an issue ?
Thanks,
I have been searching on the web to find a good doc to give me details on these two Exchange DB clean up programs. It seems that most docs state that the ISINTEG is for scanning, while the ESEUTIL is actually for repairs.
While I know that Exchange does it's own online defrag, this tech support person I was speaking to was telling me how I should be running these utils consistently to clean up the database. I found this weird because I have not seen any errors in my event viewer concerning the DB. I get nice messages like :
The database "First Storage Group\Mailbox Store (Server Name)" has 131 megabytes of free space after online defragmentation has terminated.
Does anyone know of a nice doc that would explain these two utilities cleanly to me ? Perhaps also let me know if it is required that I run these constantly or just wait for an issue ?
Thanks,
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Currently, the disk drive containing my priv and pub databases is about 45 Gig used out of a 70 Gig drive, so I think we are in pretty good shape for now. We are running the enterprise edition, so the 16 Gig limitation should not be an issue.
We are also currently working on having some of our users clean up their mailboxes, so that should help with any space issues we might run into in the future.
Thank you for your assistance in explaining this issue....
We are also currently working on having some of our users clean up their mailboxes, so that should help with any space issues we might run into in the future.
Thank you for your assistance in explaining this issue....
VS,
One more item to consider is the amount of time/space required to do backups/restores. If your priv.edb is 20+ gigs, having users clean up their mailboxes then running eseutil /d would probably reduce it's size dramatically. I run it periodically on my databases, as for backup/restore purposes I don't like my database size to be more than 20 gigs.
Since you're running the Enterprise version of Exchange (as I do), you can create more than one storage group and/or more than one database per storage group. This can help keep individual database sizes in check. A small book or class on Exchange would probably be very beneficial to you.
Cheers,
Kris.
One more item to consider is the amount of time/space required to do backups/restores. If your priv.edb is 20+ gigs, having users clean up their mailboxes then running eseutil /d would probably reduce it's size dramatically. I run it periodically on my databases, as for backup/restore purposes I don't like my database size to be more than 20 gigs.
Since you're running the Enterprise version of Exchange (as I do), you can create more than one storage group and/or more than one database per storage group. This can help keep individual database sizes in check. A small book or class on Exchange would probably be very beneficial to you.
Cheers,
Kris.
ISINTEG works on the links between the tables within the database. This is why it is always a good idea to run ISINTEG -FIX after running ESEUTIL /P.