nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

TeamSite 7.3.1 High-availability

pdasarat

Hi,

I'm trying to setup a 7.3.1 (active/passive) configuration, since now 7.3.1 is using DB's extensively, how will the DB mapping work with an active/passive configuration. Is there any manual DB configuration changes that needs to be done if we fail over to the other TeamSite server?

I'm currently trying the installation on the active/passive node, but any expert thoughts if it was already implemented?

Thanks,
Pradeep

Find more posts tagged with

Comments

mart2001

Suppose that you have teamsite1 and teamsite2 server each pointing to their own db (db1, db2). You could have the db1 replicated to db2 and if any entries in the db itself contains the ts server name, you could put in a dns entry for the ts server. Then when you fail over, the database should have the correct name. You could have dns entries for the db itself, then when the teamsite2 server takes over, you can have that already pointing at the correct db without much effort.

pdasarat

Thanks. That's how the current setup is for 6.7.2 without the DB portion.

In 7.3.1, we just have one DB server, so to test the installation on the second TeamSite instance, we have to spoof the testing with a local hosts file.

kannan

Yes, we did that recently.

As per 7.3.1. Infrastructure Components like Common Services has been introduced which is used by ReportCenter, Administration Console for authentication and configuration information. Service IDs for different components have been introduced which get stored in IR_SERVICEINFO table along with server hostname.

Installing TeamSite on node A would have registered the hostname of node A in the IR service registry.

use cms_common_services;
Select * from IR_SERVICEINFO;

The hostname column value is register as installed node name.

Ask you system admin to configure the same hostname for both the node and update the IR_SERVICEINFO table hostname column info will work.

pdasarat

Thanks Kannan.

So in your case, you have two instances of databases running for each instance of TeamSite or one common DB and then manually update the IR_SERVICEINFO table with the active teamsite host name?

kannan

if you using hardware HA , only one DB instance need to be installed.

kannan

Is 2 instances of TeamSite running on the same host ?

pdasarat

No we are using 2 separate hardware for TeamSite. I basically tried installing the second instance of teamsite using the same shared common services which i installed on Node A. The installer didn't allow me to install TeamSite on Node B.

Moreover there were some clash on the SERVICEINFO tables. There needs to be some manual update of data when we failover to second server.