locked
SQL 2k8 cluster migration via mirroring RRS feed

  • Question

  • I have a 2-node SQL2k8 cluster that needs to be retired.

    I've created a new 3-node cluster to replace it - actually 2 clusters. One node will be the failover for the other 2 nodes.

    My plan was to mirror the databases to the different clusters, allow others to verify everything still works, set the mirrored databases to principal, change the connection strings & then delete the original cluster. I configured clustering with a witness on a database in SSMS, but when I click start mirroring, I encounter an error regarding a connection to the destination/mirror server - 1418.

    I can connect between the clusters (cluster1.xx.local to cluster2.xx.local) using port 5022, but I cannot connect to the individual servers inside the clusters on port 5022. So from server1 of cluster1 the command telnet cluster2.xx.local 5022 works, but telnet serverxx.xx.local 5022 does not.

    Does anyone know how to get around this issue?

     

    Thanks in advance.

     

    BigSam


    Sam Lowry
    Monday, May 30, 2011 3:33 PM

Answers

  • Hi Sam,

    It might be a connectivity issue, please check the following:

    1. all servers within old cluster, new cluster and virtual network servers and witness can ping each other. If not, the ping command may be blocked in the firewall; you can enable it in the firewall following http://technet.microsoft.com/en-us/library/cc739791(v=ws.10).aspx#BKMK_4 in Books Online.

    2. In Database Mirroring, each service account of Principal, Mirror and Witness needs to be added as a login in other's server and grant CONNECT mirroring endpoint if they do not use the same domain account. For more information, see Database Mirroring topic in Books Online.

    Hope this helps.


    Best Regards,
    Chunsong Feng

    Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Tuesday, May 31, 2011 2:04 AM

All replies

  • Hi Sam,

    It might be a connectivity issue, please check the following:

    1. all servers within old cluster, new cluster and virtual network servers and witness can ping each other. If not, the ping command may be blocked in the firewall; you can enable it in the firewall following http://technet.microsoft.com/en-us/library/cc739791(v=ws.10).aspx#BKMK_4 in Books Online.

    2. In Database Mirroring, each service account of Principal, Mirror and Witness needs to be added as a login in other's server and grant CONNECT mirroring endpoint if they do not use the same domain account. For more information, see Database Mirroring topic in Books Online.

    Hope this helps.


    Best Regards,
    Chunsong Feng

    Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Tuesday, May 31, 2011 2:04 AM
  • The way you describe it I would go with Chuns second comment. Per default the mirroring wizard does not grant the CONNECT permission on the endpoint. You need to issue a

    GRANT CONNECT ON ENDPOINT::<name of the endpoint> TO <name of your service user>

    Lucifer

    Tuesday, May 31, 2011 6:51 AM
  • That indicates port might not be reachable

    1. Firewall port might be closed

    2. The service account does not have enough permissions on all servers (principal, mirror and witness)

    3. Account under endpoints configured might not have enough permissions.

    here is the best place to look http://msdn.microsoft.com/en-us/library/ms189127.aspx

     

     

     


    http://uk.linkedin.com/in/ramjaddu
    Tuesday, May 31, 2011 10:47 AM