Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
You may notice a loss of Workspace ONE Access Open Virtualization Format (OVF) properties during vCenter Virtual Machine (VM) export and import. Version Identified Workspace ONE Access 20.01VMware Identity Manager 19.03VMware Identity Manager 3.3.2VMware Identity Manager 3.3.1VMware Identity Manager 3.3
There are several possible recommended backup and restore options: 1. Non-memory snapshot with quiesce - fastest backup and restore, less safe as storage is not copied elsewhere. and too many snapshots could slow the VM down.2. Clone or Copy - not as fast but safer, but still not full offsite backup.3. Snapshot aware backup software. Best option but requires extra purchases.4. OVF export/import - requires fast network and disk space but functional.Note: There is a known intermittent issue where OVF export/import loses the advanced VMware Identity Manager (vIDM) OVF networking and license properties. There is an addendum at the end on how to recreate the properties manually in this case. This document covers option #4 OVF Export/Import. OVF Export/Import You must power down any VMs and it is recommended that you remove all snapshots before performing this backup procedure. If using an external Database, please use the database export functionality offered by the external DB (Microsoft SQL, Postgres). For each VM in the cluster perform the following: Backup 1. Log in to the vSphere Web Client.2. Select a VM in the object navigator.3. Right click and select Template > Export OVF Template4. Enable Advanced Options and check the Include MAC addresses and Include Extra Configuration boxes. Click OK.5. A number of pop-up Save dialog boxes will show for each file it will download. Click OK on each Save dialog for each VMDK and OVF file.6. After sometime to download all the files, the VM backup is complete.7. Copy the files to a safe location. Note: These files can be very large so it is recommended that you download them from a web client machine that in the same network location as vCenter for quicker backup. Restore Make sure that you restore on same version of Elastic Sky X (ESX) or higher. 1. Log in to the vSphere Web Client.2. Right click on a folder and select Deploy OVF Template.3. Click on Local File and click Browse and multiple select all the VMX and VMDK files you previously exported in the backup exercise.4. Follow the instructions for deployment, including license and networking, especially if the networking/IP has changed in the new location.5. Now you should be able to start up the VM.
Workaround for vCenter issue on properties loss If you are using vCenter prior to 6.7 there is an intermittent issue that destroys all the custom vIDM OVF properties when using OVF export/import on the target environment. If this happens please use the following instructions to manually restore the advanced vApp properties for vIDM networking, etc. Manually Restoring OVF Properties for vIDM/Access 1. Create the ovfEnv.xml file if the file is empty or missing: $ vi /opt/vmware/etc/vami/ovfEnv.xml and copy paste below content and make sure to replace the values to actual ones <?xml version="1.0" encoding="UTF-8"?> <Environment xmlns="http://schemas.dmtf.org/ovf/environment/1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:oe="http://schemas.dmtf.org/ovf/environment/1" xmlns:ve="http://www.vmware.com/schema/ovfenv" oe:id="" ve:vCenterId="vm-825282"> <PlatformSection> <Kind>VMware ESXi</Kind> <Version>6.7.0</Version> <Vendor>VMware, Inc.</Vendor> <Locale>en</Locale> </PlatformSection> <PropertySection> <Property oe:key="ceip.enabled" oe:value="false"/> <Property oe:key="vami.DNS.IdentityManager" oe:value="10.0.0.1"/> <Property oe:key="vami.domain.IdentityManager" oe:value=""/> <Property oe:key="vami.gateway.IdentityManager" oe:value="10.2.1.1"/> <Property oe:key="vami.hostname" oe:value=""/> <Property oe:key="vami.ip0.IdentityManager" oe:value="10.2.119.1"/> <Property oe:key="vami.netmask0.IdentityManager" oe:value="255.255.255.0"/> <Property oe:key="vami.searchpath.IdentityManager" oe:value=""/> <Property oe:key="vamitimezone" oe:value="Etc/UTC"/> <Property oe:key="vm.vmname" oe:value="IdentityManager"/> </PropertySection> <ve:EthernetAdapterSection> <ve:Adapter ve:mac="00:50:56:01:44:cf" ve:network="vxw-dvs-20-virtualwire-78288-sid-10073-dvs.VCDVSus01-2-euc-idmtest-t-e-1-3994294" ve:unitNumber="7"/> </ve:EthernetAdapterSection> </Environment> 2. Create the following properties using the vCenter User Interface (UI). 1.Vname 2. ceip.enabled 3. vami timezone4. DNS5. Default Gateway6. Domain Name7. Domain Search Path8. Host Name (FQDN)9. IP Address10. Netmask
Deploying Workspace ONE Access On - Premises, there is no specific method for backups and restores. When deploying nodes: Backup Nodes are created cluster form. Nodes are built through odd numbers such as 3, 5, and so on. Generally, nodes are deployed in a 3 node cluster. This increases redundancy if one of the nodes is down, other available nodes over the network will act as a backup node.Multi-data centres deployment in the form of primary and secondary data centre, if the primary is down secondary will act as backup; serving the purpose of primary datacentre. This method increases high availability. Restore A snapshot or restore checkpoint of each and every node from Host itself (ESXI/V-sphere/V-centre) can be created by performing the following: Right - click on the node.Look for Snapshot.Create new snapshot. Once the snapshot or restore checkpoint is created, this will act as a restore point for you.