mirror--different SQL Server versions use the default mirroring endpoint encryption algorithm

In the construction of the image encountered a small problem, building the mirror times wrong, troubleshooting long time, certificate/user/login/connection authorization and other aspects have done one by one, did not find the exception, and finally generate the mirror endpoint creation script, only to find the cause of the problem:

The mirroring endpoint creation script for the Mirror Master node (10.50.4276) is:

CREATE ENDPOINT [Endpoint_mirror_server]     state =STARTED    5022, listener_ip = all )    = all, authentication == REQUIRED algorithm RC4)

In the Mirror-ready node (10.50.2500) Mirroring endpoint creation script is:

CREATEENDPOINT[Endpoint_mirror_server] State=STARTED asTCP (Listener_port= 5022, LISTENER_IP=  All)     forData_mirroring (ROLE=  All, authentication=CERTIFICATE[cert_2], encryption=REQUIRED algorithm AES)

Because the encryption algorithm is not specified when the mirroring endpoint is created, and the default encryption algorithm is different for different versions, resulting in the last image not being built properly, the workaround: Modify one of the nodes ' encryption algorithms to use the same encryption algorithm on both sides of the mirror.

--===================================

Summarize:

1. The encryption algorithms on both sides of the mirror must be consistent or not be built

2. If the mirror ends are only minor versions, you can set up the image (first make sure the backup node can back up the primary node)

--=================================

Sister pressure Field

mirror--different SQL Server versions use the default mirroring endpoint encryption algorithm