VMware vFabric Data Director 1.0 Release Notes

VMware vFabric Data Director 1.0 | 08 Sep 2011 | Build 476412

VMware vFabric Postgres 1.0 | 08 Sep 2011 | Build 476412

Check for additions and updates to these release notes.

What's in the Release Notes

These release notes cover the following topics:

Installation Notes for This Release

Read the vFabric Data Director Installation documentation for step-by-step guidance on installing and configuring Data Director. Use the vFabric Data Director Worksheets to help you plan your Data Director configuration.

Known Issues

Data Director 1.0 and vFabric Postgres 1.0 have the following known issues. If you encounter an issue that is not in this known issues list, search the VMware Knowledge Base, or let us know by providing feedback.

  • vCenter Server IP Address change is not propagated to Management Server.
    You power off the Management Server. You change the vCenter Server IP Address and power on the Management Server. The Management Server cannot connect to the vCenter Server system.

    Workaround: Remove the vCenter Extension service and add it back, as follows:

    1. Select and power off the Management Server virtual machine.
    2. Click Edit Settings and select the vServices tab.
    3. Select vCenter Extension Installation and click Edit.
    4. Select <No Provider> as the provider and click OK twice to exit.
    5. Select the Management Server virtual machine again.
    6. Click Edit Settings and select the vServices tab.
    7. Select vCenter Extension Installation and click Edit.
    8. Select vCenter Extension vService as the provider and click OK twice to exit.
  • You cannot migrate the Data Director vApp to another cluster.
    Migrating the Data Director vApp to another cluster is not supported.

    Workaround: None.

  • Cannot resize parent database even after the last linked clone is deleted.
    A database with linked clones cannot be resized. Normally, after you delete all the linked clones, the parent database can be resized. However, you might get a message that The operation is not allowed with the current database server status, even after you delete the last linked clones.

    Workaround: Create a snapshot of the parent database, delete the snapshot again, and retry the resize operation.

  • Database import fails if available storage is less than database configuration template.
    You try to import a database and choose a database configuration template that is predefined with a larger size than the database itself. If the database group does not have enough storage for the database configuration template, the import process fails even if enough storage for the database itself exists.

    Workaround: Override the database size configuration to match the actual size of the imported database.

  • Can create event-based alarm to trigger when resource bundle is created even though resource bundles cannot be created at the organization level.
    When you define an event-based alarm at the organization level on the resource bundle object type, the resource bundle alarm options include the event-based alarm Resource bundle is created, which triggers on resource bundle creation. However, resource bundles can be created only at the system level. You can define the alarm at the organization level, but it will never happen.

    Workaround: None.

  • Clone, reconfigure, or import of database fails when you use a database template that has a smaller memory configuration than the original database.
    When you clone a database and specify a database configuration template with a smaller memory size than the original template used for the database, the clone operation fails. When you import a database and specify a database configuration template with a smaller memory size than the original template used for the database, the import operation fails. When you reconfigure a database and specify a database configuration template with a smaller memory size than the original template used for the database, the reconfigure operation fails.
    The reason for this problem is that the Postgres server does not start if the memory configuration specified for a database is too small to satisfy other configurations in the database template.

    Workaround: If you want to make the memory configuration smaller, you cannot perform the operation in one step.

    1. Clone, reconfigure, or import the database by using the original database size or by using a large template if you do not know the original size.
    2. Apply a smaller configuration template to the database, but temporarily override the memory size to keep it unchanged.
    3. After step 2 finishes, change the memory size of the database to the smaller size specified that is specified in the template by default.

  • Cannot delete a view from the navigation tree.
    When you open a view in the Manage & Monitor tab, the view appears in the navigation tree in the left pane. If you right-click the view and select Delete or Cascade delete from the drop-down menu, the view is not deleted and no message appears.

    Workaround: In the middle pane, click the view in the Views list, and select Delete or Cascade delete from the drop-down menu. The delete operation succeeds.

  • Cannot click Apply after setting the maximum number of tags per user.

    1. Log in to Data Director as a system administrator.
    2. Click Administration, and click General.
    3. Enter a number in the Maximum number of tags per user text box.

    The Apply button remains inactive.

    Workaround: Press Enter after you enter the number, or click the up or down arrows after you enter the number. The Apply button activates.

  • An alarm triggers when Disabled and Development backup templates have point-in-time recovery storage allocation of 0.
    By default, PITR Storage is at least 1GB. However, PITR can become 0 in these cases:

    • You create a template that has PITR disabled and provision a database with it.
    • You reconfigure the Disabled or the Development backup template, which both have PITR disabled, and you provision a database with one of the reconfigured templates.

    If PITR becomes 0, Data Director displays the following alarm:
    Disk ARCHIVE size mismatch


    1. Manually reconfigure the database's point-in-time recovery storage allocation to a non-zero value.
    2. Repair the alarm.

  • A Data Director database located on a datastore local to an ESXi host cannot be imported into Data Director.
    If you attempt to import a database that resides in one or more datastores that are not local to the ESXi host, the import operation cannot complete and the following error appears.

    Failed to execute vCenter Server command: Invalid configuration for device '0'..
    All Data Director databases must must reside on a shared datastore, whether the databases are created in Data Director or imported into Data Director.

    Workaround: Use storage vMotion to move the database to a shared datastore before you import the database.

  • Performing a point-in-time recovery operation on a stopped database results in losing the last transaction logs.
    If a database is stopped when you perform a point-in-time recovery operation, the restore process does not copy any unarchived logs on the data disk. This results in a truncated point-in-time recovery timeline and an incomplete database restore operation.

    Workaround: Start the database, then perform the point-in-time recovery operation, or repair the database.