Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Workspace ONE Access/vIDM Backup/Restore Procedure - Open Virtualization Format (OVF) Export Issue Workaround (79131)

Last Updated: 11/3/2022Categories: TroubleshootingTotal Views: 8954Language:
JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

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.01
VMware Identity Manager 19.03
VMware Identity Manager 3.3.2
VMware Identity Manager 3.3.1
VMware Identity Manager 3.3

Resolution

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 Template
4. 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

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 timezone

4. DNS

5. Default Gateway

6. Domain Name

7. Domain Search Path

8. Host Name (FQDN)

9. IP Address

10. Netmask

Related Information

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.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
JapaneseEnglish

Attachments

Additional Resources

KB
•
Workspace ONE Intelligent Hub 20.05 for macOS リリースのお知らせ (79050)

KB
•
Workspace ONE Notebook 1.4 for iOS リリースのお知らせ (79155)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Workspace ONE Access

VMware Workspace ONE

VMware Identity Manager

Related Versions:

VMware Identity Manager 3.0

Take Our Survey

Support Assistant