VMware

VMware vFabric Data Director 2.7 Release Notes

VMware vFabric Data Director 2.7 | 16 May 2013 | Build 1121097

VMware vFabric Postgres 9.2.4 | 16 May 2013 | Build 1080158

Check these release notes for additions and updates.

What's in the Release Notes

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

What's New in vFabric Data Director 2.7

vFabric Data Director is a database virtualization platform that enables provisioning and lifecycle management of Oracle, Microsoft SQL Server, MySQL, and vFabric Postgres on VMware vSphere. This release provides the following new features and enhancements.

  • MySQL support. Data Director 2.7 expands the platform to include support for MySQL 5.5.27 Community Edition.

  • Flexible Disk Layout and Configuration. Data Director allows you to define virtual disks to which you can map your DBVM's operating system, data, log, and backup disks. You can map the virtual disks to different datastores using disk provisioning and storage allocations you specify to improve disk usage, performance, and redundancy. For example, you can create dedicated datastores to service I/O intensive database workloads.

  • SQL Server Snapshot & Restore. You can take snapshot backups of SQL Server databases. Snapshot backups capture changes to the database after the snapshot is taken, and allow you to quickly revert changes without DBA intervention.

  • Replication Support for vFabric Postgres 9.2.4. Replication—the sharing of data between redundant resources to improve reliability, fault-tolerance, and accessibility—is available for vFabric Postgres databases.

  • High Availability (HA) Support for Linux and Windows DBVMs. Data Director provides high availability functionality through vSphere, and uses vSphere High Availability (HA) and vSphere Distributed Resource Scheduler (DRS). vSphere HA provides high availability for applications running in virtual machines. In the event of physical server failure, affected virtual machines restart on other production servers with spare capacity. In the event of operating system or database failure, vSphere HA restarts the affected virtual machine on the same physical server.

  • vSphere DRS Ensures the Database is Running on a Licensed Host. You can use DRS to ensure that databases you provision on a shared cluster are deployed only on licensed hosts.

  • Single Sign-On. You use vCenter Single Sign-On to authenticate and manage users of vFabric Data Director. vCenter Single Sign-On is not only an authentication broker, but also a security token exchange providing a more secure way of accessing your vSphere and Data Director environments.

  • Host Names for DBVMs. You can define the Linux host name to use for a database during provisioning.

  • SQL Server Default (Unnamed) Instance or Named Instance. Data Director supports the creation of a stand-alone SQL Server instance using the default (unnamed) instance or a named instance.

  • A SQL Server instance is either an unnamed instance or a named instance. When you install SQL Server as an unnamed instance it does not require clients to specify the name of the instance to make a connection. Clients only have to know the server name. A named instance is identified by the network name of the computer plus the instance name you specify during installation. The client must specify both the server name and the instance name when connecting. By default SQL Server installs as an unnamed instance unless you specify an instance name.

  • Expanded Configuration Parameters for Oracle and SQL Server databases. All Oracle and SQL Server configuration parameters are available for you to assign to a database instance during provisioning. Database parameters define the overall instance configuration, such as how much memory should be allocated to the database, file locations, and internal optimization parameters.

  • The parameters are divided into two categories: Basic and Advanced. You can use the default settings for each parameter group, or override them with custom settings that you define and apply to new databases that you provision.


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 the installation process, use the vFabric Data Director Deployment Worksheets to help you plan your Data Director deployment.


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 all versions directly to 2.7. 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 following documentation.


vFabric Data Director 2.7 Replaces vFabric Data Director 2.5

vFabric Data Director 2.7 replaces the previous version of the software, vFabric Data Director 2.5. The previous version of the software will no longer be available for download.


Support for vFabric Data Director for Hadoop

vFabric Data Director 2.7 no longer includes vFabric Data Director for Hadoop, which was available as part of vFabric Data Director 2.5. If you previously installed vFabric Data Director for Hadoop as part of vFabric Data Director 2.5, your existing vFabric Data Director for Hadoop deployment will not be impacted by upgrading to version 2.7.

To use vFabric Data Director for Hadoop with vFabric Data Director 2.7, you use the Data Director for Hadoop Web Console to manage and monitor your Hadoop deployment. You can log in to the Data Director for Hadoop Web console using a Web browser. The Web console is the graphical user interface that you use to perform administrative tasks when operating Data Director for Hadoop.

For information on accessing the Data Director for Hadoop Web console independently of Data Director, see the topic "Log in to Data Director for Hadoop Web console" in Chapter 2, "Getting Started with vFabric Data Director for Hadoop" in Using VMware vFabric Data Director for Hadoop.


Notes for the Product Guides

The following information is not currently addressed by the product guides.

When repairing a database, the available database storage allocation must be equal to or greater than the storage used by the database. This is because the repair procedure clones the database before repairing it, and there must be enough storage available to create a temporary copy of the database.


Known Issues

Data Director 2.7 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 contacting VMware Technical Support.

  • Recovering vFabric Postgres 9.2.4 with a vFabric Postgres 9.1 Snapshot or External Backup Creates a Version 9.1 Master Database
    If you upgrade an instance of vFabric Postgres from version 9.1 to 9.2.4, then revert to a previously existing snapshot or external backup of version 9.1, the newly recovered vFabric Postgres 9.1 database assumes the role of the master instance. The replication cluster continues to exist until you failover to a slave instance replicated from the vFabric Postgres 9.2.4 database instance, promote it to the role of master, and redirect any slave instances to use the new master instance.

    Workaround:

    Failover to an existing slave instance from the vFabric Postgres 9.2.4 database, promote it to the master role, and create slaves from the new master database instance.

  • Data Director Fails to Recognize Resource Pools When Creating Resource Bundles
    If vSphere is operating under a heavy workload when you attempt to create a resource bundle, Data Director may not recognize the resource pool. This happens when the maximum lifetime of the resource bundle creation task is exceeded, and vSphere removes the task from its queue.

    Workaround:

    1. In the vSphere Client, right-click the resource pool in the inventory and select Edit Settings.
    2. In the Edit Settings dialog box, do not modify any of the existing settings, and click OK.

      This triggers a reconfiguration task in which Data Director can register the resource pool, which then becomes visible within the Data Director administrative interface.