Excellent post, one small addendum.....copy the mailstore and repair and defrag the copy....no downtime...replace the bad with good when it suits....:)) Done that a few times now. S -----Original Message----- From: Young, Gerald G [mailto:Gerald.Young@xxxxxxxxxx] Sent: Tuesday, March 14, 2006 6:14 PM To: ISA Mailing List Subject: [isalist] RE: OT: Good source for Exchange Mailstore Management http://www.ISAserver.org As long as my messages provide value to people, that's all I can ask for. :) Thank you for the kind words. :) Cordially yours, Jerry G. Young II MCSE (4.0/W2K) Atlanta EES Implementation Team Lead HHS Engineering Unisys 11493 Sunset Hills Rd. Reston, VA 20190 Office: 703-579-2727 Cell: 703-625-1468 THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. -----Original Message----- From: Thor (Hammer of God) [mailto:Thor@xxxxxxxxxxxxxxx] Sent: Tuesday, March 14, 2006 3:31 PM To: [ISAserver.org Discussion List] Subject: [isalist] RE: OT: Good source for Exchange Mailstore Management http://www.ISAserver.org OT posts are good sometimes ;) t On Mar 14, 2006, at 12:24 PM, Talley, Scott wrote: > http://www.ISAserver.org > > Gerald, I just wanted to add my $.02 that your responses to the > NON-ISA questions posted to this list are GOLD!! I don't think there > is one that hasn't been useful to me, even though I didn't ask the > question. Thanks for your valuable time and thorough and > understandable information. > > Thank you, > > Scott Talley > IT Manager, The Combined Group > e> stalley@xxxxxxxxxxxxxxxxx > p> 469.892.9829 > f> 469.892.9710 > > -----Original Message----- > From: Young, Gerald G [mailto:Gerald.Young@xxxxxxxxxx] > Sent: Tuesday, March 14, 2006 1:54 PM > To: [ISAserver.org Discussion List] > Subject: [isalist] RE: OT: Good source for Exchange Mailstore > Management > > > http://www.ISAserver.org > > You're going to want to check the integrity of your database file > using the eseutil /k command. Unfortunately, that means you'll need > to dismount the store. Did your Exchange server crash sometime > recently? > Or was it just after the issue you were having with the disk in the > shared storage that you started having problems? > > Since you got to take down the store to check the database integrity, > you might want to go ahead and perform an offline backup, too. Check > out KB Article 237767 (XADM: Understanding Offline and Snapshot > Backups) > for additional information on how to do so. Be sure to grab a copy of > all log files between the last time you took a successful backup and > now to be sure you can reply them against the offline backup, if > necessary. > > So, if you're not able to take a backup, what's your log file free > disk space looking like? My guess would be that it's filling up. > Dismounting the store should commit any data in the log files to the > database. You can confirm this by running the eseutil /mh command > against your database file once you stop the store. The state should > be listed as Clean Shutdown. > > 90GB database file in and of itself isn't necessarily problematic. It > is, however, unwieldy. We're running off of a fibre SAN with fibre > drives in our environment. Even so, backup and restore takes a long > time. It's probably in your best interest to separate your users, if > only to decrease the total size of a single database. While this may > increase the complexity of your Exchange and disk configuration, it > will help minimize the issues that can occur when you do have large > stores. > > For backup, restore, and archival (I realize you're already using a > solution but I figured I'd throw this out anyway since it addresses > all functionality), take a look at the NearPoint solution from Mimosa > Systems (www.mimosasystems.com). It uses a pretty slick architecture > that enables pretty much near realtime restoration of Exchange data > right down to the individual mail message level. It does this by > copying your production database from your Exchange server to itself > and then through log shipping (both periodic [you set the period > between shipments] and dynamic [each time a log file is created, it's > copied to the NearPoint server]), it replays those log files directly > against its copy of your Exchange database. It also has a zero > footprint on both your Exchange servers and clients (no agents). > > If you have more questions about any of this, feel free to ping me > offlist. :) > > Cordially yours, > Jerry G. Young II > MCSE (4.0/W2K) > Atlanta EES Implementation Team Lead > HHS Engineering > Unisys > > 11493 Sunset Hills Rd. > Reston, VA 20190 > Office: 703-579-2727 > Cell: 703-625-1468 > > THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE > PROPRIETARY MATERIAL and is thus for use only by the intended > recipient. If you received this in error, please contact the sender > and delete the e- mail and its attachments from all computers. ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=isalist ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp ISA Server FAQ: http://www.isaserver.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Visit TechGenix.com for more information about our other sites: http://www.techgenix.com ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: isalist@xxxxxxxxxx To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=isalist Report abuse to listadmin@xxxxxxxxxxxxx