VMware vFabric Data Director 2.0 Release Notes

VMware vFabric Data Director 2.0 | 10 July 2012 | Build 760442

VMware vFabric Postgres 9.1 | 10 July 2012 | Build 760442

Check these release notes for additions and updates.

What's in the Release Notes

These release notes apply to vFabric Data Director Release 2.0.0 and discuss the following topics:

What's New in vFabric Data Director 2.0

vFabric Data Director supports automation of lifecycle management for databases and allows DBAs to delegate routine database tasks to application developers and analysts through a self-service portal.

Data Director 2.0 includes support for Oracle databases and expands the database lifecycle management features from version 1.0. Data Director now supports database ingestion and provides new options for provisioning, backup, restore, cloning and monitoring operations. The new IP pools feature allows you to manage the internal and DB name service networks. The following list summarizes the new features.

  • Oracle support.
    • Support of selected Oracle features.
    • Custom Oracle templates.
    • Simplification of the clone and refresh process from production databases to development or QA databases.
  • Backup and cloning enhancements. Back up and clone both vPostgres and Oracle databases, and use the following features.
    • Post-clone scripts.
    • Data refresh from a cloned database.
    • Backup before database deletion.
  • Database ingestion. Create a database by importing an external database. Ingestion refers to the initial capture of a database outside of Data Director to create a golden clone that cannot be modified within Data Director.
  • Database patching and update. Patch and update your databases and database environments.
  • Data Director point-in-time recovery. Perform a PITR on the management server database by leveraging VMware Data Recovery (VDR).
  • Integration with VMware vCloud Director. If vCloud Director integration is enabled, Data Director system administrators can import vCloud Director organizations and their users into Data Director and allow operations on vCloud Director organizations through the Data Director user interface
  • IP pool management. IP pools allow you to manage the internal network and the DB name service network. You configure these networks either with DHCP or by using IP pools. If you select the IP pool option, Data Director manages the IP addresses for the corresponding network.
  • SSL certificate management. Data Director supports two kinds of certificates.
    • Auto-generated certificates. When Data Director is deployed in vCenter Server, certificates for each SSL component are generated.
    • Custom certificates. Custom certificates support customer-provided private keys and certificates for customers with special security requirements.
  • Database catalog. Databases in the catalog can be used to easily provision standard databases prepopulated with schema and data across the organization.
  • Set expiration of provisioned databases. Provide expiration (time-to-live) options for provisioned databases.
  • IP whitelists. Specify a set of IP addresses for each database from which connections are accepted by the database.
  • Batch operations. Perform batch operations on databases.

Installation Notes for This Release

Read the vFabric Data Director Installation documentation for step-by-step instructions on installing and configuring Data Director. Before you start installation, use the vFabric Data Director Deployment Worksheets to help you plan your Data Director configuration.

Upgrades for This Release

A vFabric Data Director upgrade might involve two tasks: upgrading the Data Director virtual appliance and upgrading the database virtual machines (DBVMs). A particular upgrade might require that you upgrade only the Data Director virtual appliance or that you upgrade the database virtual machines as well. The Data Director virtual appliance supports in-place upgrades from version 1.0 or 1.0.1 to version 2.0. Use VMware vSphere Upgrade Manager to upgrade the Data Director virtual appliance. See the vFabric Data Director Installation documentation for information on upgrading the database virtual machines.

For information about upgrading using vSphere Upgrade Manager, see the vSphere Upgrade documentation or the Installing and Administering VMware vSphere Update Manager documentation

Release 1.0 and 1.0.1 Product Guides

The product guides for vFabric Data Director Release 1.0 and Release 1.0.1 are available in the vFabric Data Director 1.0 Documentation archive.

Known Issues

Data Director 2.0 has 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.

  • Error: "Failed to execute vCenter Server command: Invalid configuration for device ‘0’" when trying to restore or clone a database from a snapshot.
    If you delete, refresh, or restore linked clones of a database, any snapshots of the parent database might become unavailable. The invalid configuration error appears.

    Workaround: Follow these steps

    1. Stop the database from Data Director.
    2. Log in to vSphere as the vSphere administrator user.
    3. Migrate the database virtual machine to another host in the same vSphere cluster, in the same resource pool.
    4. Restart the database from Data Director, and retry the failed operation.
    To avoid the problem, use External Backup and not Snapshot as the backup solution for your databases if you expect to create linked clones for a database.

  • Cloning a database results in invalidation error.
    If you attempt to clone a database, and if the selected database group does not have enough storage, cloning cannot proceed. If you change to a different database, the operation still results in an invalidation error even if that database group has enough storage.

    Workaround: Cancel the cloning process and start the process again, selecting a database group that has enough storage.

  • Error: Cannot create the database. Backup setting is not suitable for this template.

    The error results if you follow these steps:
    1. Change the minimum PITR storage for a database to a value larger than 1GB.
    2. Convert the database to a database template.
    3. Assign the template to a resource bundle and assign the resource bundle to an organization.
    4. From the organization, provision a database from the template
    5. Add the database to a catalog, provision from that catalog, and switch to the backup template.
    6. Click Finish

    Workaround: Do not switch to the backup template when provisioning a database from a catalog. Use the default template.

  • Heartbeat Failure alarm for Oracle database
    When you perform one of the following operations for an Oracle database, an alarm appears even though the operations execute without errors.

    • Stop the database.
    • Reconfigure the database.
    • Recover the database from its last known state.
    • Recover the database from a backup.

    Workaround: No workaround needed. This alarm does not impact the feature itself and is displayed in error.

  • Provisioning Oracle databases with Oracle Enterprise Management on SUSE Linux does not complete.
    If managed resource pools are over-provisioned, or if the memory reservation for the target database is not sufficient, provisioning does not complete. This happens only if you enable Oracle Enterprise Management (OEM) during provisioning or reconfiguration. This is a known issue for OEM, even on physical machines.

    Workaround: Cancel the task, adjust the resource settings, and try again. If you still do not succeed, disable OEM.

  • Cannot log in to vFabric Data Director.
    If a user's username has non-ASCII characters, that user might be unable to log in to Data Director.

    Workaround: None.Do not use non-ASCII characters in user names.

  • If you specify non-ASCII characters in emails preconfigured from the Monitoring tab, those characters do not display correctly in the email.
    Assume you perform the following tasks:

    1. Log in to Data Director, and select the System tab.
    2. Click System settings>Other settings>Monitoring.
    3. Enter non-ASCII characters in the Email subject prefix and send test email
    4. An incorrect prefix appears in the test email's Subject line.

    Workaround: None. Use only ASCII characters when configuring email settings. .

  • Running virtual machines do not recognize new DNS servers that you add to an IP pool.
    If you add one or more DNS servers to an existing IP pool, and if virtual machines that are currently running use IP addresses from that IP pool, the running virtual machines are not updated to include the new DNS servers until the virtual machines are rebooted.

    Workaround: Power-off and power-on the already running virtual machines that use addresses from the IP pool.

  • Cannot connect to Data Director when using LDAP
    By default, LDAP validates the server certificate upon connection (TLS_REQCERT = demand). Because the Data Director server has a self-signed certificate, the validation handshake fails. As a result, the following error results if you attempt to connect to the server using LDAP:
    VMware vPostgres: error : ldap start tls connection failed

    Workaround: Three possible workarounds exist.

    • Set or export the LDAPTLS_REQCERT environment variable to allow, as follows:
      LDAPTLS_REQCERT=allow /opt/aurora/postgresql/bin/psql.bin -U t -h {XX}.server-ldap.company.com >-d serverdb1 Password for user t:
    • Add the following line to the ldap.conf file on the client.
      # vim /etc/openldap/ldap.conf
    • Set up the Data Director client to trust the self-signed certificates from the Data Director server.
      # scp root@machine.domain.com:/opt/aurora/data/trustCA.pem /etc/openldap/ root@jmachine.domain.com's password: trustCA.pem # echo "TLS_CACERT /etc/openldap/trustCA.pem" >> /etc/openldap/ldap.conf
  • User cannot perform any operations on Oracle databases after the Oracle password expires.
    By default, Oracle passwords expire. If you neglect to renew the password when the UI reminds you (after 83 days), you can no longer perform database operations.

    Workaround: Log in to the vCenter Server system as root, and run the passwd oracle command to change the password.

  • Enter SQL dialog does not work correctly on Firefox on Windows 7, 64 bit.
    When you click the Open button on certain versions of Firefox, a Save dialog appears instead of an Open dialog and you cannot open an existing SQL file.

    Workaround: Use a different browser

  • Problems with scheduling more than one update task.
    You might encounter one of the following problems when working with update tasks:

    • If an update task already exists, and you attempt to create a second update task, an error results because only one update task is permissible.
    • If you already scheduled an update task and reschedule that task, the system generates a second update tasks and an error results.

    Workaround: No workaround for the first issue. If you want to reschedule an update, cancel the existing update and schedule the new update.

  • A restore operation from a PITR (point-in-time recovery) backup for a stopped Oracle database is not successful.
    Assume you perform the following actions:

    1. Create an Oracle database and enable point-in-time recovery.
    2. Stop the database.
    3. Perform a restore from the PITR backup to a valid point.

    The restore operation fails.

    Workaround: None. You cannot use PITR restore for a stopped Oracle database.

  • Error if ingesting external database with non-ASCII characters in path.
    If you create a backup of your Oracle database, and then attempt to ingest the database into Data Director from a path that includes non-ASCII characters, a UnicodeEncodeError error results.

    Workaround: Copy the backup files to a location that includes only ASCII characters in the filename, then ingest into Data Director.

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