Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

Configuring Database Mirroring Expand / Collapse
Author
Message
Posted Monday, January 31, 2011 11:33 PM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Thursday, July 24, 2014 1:06 PM
Points: 416, Visits: 202
Comments posted to this topic are about the item Configuring Database Mirroring
Post #1056617
Posted Tuesday, February 1, 2011 1:42 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Sunday, August 21, 2011 10:54 PM
Points: 2, Visits: 41
I had also the same error:

[color=#FF0000]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.[/color]

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
Post #1056657
Posted Tuesday, February 1, 2011 3:48 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, April 28, 2014 5:08 AM
Points: 2, Visits: 33
Very Useful information with Statements from starting of the Mirroring Configuration till the end with Error messages .

Sireesha
Post #1056695
Posted Tuesday, February 1, 2011 3:58 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, April 28, 2014 5:08 AM
Points: 2, Visits: 33

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

Post #1056703
Posted Tuesday, February 1, 2011 4:37 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Sunday, August 31, 2014 10:04 AM
Points: 89, Visits: 294
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
Post #1056723
Posted Tuesday, February 1, 2011 4:39 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Sunday, August 31, 2014 10:04 AM
Points: 89, Visits: 294
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
Post #1056726
Posted Tuesday, February 1, 2011 5:20 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, July 3, 2012 6:51 AM
Points: 3, Visits: 76
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.

Post #1056739
Posted Tuesday, February 1, 2011 5:26 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Sunday, August 31, 2014 10:04 AM
Points: 89, Visits: 294
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
Post #1056741
Posted Tuesday, February 1, 2011 5:55 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, July 3, 2012 6:51 AM
Points: 3, Visits: 76
-- 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?
Post #1056752
Posted Tuesday, February 1, 2011 7:14 AM


Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Thursday, November 20, 2014 7:59 AM
Points: 362, Visits: 893
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/
Post #1056794
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse