Setting up HDR - 11.50.FC1
Posted in 2010
Topics: High Availability & Replication, Storage & Space Management, Server Administration, Logging & Checkpoints, Networking & sqlhosts Configuration, Platform-Specific Issues
Hi,
I am trying to setup HDR in two Linux servers inftest1 and inftest2. I
followed the instruction below, but step #7 below was confusing. I tried
"onmode -d primary inftest1". The result from onstat - is "On-Line (Prim)".
But I also get message from the online.log
09:53:02 SCHAPI: Started dbScheduler thread.
09:53:02 DR: new type = standard
09:53:46 DR: new type = primary, secondary server name = inftest1.newpiper.net
09:53:46 DR: Cannot connect to secondary server
09:53:46 DR: Turned off on primary server
The backup and restore were good from both servers. I confuse with the onmode
-d from both primary and secondary servers which are inftest1, inftest2
respectively.
On the primary
1. Edit the HDR configuration parameters (DRAUTO, DRTIMEOUT,
DRINTERVAL, DRLOSTFOUND, DRIDXAUTO and, optionally,
LOG_INDEX_BUILDS) in the $ONCONFIG file.
2. Add entries to the $INFORMIXSQLHOSTS and /etc/services files for network
connections.
3. Modify the /etc/hosts.equiv or the .rhosts file for the informix user ID to
enable
trusted communication.
4. Make sure the databases to be replicated are in logged mode.
5. Send a copy of the primary instances $ONCONFIG file to the secondary
server.
6. Make a level 0 archive.
7. Run onmode -d primary secondary_server.
On the secondary
1. Add entries to the $INFORMIXSQLHOSTS and /etc/services files for network
connections.
2. Modify the /etc/hosts.equiv or the .rhosts file for the informix user ID to
enable
trusted communication.
3. Modify the ONCONFIG parameters for the secondary server:
DBSERVERNAME and DBSERVERALIASES4. Make sure that all chunk paths are created, have the correct permissions,
and
ensure that there is enough space on the disks for the data to reside.
5. Do a physical restore of the physical archive.
6. If necessary, run onmode -l to roll forward any logical logs that may have
been saved on the primary before the secondarys physical restore finished.
7. Run onmode -d secondary primary_server.
TRI TRINH wrote:
> Hi,
>
> I am trying to setup HDR in two Linux servers inftest1 and inftest2. I
> followed the instruction below, but step #7 below was confusing. I tried
> "onmode -d primary inftest1". The result from onstat - is "On-Line (Prim)".
> But I also get message from the online.log
>
> 09:53:02 SCHAPI: Started dbScheduler thread.
> 09:53:02 DR: new type = standard
> 09:53:46 DR: new type = primary, secondary server name =
inftest1.newpiper.net
> 09:53:46 DR: Cannot connect to secondary server
> 09:53:46 DR: Turned off on primary server
>
> The backup and restore were good from both servers. I confuse with the onmode
> -d from both primary and secondary servers which are inftest1, inftest2
> respectively.
>
> On the primary
> 1. Edit the HDR configuration parameters (DRAUTO, DRTIMEOUT,
> DRINTERVAL, DRLOSTFOUND, DRIDXAUTO and, optionally,
> LOG_INDEX_BUILDS) in the $ONCONFIG file.
> 2. Add entries to the $INFORMIXSQLHOSTS and /etc/services files for network
> connections.
> 3. Modify the /etc/hosts.equiv or the .rhosts file for the informix user ID
to
> enable
> trusted communication.
> 4. Make sure the databases to be replicated are in logged mode.
> 5. Send a copy of the primary instances $ONCONFIG file to the secondary
> server.
> 6. Make a level 0 archive.
> 7. Run onmode -d primary secondary_server.
This tells the primary that it will be the primary and what the name of
the secondary will be so that it can watch out for it.
> On the secondary
> 1. Add entries to the $INFORMIXSQLHOSTS and /etc/services files for network
> connections.
> 2. Modify the /etc/hosts.equiv or the .rhosts file for the informix user ID
to
> enable
> trusted communication.
> 3. Modify the ONCONFIG parameters for the secondary server:
> DBSERVERNAME and DBSERVERALIASES> 4. Make sure that all chunk paths are created, have the correct permissions,
> and
> ensure that there is enough space on the disks for the data to reside.
> 5. Do a physical restore of the physical archive.
> 6. If necessary, run onmode -l to roll forward any logical logs that may have
> been saved on the primary before the secondarys physical restore finished.
> 7. Run onmode -d secondary primary_server.
This tells the secondary that it's a secondary and what the name of the
primary is, so that it can contact.
--
Cheers,
Obnoxio The Clown
http://obotheclown.blogspot.com
I will now proceed to pleasure myself with this fish.
--
This message has been scanned for viruses and
dangerous content by OpenProtect(http://www.openprotect.com), and is
believed to be clean.
I issue the command "onmode -d primary inftest1.newpiper.net -d secondary
inftest2.newpiper.net" and this is what I get "DR: Unable to change server type
onmode: Please check the message log for errors."
online.log result
10:24:10 DR: new type = standard
10:24:10 SCHAPI: Started dbScheduler thread.
10:25:22 DR: Error - Server must be in recovery mode
Do I have the right format for the onmode -d?
----- Original Message -----
From: "TRI TRINH" <tri_trinh@hotmail.com>
To: <ids@iiug.org>
Sent: Tuesday, August 24, 2010 9:05 AM
Subject: Setting up HDR - 11.50.FC1 [21030]
> Hi,
>
> I am trying to setup HDR in two Linux servers inftest1 and inftest2. I
> followed the instruction below, but step #7 below was confusing. I tried
> "onmode -d primary inftest1". The result from onstat - is "On-Line
> (Prim)".
> But I also get message from the online.log
>
> 09:53:02 SCHAPI: Started dbScheduler thread.
> 09:53:02 DR: new type = standard
> 09:53:46 DR: new type = primary, secondary server name =
> inftest1.newpiper.net
> 09:53:46 DR: Cannot connect to secondary server
> 09:53:46 DR: Turned off on primary server
If you want inftest1 to be the Primary and inftest2 to be the Secondary then
you should
run 'onmode -d primary inftest2' on inftest1, you will get similar errors in
the online log because inftest2 has not yet been instructed to be a
secondary and therefore will not allow an HDR connection from inftest1.
run 'onmode -d secondary inftest1' on inftest2. After this command is run
and if everything is configured correctly the two servers will start talking
and syncing and HDR will be running.
If you haven't already, check out my blog post on HDR:
http://www.informix-dba.com/2010/08/informix-hdr-will-save-your-butt.html
Andrew
Thank you Obnoxio and Andrew. I got it now. The instruction is quite clear. It's me that I do need you to point it out for me. I love the forum. Thanks again, and for the blog. tri