VMware vFabric Data Director - 2.7 Administrator’s Guide

VMware vFabric Data Director
Administrator and User Guide
vFabric Data Director 2.7
This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions of this document, see http://www.vmware.com/support/pubs.
EN- 001185-00
You can find the most up-to-date technical documentation on the VMware Web site at:
http://www.vmware.com/support/
The VMware Web site also provides the latest product updates.
If you have comments about this documentation, submit your feedback to:
docfeedback@vmware.com
Copyright © 2013 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. VMware products are covered by one or more patents listed at http://www.vmware.com/go/patents.
VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies.
VMware, Inc.
3401 Hillview Ave. Palo Alto, CA 94304 www.vmware.com
2 VMware, Inc.

Contents

About VMware vFabric Data Director Administrator and User Guide 9
VMware vFabric Data Director Overview 11
1
Data Director System Architecture 11
VMware Data Director Components 12
Data Director User Management Modes 12
About Data Director Administration 13
Data Director Supported Databases 14
Managing Data Director Resources 19
2
Resource Management Overview 19
Resource Bundles and Resource Pools 20
Storage Resources and Data Director 21
System Resource Bundle 22
Resource Assignment 23
vSphere Resource Pools and Data Director 24
Viewing Resource Information 26
Create the System Resource Pool 26
Create the System Resource Bundle 27
Monitor Resource Usage 28
Create a Resource Pool 28
Create a Resource Bundle 29
Assign a Resource Bundle to an Organization 31
Perform Advanced Cluster Configuration 31
VMware, Inc.
Managing Users and Roles 33
3
User Management Overview 34
Authenticating Users 35
Role-Based Access Control 35
Predefined Roles 36
Privileges 37
Propagation of Permissions and Roles 38
Organization Privileges and Permissions 38
Add Users to Your Organization 39
Add Roles to an Organization 39
Grant a Permission to a User 40
Modify Organization Security Settings 40
About vCenter Single Sign-On 41
Register vFabric Data Director with the vCenter Single Sign-On Service 41
Import vCenter Single Sign-On Service Users 42
Remove vCenter Single Sign-On Registration Before Uninstalling vFabric Data Director 43
3
Building DBVMs and Base DB Templates 45
4
Database Virtual Machine OVA Files 48
Deploy a DBVM OVA File 48
Disk Configuration for DBVMs and DB Templates 49
Build an Oracle, SQL Server, or Empty Base DBVM 50
Build a MySQL Base DBVM 51
Build an Oracle and SUSE Linux Base DBVM 56
Build an Oracle DBVM with a Custom Linux Operating System 56
Requirements for the Kickstart File 60
Build a Base DBVM with a Custom Operating System 63
Create and Validate a Base DB Template 65
Database Update Configuration 68
Configure a vFabric Postgres Update Chain 69
Update an Oracle Database 70
Managing Organizations 77
5
Organization Structure 77
Operating Organizations 78
Managing Resources For Organizations 79
Managing Organization Users 80
Create a Data Director Organization 80
Bind a vCloud Director Organization to Data Director 81
IP Whitelists 83
6
Create an Organization IP Whitelist 83
Apply IP Whitelists to Databases 84
Create Custom IP Whitelists 84
Managing Database Groups 87
7
Database Group Management Overview 87
Managing Resources for Database Groups 88
Storage Reservation 89
Database Groups and Security 89
Create a Database Group 89
Managing Database Templates 91
8
Introduction to Database Templates 91
Enable a Base DB Template 92
Create a DB Parameter Group 93
Create a Resource Template 93
Modify a Resource Template 94
Create a Backup Template 95
Modify a Backup Template 96
Managing Databases 99
9
Database Lifecycle 99
Requirements for Creating Databases 101
4 VMware, Inc.
Database Creation 102
Using Tags 116
Managing the Organization Catalog 117
Batch Operations and Scheduled Tasks 119
Updating Databases 120
Database Administration 121
Contents
Cloning Databases 127
10
Clone Types 127
Cloning Customizations 129
Clone a Database 129
Managing Post-Clone Scripts 133
Managing a Cloned Database Refresh 137
Managing Database Entities 141
11
Database Entity Management 141
SQL Management 146
Safeguarding Data 149
12
Backup Strategies 150
Backup Types 150
Backup Template Settings 152
Preconfigured Backup Templates 153
Select a Database Backup Template 153
Schedule Regular Database Backups 154
Create a Database Snapshot 155
Recover a Database from Backup 156
Import Backups 156
Recover a Database from Last State 157
Use VMware Data Recovery to Back Up Data Director 158
Database End of Life and Backups 160
Perform Point-in-time Recovery of Management Server Database 160
Add Pre-Action and Post-Action Scripts to the DBVM for Selected Agents 161
High Availability and Replication 163
13
About High Availability in Data Director 163
vPostgres Database Replication 164
Monitoring the Data Director Environment 167
14
Explore Monitoring Customization and Filtering 167
Monitoring for System Administrators 168
Monitoring for Organization Administrators 172
Explore Database Monitoring 176
Working with Alarms 177
About aurora_mon Configuration 179
aurora_mon Configuration Parameters 180
VMware, Inc. 5
Managing Licenses 185
15
License Management Overview 185
Counting Data Director Licenses 187
About Evaluation Licenses 187
Add License Keys 188
View License Information 188
View License Usage Information 189
Change the vFabric Postgres Database Usage Type 189
Remove License Keys 190
IP Pool Management 191
16
Add an IP Pool 191
Edit IP Pool 192
Delete an IP Pool 192
VMware vCloud Director Integration 195
17
Enable vCloud Director Integration in Setup 196
Enable vCloud Director Integration after Setup 196
Edit or Disable vCloud Director Integration 197
Add a vCloud Director Organization Administrator 197
Reconfiguring Data Director Networks 199
18
Change the vCenter IP Address 199
Reconfigure the Web Console Network Mapping or Network Adapter 200
Reconfigure the vCenter Network Mapping 201
Reconfigure the vCenter Network Adapter Settings 201
Reconfigure the DB Name Service Network or DB Name Service Network Adapter 202
Reconfigure the Internal Network or Internal Network Adapter Mapping 203
Verify Network Settings in Data Director 204
Reconfigure the Database Access Network Used by a Database Group 204
Modify IP Pool Settings 205
Managing SSL Keys and Certificates 207
19
Regenerate Management Server Key and Certificate 207
Import Management Server Key and Certificate 208
Edit Management Server Certificate 209
Regenerate DB Name Server Key and Certificate 209
Import DB Name Server Key and Certificate 210
Edit DB Name Server Certificate 210
Regenerate DBVM Key and Certificate 211
Import DBVM Key and Certificate 211
Edit DBVM Certificate 212
Data Director Troubleshooting 213
20
vCenter Server Stops Responding 213
Disk Usage Exceeds Acceptable Levels 214
Resource Bundles Become Unusable Because DRS Is Disabled 214
Missing Resource Pool 214
6 VMware, Inc.
Troubleshooting for SSL Communication 215
Database Cannot Be Connected Using the JDBC Connection String 216
Unable to Import or Login Users of the Single Sign-On Service 217
Index 219
Contents
VMware, Inc. 7
8 VMware, Inc.

About VMware vFabric Data Director Administrator and User Guide

The VMware vFabric Data Director Administrator and User Guide describes the features of VMware® vFabric Data Director.
VMware vFabric Data Director is an enterprise class database-as-a-service (DBaaS) solution on VMware vSphere that provides self-service lifecycle management for heterogeneous databases. The solution includes the following features.
n
Database creation, cloning, backup, and restore.
n
Flexible, policy-based resource management.
n
Resource isolation within organizations and within databases.
n
Security policy implementation through role-based access control.
n
Database ingestion.
Self-service database lifecycle management enables administrators to create databases, manage schemas, configure backups, perform restores, clone databases for testing and development, scale up database sizes, and decommission databases. Administrators can assign permissions to perform these functions to others, such as application developers, QA (test), and production engineers.
Customizable templates for database configuration and backups simplifies database creation and resource allocation, enabling administrators to control database parameters and enforce resource allocation policies.
Administrators perform the following types of tasks.
n
Create organizations and database groups.
n
Allocate resources.
n
Create database templates.
n
Create, clone, backup and restore databases.
n
Monitor the Data Director environment.
Administrators also manage users and roles by assigning various permissions to enable users to perform specific database management tasks.
Intended Audience
This document is for administrators any user to whom an administrator might grant database permissions.
n
System administrators use this document to learn how to manage and monitor a Data Director environment.
n
Organization administrators use this document to learn how to manage and monitor database groups and databases.
VMware, Inc.
9
n
Application developers use this document to learn how to create, manage and monitor databases.
n
Application developers, QA and production engineers, and others use this document to learn how to perform functions for which they have been granted permissions.
10 VMware, Inc.
VMware vFabric Data Director
Overview 1
VMware vFabric Data Director is a software solution that powers Database-as-a-service in your cloud. It enables you to implement database-aware virtualization on vSphere and provides self-service lifecycle management for heterogeneous databases.
This chapter includes the following topics:
n
“Data Director System Architecture,” on page 11
n
“VMware Data Director Components,” on page 12
n
“Data Director User Management Modes,” on page 12
n
“About Data Director Administration,” on page 13
n
“Data Director Supported Databases,” on page 14

Data Director System Architecture

vFabric Data Director automates deployment, management, and governance of thousands of databases and enables policy-based self-service database management for application developers.
Data Director supports the following databases.
n
Oracle 11gR2 Enterprise and Standard editions.
n
Oracle 10gR2 Enterprise and Standard editions.
n
Microsoft SQL Server 2012 Enterprise and Standard editions.
n
Microsoft SQL Server 2008 R2 Enterprise and Standard editions.
n
MySQL 5.5.27
n
vFabric Postgres 9.1 and 9.2.3 a VMware vSphere optimized relational database based on PostgreSQL.
Data Director provides flexible, policy-based resource management at the system level, and isolation at the organization and database level. Data Director system administrators can implement security policies through role-based access control to restrict system access to authorized users. System administrators use database templates to guarantee corporate compliance to standardization, and carry out important database lifecycle management tasks such as provisioning, backup, snapshots, point-in-time recovery, cloning, updating, monitoring, and so on.
Database administrators and authorized users can configure databases by using customizable parameters. Resource and backup templates simplify database creation. After an administrator assigns appropriate permissions, users can create databases and allocate resources to them. Users can schedule backups, perform restores, and clone databases to use in testing and development environments. They can scale up databases according to system needs, and decommission databases when they are no longer required.
VMware, Inc.
11

VMware Data Director Components

The Data Director hierarchy consists of organizations, each with its own discrete database groups and databases. Currently supported databases include vFabric Postgres, Microsoft SQL Server, and Oracle.
System administrators perform management tasks at the system level, which is the top level of the hierarchy. To edit system-level settings you must have system privileges, but having system privileges does not automatically allow you to make changes at the other levels.
A system can contain multiple organizations, each with multiple database groups. A database group can contain multiple databases. You can create database groups only within organizations. Databases can exist only within database groups.
Figure 1-1. Data Director System Hierarchy
System administrators manage Data Director resources at the system and organization levels. System administrators create resource bundles from vSphere resource pools (CPU and memory resources) and storage and network resources, and allocate one or more resource bundles to each organization.
Organization administrators assign resources from the given resource bundles to database groups for consumption by databases.

Data Director User Management Modes

Data Director user management modes control how users are assigned and managed among different organizations. Data Director has two user management modes: Global mode (for enterprises) and By Organization mode (for service providers). Global user management mode is the default.
User management mode must be set to By Organization for VMware vCloud Director integration. See
“Organization Structure,” on page 77.
By Organization user management mode has the following characteristics.
n
Organizations are set up as separate, isolated enterprises with no visibility into other organizations.
n
The Data Director system user list is not visible to organizations.
n
No organization can see another organization's user list.
n
Organization administrators send email to invite users to join their organization, or register users directly.
n
Users can navigate to the Data Director web console URL and register for an account, pending approval from the organization administrator.
12 VMware, Inc.
Global user management mode has the following characteristics.
n
Organizations are set up as separate departments, business units, or groups within one enterprise, such as a corporation's HR and Finance departments.
n
All Data Director users are visible to all organizations within Data Director.
n
Organization administrators grant access to users to the organization or grant access directly from the system user list.
n
Users can navigate to the Data Director web console URL and register for an account, pending approval from the organization administrator.

About Data Director Administration

Data Director system administrators perform Data Director administration on the system level. Organization administrators perform Data Director administration on the organization level.
You create the initial account for the Data Director system administrator during Data Director setup. That system administrator creates the system resource bundle, base database virtual machines (base DBVMs), and base database templates.
By default, users do not have roles or permissions and cannot access any organizations. Organization administrators assign roles and permissions to users and grant them access to specific organizations.
Chapter 1 VMware vFabric Data Director Overview
System administrators perform system-level operations for Data Director or for an entire organization. System administrators perform the following tasks.
Table 1-1. System-Level Operations
Operation Type Examples
Resource management operations
User and organization management operations
n
Creating and managing the system resource bundle.
n
Creating and managing resource bundles.
n
Creating and managing database virtual machines (DBVMs).
n
Managing base database templates.
n
Assigning base database templates to resource bundles.
n
Assigning resource bundles to organizations.
n
Creating and managing resource templates.
n
Creating and managing backup templates.
n
Creating system users.
n
Creating system administrators.
n
Creating organizations.
n
Creating organization administrators.
n
Designating existing users as organization administrators.
Organization administrators perform organization-level operations within their organizations. Organization administrators perform the following tasks.
VMware, Inc. 13
Table 1-2. Organization-Level Operations
Operation Type Examples
Resource management operations
User management operations
By default, Data Director system administrators do not have access to organizations. Organization administrators have access to only their own organization. They can create organization users and can grant access to existing Data Director users.
Data Director system administrators can create users, but only organization administrators can grant those users access to organizations.
n
Creating database groups.
n
Enabling base database templates in resource bundles.
n
Creating resource templates.
n
Creating backup templates.
n
Allocating resources to database groups within the organization.
n
Creating and managing organization users.
n
Granting organization access to existing Data Director users.
n
Assigning organization roles to users in the organization.
n
Creating and managing organization roles and granting roles to organization user.
n
Defining organization permissions and granting permissions to organization users.

Data Director Supported Databases

Data Director supports self-service database provisioning and automation through a web interface and compatible client tools and drivers.
Data Director supports the following databases.
n
“VMware vFabric Postgres Databases,” on page 15
n
“Oracle Databases,” on page 15
n
“Microsoft SQL Server Databases,” on page 15
n
“MySQL Databases,” on page 17
Database administrators and application developers administer databases within their organizations. Database administration includes the following tasks.
n
Creating databases and allocating resources to them.
n
Cloning databases.
n
Managing database users, roles, privileges, and permissions.
n
Maintenance such as performing backups and restores.
n
Scaling up databases.
n
Updating databases.
n
Monitoring database usage and performance.
n
Monitoring database alarms.
n
Decommissioning databases.
14 VMware, Inc.
Chapter 1 VMware vFabric Data Director Overview

Oracle Databases

As a system administrator, you upload, test, and manage the Oracle base database templates that organization administrators, DBAs, and application developers use to create Oracle databases.
The recommended practice for using Oracle with Data Director is to set up a dedicated vSphere ESXi cluster for hosting Oracle resources, including operating system, Oracle database server, and client tools. You create Oracle base database virtual machines (DBVMs) using the dedicated Oracle resources in vSphere, then upload the DBVMs to Data Director to use as database templates.
Data Director supports the following Oracle versions.
n
Oracle 11gR2 on SUSE, RHEL, or Oracle Linux.
n
Oracle 10gR2 on SUSE, RHEL, or Oracle Linux.

VMware vFabric Postgres Databases

Data Director provides self-service database provisioning and automation with vFabric Postgres databases. vFabric Postgres is built on the open source Postgres database.
vFabric Postgres is compatible with pSQL and the PostgreSQL tools and client drivers. vFabric Postgres databases are fully compliant with ACID and ANSI SQL. The ACID properties, Atomicity, Consistency, Isolation, and Durability, guarantee that database transactions are processed reliably.
For information about the Postgres database features for Data Director, see the Using VMware vFabric Postgres for Data Director.

Microsoft SQL Server Databases

As a Data Director system administrator you upload and manage the SQL Server base database templates that organization administrators, DBAs, and application developers use to provision SQL Server databases.
Use SQL Server with Data Director to set up a dedicated vSphere ESXi cluster for hosting SQL Server resources, including operating system, SQL Server database server, and client tools. You create SQL Server base database virtual machines (DBVMs) using the dedicated SQL Server resources in vSphere, and upload the DBVMs to Data Director to use as database templates from which you can provision SQL Server databases.
Data Director supports the following SQL Server versions.
n
SQL Server 2012 Enterprise and Standard editions.
n
SQL Server 2008 R2 Enterprise and Standard editions.
About Provisioning SQL Server Databases
Data Director supports the creation of a stand-alone SQL Server instance using the default (unnamed) instance or a named instance. The default instance name is the same as the host name. You can have only one default instance per virtual machine.
NOTE A SQL Server instance is either an unnamed instance or a named instance. When SQL Server is installed as an unnamed instance, it does not require a client to specify the name of the instance to make a connection. The client only has to know the server name. A named instance is identified by the network name of the computer plus the instance name that 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.
VMware, Inc. 15
The Data Director provisioning process prepares and configures the SQL Server software as described in the following list.
n
The SQL Server DBVM can join an existing Windows domain during provisioning. You must provide a Windows Active Directory credential with sufficient privileges to join the domain. If a SQL Server DBVM joins a domain, Windows authentication is the authentication method. The user-supplied domain account is added to the sysadmin role of the SQL Server instance.
n
If the DBVM does not join a domain, Data Director uses mixed authentication, and prompts for the SQL Server System Administrator (SA) password.
n
No user databases are created when provisioning within Data Director.
About SQL Server Snapshot Backups
Data Director supports manually initiated, snapshot backups with SQL Server DBVMs. You cannot use automatic, external, or point-in-time recovery (PITR) backups when using a SQL Server a DBVM.
If you create a snapshot backup of a SQL Server DBVM, then change the configuration properties of the DBVM and try to recover from the now out-of-date (or un-synchronized) snapshot, the virtual machine may become unstable, or the configuration values displayed in the Data Director interface for the SQL Server DBVM may not be accurate.
Also, snapshot backups may decrease the I/O performance of a SQL Server DBVM.
For these reasons VMware recommends that you only use snapshots as a temporary backup solution, and that you maintain them for a limited amount of time. You can use snapshot backups before performing system maintenance, such as applying patches to the operating system or database software, or performing database operations that may cause a loss of data. When you have successfully completed the maintenance or data changing tasks, delete the snapshot backup.
See “Snapshot Backups,” on page 151 and “Create a Database Snapshot,” on page 155.
Data Director Support for SQL Server
You can provision new, empty SQL Server databases using Data Director. To learn more about creating a SQL Server database, see “Create an Empty SQL Server Database,” on page 105.
The following Data Director features are not available for use with SQL Server. When managing SQL Server databases the user interface controls for these features are not available in the Data Director administration console.
n
Database cloning.
n
Adding databases to the organization catalog.
n
Database ingestion.
n
Use of IP whitelists.
n
Changing disk size.
n
DBVM reporting.
n
Editing database resources.
n
Adding database owners.
n
Base DB template validation.
n
Upgrading.
16 VMware, Inc.
Chapter 1 VMware vFabric Data Director Overview

MySQL Databases

As a Data Director system administrator you upload and manage MySQL base database templates that organization administrators, DBAs, and application developers use to provision MySQL databases.
Use MySQL with Data Director to set up a dedicated vSphere ESXi cluster for hosting MySQL resources, including operating system, MySQL database server, and client tools. You create MySQL base database virtual machines (DBVMs) using the dedicated resources in vSphere, and upload the DBVMs to Data Director to use as database templates from which you can provision MySQL databases.
Data Director supports MySQL Community Edition 5.5.27.
Data Director Support for MySQL
The following Data Director features are not available for use with MySQL. When managing MySQL databases the user interface controls for these features are not available in the Data Director administration console.
n
Provision a database by ingestion.
n
Schema only clone.
n
Import or regenerate SSL keys.
n
Connection string to identify a DB Name server.
n
Performance monitoring and database statistics.
n
Alarms alerting you to MySQL specific thresholds and problems.
n
Upgrading and patching.
VMware, Inc. 17
18 VMware, Inc.

Managing Data Director Resources 2

System administrators manage CPU, memory, storage, and networking resources, as well as system-wide database and backup configuration templates. Organization administrators manage resources for database groups and for databases and enable database templates for their organizations.
This chapter includes the following topics:
n
“Resource Management Overview,” on page 19
n
“Resource Bundles and Resource Pools,” on page 20
n
“Storage Resources and Data Director,” on page 21
n
“System Resource Bundle,” on page 22
n
“Resource Assignment,” on page 23
n
“vSphere Resource Pools and Data Director,” on page 24
n
“Viewing Resource Information,” on page 26
n
“Create the System Resource Pool,” on page 26
n
“Create the System Resource Bundle,” on page 27
n
“Monitor Resource Usage,” on page 28
n
“Create a Resource Pool,” on page 28
n
“Create a Resource Bundle,” on page 29
n
“Assign a Resource Bundle to an Organization,” on page 31
n
“Perform Advanced Cluster Configuration,” on page 31

Resource Management Overview

System administrators allocate resources to organizations. These virtual resources come directly from the physical resources of the cluster on which Data Director runs. Organization administrators assign organization resources to database groups and databases.
A vSphere cluster consists of several ESXi hosts that provide the physical CPU and memory resources for the databases managed by Data Director. As part of installation, you create the cluster and enable vSphere High Availability (HA) and vSphere Distributed Resource Management (DRS) for the cluster. Data Director can take advantage of the vSphere HA and vSphere DRS functionality because Data Director runs on top of the cluster. See the vSphere Availability and the vSphere Resource Management documentation for details.
VMware, Inc.
19
A Data Director resource bundle includes CPU, memory, storage, and networking resources. The CPU and memory resources come from a resource pool in the vSphere cluster. The storage and networking resources are assigned to Data Director during installation or at a later time. Data Director includes a set of VLANs to carry different types of network traffic.
Data Director provides the following types of resource bundles.
n
System resource bundle. Data Director system administrators create one system resource bundle at the Data Director system level. In addition to providing virtual resources, the system resource bundle contains the database virtual machines (DBVMs) and base database templates that support creating and provisioning databases. See “System Resource Bundle,” on page 22.
n
Resource bundle. Data Director system administrators create one or more resource bundles to provide operating resources to organizations.
When system administrators create an organization, they can assign virtual resources to the organization as resource bundles. When organization administrators create a database group, they assign virtual resources to the database group. These virtual resources are backed by the physical resources of one or more clusters. vSphere clusters provide failover protection and support efficient use of physical resources.
System administrators can assign resources when they create an organization (see “Create a Data Director
Organization,” on page 80) or assign resources to an existing organization (see “Assign a Resource Bundle to an Organization,” on page 31). Organization administrators can assign resources when they create a
database group or assign resources to existing database groups.
NOTE If you chose the Express installation in the Data Director Setup wizard and enabled Create defaults, a system resource bundle and Default resource bundle is already created. A Default organization and Default database group is also created, and the Default resource bundle is assigned to the Default organization.
To help you specify the resources associated with a database template, Data Director includes a calculator that computes the optimum resource configuration based on the anticipated usage patterns. When you create databases from the template, the specified resources are allocated.

Resource Bundles and Resource Pools

A resource bundle is a set of compatible IT resources for provisioning databases. To assign the appropriate amount of resources to each organization, system administrators create resource bundles and assign them to organizations.
System administrators specify a resource pool and storage and networking resources when they create a resource bundle.
NOTE If you deployed Data Director using the Express installation, and selected the Create defaults option to specify resources, a Default resource bundle is created and assigned to a Default organization.
Resource Pool
Storage Resources
All CPU and memory resources of a resource bundle come from a vSphere resource pool that is created in the vSphere Client with reservation equal to limit. See “Create a Resource Pool,” on page 28.
Each resource bundle includes storage resources for the operating system, database binary, data, log, and backup storage needs for each database virtual machine that you create. The storage resources must be visible to all hosts that use the resource bundle.
DB Access Networks
DB Access Networks provide communication for databases. A DB Access Network corresponds to a vSphere port group. Each network must be visible to all hosts that use the resource bundle. DHCP or IP Pool is required. See
Chapter 16, “IP Pool Management,” on page 191
20 VMware, Inc.
vSphere
source RPs
source datastores
source port groups
CPU & memory
network
resource bundle
CPU & memory
network
Data Director
resource bundle
OS
storage
data
storage
backup storage
log
storage
OS
storage
data
storage
backup storage
log
storage
Chapter 2 Managing Data Director Resources
Selecting one or more DB Access Networks allows you to isolate different database groups from one another, for example, to isolate a QA database group from a Production database group. When no DB Access Networks have been assigned in the environment, select the network that is mapped to the Web Console Network. Do not select internal networks for DB Access Network traffic.
The figure shows how Data Director resources come from vSphere resource pools, datastores, and port groups. When administrators create a resource bundle, the resources are always coming from the underlying vSphere environment.
Figure 2-1. Resources in vSphere and Data Director

Storage Resources and Data Director

VMware, Inc. 21
“Resource Assignment,” on page 23 explains how resource assignment differs for the different levels of the
hierarchy.
Storage configuration is essential for any successful database deployment, especially in virtual environments where you can consolidate many different database workloads on a single ESXi host. Your storage subsystem should provide sufficient I/O throughput as well as storage capacity to accommodate the cumulative needs of all database virtual machines (DBVMs) running on your ESXi hosts.
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 then map the virtual disks to different datastores using disk provisioning and storage allocations that you specify to improve disk usage, performance, and redundancy. For example, you can create dedicated datastores to service I/O intensive database workloads.
Storage Virtualization Concepts
VMware storage virtualization can be categorized into three layers of storage technology.
n
The storage array is the bottom layer, consisting of physical disks presented as logical disks in the form of either storage array volumes or logical unit numbers (LUNs) to the layer above.
n
The next layer is the virtual environment occupied by vSphere. Storage array LUNs are presented to ESXi hosts as datastores and are formatted as VMFS volumes.
n
Virtual machines consist of virtual disks that are created in the datastores and presented to the guest operating system as disks that can be partitioned and used in file systems.
VMFS is a cluster file system that provides storage virtualization optimized for virtual machines. Each virtual machine is encapsulated in a set of files and VMFS is the default storage system for these files on physical SCSI disks and partitions. VMFS allows multiple ESXi instances to access shared virtual machine storage concurrently. It also enables virtualization-based distributed infrastructure services such as vMotion, DRS, and VMware HA to operate across a cluster of ESXi hosts.
Consolidated Versus Dedicated Datastores
A generally accepted best practice is to create a dedicated datastore if an application has a demanding I/O profile. Databases fall into this category. The creation of dedicated datastores allows you to define individual service level guarantees for different applications, and is analogous to provisioning dedicated LUNs in a physical server environment.
Partition Alignment
Aligning file system partitions is a well-known storage best practice for database workloads. Partition alignment on both physical machines and VMware VMFS partitions prevents I/O performance degradation caused by I/O crossing track boundaries. Using the vSphere Client to create VMFS partitions avoids this problem since, beginning with ESXi 5.0, it automatically aligns VMFS3 or VMFS5 partitions along the 1MB boundary.
When creating partitions VMware recommends the following best practices:
n
Create VMFS partitions from within vCenter because they are aligned by default
n
Align the data disk for heavy I/O workloads using diskpart.
n
Consult with the storage vendor for recommendations on how best to use their hardware in conjunction with your Data Director deployment.

System Resource Bundle

The system resource bundle provides CPU, memory, network, and storage resources for the base database virtual machines (base DBVMs) and base database templates that you use to create and provision databases. Each Data Director installation must have one system resource bundle. If you chose Create defaults in the Express installation, a system resource bunde is created automatically.
Data Director system administrators create the system resource bundle before setting up other Data Director entities and populate it with base database templates and base DBVMs.
The Data Director system administrator creates the system resource bundle at the system level. This ensures that the CPU, memory, storage, and networking resources, base database templates, and base DBVMs apply to the entire Data Director platform. The system administrator creates resource bundles and assigns base database templates to them, and assigns the resource bundles to organizations. The organization administrator enables base database templates for use in that organization.
See “Create the System Resource Bundle,” on page 27.
22 VMware, Inc.

Resource Assignment

Resource assignment differs for organizations, database groups, and databases.
Resource Assignment for Organizations
System administrators can assign multiple resource bundles to each organization. System administrators can assign a particular base database template to multiple resource bundles. Organization administrators allocate the resource bundles to database groups and enable base DB templates. When you create databases, they draw on the resources assigned to the database group and the base database templates enabled in the organization. This resource isolation guarantees that different organizations and different database groups have control over their resources.
If you chose the Express installation and enabled Create defaults in the Data Director Setup wizard, a system resource bundle and Default resource bundle are created during setup. A Default organization with a Default database group within that organization is also created, and the Default resource bundle is assigned to the Default organization.
Resource Assignment for Database Groups
When you create a database group, you assign a resource bundle that specifies the resources for that group. You cannot assign more than one resource bundle to one database group. Multiple database groups can share one resource bundle.
Chapter 2 Managing Data Director Resources
When you assign a resource bundle to a database group, you can specify how to allocate each resource.
n
CPU priority or reservation.
n
Memory priority or reservation.
n
Storage allocation.
n
Storage reservation percentage.
n
A network for the database group. You cannot divide the network. You can select only one network when you create a database group even if several networks are associated with the resource bundle.
If you do not specify the CPU or memory allocation, Data Director sets the reservation to zero but sets expandable reservations to true. If expandable reservations is set to true, the CPU or memory can expand beyond the specified value.
Resource Assignment for Databases
A database consumes the resources assigned to its database group.
n
You can specify the number of virtual CPUs, the memory size, and CPU and memory priority for each database that you create.
n
You cannot specify storage allocation. All databases consume the data and the backup storage allocated to their parent database group. You can specify the size of data or PITR disk of each database.
n
Each database uses the network assigned to the database group as the DB access network.
VMware, Inc. 23

vSphere Resource Pools and Data Director

A vSphere resource pool is a logical abstraction for flexible management of CPU and memory resources.You add CPU and memory resources to Data Director resource bundles by adding a vSphere resource pool to the bundle.
Data Director has the following types of resource pools.
Resource Pools for Databases
System Resource Pool
CAUTION Data Director can use only resource pools for creating databases if the corresponding cluster is enabled for DRS and HA. Do not disable DRS. If you do, Data Director cannot use the resource pools even if you reenable DRS. See “Resource Bundles Become Unusable Because DRS Is Disabled,” on page 214.
Resource pools allow you to group available CPU and memory resources. You can allocate resources explicitly, or use the resource pool share mechanism. You can hierarchically partition available CPU and memory resources by grouping resource pools into hierarchies. You can allow different organizations access to different resource pools. For example, a QA department might need large amounts of CPU and memory for running tests while the marketing department might require smaller amounts.
Data Director expects you to group the hosts that provide the CPU and memory resources into clusters. Each cluster owns the resources of all hosts. You can create one or more resource pools for the cluster, which has an invisible root resource pool. Each resource pool owns some of the cluster's resources. If necessary, you can create child resource pools. Child resource pools represent successively smaller amounts of CPU and memory.
vSphere administrators create one or more resource pools to enable Data Director users to create databases. Resource pools for databases require configuration settings such as DRS and HA enabled, and CPU and memory limits equal to reservation.
There is one system resource pool for one Data Director instance. vSphere administrators can deploy database virtual machine (DBVM) OVA files into the system resource pool at any time. The configuration settings for the system resource pool are different from the configuration settings for database resource pools. You do not have to enable HA, and CPU, and memory limits do not have to equal reservations. The reservation must be greater than 0.
You can also enable expandable CPU and memory. See “Create the System
Resource Pool,” on page 26.
CAUTION To use Oracle with Data Director, create a cluster specifically for Oracle use. To avoid licensing issues, assign only resources from your dedicated Oracle cluster to organizations that create and provision Oracle databases and DBVMs.
How you allocate CPU and memory resources to database groups differs from how you allocate those resources to databases.
24 VMware, Inc.
Chapter 2 Managing Data Director Resources
Creating Resource Pools for Databases
You create resource pools for databases by using a vSphere Client connected to a vCenter Server system. Specify the following resource pool settings to ensure that Data Director always receives all of its allocated resources and does not have different amounts of CPU and memory available if the cluster is experiencing a light or a heavy load.
NOTE If you do not configure your resource pool with these settings, problems with resource bundle creation or other Data Director tasks might result. Resource pools with incorrect settings do not appear in the list of available resource pools when you create a resource bundle.
Set the Limit equal to the Reservation.
Set Expandable Reservation to checked
If the system never allocates more resources than you reserved, you do not experience resource fluctuations.
If the system does not attempt to allocate more resources than you reserved, you do not experience resource fluctuations.
or unchecked.
Set Unlimited to unchecked.
Data Director requires this setting to avoid a resource bundle taking more than its share of the resource pool.
After you create the resource pool, you create resource bundles. Each resource bundle uses one resource pool.
See “Create a Resource Pool,” on page 28 and “Create a Resource Bundle,” on page 29.
Allocating CPU and Memory Resources to Database Groups
When you create a database group and set its CPU and memory allocation, Data Director creates a child resource pool of the resource pool that you select. Data Director configures the resource pool with the allocation that you specify. Having a different resource pool for each database group isolates the database group's allocation and makes different groups independent.
n
If you specify the CPU and memory allocation, Data Director uses the following settings for the resource pool it creates.
n
Reservation is set to the value you specify.
n
Expandable reservation is set to False.
n
Limit is set to unlimited.
n
If you do not specify CPU or memory allocation, Data Director uses the following settings for the resource pool it creates.
n
Reservation is set to 0.
n
Expandable reservation is set to True, allowing the database group to consume resources as they are available.
n
Limit is set to unlimited.
Allocating CPU and Memory Resources to Databases
In the Data Director environment, a database is a virtual machine that consumes resources from the database group. You can specify the CPU and memory allocation for the database. Data Director always sets the limit to unlimited.
VMware, Inc. 25

Viewing Resource Information

Data Director system administrators can view resource usage information for an organization from the Data Director Manage & Monitor tab.
When you log in to Data Director as a system administrator, you can view information about the resource usage of the different organizations and about the resource bundle or resource bundles that are being used by each organization.
n
The Organizations pane allows you to manage organizations. You can view organization information, assign and unassign resource bundles, delete the organization, and view the organization's properties.
n
The Resource Bundles pane allows you to view all resource bundles currently created for this instance of Data Director. You can display either allocation information or vCenter Server Object information.
n
You can click on an item in the heading, such as Organization, to re-sort the table based on that column. Right-click any resource bundle name and choose Properties to see detailed information about each resource bundle.
n
If you select vCenter Server Objects, Data Director displays the names of resource pools, datastores, and networks that you see in the vSphere Client UI.
n
The Datastore Usage pane shows datastore usage for the main datastore and the backup datastore. You can see how resource bundles map to datastores and examine storage allocation information for each datastore.
See Chapter 14, “Monitoring the Data Director Environment,” on page 167 for details on using the monitoring interface.

Create the System Resource Pool

vSphere administrators create one system resource pool from a vSphere Client connected to a vCenter Server system. vSphere Administrators deploy the Data Director database virtual machine (DBVM) OVAs to the system resource pool.
Prerequisites
n
Connect to the vCenter Server system by using a vSphere Client. You cannot create resource pools if the client is connected directly to a host.
n
Verify that you have permissions sufficient to create a resource pool.
n
Choose a location for the resource pool. Data Director cannot use resource pools at the top level.
n
See vSphere Resource Management for information about resource pools.
n
Before you create any resource pools, you must prepare a cluster. You must have at least one host in the cluster. See the vFabric Data Director Installation Guide for information.
Procedure
1 In the vSphere Client, select Home > Inventory > Hosts and Clusters.
2 Select the cluster to which all Data Director hosts have been assigned.
3 Specify the settings for the system resource pool.
Option Description
Name
CPU Shares
CPU Reservation
26 VMware, Inc.
Name of the resource pool.
Leave CPU shares set to Normal.
CPU resources to allocate to this resource pool. Set CPU reservation equal to CPU limit value. Must be greater than 0.
Option Description
Expandable Reservation
CPU Limit
Unlimited
Memory Shares
Memory Reservation
Expandable Reservation
Memory Limit
Unlimited
Can be checked or unchecked.
Maximum CPU resources available to this resource pool. Set CPU limit equal to CPU reservation value.
Leave unchecked.
Leave memory shares set to Normal.
Memory resources to allocate to this resource pool. Must be greater than 0.
Can be checked or Unchecked.
Maximum memory resources available to this resource pool. Because this is the system resource pool, limit does not have to equal reservation.
Unchecked.
After the system resource pool is set up, you can deploy Data Director OVA files and point to the system resource pool when you create the Data Director system resource bundle.
What to do next
Create the system resource bundle. See “Create the System Resource Bundle,” on page 27.

Create the System Resource Bundle

Chapter 2 Managing Data Director Resources
The system resource bundle resides at the Data Director system level, and enables you to create, test, and run base database virtual machines.
Prerequisites
n
Create a resource pool to use for allocating CPU and memory resources. See “Create a Resource Pool,” on page 28.
n
Determine the storage resources that you want to include in the system resource bundle. Plan for storage resources for database storage and resources for backup storage.
n
Determine the networking resource that you want to include in the system resource bundle. You can assign only one network to the system resource bundle. The networking resource is used by the base DBVMs for building base database templates.
NOTE If you do not configure your resource pool with these settings, you might have problems with system resource bundle creation or other Data Director tasks.
Procedure
1 Log in to Data Director with system administrator privileges.
2 Select System, and click System Settings.
3 Click System Resource Bundle in the left pane.
4 Click Create System Resource Bundle
5 Specify the following information about the resource bundle in the wizard.
Wizard screen Action
Name and Description
CPU and Memory
VMware, Inc. 27
Type a name and optional description and click Next.
Select the resource pool from which you want to assign CPU and memory resources and click Next.
Wizard screen Action
Storage
Networks
The resource bundle is created.
What to do next
Create a base DBVM. See Chapter 4, “Building DBVMs and Base DB Templates,” on page 45.

Monitor Resource Usage

System administrators can view usage information for resource bundles and datastores and can reassign resource bundles from the Manage & Monitor tab.
The focus of this task is on monitoring, not on changing current settings.
Prerequisites
Click Edit to select a datastore, and allocate the number of gigabytes to use with Data Director, or allocate all unallocated space. Repeat the process for backup storage.
NOTE Do not select a datastore that is in a datastore cluster.
Select the networks that you want to have available to this resource bundle. These networks provide the public network for the organization's databases. Resource bundles must use a database network when available.
n
Log in to Data Director as a user with system administrator privileges.
n
Verify that one or more organizations exist in your environment.
n
Verify that resource bundles and datastores have been assigned to the organizations.
Procedure
1 In Data Director, click the System tab, and click the Manage & Monitor tab.
The Organizations panel displays resource allocation information about each organization.
2 Click one of the columns, for example Total Memory, to reorder the rows of the table.
3 Click one of the organizations to display resource bundle information for the selected organization.
4 Click Resource Bundles to display the Resource Bundles pane.
5 Click Datastore Usage to display information about available datastores, their capacity, and the allocated
and unallocated storage for each.
6 Click one of the datastores to display the associated resource bundles and their storage allocation.
What to do next
You can change the resource bundle information by clicking the Actions icon and selecting Properties. If properties are dimmed, you do not have permissions to change them.

Create a Resource Pool

You allocate CPU and memory resources to Data Director by creating one or more resource pools from a vSphere Client connected to a vCenter Server system. From the Data Director user interface, you can then assign the resources from those resource pools to database groups and databases.
Before you create the resource pools, you must prepare a cluster. Enable the cluster for HA and DRS, and add all Data Director hosts to the cluster. See the vFabric Data Director Installation Guide for information.
28 VMware, Inc.
Chapter 2 Managing Data Director Resources
Prerequisites
n
Connect to the vCenter Server system by using a vSphere Client. You cannot create resource pools if the client is connected directly to a host.
n
Verify that you have permissions sufficient to create a resource pool.
n
Choose a location for the resource pool. Data Director cannot use resource pools at the vApp top level. For information about resource pools, see the vSphere Resource Management documentation .
Procedure
1 In the vSphere Client, select Home > Inventory > Hosts and Clusters.
2 Select the cluster to which all Data Director hosts were assigned.
3 Configure the resource pool.
Option Description
Name
CPU Shares
CPU Reservation
Expandable Reservation
CPU Limit
Unlimited
Memory Shares
Memory Reservation
Expandable Reservation
Memory Limit
Unlimited
Name of the resource pool.
Do not specify CPU shares. Instead, specify the CPU reservation.
CPU resources to allocate to this resource pool. Must be greater than 0.
Checked or unchecked.
Maximum CPU resources available to this resource pool. Set Limit to be equal to CPU Reservation.
Unchecked.
Do not specify memory shares. Instead, specify a memory reservation.
Memory resources to allocate to this resource pool. Must be greater than 0.
Checked or Unchecked.
Maximum memory resources available to this resource pool. Set Limit to be equal to Memory Reservation.
Unchecked.
After you create and configure the resource pool, you can point to the resource pool when you create the Data Director resource bundle.
What to do next
Create a resource bundle. See “Create a Resource Bundle,” on page 29.

Create a Resource Bundle

Resource bundles allow you to bundle CPU, memory, storage, database template, and networking resources. You create resource bundles using the Data Director user interface.
When you create a resource bundle, the wizard displays only resource pools with a parent cluster that meets the following requirements.
n
vSphere DRS and vSphere HA are enabled.
n
VM Monitoring is set to VM and Application Monitoring.
n
VM Restart Priority is not disabled for any of the virtual machines.
n
Host monitoring and admission control are enabled.
See “Perform Advanced Cluster Configuration,” on page 31 for details on recommended settings.
VMware, Inc. 29
Prerequisites
n
Create a resource pool to use for allocating CPU and memory resources. See “Create a Resource Pool,” on page 28.
n
Decide on the storage resources that you want to include in the resource bundle. Plan storage resources for database storage, backup storage, and log storage. For more information on storage types, and how they relate to the disk mappings you create for the DBVMs and DB templates, see “Disk Configuration
for DBVMs and DB Templates,” on page 49.
n
Decide on the database templates (base DB templates) that you want to assign to the resource bundle. Organization users can create and provision databases only when base DB templates are assigned to, and enabled in, an organization's resource bundle(s). You can assign additional base DB templates to resource bundles at any time.
n
Decide on the networking resources that you want to include in the resource bundle. The resource bundle's networking resources are used for the DB access network for databases in an organization.
NOTE If you do not configure your resource pool with these settings, you might have problems with resource bundle creation or other Data Director tasks.
Procedure
1 Log in to Data Director with system administrator privileges.
2 Select System, and click Manage & Monitor.
3 Click Resource Bundles.
4 Click the plus (+) icon.
5 Specify the following information about the resource bundle in the wizard.
Wizard Screen Action
Name and Description
Resource Pool
Storage Allocation
Type a name and optional description.
a Select the resource pool from which you want to assign CPU and
memory resources.
b (Optional) Select the VM DRS Group checkbox, and then select the DRS
Group to assign to the resource bundle from the drop-down menu.
a Click the checkbox next to the name of the datastore whose storage you
want to allocate, and specify the number of gigabytes to use with Data Director, or allocate all unallocated space.
NOTE Do not select a datastore that is in a datastore cluster.
b Select a storage type to assign to the selected datastore. The available
storage types are: OS (operating system), Backup, Data, and Log.
You can only assign the OS and Backup storage types to a single datastore within a given resource bundle. Once you assign the OS and Backup storage types to a datastore, they are not available to assign to another datastore within that resource bundle, and are removed from the list of available storage types.
You can assign the Data and Log storage types to multiple datastores within the same resource bundle.
c Specify the storage reservation. The default is 100%. The minimum
storage reservation is the lower bound of the storage reservations of database groups created under the resource bundle. System administrators typically use this reserve to control how much storage over allocation can be allotted by organization administrators with this resource bundle. See Chapter 7, “Managing Database Groups,” on page 87 for more information about storage reservation.
30 VMware, Inc.
Loading...
+ 194 hidden pages