Virtual Desktop Infrastructure High Availabilty/Failover Appears To Not Be Available (Doc ID 1360417.1)

Last updated on OCTOBER 15, 2014

Applies to:

Oracle Virtual Desktop Infrastructure - Version 3.3 to 3.5.1 [Release 3.0]
Information in this document applies to any platform.

Symptoms

With Virtual Desktop Infrastructure (VDI) version 3.3+ configured in High Availability mode as outlined in the Product Documentation, the following state may be observed in the cluster after an incomplete Failover attempt:

From master server:

# vda-db-status

Ip/Hostname Database host Role Status
----------------------------------------------------------------------
vdi-primary.vdicustomer.local Master up
vdi-secondary-first.vdicustomer.local Slave down

# vda-center status

HOST NAME HOST STATUS SERVICE SERVICE STATUS
vdi-secondary-second.vdicustomer.local Up - -
vdi-primary.vdicustomer.local Up VDI Database Up
vdi-secondary-first.vdicustomer.local Up VDI Database Replication Down

3 host(s) in center.

From the slave:

# vda-db-status

Ip/Hostname Database host Role Status
----------------------------------------------------------------------
vdi-secondary-first.vdicustomer.local Master up
vdi-primary.vdicustomer.local Slave down


# vda-center_status

HOST NAME HOST STATUS SERVICE SERVICE STATUS
vdi-secondary-second.vdicustomer.local Up - -
vdi-primary.vdicustomer.local Up VDI Database Replication Down
vdi-secondary-first.vdicustomer.local Up VDI Database Up

3 host(s) in center.


As can be seen, the master thinks the secondary is down and vice versa. VDI services though are running and available on all the servers. In addition, from comparing the file /var/opt/SUNWvda/cluster.map on the primary and the slave it is noticed that:

From master:

db.master.host.id=vdi-primary.vdicustomer.local
db.replicate=true
db.replication.autoconfig=true
db.replication.host.ids=vdi-secondary-first.vdicustomer.local
srs.primary.host.id=vdi-primary.vdicustomer.local

From slave:

db.master.host.id=vdi-secondary-first.vdicustomer.local
db.replicate=true
db.replication.autoconfig=true
db.replication.host.ids=vdi-primary.vdicustomer.local
srs.primary.host.id=vdi-secondary-vdicustomer..local

Here we can see that the db.master.host.id= is set incorrectly on the slave. It should set to the master.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms