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

Backup and Restore procedure for Horizon 7 environment (74875)

Last Updated: 9/19/2023Categories: How toTotal Views: 9899Language:
English

5 like this article

Subscribe to get an email
newsletter with new updates

5 people found this helpful Please provide article feedback:

Details

This article provides steps to perform an end-to-end backup of VMware Horizon 7.

It is intended for Horizon 7, v7.2 and later, and to complement the recovery scenarios presented in Recovery scenarios for Horizon 7 environment (70906).
For Horizon 6, v6.2.2 to Horizon 7, v7.1, see Performing an end-to-end backup and restore for VMware View Manager (1008046) and Restoring a View Connection Server instances in a Cloud Pod Architecture pod federation (2080522).
Beginning with Horizon 7, v7.10, it is possible to back up the Horizon Global AD LDS database, which stores configuration data for Cloud Pod Architecture (CPA) federations.

Solution

To prepare for the worst, a multi-level backup strategy is needed, beginning with infrastructure components such as AD and DNS. It is likely that you will already have these covered in your DR plan so we won’t dwell on them here, other than to point out that loss of AD would invalidate every user, service and machine account.

It is also necessary to take a whole-machine backup of one of the Connection Servers in each cluster or pod every three months with associated Database Backups at appropriate Intervals such as the Horizon Event Database.

This is because there are many keys and certificates used to secure communications, and these change automatically on a quarterly basis. For more information see  Certificate Thumbprint Verification and Automatic Certificate Generation.

Options include cloning the VM (do not select customization option while cloning) or creating a copy of the VM on storage accessible to the ESXi host. See Notes - Off-site storage for more recommendations.

With these items part of the larger DR plan, this article sets out a procedure to back up the Horizon environment state on a more frequent basis. Any Databases should be backed up as per vendors best practice.

To perform an end-to-end backup of VMware Horizon 7:

•    VMware recommends that all components are backed up at the same time to avoid data discrepancies.
•    Backup must be performed in the order provided in this article.
•    This is a summary of steps. For full details, see Backing Up Horizon Connection Server Data

Pause operations

Open Horizon Console and 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:

•    In Horizon Console, select Horizon Configuration > Servers
•    Open the vCenter Servers tab
•    Highlight each entry, click Disable Provisioning and click OK

Back up Connection Server databases

Logon to Connection Server with an account with the Horizon Global Administrator role and open a Windows command prompt.

LDIF data is exported from the Horizon AD LDS databases using the export tool that is installed on each Connection Server. This is on the path by default.

The Local database can be backed up by executing: vdmexport -f filename.

For example: vdmexport -f localconfig.ldf

The Global database can be backed up by executing: vdmexport -g filename

For example: vdmexport -g globalconfig.ldf

Back up locked.properties file and trust store files

Using Explorer, navigate to,

install_location\VMware\VMware View\Server\sslgateway\conf

Check for trust store files (typically truststore.key) and locked.properties.

If these files are present, then copy them to a backup location too.

Back up Horizon 7 Composer

On the computer where Horizon 7 Composer is installed, stop the ‘VMware Horizon 7 Composer’ service. This ensures you get a clean backup of the database.

Note: Stopping this service stops Composer accepting any new requests for linked-clone related operations. Any current action on the Horizon 7 Composer database will finish before the service shuts down. Further recompose or refresh operations will fail, which can leave clones in an error state. This can be fixed by manually recomposing or refreshing after the service is restarted.

Open a Windows command prompt and navigate to the Composer installation directory.

Export Composer data as follows:

sviconfig -operation=exportdata -DsnName=DSN
-Username=db_admin_username -Password=db_admin_password
-OutputFilePath=path_to_backup_file

Navigate to %windir%\Microsoft.NET\Framework\v2.0xxxxx.

Save the RSA key pair to a local file:

aspnet_regiis -px "SviKeyContainer" "keys.xml" -pri

The ASP.NET IIS registration tool exports the RSA public-private key pair from the SviKeyContainer container to the keys.xml file on the local file system.

Back up vCenter

vCenter backup is critical. See Overview of Backup and Restore options in vCenter Server 6.x (2149237).

Continue operations

On the computer where Horizon 7 Composer is installed, start the ‘VMware Horizon 7 Composer’ service.

Open Horizon Console and select Desktops and Pools.

Select each pool and click on Enable or Disable.

Click Enable Provisioning and click OK.

Notes

Automatic backups

The above describes manual steps to back up the Horizon Local, Global and Composer databases. Note that the Local database (and the Composer database if part of the environment) is backed up automatically on a daily basis. From Horizon 7.10, if the Connection Server is a member of a Cloud Pod Architecture pod, the Global database is also part of this automatic backup. By default, backups are written to the Connection Server’s local file system at this location:

C:\Programdata\VMWare\VDM\backups

For more information, see Backing Up Horizon Connection Server and View Composer Data.

Even if you rely on automatic backups for these components, you will still need to back up locked.properties files and trust store files.

Off-site storage

Whether manually or automatically generated, backups should be copied to another site or stored in an off-site tape archive, in case the entire site is lost.

Recovery scenarios

For restoring a component or a site see Recovery scenarios for Horizon 7 environment (70906).

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

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

KB
•
vRealize Automation 8.0 のインストールとインストール後の作業に関する既知の問題とトラブルシューティング (76532)

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 Horizon

Related Versions:

VMware Horizon 8

VMware Horizon 7

Take Our Survey

Support Assistant