How it Works
VMware
Loading...
V
Loading...
Loading...
vFabric Data Director - 2.5
Programming Guide
38 pgs414.44 Kb0
Administrator’s Guide
196 pgs1.18 Mb0
Installation Manual
50 pgs523.62 Kb0
Table of contents
Loading...

VMware vFabric Data Director - 2.5 Installation Manual

VMware vFabric Data Director
Installation Guide
vFabric Data Director 2.5
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-001062-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 © 2012 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 5
Installation Prerequisites and vSphere Setup 7
1
Prerequisites for vFabric Data Director 7
Express Setup and Advanced Setup 9
vSphere Settings for Data Director 9
Planning the Network Configuration 13
2
Network Configurations for vFabric Data Director 13
Relating Networks in vSphere and Data Director 15
Data Director Networks, IP Allocation, and Firewalls 15
Four VLAN Network Configuration 18
Two VLAN Network Configuration 20
One VLAN Network Configuration 21
Deploy the vFabric Data Director vApp 23
3
Start the Wizard and Specify vApp Properties 24
Specify Network Mappings 24
Specify Network Properties 25
Finish Data Director vApp Deployment 26
Perform vFabric Data Director Express Setup 27
4
Start the Data Director Setup Wizard 28
Choose Express Setup 28
Accept the License Agreement 28
Configure Network Setup 29
Create Default Resource Bundle, Organization, and Group 29
Create the Data Director System Administrator Account 30
Enter License Information 30
Review Data Director Setup 31
VMware, Inc.
Perform vFabric Data Director Advanced Setup 33
5
Start the Data Director Setup Wizard 34
Accept the License Agreement 34
Choose Advanced Setup 35
Create the Initial Data Director System Administrator Account 35
Set User Management Mode 35
Configure the Branding Settings 36
Configure SMTP Settings 36
Configure the vCenter Network and Its Network Adapters 37
Configure Network Mapping 37
3
Configure Networks and Network Adapters 38
Enter License Information 38
Review Data Director Setup 39
vFabric Data Director Upgrade 41
6
About the vFabric Data Director Upgrade Process 42
Data Director Virtual Appliance Upgrade Process Overview 42
Data Director Upgrade Database Virtual Machines Process Overview 43
Upgrade a Data Director Virtual Appliance 43
Upgrade Data Director Database Virtual Machines (DBVMs) 47
Index 49
4 VMware, Inc.

About VMware vFabric Data Director

The VMware vFabric Data Director Installation Guide provides information about installing VMware® vFabric Data Director, including configuring networks, deploying Data Director in vSphere Client as a virtual appliance (vApp) running on a vCenter Server, and performing setup and configuration using the Data Director administration UI.
The Data Director software solution enables you to manage an environment with large numbers of databases, and offers application developers self-service database creation and resource allocation. Data Director supports flexible, policy-based resource management, and provides resource isolation at the organization and database levels. Data Director enables you to implement security policies through role-based access control. You can delegate and grant customizable roles and privileges to specify users' allowed actions.
Self-service database lifecycle management enables application developers to create new databases, manage schemas, set up backups, perform restores, clone databases for testing and development, scale database sizes up, and decommission databases. Customizable database configuration and backup templates enable administrators to control database parameters and enforce resource allocation policies, while simplifying database creation and resource allocation for application developers.
Intended Audience
This document is for administrators and application developers.
n
System administrators use this document to learn about managing and monitoring a Data Director environment. System administrators create organizations, allocate resources to them, and perform other high-level tasks.
VMware, Inc.
n
Organization administrators use this document to learn about managing and monitoring database groups and databases. Organization administrators can use and customize database templates, can assign resources, and can monitor their organization.
n
Application developers use this document to learn about managing and monitoring databases.
5
6 VMware, Inc.
Installation Prerequisites and vSphere
Setup 1
Before you start installing Data Director, you must understand the environment requirements, you must set up vSphere, and you must determine your networking configuration.
This chapter includes the following topics:
n
“Prerequisites for vFabric Data Director,” on page 7
n
“Express Setup and Advanced Setup,” on page 9
n
“vSphere Settings for Data Director,” on page 9

Prerequisites for vFabric Data Director

Before you can install and run Data Director, your environment must meet the prerequisites.
n
To use vFabric Data Director, you must have installed and set up the following VMware products.
n
One of the following vSphere releases:
n
vSphere 5.0 Enterprise or vSphere 5.0 Enterprise Plus
n
vSphere 5.1 Enterprise or vSphere 5.1 Enterprise Plus
n
VMware vSphere Client 5.0 or 5.1
n
VMware vCenter Server 5.0 or 5.1, and any related modules (ISO or ZIP)
n
ESXi ISO or ESXi offline bundle ZIP
n
vSphere Update Manager
n
vSphere VMFS-5
n
VMware Virtual Hardware 7 or later
n
Operating system support for base database templates. The following operating systems are valid to include in a base template.
n
Microsoft Windows Server 2008 R2
n
Red Hat Enterprise Linux 5.4 and later (6.0 is not supported)
n
Oracle Linux 5.4 and later (5.7 and 6.0 are not supported)
n
SUSE Linux Enterprise Server 11 SP1
n
vFabric Postgres. Download the following client tools and drivers from the Data Director Download page.
n
Data Director Client Tools (Linux 32-bit or 64-bit)
n
Data Director JDBC drivers
VMware, Inc.
7
n
Database. You can use Data Director with vFabric Postgres, which comes with Data Director, or you can use one of the supported databases.
n
Microsoft SQL Server 2012
n
Microsoft SQL Server 2008 R2
n
Oracle 11g Release 2
n
Oracle 10g Release 2
n
Web interface support. vFabric Data Director supports the following Web browsers.
n
Firefox 8.0 or later. Also requires Adobe Flash Player Plug-in 10.1 or later.
n
Internet Explorer 8.0 or later. Also requires Adobe Flash Player Plug-in 10.1 or later.
n
Chrome 16.0 or later. Also requires Adobe Flash Player Plug-in 10.1 or later.
The Data Director Web interface requires a minimum monitor resolution of 1024x768.
The following are the minimum requirements for Data Director.
n
2 ESXi servers with 32GB of RAM combined.
n
1 vCenter Server system (can be running on a virtual machine).
n
1 Windows system for running vSphere Client.
n
250GB of shared storage, configured as two datastores.
n
1 Gigabit Ethernet VLAN.
This VLAN will carry Data Director network traffic.
n
One or more Gigabit Ethernet VLANs for one or more database networks.
Database networks carry SQL traffic to and from Data Director databases. Database clients such as JDBC and libpq send and receive SQL traffic from database servers on these networks. Data Director supports multiple database networks for better network isolation, for example, to isolate QA SQL traffic from production SQL traffic. See Chapter 2, “Planning the Network Configuration,” on page 13.
n
Hardware to run the test application.
Check with your company's network administrators or IT staff to determine a setup that is appropriate for your organization. For example, here is one possible setup for a 4-VLAN configuration .
n
4 ESXi servers with 64GB of RAM combined.
n
1 vCenter Server.
n
1 Windows system for running vSphere Client.
n
500GB of shared storage configured as two or more datastores.
n
4 Gigabit Ethernet VLANs.
These Gigabit Ethernet VLANs carry Data Director network traffic.
n
One or more Gigabit Ethernet VLANs for one or more database networks.
Database networks carry SQL traffic to and from Data Director databases. Database clients such as JDBC and libpq send and receive SQL traffic from database servers on these networks. Data Director supports multiple database networks for better network isolation, for example, to isolate QA SQL traffic from production SQL traffic. See Chapter 2, “Planning the Network Configuration,” on page 13.
n
Hardware to run the test application
Data Director licensing supports up to 32 vCPUs.
8 VMware, Inc.
Chapter 1 Installation Prerequisites and vSphere Setup
Data Director provides several database resource templates in different sizes: tiny, small, medium, large, and giant. Estimate the resources that your Data Director deployment requires based on your installation's expected database sizes. For example, a database instance that uses the Tiny database resource template has the following settings.
Table 1-1. Settings for a Tiny Database Configuration
Resource Setting
vCPUs 1
Memory size 512MB
Recommended database storage allocation 2GB
For a base installation that uses the Tiny database template, use a cluster with the following CPU and memory resources.
Table 1-2. Resource Requirements for a Base Installation Using the Tiny Resource Template
Resource Requirements
CPU 4GHz and an additional 400 MHz for each database instance
Memory 8GB of available memory and an additional 512 MB of available memory for each database instance

Express Setup and Advanced Setup

Data Director provides Express and Advanced setup options. Express setup lets you deploy Data Director for development or experimentation. Advanced setup is suitable for production environments that require high availability and performance.
Before beginning the Data Director installation, determine whether to use Express setup to create a simplified Data Director deployment for development, or Advanced setup to create a production deployment.
Express setup is supported for a single VLAN network used with static IP addresses instead DHCP. If you do not adhere to these requirements, the Express setup option is disabled, and you must perform the Advanced setup.
vSphere Settings for Data Director
Before you can install Data Director, set up the vSphere Cluster to deploy Data Director to, and enable the cluster for vSphere High Availability (HA), and vSphere Dynamic Resource Scheduler (DRS). Data Director also requires that you have Network Time Protocol (NTP) enabled in your environment.

Create and Configure the Data Director Cluster

Before you can install the Data Director vApp, you have to create and configure the Data Director cluster.
A cluster is a group of hosts. When a host is added to a cluster, the host's resources become part of the cluster's resources. Clusters enable the vSphere High Availability (HA) and vSphere Distributed Resource Scheduler (DRS) solutions. Cluster settings must be compatible with Data Director.
Prerequisites
n
Connect to the vCenter Server system by using a vSphere Client.
n
Verify that you have sufficient permissions to create a cluster.
n
Verify that a datacenter exists in the vCenter Server inventory.
n
Create a vSphere cluster for use by Data Director. See the vSphere Resource Management documentation and the vSphere Availability documentation.
VMware, Inc. 9
Procedure
1 In the vSphere Client, select Home > Inventory > Hosts and Clusters.
2 Right-click a datacenter or a folder within a datacenter and select New Cluster.
3 Complete the Cluster Features page.
a Name the cluster.
b Select the Turn On vSphere HA and Turn On vSphere DRS check boxes.
vSphere DRS must be enabled. Do not change this setting.
c Click Next.
In DRS clusters, Storage I/O Control is enabled by default. Do not change this setting.
4 On the vSphere DRS page, set the automation level to Partially automated and click Next.
5 On the Power Management page, leave power management set to Off or select a power management
setting appropriate for your environment, and click Next.
6 On the vSphere HA page, select the HA settings required for the Data Director cluster and click Next.
Option Description
Host Monitoring Status
Admission Control
Admission Control Policy
7 On the Virtual Machine Options page, select the settings required for the Data Director cluster settings
and click Next.
Leave Enable Host Monitoring selected.
Leave Enable selected.
Specify a policy suitable for your environment. See the vSphere High Availability documentation.
Option Description
VM Restart Priority
Host Isolation Response
Any option that does not disable VM restart priority is acceptable. Data Director requires that VM restart priority is enabled.
Leave the default or change the setting to support your environment.
8 On the VM Monitoring page, select the following settings and click Next.
Option Description
VM Monitoring
Default Cluster Settings
Select VM and Application Monitoring.
Leave the monitoring sensitivity at the default.
9 Finish the cluster setup.
a Leave VMware Enhanced vMotion Compatibility disabled and click Next.
b Leave the swap file location at its default and click Next.
c Review the cluster settings and click Finish.
What to do next
You can customize the cluster even further to suit your environment requirements. See the vFabric Data Director Administrator and User Guide.
10 VMware, Inc.
Chapter 1 Installation Prerequisites and vSphere Setup

Enable vSphere Network Time Protocol

The Network Time Protocol (NTP) daemon ensures that time-dependent processes occur in sync across hosts. Enable the NTP daemon on the ESXi hosts.
Prerequisites
Verify that the ESXi hosts in the Data Director clusters are running.
Procedure
1 Using a vSphere Client, connect to the vCenter Server system that manages the ESXi hosts in the Data
Director cluster.
2 In the left navigation pane, select one of the hosts.
3 In the main pane, click the Configuration tab, and click Time Configuration.
4 Click Properties and click Options.
5 Click NTP Settings and click Add.
6 In the Add NTP Server dialog box, type a valid NTP server address and click OK.
7 Select the Restart NTP service to apply changes check box and click OK.
8 In the Time Configuration dialog, confirm that the NTP Client Enabled check box is selected.
n
If it is selected, click OK.
n
If it is not selected, click the Options button. In the Service Commands section of the NTP Daemon (ntdp) Options dialog, click Start and click OK.
9 Repeat for the other hosts in the Data Director cluster.

Virtual Switches and Port Groups in vSphere

You create virtual switches and port groups in vSphere for use in Data Director.
vSphere port groups correspond to networks in Data Director. You can later allocate the vSphere port groups for resource bundles for the Data Director Management Server or DB Access Networks. See the vFabric Data Director Administrator and User Guide.
NOTE Do not change the port group in your vSphere network setup. If you must change the port group, make the same change to all hosts in the vSphere environment on which Data Director runs.
VMware, Inc. 11
12 VMware, Inc.

Planning the Network Configuration 2

When you install Data Director, the installer prompts you for the IP addresses for the different networks in the Data Director environment. Data Director network traffic runs on several different networks. Before you start the installation, review the supported Data Director network configurations and plan your Data Director network configuration.
Work with your enterprise's network and IT staff and use the vFabric Data Director Worksheets to plan and implement the VLANs, virtual switches, and port groups (networks) that will carry Data Director network traffic.
For information about vSphere networking, see the vSphere Networking documentation.
This chapter includes the following topics:
n
“Network Configurations for vFabric Data Director,” on page 13
n
“Relating Networks in vSphere and Data Director,” on page 15
n
“Data Director Networks, IP Allocation, and Firewalls,” on page 15
n
“Four VLAN Network Configuration,” on page 18
n
“Two VLAN Network Configuration,” on page 20
n
“One VLAN Network Configuration,” on page 21

Network Configurations for vFabric Data Director

The Data Director system carries different types of network traffic on different networks. To prepare the vFabric Data Director Worksheets for your deployment, you must understand the different networks and servers in the
Data Director environment.
Data Director Management Server and DB Name Server
Data Director deploys the Management Server and a DB Name Server on virtual machines.
Management Server
DB Name Server
VMware, Inc. 13
The Management Server performs all management operations.
The DB Name Server provides the DB Name Service. The DB Name Service provides a single entry point to databases. When Data Director creates a database, it provides a connection string for that database. The connection string contains the DB Name Service IP address, port, database server id, database name, and user name.
Data Director Networks
Data Director uses the following networks to carry different types of network traffic.
When a database client or application connects to a database using the Data Director JDBC or database drivers, the driver retrieves the database IP address from the DB Name Server using the connection string. The driver sets up the connection between the application and the target database. When you use the application to access the database, the application uses that connection. This means that the DB Access Network must be visible from all database clients.
The advantage provided by DB Name Service is that the database applications are not affected when the database server's IP address changes. This enables databases to use dynamic IP addresses from a DHCP server, or from an IP pool, and lowers management costs.
vCenter Network
Carries management traffic between vCenter Server and the Data Director Management Server. This network carries commands that the Management Server uses to interact with vCenter Server and all the ESXi hosts managed by that vCenter Server.
Internal Network
Carries internal management traffic among databases, the Data Director Management Server, and the DB Name Server.
Web Console Network
Carries traffic between Web clients (console) and the Data Director Management Server.
DB Name Service Network
Carries traffic for the name service for databases. The DB Name Server performs database name to IP address translation (database connection services) and must be reachable from database clients.
DB Access Networks
Data Director includes one or more DB Access Networks for carrying SQL traffic between database clients and database virtual machines (DBVMs). Each DB Access Network must have IP pool or DHCP enabled.
Traffic for more than one Data Director network can be on the same physical network. For example, vCenter Network traffic can share the identical vSphere network with the Web Console Network traffic.
Some possible network configurations are as follows.
n
Four separate networks, one for carrying each type of Data Director network traffic, plus one or more networks for carrying database (SQL) network traffic to and from databases. See “Four VLAN Network
Configuration,” on page 18.
n
Two networks, one for carrying database (SQL) network traffic and one shared network that carries all Data Director Management Server network traffic. This configuration is the minimum network configuration. See “Two VLAN Network Configuration,” on page 20.
Database clients send and receive SQL traffic from database servers on the DB Access Network. Data Director supports more than one database network VLAN for better network isolation, for example, to isolate QA SQL traffic from production traffic.
If you set up two separate database networks, the database network traffic can use the vCenter Network, Web Console Network, or DB Name Server Network.
You can have as many database networks as your site requires. However, database clients must have access to the DB Name Service Network.
14 VMware, Inc.

Relating Networks in vSphere and Data Director

Data Director components communicate by using vSphere networking resources. Before you start planning your network, you must understand vSphere and Data Director networking.
Data Director requires networks to carry communications among its components, including the following.
n
Communication between the Data Director Management Server and database servers.
n
Communication between database servers and applications.
n
Communication between the Data Director DB Name Server and applications.
vSphere administrators create switches and networks for each ESXi host. As a vSphere administrator, you can either designate existing networks for Data Director use, or create and configure networks for Data Director use. These networks will be used for the Management Server and for one or more DB Access Networks.
You specify the different networks at different times in the installation and setup process.
Chapter 2 Planning the Network Configuration
vCenter Network and Web Console Network
Internal Network and DB Name Service Network
DB Access Network
Best practice is to set up your Data Director networks as separate subnets, such as using different VLANs, to provide the best security. Use VLANs with 1-Gigabit or higher speed Ethernet interfaces.
In addition to network setup, you must also open certain ports in your firewall. See “Data Director Networks,
IP Allocation, and Firewalls,” on page 15.
You specify the vSphere port groups (networks) to use for vCenter Network and Web Console Network during Data Director vApp deployment.
NOTE Set up vSphere Update Manager to use the vCenter Network to communicate with Data Director. If vSphere Update Manager uses a different network, it cannot function properly.
You set up the Internal Network and DB Name Service Network after the Data Director vApp deploys, during the Data Director setup process. See “Configure
Network Mapping,” on page 37. DHCP or IP pool must be enabled on these
networks.
A DB Access Network is the interface to the database virtual machines (DBVMs) and carries SQL traffic. DBVMs run the actual databases and are created when users create databases. DHCP or IP pool must be enabled on DB Access networks. You can configure as many DB Access networks as there are databases. You select the vSphere networks to use for the DB Access Network when you create resource bundles. See the vFabric Data Director Administrator and User Guide.

Data Director Networks, IP Allocation, and Firewalls

Data Director supports DHCP and IP pool for network configuration. To plan your network, you must understand DNS Server requirements and know which firewall ports must be open for Data Director traffic.
The Data Director vApp requires the use of a DHCP or IP pool address allocation policy. Set up a DHCP server or IP pool for the Internal Network and the DB Access Network. See the vFabric Data Director Administrator and User Guide for information about IP pool setup. If you select a static IP address for the Web Console Network adapter on the Management Server, a DHCP server or IP pool on the Web Console Network is not required.
You can assign static IP addresses to the DB Name Service Network Adapter on the DB Name Server and the vCenter Network adapters on both the Management Server and the DB Name Server. IP pool or DHCP service is not required on their corresponding networks.
VMware, Inc. 15
Loading...
+ 35 hidden pages
Buy Points How it Works FAQ Contact Us Questions and Suggestions Privacy Policy Cookie Policy Terms of Use