When the primary data center fails, you can fail over to the secondary data center. To fail over, you need to modify the global load balancer or DNS record to point to the load balancer in the secondary data center.

Depending on your database setup, the VMware Identity Manager appliances in the secondary data center are either in read-only mode or in read-write mode. For all databases except SQL Server Always On, the VMware Identity Manager appliances are in read-only mode. Therefore, most administrator operations, such as adding users or apps, or entitling users, are not available.

If you are using a SQL Server Always On deployment, the VMware Identity Manager appliances in the secondary data center are in read-write mode.

Important:

After you fail over to the secondary data center, you must clear all caches on the original primary data center. In case you need to fail over to the original primary data center, caches in that data center should be empty.

You can use a REST API to clear the cache. Run the following REST API from a REST client such as Postman:

PATH: /SAAS/jersey/manager/api/removeAllCaches

Method: POST

Add Headers:

Authorization: HZN <cookie_value>
Accept: application/vnd.vmware.horizon.manager.cache.removal.response+json
Content-type: application/vnd.vmware.horizon.manager.cache.removal.request+json’

Add in Body (raw) section:

{
"cacheNames”:[ 
]
}

Empty cacheNames indicates remove all caches.

Another way to clear cache is to reboot the virtual appliances.