This post is more than 5 years old
2 Intern
•
146 Posts
0
701
June 22nd, 2007 09:00
RM 5.x and Exchange ESEUtil Dirty Shutdown Question
So looking at the end result of the Exchange database after a successful RM job, the actual clone database is in a "Dirty Shutdown" state (try it: eseutli /mh database.edb).
Because the database is in a dirty shutdown state, we cant run test scripts against the DB's (such as timing how long an offline defrag will take). Based on what I am reading on MS support, a recovery must be ran against the database (eseutil /r e00 /l [path to logs] /s [path the checkpoint] /d [path to db]
To be honest, I would have thought RM would somehow of integrated this into the resulting output of the RM process. So here is my question:
What is anyone doing out there with post replication scripts to possibly automate the ESEutil recovery process? Or is this the first time you have heard about this? Or am I missing the boat here and running an esutil recovery would screw up the process for recovering the database in the event a clone restore to production is needed?
I opened this question with SAC and received a scary comment that what we are attempting to do is outside of what RM promises customers they will be able to do with their replica.
Because the database is in a dirty shutdown state, we cant run test scripts against the DB's (such as timing how long an offline defrag will take). Based on what I am reading on MS support, a recovery must be ran against the database (eseutil /r e00 /l [path to logs] /s [path the checkpoint] /d [path to db]
To be honest, I would have thought RM would somehow of integrated this into the resulting output of the RM process. So here is my question:
What is anyone doing out there with post replication scripts to possibly automate the ESEutil recovery process? Or is this the first time you have heard about this? Or am I missing the boat here and running an esutil recovery would screw up the process for recovering the database in the event a clone restore to production is needed?
I opened this question with SAC and received a scary comment that what we are attempting to do is outside of what RM promises customers they will be able to do with their replica.
No Events found!
JamesBEMC
257 Posts
0
June 29th, 2007 02:00
To clarify some things
1) It is a Microsoft requirement and a VSS function that we must have the Exchange database set in "dirty shutdown". We cannot change that.
2) The scope of Replication Manager is to present and integrity check the Exchange database only. This is what we do successfully.
3) If you modify a mounted replica and perform a recovery on the database, you absolutely will affect the ability to restore. You will not be able to roll forward from the latest set of transaction logs on the host.
4) My recommendation to you is to either
a) Make a copy of the replica and modify that
or
b) Do an Exchange Copy Replica job.
Hope it helps
James.
mkonstas
1 Message
0
December 6th, 2007 12:00
-Mike-