configuring redundant cfg dbservers

[Williams]

Rene,
below is my dbserver.cfg file for my backup db server:

[dbserver]
host=s-qa-genapp
port=4040
management-port =4041
dbprocesses_per_client=1
dbprocess_name=./dbclient_msql
#
oracle_name=./dbclient_oracle
informix_name=./dbclient_informix
msql_name=./dbclient_msql
sybase_name=./dbclient_sybase
db2_name=./dbclient_db2
#
connect_break_time=1200
tran_batch_mode=off
#
#---------- dbserver log options ----------
#
[log]
verbose=all
all=c:\gcti\logs\cfg_dbserver_b\db

[lca]
lcaport=4999

[victor]

I was able to get PRIMARY/BACKUP:
[attachimg=1]

My suggestion would be the following:

1. remove backup server definition from your cfg_dbserver in CME.
2. press APPLY
3. check that both of them are shown as PRIMARY in SCI
4. select cfg_dbserver_b as BACKUP SERVER for cfg_dbserver in your CME again and select WARM standby
5. press APPLY

it should then show PRIMARY/BACKUP in your SCI.

[René]

Cavagnaro - The license key "occ_full" means that you can run the campaigns in all supported modes (preview, predictive, progressive). That license has no relation to HA. If you have license "HA_redundancy" for SCS then you can run OCS in HA and SCS will switchover to backup server if the primary fails.

R.

[René]

Williams,

Maybe the way suggested by Victor would be the best one. Uninstall all cfg_dbserver applications, delete these from CME and start again for scratch. I would say we've checked all configurations and these seem to be correct...

R.

[Williams]

Rene,Victor,

Many thanks for your help. After taking the backup off of the primary and then applying it again...the backup started up in backup mode. I guess after I made all the to the command line argument in CME, the startserver.bat file and the image path, I needed to do the above.

Here's an excerpt from the log:

13:20:03.223 Trc 06084 Configuration option set: 'lca':'lcaport' = '4999'
Open LCALayer on port=4999
LCA Library version 7.5.000.05
13:20:03.223 Std 05060 Application started
Open server port: = (
  "name" = "dbserver"
  "server-type" = "46"
  "port" = "4040"
)
13:20:04.269 Std 04525 Port 4040 opened for listening
************************************
LCALayer: REventRegistered on LCA...
************************************
LCALayer: DBID changed from 0 to 255
Listener (port id = dbserver fd = 260) is being closed. Checking for clients on listener...
Listener with port id = dbserver has been closed and deleted from list of current ports. Number of db app connections affected: 0
13:21:54.588 Std 04560 Warm Standby (backup) mode activated

[victor]

It would be nice to say that SOMEBODY [hint-hint ] called you and SOMEBODY [once again...hint! ] on their vacation took the time out to help you out while having his really upset girlfriend next to him demand to choose between Genesys or her...

[Williams]

Tell your girlfiend, I am very very sorry.
but seriously, I couldn't even get genesys tech support to help me with this. they had to escalate on their side.

thanks again to everyone that took time out to support and provide specific instructions

[cavagnaro]

[quote author=victor link=topic=2706.msg10799#msg10799 date=1199915334] while having his really upset girlfriend next to him demand to choose between Genesys or her...
[/quote]
Why is this is getting more common every day?
We the non understood...

[SorinM]

Hello to all,

I'm realy new with Genesys, i took some courses. We want to find a method to have a backup server for entire Genesys installation. Do you know how i can do this? If i want to use the HA from Genesys, how should the second server be installed? I will install the first server without specifying backup server?Then i will install again Genesys on another server and then i should make the connection between them through the backup server field for every component? How can i ensure the redundancy of Databases? It has to be smth. else independent from Genesys?

Thank you!

[cavagnaro]

Yes, on the main application you need to define the backup application so when main goes down SCS can send the order to standby server to start.
Usually you have two kinds of HA, Warm and Hot standby, each one of them is specified on the servers deployment guides. Basically on warm standby it will not receive data until SCS tells it to be main, while on hot standby it will be alive and receiving all events so when main goes down it will easily take main, however both has pro/cons like bandwidth consumption on one side and time to be ready on the other hand for example.
About DB it is not a Genesys task, you must talk to your DBAs for that sort of configuration.