Search the VMware Knowledge Base (KB)
View by Article ID

Performing an end-to-end backup and restore for VMware View Manager (1008046)

  • 9 Ratings

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 View Manager ADAM database

To back up the View Manager ADAM database:
 
Note: For more information, see the View Manager Administration Guide.
  1. Verify that there are no ongoing create, recompose, and delete operations in progress.
  2. Disable provisioning of new virtual machines from all pools to prevent data synchronization problems.

    To perform this task:
    1. Click View Administrator > View Configuration > Servers.
    2. Select vCenter Server.
    3. 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:

      • View 3.x – C:\Program Files\VMware\VMware VDM\Server\bin\vdmexport.exe
      • View 4.x and 5.x – C:\Program Files\VMware\VMware View\Server\tools\bin\vdmexport.exe

  3. 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
NoteFrom VMware View 6.x we can schedule View Configuration data to be backed up at regular intervals automatically For more information refer: 

Backing up the View Composer database

To back up the View Composer database:
  1. Stop the View Composer service to ensure you get a clean backup of the database.

    To stop the View Composer service:

    1. Click Start > Administrative Tools > Services.
    2. Right-click VMware View Composer service.
    3. 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.

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

    For quick verification with Microsoft SQL 2005 databases:

    1. Right-click the database and click Tasks.
    2. 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:
  1. Perform the backup of the vCenter Server database. Follow your database vendors recommendation for backing up the database.
  2. Restart the View Composer service.
  3. Enable provisioning of new virtual machines from all pools.

    To enable provisioning of new virtual machines from all pools:

    1. Click View Administrator > Desktops and Pools.
    2. Select each pool and click Enable or disable.
    3. Click on Enable provisioning new VMs and click OK.

Restore

  1. Verify that there are no ongoing create, recompose, and delete operations in progress.
  2. Stop the View Connection Server service.

    To stop the View Connection Server service:

    1. Click Start > Administrative Tools > Services.
    2. Right-click VMware View Connection Server service and click Stop.

  3. Stop the View Composer Service.

    To stop the View Composer service:

    1. Click Start > Administrative Tools > Services.
    2. Right-click VMware View Composer service and click Stop.

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

  5. 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.

    For quick verification with Microsoft SQL 2005 databases:

    1. Right-click on the database and click Restore.
    2. Click Database.

  6. For the View Manager ADAM database:
     
    1. Follow the instructions outlined in the View Manager Administration Guide.
    2. 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:

      1. Click Start > Control Panel > Add/Remove Programs.
      2. Click VMware View Connection Server and ADAM Instance VMwareVDMDS and click Remove.

    3. Reinstall View Connection Server, ADAM is installed with View Connection Server. If restoring to a multi broker environment, only install one instance of the Connection Server.
    4. 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:

      1. cd C:\Program Files\VMware\VMware View\Server\tools\bin
      2. For View 5.1 and later releases 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.
      3. and finally:

        vdmimport -f VDMConfig.LDF

    5. If this is a single Connection Server environment, proceed to Step f. If restoring to a multi broker environment, reinstall remaining Connection Servers making them replicas of the one that was restored.
    6. Verify the View Connection Server, View Composer and VirtualCenter Server services are started.

      Note: To restore the View Manager 5.1 ADAM database, see the Restoring View Connection Server and View Composer Configuration Data in the VMware View 5.1 Administration Guide.

Reconciliation

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

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

  1. An administrator deleted pools/desktops
  2. 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 View Manager Admin user 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 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 VMware Infrastructure Client, restart the VirtualCenter Server service. Disconnected virtual machines may appear with erroneous status of READY in View Server ADMIN UI.
Contact VMware Support for instructions for removing orphan sources and replicas under VMwareViewComposerReplicaFolder after a restore from back up. Some orphan replicas and sources are removed by View Composers subsequent actions.

Additional Information

For more information on Backing up and Restoring View configuration Data, see VMware View 5.2 Administration Guide.

See Also

Update History

08/31/2012 - Added link to the View Manager 5.1 Admin guide to perform an ADAM DB Restore. 10/12/2012 - Added information about vdmimport. 04/02/2013 - Updated the Products section. 05/07/2013 - Added command for Horizon View 5.1 and later releases of the restore process. 12/09/2013 - Added Horizon View 5.3 to Product Versions.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 9 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 9 Ratings
Actions
KB: