Cold Standby DR BES server won't register with Production BES server

Usage and Config Platform
1

(imported topic written by Pete_Andrews19)

I have a Disaster Recovery BES server which has BES server software installed. During business-as-usual operation, all the BES services are stopped (except for the client) and I want this server to be manageable from the production BES server. However, the DR server cannot register with production BES - the following entry appears in the BES client log on the DR host :

At 09:54:46 +1100 -

RegisterOnce: Attempting to register with ‘http://127.0.0.1:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe60&ClientVersion=6.0.12.5&Body=1162502407&SequenceNumber=6365&MinRelayVersion=6.0.0.0’

At 09:54:47 +1100 -

RegisterOnce: GetURL failed

The server can resolve “bigfix” to the production host, and the host file only contains the following entry :

127.0.0.1 localhost

It looks as though the BES client on the DR host is setting it’s focus to localhost for some reason, despite all the server services being stopped, and the DNS alias “bigfix” resolving to the production host. We don’t see this for any other client in the enterprise. Has anyone seen this before ?

We are running the following BES versions currently :

Server 6.0.12.5

Client 6.0.15.7

2

(imported comment written by jessewk)

Pete,

The client on a box with the server installed cannot report to a different server.

Jesse

3

(imported comment written by SystemAdmin)

Pete,

The BES Client checks to see if the BES Root Server service is present and will use the loop back if so.

The only way I have found to work around this would be to change the name of the BES Root Server service. It would need to be changed back prior to failing over to it though.

Tyler