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.