If you resume mirroring for this database, and if transactions are committed at '{0}' but the log was not sent to the former ...

If you resume mirroring for this database, and if transactions are committed at '{0}' but the log was not sent to the former mirror server instance, the transactions are rolled back. This situation can occur after the following sequence of events:

(1) The connection between the principal and mirror server instances is lost.

(2) The principal continues to commit transactions locally but cannot send the log records to the mirror.

(3) A FORCE_SERVICE_ALLOW_DATA_LOSS command forces service to the mirror database, which assumes the principal role.

(4) The connection between the partners is reestablished, the original principal server assumes the mirror role, and mirroring is suspended.


Do you want to resume mirroring and roll back any transactions committed at server instance '{0}' but not sent to server instance '{1}'?

If you answer "Yes," any transactions whose log is unsent will be lost. If you answer "No," you can remove mirroring and bring the database at '{0}' online, to help you identify those transactions.