Skip to main content

VMware workspace one swap primary role between two sites

 

Environment setup:
Three Workspace one nodes per site and have AVI load balancer with external Database.

Here are the steps for testing that failover:

  1. Change the LB to point to the DR site.
  1. You will need to clear caches in the primary datacenter by following the steps listed here: https://docs.vmware.com/en/VMware-Workspace-ONE-Access/21.08/workspace_one_access_install/GUID-A794E38F-974E-48B9-8BFF-3737472BC1BB.html
  1. Restart all connector services from both the primary and DR site
  1. Stop the horizon-workspace service on the primary nodes. As we can only have 1 read/write cluster on at a time.
  1. Promote the DR site to the primary by editing: /usr/local/horizon/conf/runtime-config.properties in the following ways on each of the nodes:
  1. read.only.service=true to read.only.service=false
  1. cache.service.type=ehcache to cache.service.type=rds
  1. Save
  1. Restart the horizon-workspace server on each node in DR.
  1. restart the connectors again (to establish a new s-channel
  1. We should no longer see that banner in the console.
  1. Start the horizon-workspace service on each of the primary datacenter’s nodes.
  1. Change LB back to primary datacenter.
  1. Change back the DR site to read-only= true
  1. Change back the DR site to cache.srevicetype=ehcache
  1. Restart the horizon-workspace service in DR.
  1. Restart connectors in DR & primary.

Comments

Popular posts from this blog

Calculate how much data can be transferred in 24 hours based on link speed in data center

  In case you are planning for migration via DIA or IPVPN link and as example you have 200Mb stable speed so you could calculate using the below formula. (( 200Mb /8)x60x60x24) /1024/1024 = 2TB /per day In case you have different speed you could replace the 200Mb by any rate to calculate as example below. (( 5 00Mb /8)x60x60x24) /1024/1024 =  5.15TB  /per day So approximate each 100Mb would allow around 1TB per day.

Integration with vCloud Director failing after NSXT upgrade to 4.1.2.0 certificate expired

  Issue Clarification: after upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Issue Verification: after Upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Root Cause Identification: >>we confirmed the issue to be related to the below KB NSX alarms indicating certificates have expired or are expiring (94898)   Root Cause Justification:   There are two main factors that can contribute to this behaviour: NSX Managers have many certificates for internal services. In version NSX 3.2.1, Cluster Boot Manager (CBM) service certificates were incorrectly given a validity period of 825 days instead of 100 years. This was corrected to 100 years in NSX 3.2.3. However any environment originally installed on NSX 3.2.1 will have the internal CBM Corfu certs expire after 825 regardless of upgrade to the fixed version or not. On NSX-T 3.2.x interna...

Recreating a missing VMFS datastore partition in VMware vSphere 5.x and 6.x

    Symptoms A datastore has become inaccessible. A VMFS partition table is missing.   Purpose The partition table is required only during a rescan. This means that the datastore may become inaccessible on a host during a rescan if the VMFS partition was deleted after the last rescan. The partition table is physically located on the LUN, so all vSphere hosts that have access to this LUN can see the change has taken place. However, only the hosts that do a rescan will be affected.   This article provides information on: Determining whether this is the same problem Resolving the problem   Cause This issue occurs because the VMFS partition can be deleted by deleting the datastore from the vSphere Client. This is prevented by the software, if the datastore is in use. It can also happen if a physical server has access to the LUN on the SAN and does an install, for example.   Resolution To resolve this issue: Run the  partedUtil  command on the host wit...