Connections for High Availability Servers

[pspenning]

Good Day All,

I think I know this answer but I want to bounce this off of you for your take on it…

My scenario is:
ReportingStatServer_A – Atlanta, GA
ReportingStatServer_B – Covington, GA (Hot Standby)

AvayaTServer_A – Atlanta, GA
AvayaTServer_B – Covington, GA (Hot Standby)

Should my connection tab for ReportingStatServer_A include both Avaya T-Servers or only the A Server?
Should my connection tab for ReportingStatServer_B include both Avaya T-Servers or only the B Server?

I think both ReportingStatServers should include any and all redundant servers that need to connect to them such as the T-Servers as well as the Message Servers.

Am I thinking on the right path and would this logic hold true for any other High Availability servers?

The reason I think this is in case the hardware fails on one server, the backup server will know which primary server to talk to.  i.e. - ReportingStatServer_A fails but AvayaTServer_A is still happy.  ReportingStatServer_B (Which is now primary) would have a connection to AvayaTServer_A and therefore would still be able to get stats.

Am I thinking right on this?
Thanks,
Perry

[mark]

Both should have connections to Primary T-Servers.

[pspenning]

Thanks!
So I would assume this is the same with other server connections which are High Available as well?
Thanks again,
Perry

[catanirex]

Hi,

If I'm not wrong, StatServer only supports Warm standby.

And you do not (dont need to) set up connections on the backup application. When you define it as a backup server on the primary applications - all connections are inherited from that one. (In 7.5/7.6 at least) It almost magic :-)

[pspenning]

Thanks...  I just E-mailed my instructor from Genesys U. and he said the same thing.

Quote:  "Each Stat Server should include a connection to the *primary* T-Server (and vice-versa: each Stat Server has connection to primary T-Server).  The management layer will then handle failover to the redundant Stat Server in the event the primary becomes unavailable.  Upon startup, Genesys servers contact the config layer and learn the clustering of HA components.  So in your situation, ReportingStatServer_A will connect to AvayaTServer_A and learn that it has redundancy provided by AvayaTServer_B.  When notification arrives from the management layer that failover has occurred, it will know where to failover to."

Thanks Ryan!

[mark]

[quote author=catanirex link=topic=2597.msg10142#msg10142 date=1195674739]
Hi,

If I'm not wrong, StatServer only supports Warm standby.

And you do not (dont need to) set up connections on the backup application. When you define it as a backup server on the primary applications - all connections are inherited from that one. (In 7.5/7.6 at least) It almost magic :-)


[/quote]

That is a good point, it does inherit the connections from the primary app from the HA pair. Makes me wonder how they put this little feature in but seem to miss so many others!!