Cluster project
Posted in 2016
Asked whether 15 Informix instances can be replicated across two servers using HDR. Answer: yes — each primary gets its own HDR secondary on the other box (up to 255 instances per machine), with ROOTPATH, DBSERVERNAME, DBSERVERALIASES, HA_ALIAS and DBSERVERNUM set uniquely per instance. Contributors added practical advice: unique port per instance, environment-setting scripts, KAIO/AIO tuning on Linux, separate INFORMIXDIR for independent upgrades, and the caution that 15 instances means 15 backups/logs to manage — suggesting fewer instances with multiple databases, or multi-tenancy, instead.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Topics: High Availability & Replication, Clustering, Grid & MACH11
Hi, I have one customer that request a project to replicate 15 instances over two servers on HDR. Is that possible? How can I do it? Thanks for any help. SP sergio.peres@airc.pt
Yes, it can be done. Each primary instance will have its own HDR secondary instance on the other machine. Set the following ONCONFIG parameters to be different for each primary server: ROOTPATH, DBSERVERNAME, DBSERVERALIASES, HA_ALIAS, DBSERVERNUM The ROOTPATH will be the same between a primary and its corresponding HDR secondary (and optionally the DBSERVERNUM can be the same), but again, the rest of these parameters will be different for the secondaries as well. Art Art S. Kagel, President and Principal Consultant ASK Database Management www.askdbmgt.com Blog: http://informix-myview.blogspot.com/ Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. On Wed, Dec 28, 2016 at 2:05 PM, SERGIO PERES <sergio.peres@airc.pt> wrote: > Hi, > > I have one customer that request a project to replicate 15 instances over > two > servers on HDR. Is that possible? How can I do it? > > Thanks for any help. > > SP > sergio.peres@airc.pt > > > ************************************************************ > ******************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --001a1148d7be0e121c0544bd6ac5
Up to 255 instances (SERVERNUMs) possible on one box (OS). Up to 255 more=20 on a second box which could be secondaries to those instances on first=20 box. No different to having a single primary and secondary on two boxes. HTH, Andreas From: "SERGIO PERES" <sergio.peres@airc.pt> To: ids@iiug.org Date: 28.12.2016 20:06 Subject: Cluster project [38384] Sent by: ids-bounces@iiug.org Hi,=20 I have one customer that request a project to replicate 15 instances over=20 two=20 servers on HDR. Is that possible? How can I do it?=20 Thanks for any help.=20 SP=20 sergio.peres@airc.pt=20 ***************************************************************************= ****=20 Forum Note: Use "Reply" to post a response in the discussion forum.=20
You might want to consider using multi-tenancy as is part of the current releases so you can reduce the complexity of the operational environment that would be created by having multiple instances on a single machine. That way there would only be a need for a single primary instance and a single secondary instance. Madison Pruet Retired and Loving it On Wednesday, December 28, 2016 1:06 PM, SERGIO PERES <sergio.peres@airc.pt> wrote: Hi, I have one customer that request a project to replicate 15 instances over two servers on HDR. Is that possible? How can I do it? Thanks for any help. SP sergio.peres@airc.pt ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.
Thank you all for the answers, as I understand correct me please if I am wrong, I should have 15 instances on both servers. So I can have one replica for each client instance? SP sergio.peres@airc.pt
Affirmative. Art On Dec 28, 2016 4:19 PM, "SERGIO PERES" <sergio.peres@airc.pt> wrote: Thank you all for the answers, as I understand correct me please if I am wrong, I should have 15 instances on both servers. So I can have one replica for each client instance? SP sergio.peres@airc.pt ************************************************************ ******************* Forum Note: Use "Reply" to post a response in the discussion forum. --001a114b71b8d9f5e10544bf2581
Hi,
you can do it that way, although you should try to find a structure to
overview your instances.
(to not use accidentally the wrong one for certain actions).
Open admin tool can help with this.
Each instance needs to have a peer on the secondary server (and can be
switched to the
other machine by swapping the roles (and maybe the primary IP adresses)).
Because the primary service for each instance can be located on any of the
machines, you might get fuzzed
which instance is running where and which hard disk spaces are assigned to
which instance ...
We are running multiple instances on one machine with lvm to have "speaking"
names for the partitions.
And of course, you will have to take 15 backups and manage 15 log files,
search 15 instances for expensive statements ....
Each instance should have a listener on a specific IP/Port combination. The
recommendation would
be to have a unique TCP listener (on a separate port) for each instance and
not deal with a separate IP adress per instance.
That way, you can handle the instances with less IP adresses, perhaps use only
ports to differ the services.
Also, provide scripts somewhere in your search path to easily switch between
instances on the command line.
Something like
$ . ifxinstance1(which would modify the environment INFORMIXSERVER, INFORMIXDIR,
ONCONFIG,maybe IFX_ONTAPE_FILE_PREFIX).
Additionally, when running multiple instances (at least on linux), you should
care about the KAIOON environment.
The aio consumption of each instance has to be controlled, otherwise some
instances might not get enough resources.
For us, it was always easier to have many databases in one instance, so you do
not have
to care about so many instances, backups, statistics, memory settings, locks,
chunk assignment, space consumption ...
Within one instance (or maybe lets say 3 instead of 15) the whole management
might be easier.
But if the requirement is to have separate instances, it should work.
If the instances are used almost identically, the memory and space
requirements could be copied between instances,
but if the instances have different amount of data to carry and different
number of sessions (= memory), you should
take care how much memory each instance will be assigned.
Just keep in mind, you will have to upgrade all instances at the same time,
when it comes to new versions.
In case you want to prevent that, you should have also different installation
folders (maybe containers for each instance)
to run them really separately, especially when there are service level
agreements in place you have to fulfil.
Hope this helps,
Marcus Haarmann
Von: "SERGIO PERES" <sergio.peres@airc.pt>
An: "ids" <ids@iiug.org>
Gesendet: Mittwoch, 28. Dezember 2016 22:18:47
Betreff: Re: Cluster project [38392]
Thank you all for the answers, as I understand correct me please if I am
wrong, I should have 15 instances on both servers. So I can have one replica
for each client instance?
SP
sergio.peres@airc.pt
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
Begs the question: "Why are there 15 instances to begin with?"
Art
Art S. Kagel, President and Principal Consultant
ASK Database Management
www.askdbmgt.com
Blog: http://informix-myview.blogspot.com/
Disclaimer: Please keep in mind that my own opinions are my own opinions
and do not reflect on the IIUG, nor any other organization with which I am
associated either explicitly, implicitly, or by inference. Neither do
those opinions reflect those of other individuals affiliated with any
entity with which I am affiliated nor those of the entities themselves.
On Wed, Dec 28, 2016 at 6:21 PM, Marcus Haarmann <marcus.haarmann@midoco.de>
wrote:
> Hi,
>
> you can do it that way, although you should try to find a structure to
> overview your instances.
> (to not use accidentally the wrong one for certain actions).
> Open admin tool can help with this.
> Each instance needs to have a peer on the secondary server (and can be
> switched to the
> other machine by swapping the roles (and maybe the primary IP adresses)).
> Because the primary service for each instance can be located on any of the
> machines, you might get fuzzed
> which instance is running where and which hard disk spaces are assigned to
> which instance ...
> We are running multiple instances on one machine with lvm to have
> "speaking"
> names for the partitions.
>
> And of course, you will have to take 15 backups and manage 15 log files,
> search 15 instances for expensive statements ....
> Each instance should have a listener on a specific IP/Port combination. The
> recommendation would
> be to have a unique TCP listener (on a separate port) for each instance and
> not deal with a separate IP adress per instance.
> That way, you can handle the instances with less IP adresses, perhaps use
> only
> ports to differ the services.
> Also, provide scripts somewhere in your search path to easily switch
> between
> instances on the command line.
> Something like
> $ . ifxinstance1> (which would modify the environment INFORMIXSERVER, INFORMIXDIR,
> ONCONFIG,maybe IFX_ONTAPE_FILE_PREFIX).
>
> Additionally, when running multiple instances (at least on linux), you
> should
> care about the KAIOON environment.
> The aio consumption of each instance has to be controlled, otherwise some
> instances might not get enough resources.
>
> For us, it was always easier to have many databases in one instance, so
> you do
> not have
> to care about so many instances, backups, statistics, memory settings,
> locks,
> chunk assignment, space consumption ...
> Within one instance (or maybe lets say 3 instead of 15) the whole
> management
> might be easier.
> But if the requirement is to have separate instances, it should work.
> If the instances are used almost identically, the memory and space
> requirements could be copied between instances,
> but if the instances have different amount of data to carry and different
> number of sessions (= memory), you should
> take care how much memory each instance will be assigned.
> Just keep in mind, you will have to upgrade all instances at the same time,
> when it comes to new versions.
> In case you want to prevent that, you should have also different
> installation
> folders (maybe containers for each instance)
> to run them really separately, especially when there are service level
> agreements in place you have to fulfil.
>
> Hope this helps,
>
> Marcus Haarmann
>
> Von: "SERGIO PERES" <sergio.peres@airc.pt>
> An: "ids" <ids@iiug.org>
> Gesendet: Mittwoch, 28. Dezember 2016 22:18:47
> Betreff: Re: Cluster project [38392]
>
> Thank you all for the answers, as I understand correct me please if I am
> wrong, I should have 15 instances on both servers. So I can have one
> replica
> for each client instance?
>
> SP
> sergio.peres@airc.pt
>
>
> ************************************************************
> *******************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
> ************************************************************
> *******************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--089e0122ae9ab1908a0544c114f4