June 14, 2011 at 7:32 am
i want to configure mirror like this :
Principal : TCP://[192.168.0.30]:5022
Mirror : TCP://[192.168.0.31]:5022
but i get an error : TCP://[192.168.0.30]:5022 CANNOT BE REACHED
my Service is running under Administrator (should i change it to network service?)
any idea?
Thanks
peleg
June 14, 2011 at 7:38 am
As far as I know mirroring configuration must be done with hostnames. add those IPs to host file and use their hostnames.
Regards,
MShenel
June 14, 2011 at 7:46 am
i did, the same problem.
June 14, 2011 at 7:49 am
Check if firewall is OFF in both servers. IF your OS is Windows 2008 it comes with firewall ON
Regards,
MShenel
June 14, 2011 at 8:06 am
You can create an endpoint with an IP as per http://msdn.microsoft.com/en-us/library/ms181591.aspx
You do need to be consistent and be sure the partner knows the IP, but this sounds like a networking issue. Check the firewalls, as noted by msenel, or any routers in between the servers.
June 14, 2011 at 2:05 pm
Can you ping each server via IP? If ping works, verify the connectivity via telnet as SQL Mirroring uses this protocol. Test from both principal to mirror and then mirror to principal.
Also - check the sql Server error log for specific errors regarding the connectivity.
If you have errors, please post.
June 15, 2011 at 12:49 am
ping and telnet works on both directions.
i dont see any errors.
the thing is that the server are not in a domian,
so i can't build a fully qualified domain for the mirror.
more info that may help : its win2008 R2 sp1,sql2008sp1, the sql service runs under the windows Admin (should be changed to network service? - i tried it out, but the sql wont start beacuse it says it can't access the sys-db's which i have moved to another drive from the sql install drive).
June 16, 2011 at 9:33 am
Are you using certificate authentication to connect the endpoints? Windows authentication won't work if the SQL Server services are not both running under trusted domain accounts.
Administrator might be okay for testing and development, but I would suggest running the production services under an unprivileged user account.
HTH
June 16, 2011 at 12:41 pm
what do ypu mean by
"but I would suggest running the production services under an unprivileged user account. "
June 17, 2011 at 4:10 am
Sorry, I was thinking about this BOL page http://msdn.microsoft.com/en-us/library/ms143504%28v=SQL.100%29.aspx, particularly for the computer that is not in the domain, if I have read the thread right.
June 20, 2011 at 12:56 am
Why not use FQDN?Are you getting error 1418?
“When I hear somebody sigh, ‘Life is hard,’ I am always tempted to ask, ‘Compared to what?’” - Sydney Harris
June 20, 2011 at 1:40 am
i am getting 1418.
i tried to use FQDN, something like :
tcp://server.fakedomain:5023
where i put : server.fakedomain in the host file
or should i try to do it in another way?
June 20, 2011 at 12:17 pm
Make sure your endpoints are set up for mirroring by certificate (I don't believe you have any choice about this if you are not on a domain) - I don't remember if you can do this with the SSMS wizard.
You should then be able to run the following to start the mirror session:
-- Mirror ... start mirroring to primary
ALTER DATABASE xxxx SET PARTNER = 'tcp://ip:port' --(use primary ip/port info)
-- Primary ...
ALTER DATABASE xxxx SET PARTNER = 'tcp://ip:port' --(use mirror ip/port info)
The SSMS wizard validates the FQDN so you have to do this by script.
June 20, 2011 at 12:51 pm
first thanks - i will check it out.
i understand that that i need to run the 2 commands from the principal server? and if yes, how does it know to first set the defenition for the principal and then to the mirror?
10x
peleg
June 20, 2011 at 12:58 pm
Sorry, I wasn't clear enough - run the first command from the mirror server, and the second command from the primary.
Viewing 15 posts - 1 through 15 (of 16 total)
You must be logged in to reply to this topic. Login to reply