Ok, but would now since I have no logfiles be the time to do that? Once I get everything up I suppose I could just as easily shutdown and dismount the store and create new SGs
From: Michael B. Smith [mailto:[email protected]] Sent: Tuesday, August 31, 2010 8:00 PM To: MS-Exchange Admin Issues Subject: RE: eseutil /p You cant ignore the fact that you are operating in multiple-databases-per-SG mode. In that case, the fact that an individual DB is clean shutdown is pretty much irrelevant. You need to have all DBs in that SG in clean shutdown. Once you are in one-DB-per-SG (or at Exchange 2010 which requires that), life is much easier. You cant (without breaking stuff) bifurcate log files when you have multiple-DBs-per-SG. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Lists - Level5 [mailto:[email protected]] Sent: Tuesday, August 31, 2010 7:57 PM To: MS-Exchange Admin Issues Subject: RE: eseutil /p Yes, I have been arguing with them that their DBs need to be smaller and to implement archiving. I hate to be the I told you so and use these as lessons but hopefully the urgency will be understood now. I agree, I will split these up as soon as this is done. There really wasnt a lot of thought put into this structure when they started with 40 users and now are nearing 800 employees. Thanks for the tip MBS Just curious once I have the edb in clean shutdown and showing no logfiles needed or requested whats the chance they come online? I know there will be some data loss im just hoping its fairly contained to the actual problem which was maybe 50-100 emails when the db went offline. From: Michael B. Smith [mailto:[email protected]] Sent: Tuesday, August 31, 2010 7:25 PM To: MS-Exchange Admin Issues Subject: RE: eseutil /p At this point I think you need to wait it out. You see now why it is best to have one DB per SG. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Lists - Level5 [mailto:[email protected]] Sent: Tuesday, August 31, 2010 7:21 PM To: MS-Exchange Admin Issues Subject: eseutil /p So long story, as short as possible I have exchange 2007 running on an EQL san for the datastores and logs. We have 2 Stores with 2 DBs in each and 1 PF. The EQL san didnt auto-resize and with about 150GB left it went offline with an error dropping the connection. We manually expanded the drive and the system came back with 600GB available. Now the hard part, the BU didnt run over the weekend and was rescheduled to run Monday evening (about 6 hours before this occurred). Apparently the past few days was a vss snapshot error, so Im stuck trying to revive what I have before rolling back 2 weeks. I have corrupted log files and 2 dbs in the second storage group are dirty shutdown. When I mount them I get errors that logfiles are corrupt and tried rolling those back and then ended up with invalid timestamps on the logs. We decided to get it to clean by running eseutil /p and after having ½ the company down for a 1.5 days one of the dbs is done , and the other is still going (dbs are 120gb and 310gb). I wanted to just mount the finished db one time and then run the isinteg fix but when I do it hangs for a minute and then errors that I cannot start due to the other database is in use (event logs showed its trying to touch the other DB still in repair and errors out). Now the question is we would like to get this online , its dismounted would it hurt anything to drop it from storage group 2, and re-mount it in storage group 1 for the sake of getting it back online or could that cause more grief than its worth and just wait it out Thanks --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe exchangelist
