My test mailbox servers lost all iSCSI connections abruptly. Upon restore, the mailbox database (DAG) was not mounted
According to this Technet for Exchange 2010, I should execute this cmdlet to get the MailDB01 mounted:
Mount-Database -Identity Mailbox01\MailDB01
But it didn't work. Instead, I had this error:
Cannot process argument transformation on parameter 'Identity'. Cannot convert value "mailbox01\maildb01" to type "Microsoft.Exchange.Configuration.Tasks.DatabaseIdParameter". Error: "'mailbox01\maildb01' is not a valid value for the identity.
Parameter name: Identity"
+ CategoryInfo : InvalidData: (:) [Mount-Database], ParameterBindin...mationException
+ FullyQualifiedErrorId : ParameterArgumentTransformationError,Mount-Database
It must be another straight 'copy-and-paste' from Exchange 2007 documentation. Instead, the correct cmdlet for Exchange 2010 should be:
Get-MailboxDatabase -Identity MailDB01 | Mount-Database -force
The "-force" option may be needed to ignore other previous errors. Once the database is mounted, I have to reseed the second failed copy. For further information, see "How to Reseed a Failed Mailbox Database Copy in Exchange Server 2010".
Good tips on the link provided. Just few steps, it is easy.
ReplyDeleteAn error message in the middle of a project is the worst. Luckily there is usually a quick fix if you know what you're doing.
ReplyDeleteHi,
ReplyDeleteIncrease response rates and return on investment by selecting our highly targeted and verified Australia B2B Email Lists of prospects from our business.
Indutry Wise Email Database
Technology Wise Email Database
Country Wise Database for USA
State Wise Email Database