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

Automated backup of the ADAM or View Composer database fails (2001534)

  • 5 Ratings


  • Automated backup of the ADAM (Active Directory Application Mode) or View Composer (SVI) database fails.
  • This issue occurs when you have multiple Connection Servers and more than one is configured to back up.
  • No date and time is displayed in the Last Backup column of the View Connection Server configuration screen.

    Note: You see Manual Backup in progress and no Last Backup date and time is displayed.


This issue occurs when backups from multiple Connection Servers start at the same time.


To resolve this issue, backups must be configured so that one is complete before the next one starts.

To resolve this issue, you must adjust the backup start time. You cannot adjust the backup start time from the View Administrator GUI, but you can modify the backup start time by editing the pae-LDAPBUTime attribute.

To edit the pae-LDAPBUTime attribute:

Warning: VMware strongly recommends backing up the View Connection Server and ADAM database before proceeding. For more information, see Backing Up View Connection Server and View Composer Data section in the VMware Horizon View 5.2 Administration Guide and Performing an end-to-end backup and restore for VMware View Manager (1008046).

  1. On the VMware View Connection Servers, log in as administrator.

  2. Go to Start > All Programs > ADAM > ADAM ADSI Edit.

    Note: Record the name of the Connection Server where no date and time is displayed in the Last Backup column.

  3. Select Connect to the following node.

  4. Enter the text:


  5. Click OK. The ADAM ASDI Edit window appears.

  6. Navigate to OU=PropertiesOU=Server.

  7. Double-click the appropriate server (the name of the Connection Server recorded in step 2) in the right-hand pane.

  8. Locate the pae-LDAPBUTime attribute.

    Note: This parameter has a value of 0 by default, indicating that daily and longer frequency backups start at 12:00 PM, and hourly backups start on the hour.

  9. Change the value of the attribute.

    Note: Enter a positive value. This value is equal to an offset in minutes from 12:00 AM or from the start of the hour. For example, if you enter 10, daily backups will begin at 12:10 AM, and hourly backups will begin 10 minutes after the hour.

  10. Repeat this procedure for all other Connection Servers. Each broker needs a different offset value to properly stage the backups.

Additional Information

To determine the time taken by a backup, start a Manual Backup and look at the last backup time stamp to determine when the backup finished.

See Also

Update History

01/09/2013 - Added View 5.0.x and View 5.1.x to product versions 11/04/2013 - Added View 5.2 to product versions 01/20/2014 - Added View 5.3 to product versions 29/9/14 - Added View 6.0 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.


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