Ok, while I am researching HA standby for cfg_dbserver, here are some basic things:
- there is no need to for your cfg_dbserver to be in BACKUP mode.
- there is a section called [dbserver] in your confserv.conf file that defines your PRIMARY dbserver. inside that section, toward the end, you have "server = " option where you define your backup dbserver you want you config server to switch to, should first go down. create [dbserver_backup] section right after the last line of [dbserver] section and fill out information on your backup dbserver
I would suggest for your backup configserver to use [dbserver_backup] section as primary access point with [dbserver] as your backup. Of course, this depends on your system layout, but still...
I will try to do some tests with HA dbserver setup, but I do not see the point of having DBSERVER in backup mode. Especially "HA" - it just does not make much sense, since unlike TServer there is nothing to synchronize. DBserver is just a mean of accessing DB.
Oh, yeah, important thing: make sure you have [lca] section in your dbserver.conf file, something like this:
[lca]
lcaport=4999
this actually tells your cfg_dbserver to connect to LCA.
As I was looking through the log you have posted, you have this:
Listener (port id = dbserver fd = 232) 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
21:41:42.171 Std 04560 Warm Standby (backup) mode activated
Looks weird to me.

First of all: if you have startServer.bat, why would you not just call it from Path? You do not to specify anything other than that!
In your startServer.bat add "-service DBServer" for your primary DBSErver and "-service DBServer_b" (or whatever the name of your backup DBServer service is for backup server.
You do not need -cfg if the name of your dbserver is cfg_dbserver, BUT you will need it for cfg_dbserver_b. (Genesys knows that dbserver's name if cfg_dbserver, it means it is db server for config server and it needs to read dbserver.cfg file to get all the info.)
For your cfg_dbserver_b, I strongly suggest adding -c inside your batch file and specifying the name of your cfg_dbserver_b's config file just to avoid any potential screw ups in a future. (you DID replace Path Info in CME cfg_dbserver with the path to you batch file, right?)
Vic