BH, Hi i'm having a problem when trying to use database mirroring on two different machines. I have 2 computers. 1st computer is running server1 and Arbiter. 2nd computer is running server2. I've created 2 services (using sybase central) on computer1 with the following configurations.
-x tcpip(port=2640) -n arbiter -xa AUTH=abc;DBN=mtrs16 -xf D:\RMT\arbiter\arbiterstate.txt -su
and 2nd service:
-n mtrs16a -x tcpip(PORT=2638) -xf d:\RMT\mtrs16\mtrs16astate.txt -su sql d:\RMT\mtrs16\mtrs16.db -sn mirrordemo_test -xp partner=(ENG=mtrs16b;LINKS=tcpip(PORT=2639;TIMEOUT=1));auth=abc;arbiter=(ENG=arbiter;LINKS=tcpip(PORT=2640;TIMEOUT=1));mode=sync
On the 2nd computer I have one service running with following commands.
-n mtrs16b -x tcpip(PORT=2639) -xf d:\RMT\mtrs16\mtrs16bstate.txt -su sql d:\RMT\mtrs16\mtrs16.db -sn mirrordemo_test -xp partner=(ENG=mtrs16b;LINKS=tcpip(PORT=2638;TIMEOUT=1));auth=abc;arbiter=(ENG=arbiter;LINKS=tcpip(PORT=2640;TIMEOUT=1));mode=sync
The strange thing is, that when I have server1, server2, and arbiter all on the same computer, than it works fine. However, when I move server2 to a different computer, it does not connect to arbiter and to server1. I'm sure that the computer2 sees the computer1, because I can ping the ip and connect to computer1 using the ODBC Administrator. What am I doing wrong?
Your -xp parameter on the 2nd computer has the wrong ENG= value - it says mtrs16b and should be mtrs16a.
Also check to make sure that you don't have firewalls getting in the way: on your 2nd computer run
dbping -c ENG=mtrs16a;LINKS=tcpip(PORT=2638)
to test connectivity to your primary server and run
dbping -c ENG=arbiter;LINKS=tcpip(PORT=2640)
to test connectivity to your arbiter.
If the above two dbping commands are successful then ensure that connections in the other direction also work. I.e. run
dbping -c ENG=mtrs16b;LINKS=tcpip(PORT=2639)
I somehow solved the problem. When i connected to a different network, i was able to connect to the servers and arbitrator. I'm not exactly sure why the other network was giving me such a hard time, but the only explanation i can think of is the difference in the 3rd set of the ip addresses. For example: Senario 1. Srv1 ipv4: 192.168.254.18 Srv2 ipv4: 192.168.100.17 DOES NOT WORK.
Senario 2. Srv1 ipv4: 192.168.254.18 Srv2 ipv4: 192.168.254.17 WORKS. Could that have been possibly the problem?
answered 24 Dec '13, 18:14