SQL Mirroring - Not Working - Spot the Flaw...
Hi all,
I have configured several SQL boxes and SQL mirroring scenarios but this one has me going round in circles.
The result I get is that the principal cannot talk to the mirror and gives the error TCP://MYSERVER.DOMAIN.LOCA
Both servers are Win Server 2008 R2 running MS SQL 2008 R2 on VM Ware ESXi 4.1, as separate entities the servers are running without issue - both the OS and SQL installations are patched to the same level, the servers are on the same domain but different subnets and different AD sites.
On both servers the SQL server instance is running as the same user with domain admin privs.
To configure mirroring I have:
1) backed up and restored the relevant database to the mirror with no recovery
2) Configured security on the prinicpal with NO witness
3) Left the ports for both servers on 5022 (this is what SQL management studio had as default)
4) use the same account that SQL is currently running as for the mirroring service accounts.
Windows Firewall is off on both machines, there are not other firewalls inbetween the two devices, DNS resolves both FQDN and hostname.
When I try to start mirroring the principal cannot contact the mirror.. I'm sure I have missed something...
Help!
Cheers
K
I have configured several SQL boxes and SQL mirroring scenarios but this one has me going round in circles.
The result I get is that the principal cannot talk to the mirror and gives the error TCP://MYSERVER.DOMAIN.LOCA
Both servers are Win Server 2008 R2 running MS SQL 2008 R2 on VM Ware ESXi 4.1, as separate entities the servers are running without issue - both the OS and SQL installations are patched to the same level, the servers are on the same domain but different subnets and different AD sites.
On both servers the SQL server instance is running as the same user with domain admin privs.
To configure mirroring I have:
1) backed up and restored the relevant database to the mirror with no recovery
2) Configured security on the prinicpal with NO witness
3) Left the ports for both servers on 5022 (this is what SQL management studio had as default)
4) use the same account that SQL is currently running as for the mirroring service accounts.
Windows Firewall is off on both machines, there are not other firewalls inbetween the two devices, DNS resolves both FQDN and hostname.
When I try to start mirroring the principal cannot contact the mirror.. I'm sure I have missed something...
Help!
Cheers
K
Last Comment
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Hi all, thank you for your replies.
Network and DNS is fine between the two servers, they are both live machines (they are at different ends of my MPLS network).
Principal is on 10.7.100.3/24, Mirror is on 10.9.100.28/16 they can both reslove eachothers hostnames and FQDN
@dbaduck: I have run that query (thanks very useful) and I the information on both servers is the same, port 5022 with encryption enabled.
@sqlserver: I will read your blog now, thanks
K
Network and DNS is fine between the two servers, they are both live machines (they are at different ends of my MPLS network).
Principal is on 10.7.100.3/24, Mirror is on 10.9.100.28/16 they can both reslove eachothers hostnames and FQDN
@dbaduck: I have run that query (thanks very useful) and I the information on both servers is the same, port 5022 with encryption enabled.
@sqlserver: I will read your blog now, thanks
K
ASKER
Hi all, two problems I found.
1) The service accounts were actually running under different accounts (despite me thinking they weren't) - odd as this has not caused me an issue before.
2) I needed to restore some transaction logs to the end of the DB restore on the mirror else the prncipal threw an error.
Cheers
K
1) The service accounts were actually running under different accounts (despite me thinking they weren't) - odd as this has not caused me an issue before.
2) I needed to restore some transaction logs to the end of the DB restore on the mirror else the prncipal threw an error.
Cheers
K
Microsoft SQL Server 2008
Microsoft SQL Server 2008 is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning. Major improvements include the Always On technologies and support for unstructured data types.
50K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
Tracert is there a VPN between the sites?
What are the IPs?
Does each server instance run with the same domain account or does each use local account?