Loading

×Sorry to interrupt
CSS Error

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

Skip to main content

My Subscriptions

Loading

Knowledge Base

Performing an end-to-end backup and restore for Legacy Releases of VMware Horizon View (1008046)

Last Updated: 4/18/2024Categories: How toTotal Views: 18957Language:
Chinese (Simplified)JapaneseEnglish

5 like this article

Subscribe to get an email
newsletter with new updates

5 people found this helpful Please provide article feedback:

Purpose

This article is a legacy kb and is applicable to versions of Horizon prior to 7.2. For modern editions of Horizon, we recommend the following procedures:

Backup: Backup and Restore procedure for Horizon 7 environment (74875)
Restore: Restore Procedure for Site Recovery with Machine Backups(76765)

For additional options, please see Recovery scenarios for Horizon 8 environment (70906)

We recommend you migrate from Horizon 7 to Horizon 8 as soon as possible. Horizon 8 offers numerous improvements in performance, scale, and experience for both Administrators and end users. Please see Ensuring a successful migration from Horizon 7 to Horizon 8 (89840)  for additional advice.

This article provides steps to perform an end-to-end backup and restore for VMware Horizon View. Note that this is the only supported method to back up and restore multiple connection servers. Restoring connection servers from 3rd party backup tools is not supported.

Resolution

Backups

VMware recommends that all three components be backed up at the same time to avoid data discrepancies.

Backups must be performed in the order provided in this article.

Backing up the Horizon View ADAM database

To back up the Horizon View ADAM database:

Verify that there are no ongoing create, recompose, and delete operations in progress.

Disable provisioning of new virtual machines from all pools to prevent data synchronization problems.

To perform this task:

Click Horizon Administrator > View Configuration > Servers.

Select vCenter Server.

Click Disable provisioning and click OK.

LDIF data is exported from VMware Desktop Manager using the vdmexport.exe tool that accompanies each standard and replica VDM Connection Sever.

The path to the executable file for:

C:\Program Files\VMware\VMware View\Server\tools\bin\vdmexport.exe

From the command prompt on a standard or replica VDM Connection Server, execute this command to create a file called VDMConfig.LDF that contains the exported VDM LDAP configuration information:

vdmexport > vdmconfig.ldf

NOTE: In Horizon 8, The following command takes a backup of the Cloud Pod Architecture global LDAP:
vdmexport -f myglobalexport.LDF -g

Note: Configuration data back up steps:

Horizon 7
Horizon 8

Backing up the View Composer database

To back up the View Composer database:

Stop the View Composer service to ensure you get a clean backup of the database.

To stop the View Composer service:

Click Start > Administrative Tools > Services.

Right-click VMware View Composer service.

Click Stop.

Note: Stopping the View Composer service stops accepting any new requests for linked clone related operations. Any current action on the View Composer database finishes and the service shuts down. Any View Composer operations attempted (recompose/refresh) through the View Administrator fail, which can leave clones in an error state. This can be fixed by manually recomposing or refreshing the desktop.

Back up the View Composer database. Follow the recommended practice for backing up your database with third-party utilities.

In Microsoft SQL Serer Management Studio:

Right-click the database and click Tasks.

Click Backup. By default, the backup is stored in C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Backup\database_name.bak

Backing up the vCenter Server database

To back up the vCenter Server database:

Perform the backup of the vCenter Server database. Follow your database vendors recommendation for backing up the database.

Restart the View Composer service.

Enable provisioning of new virtual machines from all pools.

To enable provisioning of new virtual machines from all pools:

Click View Administrator > Desktops and Pools.

Select each pool and click Enable or disable.

Click on Enable provisioning new VMs and click OK.

Restore

Note:  To restore a View Connection Server instance in a Cloud Pod Architecture pod federation, see
Recovering a Cloud Pod Architecture pod (2080253)

Verify that there are no ongoing create, recompose, and delete operations in progress.

Stop the View Connection Server service.

To stop the View Connection Server service:

Click Start > Administrative Tools > Services.

Right-click VMware View Connection Server service and click Stop.

Stop the View Composer Service.

To stop the View Composer service:

Click Start > Administrative Tools > Services.

Right-click VMware View Composer service and click Stop.

For the vCenter Server database, follow your database vendor's recommendations for restoring the database.

Note: The VMware VirtualCenter Server service must be stopped before attempting a restore.

For the View Composer database, follow the recommended practice for restoring your database with 3rd party utilities.

Note: If View Composer is installed on a new server, the RSA key container from the old server is required. See the Note in the Purpose section of this article.

In Microsoft SQL Server Management Studio:

Right-click on the database and click Restore.

Click Database.

For the Horizon View ADAM database:

Uninstall View Connection Server and ADAM. If restoring to a multi broker environment, uninstall all Connection Server instances.

To uninstall View Connection Server and ADAM:

Click Start > Control Panel > Add/Remove Programs.

Click VMware Horizon Connection Server and AD LDS Instance VMwareVDMDS and click Remove.

Reinstall View Connection Server, and ADAM is installed with View Connection Server. If restoring to a multi broker environment, only install one instance of the Connection Server.

Restore the configuration data of a View Connection Server instance by importing a backup copy of the data stored in an LDIF file using the vdmimport command. From the command prompt on a standard or replica View Connection Server, run these commands to import a file called VDMConfig.LDF that contains previously exported View Manager LDAP configuration data:

cd C:\Program Files\VMware\VMware View\Server\tools\bin

You will need to decrypt the ldif file first:

vdmimport -d -p mypassword -f MyEncryptedexport.LDF > MyDecryptedexport.LDF

If you do not remember your data recovery password, type the command without the -p option. The utility displays the password reminder and prompts you to enter the password.

and finally:

vdmimport -f VDMConfig.LDF

If restoring to a multi-broker environment, reinstall the remaining Connection Servers making them replicas of the one that was restored.

Verify the View Connection Server, View Composer and VirtualCenter Server services are started.

Note: Also see the Restoring View Connection Server and View Composer Configuration Data in the VMware Horizon Administration Guide.

Reconciliation

Note: Depending on the actions taken after the backup, the Horizon View environment may be out of sync with the current state and reconciliation is required.

After a restore of the Horizon View ADAM database, missing desktops may appear in the Horizon Administrator UI if the following actions are taken after the backup but before a restore:

An administrator deleted pools/desktops

A desktop pool was recomposed resulting in the removal of un-assigned desktops (spare virtual machines).

Missing desktops/pools can be manually removed from the Horizon Administrator interface.

Some automated desktops may become disassociated from their pools as a result of creating a pool between the time the backup took place and the restore time. View Administrators may be able to return them to use by cloning the linked clone desktop as a full clone desktop through vCenter Server, creating it as an Individual Desktop in View Manager and assigning such desktops to a specific user.

After restoring vCenter Server, remove orphaned virtual machines pertaining to View Server Pools using the VMware Infrastructure Client.

If orphaned virtual machines and templates appear as disconnected in vSphere Web Client, restart the Virtual Center Server service. Disconnected virtual machines may appear with an erroneous status of READY in View Server ADMIN UI.

For additional cleanup procedures, please see:

Resolving Database Inconsistencies with the ViewDbChk Command

Determining which replica disk is used for a linked clone virtual machine

Finding and removing unused replica virtual machines in the VMware Horizon View

Related Information

For more information on Backing up and Restoring View configuration Data, see VMware View 5.2 Administration Guide. VMware View Manager のエンド ツー エンドのバックアップとリストアを実行する
对 VMware View Manager 执行端到端备份和还原
Unable to assign desktop even when unassigned desktops in manual pool are present

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Horizon

Related Versions:

VMware Horizon 7

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant