Hi,
For my setup the mountdialoverride is set to lossless which will prevent passive copy to auto mount the DBs when the active copy losses its storage. So the active copy will be dismounted and all other copy will be failed and disconnected. Well its fine for me as per settings, but when the storage was back online, the active copy still shows as dismounted and all other passive copy is "failed and disconnected" state.
i have tried to manually mount the active DB and i get the below error highlighted in bold (Event ID: 3154)....
Active Manager failed to mount database DAG1-DB1 on server server1. Error: An Active Manager operation failed. Error: The database action failed. Error: An error occurred while trying to select a database copy for possible activation. Error: The database 'DAG2-JournalDB' was not mounted because errors occurred either while validating database copies for possible activation, or while attempting to activate another copy.
An Active Manager operation failed. Error: Database 'DAG1-DB1' on server 'server1' cannot be mounted due to a previous error: At '24/12/2012 12:13:32' the Exchange store database 'DAG1-DB1' copy on this server appears to be inconsistent with the active database copy or is corrupted. For more details about the failure, consult the Event log on the server for other storage and "ExchangeStoreDb" events. A successful failover restored service. If you have addressed the underlying problem, or if you have decided to attempt to mount the database despite this error, the mount operation may be attempted by using the '-Force' parameter of the Mount-Database cmdlet..since i dint had enough time to run eseutil /mh or /p to check and repair the DB, i just run the mount command with -force parameter as suggested in the error above. it worked fine and the DB was up and running and seems no data loss.
Does anyone know what does -force parameter does? is it safe to use in case of circular logging? will it truncate the exiting uncommitted transaction logs? any data loss if so how much it can be?
any issue using the -force parameter if linear logging is enabled?
Any other suggestion to handle this kind of failure?
Thanks.
Teeju