Configuring Database Mirroring

  • william-375754

    SSC-Addicted

    Points: 498

    Comments posted to this topic are about the item Configuring Database Mirroring

  • brekee

    Grasshopper

    Points: 16

    I had also the same error:

    The server network address "TCP://<server>:5022" can not be reached or does not exist. Check the network address name and that the ports for the local and remote endpoints are operational.

    While building about 20 mirrors. And the strange was that I was able to build the first 10 mirrors, then this error appeared. But if I tried again then I was success. Than fail again and success again, or not.

    First I suspect for the network....

    Then I realized the following:

    On the mirror instance I had two SQL instances running. One of them ate 20Gigs of memory, the other one left only 600MB...

    What do you think which one was the one I tried to set up for mirroring?

    Once it got some memory (2-3 gigs) it was easily build the mirrors, and the error was gone...

    Andor

  • sireesha.budagala

    Grasshopper

    Points: 22

    Very Useful information with Statements from starting of the Mirroring Configuration till the end with Error messages . 😀

    Sireesha

  • sireesha.budagala

    Grasshopper

    Points: 22

    How Can we modify the Login permissions on SQL Mirrored Database ?

    for ex : 'abc' is the Login we need to reduce the level of permission from 'db_owner' to 'read/write' on Mirrored database . Database will be Read-only .

    Provide all your inputs on the above . 🙂

    Thanks in Advance

    Sireesha

  • clementhuge

    SSC-Addicted

    Points: 445

    This is a very nice little introduction by this article lacks of several issues that should be looked at.

    - certificate authentication

    - mirroring replication

    - linked server failovering

    - job failovering

    I had the experience with all of that for a client and I am still struggling with linked server. The failover partner solution does not work as there is a bug on Microsoft part (your login needs to be sysadmin for the linked server with failover partner to fully work). I am setting a different way as we speak as linked server is source of security breach. This needs to be definitely fix by Microsoft.

    Clement

  • clementhuge

    SSC-Addicted

    Points: 445

    sireesha.budagala (2/1/2011)


    How Can we modify the Login permissions on SQL Mirrored Database ?

    for ex : 'abc' is the Login we need to reduce the level of permission from 'db_owner' to 'read/write' on Mirrored database . Database will be Read-only .

    Provide all your inputs on the above . 🙂

    Thanks in Advance

    Sireesha

    There is no issue as the rights on a database is user-oriented or database role oriented, both objects embedded in the database. Your changes will be automatically mirrored without any issue.

    The rights that are given at the server level and OS level will not be mirrored. So if your login need to write/read specific things on disk or if your login has view server state granted for example, you need to apply those rights on both servers.

    Clement

  • jorge.rodriguez

    SSC Rookie

    Points: 39

    When I try to partner the principal to the mirror I get the error:

    The server network address "TCP://<server>:5022" can not be reached or does not exist. Check the network address name and that the ports for the local and remote endpoints are operational

    Strange thing is I cant partner the mirror to the principal.

    I have followed all the steps listed on the article all to no avail. The service account are running under the same domain account on both databases... Any help would be apreciated.

  • clementhuge

    SSC-Addicted

    Points: 445

    jorge.rodriguez (2/1/2011)


    When I try to partner the principal to the mirror I get the error:

    The server network address "TCP://<server>:5022" can not be reached or does not exist. Check the network address name and that the ports for the local and remote endpoints are operational

    Strange thing is I cant partner the mirror to the principal.

    I have followed all the steps listed on the article all to no avail. The service account are running under the same domain account on both databases... Any help would be apreciated.

    -- 1. Ping and telnet your principal and mirror servers: if you cannot ping or telnet, this can be your problem (add your ips on your host files and see if this fix your issue)

    -- 2. Firewall setup: inbound and outbound packets need to be allowed on the ports used by your listening end points

    -- 3. Windows negotiate: can you confirm you use windows negotiate for your end points?

    This is for starters.

    Clement

  • jorge.rodriguez

    SSC Rookie

    Points: 39

    -- 1. Ping and telnet your principal and mirror servers: if you cannot ping or telnet, this can be your problem (add your ips on your host files and see if this fix your issue)

    -- 2. Firewall setup: inbound and outbound packets need to be allowed on the ports used by your listening end points

    -- 3. Windows negotiate: can you confirm you use windows negotiate for your end points?

    This is for starters.

    Thanks for the prompt reply,

    I can connect through telnet on both servers, my firewall is currently off and windows negotiate is used on both endpoints.

    Any other sugestions?

  • Kendal Van Dyke

    SSCertifiable

    Points: 5972

    The article states that SQL 2008 is a prerequisite but mirroring has been around since SQL 2005 SP1.

    Also, the witness can be Express or Workgroup edition.

    Finally, I want to emphasize that one very important consideration for mirroring to work properly is that you should use the fully qualified domain name (FQDN) for servers, NOT their IP address. You will run into a myriad of reliability issues if you use IP address.

    Kendal Van Dyke
    http://kendalvandyke.blogspot.com/[/url]

  • phani31

    SSC Journeyman

    Points: 89

    article was good

  • okkam1

    Grasshopper

    Points: 15

    This is a great article. Clear, well written and with good examples. Good teaching is the ability to take the complex and make it seem simple. I would like to see more articles by this author.

  • gotas_5

    Grasshopper

    Points: 11

    could somebody exaplain me where i can do this in SQL SERVER or WINDOWS SERVER?

    how i can do it??

    The SQL database mirroring account/group has been granted "Access this computer from the network". This will be the account (or group containing the account) under which database mirroring runs, and should be a service account/group. This needs to be done on all participating servers (principal, mirror, and witness).

    1.Open up the Local Security Policy on the principal server

    2.Expand Security Settings > Local Policies > User Rights Assignment

    3.Grant the database mirroring service account "Access this computer from the network" permissions

    thanks.

  • Sudheer Cherukuri

    Grasshopper

    Points: 11

    This is amazing stuff.Thanks for the post:-)

  • dr.blowfin

    SSChasing Mays

    Points: 626

    jorge.rodriguez (2/1/2011)


    -- 1. Ping and telnet your principal and mirror servers: if you cannot ping or telnet, this can be your problem (add your ips on your host files and see if this fix your issue)

    -- 2. Firewall setup: inbound and outbound packets need to be allowed on the ports used by your listening end points

    -- 3. Windows negotiate: can you confirm you use windows negotiate for your end points?

    This is for starters.

    Thanks for the prompt reply,

    I can connect through telnet on both servers, my firewall is currently off and windows negotiate is used on both endpoints.

    Any other sugestions?

    Try recreating the endpoints with encryption disabled.

Viewing 15 posts - 1 through 15 (of 15 total)

You must be logged in to reply to this topic. Login to reply