Hi, To ensure that exchange databases are consistent in exchange 2003, do we need to perform checksum validation for both *.edb and *.stm files using eseutil? Or running eseutil against *.edb is enough to ensure consistency ? Also can we store *.edb & *.stm files on separate volumes? What is the best practice and will it cause any issue if we store in different volumes/drives ? Thanks Inmar

On Tue, 13 Jul 2010 11:18:32 +0000, inmar_mine wrote: > To ensure that exchange databases are consistent in exchange 2003, do we need to perform checksum validation for both *.edb and *.stm files using eseutil? The consistency of a database is not determined solely by verifying that individual database pages are without I/O errors. To veryify the cosistency of a database you must use "eseutil /g". > Or running eseutil against *.edb is enough to ensure consistency ? Eseutil is correct, but it not very often necessary. Is there a reason why you're taking the database offline to verify its consistency? > Also can we store *.edb & *.stm files on separate volumes? Yes, you can. >What is the best practice and will it cause any issue if we store in different volumes/drives ? Separating the two different database files onto separate sets of disks will spread the I/O load over more spindles. Are you having a problem with disks that are unable to keep up with the I/O workload? If so you might consider moving off Exchange 2003 to Exchange 2010, adding additional memory to the machine, and reaping a large reduction in IOPS. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP