Database copy '{0}' on server '{1}' has a total (copy plus replay) queue length of {2} logs, which is higher than the maximum allowed queue length of {3}. If you need to activate this database copy, you can use the Move-ActiveMailboxDatabase cmdlet with the -SkipLagChecks and -MountDialOverride parameters to forcibly activate the database copy. If the database does not automatically mount after running Move-ActiveMailboxDatabase successfully, use the Mount-Database cmdlet to mount the database.
Database copy '{0}' is in the Initializing state on server '{1}'. If you need to activate this database copy, you can use ...
Database copy '{0}' is suspended on server '{1}'. Reason: {2}. If you need to perform a switchover of this database, use ...
Database copy '{0}' on Server '{1}' component (HighAvailability) state is offline. If you need to activate this copy of the ...
Database copy '{0}' on server '{1}' has a copy queue length of {2} logs, which is higher than the maximum allowed copy queue ...
Database copy '{0}' on server '{1}' has a total (copy plus replay) queue length of {2} logs, which is higher than the maximum ...
Database copy '{0}' on server '{1}' has content index catalog files in the following state: '{2}'. If you need to activate ...
Database copy '{0}' on server '{1}' has {2} logs to inspect and replay, which is higher than maximum allowed replay queue ...
Database copy '{0}' on server '{1}' is currently a seeding source. You need to cancel the existing seed operation before ...
Database copy '{0}' on server '{1}' is currently resynchronizing its log files with the active database copy. If you need ...