DrivelFree
asked on
Database Copy in Dirty Shutdown
I have a database copy on a server (back up server, no mounted databases, only copies) that's in a failed and suspended state. Normal protocol for me would be to use eseutil to check the state (dirty), repair, check the state again (clean), and then to update the database copy. Usually that works without a hitch...not this time. It continues to remain in a dirty state even after the repair completes successfully.
I've attempted to repair the database copy every way I know how and I'm to the point now where I can either restart the server or perform a hard recovery (eseutil /p). And here is where my question comes into play: Barring in mind my configuration and since this is only a database copy, is there a risk in running eseutil /p to perform a hard recovery on a database copy? If I lose data for this copy, can it potentially cause problems for the active, mounted database? I don't see how this could impact the mounted database (different server), but I want to be sure.
Any help?
I've attempted to repair the database copy every way I know how and I'm to the point now where I can either restart the server or perform a hard recovery (eseutil /p). And here is where my question comes into play: Barring in mind my configuration and since this is only a database copy, is there a risk in running eseutil /p to perform a hard recovery on a database copy? If I lose data for this copy, can it potentially cause problems for the active, mounted database? I don't see how this could impact the mounted database (different server), but I want to be sure.
Any help?
ASKER
That was definitely the first thing I tried. I only use the above steps when Update doesn't work.
If you have backup, restore and replace the existing files, Mount it and reseed again. Latest logs will replay automatically.
If Update doesnt work nothing will help as if you do Repair or anything on the Passive Database its like a Database Mind diversion and would never help apart from Update.
Does the Update fail right away or what ?
Did you delete or move all DB and Logs across and then try Update ?
Is this only one DB or all are affected ?
- Rancy
Does the Update fail right away or what ?
Did you delete or move all DB and Logs across and then try Update ?
Is this only one DB or all are affected ?
- Rancy
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Maybe some service wasnt started or hung that got recycled during the Restart and helped
- Rancy
- Rancy
ASKER
Restarted the server.
- Rancy