Hi there, i hope you can help me again :-) We want to install HA (mirroring) on 3 server: IMS-02 (192.168.0.109), IMS-backup (192.168.0.103) and Pro-2 (192.168.10.164) This mirroring system should be running as service. I had connected to the primarydb on IMS-02 and hat created this with Interactive SQL: create mirror server PrimaryDB_primary as primary connection_string='SERVER=PrimaryDB_primary;HOST=IMS-02:46000,IMS-backup:46035'; create mirror server PrimaryDB_partner as partner connection_string='SERVER=PrimaryDB_partner;HOST=IMS-02:46000' state_file='G:\primary_db\server1.state' preferred='YES'; create mirror server PrimaryDB_mirror as mirror connection_string='SERVER=PrimaryDB_mirror;HOST=IMS-02:46000,IMS-backup:46035'; create mirror server PrimaryDB_mirror_partner as partner connection_string='SERVER=PrimaryDB_mirror_partner;HOST=IMS-backup:46035' state_file='\192.168.0.103\IMSTTEST_db\server2.state'; create mirror server PrimaryDB_Arbiter as arbiter connection_string='SERVER=PrimaryDB_Arbiter;HOST=PRO-2:46020'; set mirror option authentication_string='abc'; set mirror option synchronization_mode='synchronous'; Then i had defined a service on Pro2 for the Arbiter with the following config parameter: -n PrimaryDB_Arbiter -su sql23 -x "TCPIP(PORT=46020;DOBROAD=no)" -xf "c:\arbiter\arbiter.state" -xa "AUTH=abc;DBN=PrimaryDB" 2nd service on IMS-02 as primary server: -n PrimaryDB_Server -x tcpip(ServerPort=46000;doBroadcast=no) -xf "G:\primary_db\server1.state" G:\primary_db\primary.db -ek akira2468 -n PrimaryDB 3rd service on IMS-backup as mirror server: -n PrimaryDB_Mirror -x tcpip(PORT=46035;DOBROAD=no) -xf "F:\IMSTTEST_db\server2.state" -su sql23 F:\IMSTTEST_db\primary.db -oe "C:\error_sql_mirror.txt" -ek akira2468 -n PrimaryDB The services will be started, but in the overview on Sybase Central (Health & Statistics), there will not shown the grafic for the functions Arbiter and Mirror. If i have a look to the state file for primary server, i find this: [PrimaryDB] Owner=<partner> State=synchronizing Mode=synchronous Sequence=1 Yielding=No But the file for the mirror server is empty! I had also started the services with the following parameters for each server but the mirror system doesn't work: -xp partner=(ENG=PrimaryDB_partner;LINKS=tcpip(PORT=46000;TIMEOUT=1));auth=abc;arbiter=(ENG=PrimaryDB_Arbiter;LINKS=tcpip(PORT=46020;TIMEOUT=1));mode=synchronous Can somebody tell me what goes wrong and how to fix? thanks and best regards from germany Sabrina asked 12 Mar '15, 07:26 sabstar |
I notice a few potential problems:
answered 12 Mar '15, 09:51 Ian McHardy I had another look at the mirror server definitions. There a number of errors in the server names. The whole system has many errors. I suggest reading over the doc very carefully and paying attention to the details of the server names, mirror server definitions and command lines. See: http://dcx.sap.com/index.html#1201/en/dbadmin/database-mirroring-tutorial-setup.html http://dcx.sap.com/index.html#1201/en/dbadmin/backup-s-3894811.html http://dcx.sap.com/index.html#1201/en/dbreference/create-mirror-server-statement.html*d5e39948 Take a really close look at the server names in the AS clause description of the CREATE MIRROR SERVER link.
(12 Mar '15, 10:08)
Ian McHardy
Thanks for your answers! Is it possible to run the Arbiter on a 3rd Server? Or is it ok if it runs on the same like the primary? regards, Sabrina
(16 Mar '15, 04:20)
sabstar
Replies hidden
It is not only possible but highly recommended to run the arbiter on a 3rd server. If the arbiter runs on the same machine as the primary server (which is of course possible, too), once the network connection of this machine becomes unavailable the secondary server will not be able to take over as he cannot agree with the arbiter that he should become the primary now. Basically, you restrict the notion of "Two of the three (primary, secondary, arbiter) must be available" when putting two of them on the same hardware. Therefore you will have a restricted HA system with that configuration. Note: That's meant for production uses. When you are just about to test the HA facility, you can also run all three on one hardware...
(16 Mar '15, 04:41)
Volker Barth
The arbiter should be running on a different machine (not on one of the mirrored servers), so the arbiter will keep running if one of the servers becomes unavailable.
(16 Mar '15, 04:45)
Reimer Pods
Thanks, but where do i have to config the arbiter with "Create mirror server xyz as Arbiter...". On the same DB as the Primary DB (in Interactive SQL)? Because the 3rd Server don't knows the arbiter, if i create the arbiter on die PrimaryDB...
(16 Mar '15, 05:21)
sabstar
Replies hidden
The CREATE MIRROR SERVER statements are meant to be run on the original database before the HA setup is started, i.e. you let them run in the initial database and then copy that database to the second server and try to start your HA system, so both the primary and secondary server have the same database contents available when they start...
(16 Mar '15, 06:49)
Volker Barth
|
The SERVER=PrimaryDB_mirror_partner doesn't match anything else. answered 12 Mar '15, 09:37 Breck Carter |
I forgot something:
In the file error_sql_mirror.txt for the mirror server are these entries: Database could not be started - missing or invalid database mirroring options.