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.

Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

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...
Post a Comment
Read more

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.
Post a Comment
Read more

Device expanded/shrank messages are reported in the VMkernel log for VMFS-5

    Symptoms A VMFS-5 datastore is no longer visible in vSphere 5 datastores view. A VMFS-5 datastore is no longer mounted in the vSphere 5 datastores view. In the  /var/log/vmkernel.log  file, you see an entry similar to: .. cpu1:44722)WARNING: LVM: 2884: [naa.6006048c7bc7febbf4db26ae0c3263cb:1] Device shrank (actual size 18424453 blocks, stored size 18424507 blocks) A VMFS-5 datastore is mounted in the vSphere 5 datastores view, but in the  /var/log/vmkernel.log  file you see an entry similar to: .. cpu0:44828)LVM: 2891: [naa.6006048c7bc7febbf4db26ae0c3263cb:1] Device expanded (actual size 18424506 blocks, stored size 18422953 blocks)   Purpose This article provides steps to correct the VMFS-5 partition table entry using  partedUtil . For more information see  Using the partedUtil command line utility on ESX and ESXi (1036609) .   Cause The device size discrepancy is caused by an incorrect ending sector for the VMFS-5 partition on the ...
Post a Comment
Read more