Database copy '{0}' on server '{1}' has a copy queue length of {2} logs, which is too high to enable automatic recovery. You can use the Move-ActiveMailboxDatabase cmdlet with the -SkipLagChecks and -MountDialOverride parameters to move the database with loss. If the database isn't mounted after successfully running Move-ActiveMailboxDatabase, use the Mount-Database cmdlet to mount the database.
Database copy '{0}' can't be activated because an error occurred while trying to determine if the copy has the required log ...
Database copy '{0}' could not be suspended because a database switchover or failover is in progress. Please retry the operation ...
Database copy '{0}' couldn't be resumed because a database switchover or failover is in progress. Please retry the operation ...
Database copy '{0}' couldn't change its state because a database switchover or failover is in progress. Please try the operation ...
Database copy '{0}' on server '{1}' has a copy queue length of {2} logs, which is too high to enable automatic recovery. ...
Database copy '{0}' on server '{1}' is a seeding source. You need to cancel the seed operation before proceeding with the ...
Database copy's overall integrity is represented by this object but the issues in question want to be alerted per server. ...
Database Maintenance background task for database '%4' failed to start with error %5. For more information, click http:/ ...
Database Maintenance background task for database '%4' failed to start with error %5. For more information, click http:/ ...