2.7
Table Of Contents
- VMware vFabric Data Director Administrator and User Guide
- Contents
- About VMware vFabric Data Director Administrator and User Guide
- VMware vFabric Data Director Overview
- Managing Data Director Resources
- Resource Management Overview
- Resource Bundles and Resource Pools
- Storage Resources and Data Director
- System Resource Bundle
- Resource Assignment
- vSphere Resource Pools and Data Director
- Viewing Resource Information
- Create the System Resource Pool
- Create the System Resource Bundle
- Monitor Resource Usage
- Create a Resource Pool
- Create a Resource Bundle
- Assign a Resource Bundle to an Organization
- Perform Advanced Cluster Configuration
- Managing Users and Roles
- User Management Overview
- Authenticating Users
- Role-Based Access Control
- Predefined Roles
- Privileges
- Propagation of Permissions and Roles
- Organization Privileges and Permissions
- Add Users to Your Organization
- Add Roles to an Organization
- Grant a Permission to a User
- Modify Organization Security Settings
- About vCenter Single Sign-On
- Register vFabric Data Director with the vCenter Single Sign-On Service
- Import vCenter Single Sign-On Service Users
- Remove vCenter Single Sign-On Registration Before Uninstalling vFabric Data Director
- Building DBVMs and Base DB Templates
- Database Virtual Machine OVA Files
- Deploy a DBVM OVA File
- Disk Configuration for DBVMs and DB Templates
- Build an Oracle, SQL Server, or Empty Base DBVM
- Build a MySQL Base DBVM
- Build an Oracle and SUSE Linux Base DBVM
- Build an Oracle DBVM with a Custom Linux Operating System
- Requirements for the Kickstart File
- Build a Base DBVM with a Custom Operating System
- Create and Validate a Base DB Template
- Database Update Configuration
- Configure a vFabric Postgres Update Chain
- Update an Oracle Database
- Identify Existing Target DBVM
- Create a Base Database VM from an Existing Template
- Apply a Patch to the Base Database Virtual Machine
- Convert a Base DBVM into a Base DB Template
- Validate a Base DB Template
- Assign a Base DB Template to a Resource Bundle
- Enable a Base DB Template
- Configure an Oracle Update Chain
- Update a Database
- Managing Organizations
- IP Whitelists
- Managing Database Groups
- Managing Database Templates
- Managing Databases
- Database Lifecycle
- Requirements for Creating Databases
- Database Creation
- Using Tags
- Managing the Organization Catalog
- Batch Operations and Scheduled Tasks
- Updating Databases
- Database Administration
- Cloning Databases
- Managing Database Entities
- Safeguarding Data
- Backup Strategies
- Backup Types
- Backup Template Settings
- Preconfigured Backup Templates
- Select a Database Backup Template
- Schedule Regular Database Backups
- Create a Database Snapshot
- Recover a Database from Backup
- Import Backups
- Recover a Database from Last State
- Use VMware Data Recovery to Back Up Data Director
- Database End of Life and Backups
- Perform Point-in-time Recovery of Management Server Database
- Add Pre-Action and Post-Action Scripts to the DBVM for Selected Agents
- High Availability and Replication
- Monitoring the Data Director Environment
- Managing Licenses
- IP Pool Management
- VMware vCloud Director Integration
- Reconfiguring Data Director Networks
- Change the vCenter IP Address
- Reconfigure the Web Console Network Mapping or Network Adapter
- Reconfigure the vCenter Network Mapping
- Reconfigure the vCenter Network Adapter Settings
- Reconfigure the DB Name Service Network or DB Name Service Network Adapter
- Reconfigure the Internal Network or Internal Network Adapter Mapping
- Verify Network Settings in Data Director
- Reconfigure the Database Access Network Used by a Database Group
- Modify IP Pool Settings
- Managing SSL Keys and Certificates
- Regenerate Management Server Key and Certificate
- Import Management Server Key and Certificate
- Edit Management Server Certificate
- Regenerate DB Name Server Key and Certificate
- Import DB Name Server Key and Certificate
- Edit DB Name Server Certificate
- Regenerate DBVM Key and Certificate
- Import DBVM Key and Certificate
- Edit DBVM Certificate
- Data Director Troubleshooting
- vCenter Server Stops Responding
- Disk Usage Exceeds Acceptable Levels
- Resource Bundles Become Unusable Because DRS Is Disabled
- Missing Resource Pool
- Troubleshooting for SSL Communication
- Database Cannot Be Connected Using the JDBC Connection String
- Unable to Import or Login Users of the Single Sign-On Service
- Index
vPostgres Database Replication
You can replicate vPostgres databases to improve reliability, fault tolerance, and accessibility if a database
instance fails, or otherwise becomes unavailable.
The vPostgres database within Data Director uses Write-Ahead Logging (WAL) to replicate data between
master and slave instances. WAL is a standard approach to transaction logging in which changes to data files
are written to only after those changes have been logged. WAL allows for a significant reduction in the number
of disk writes because only the log file needs to be flushed to disk at the time of transaction committal, rather
than every data file changed by the transaction. Using WAL to replicate data is the fastest type of replication
available, allowing you to quickly create slave instances of vPostgres databases.
You can replicate a vPostgres database without any performance penalty to clients accessing the master
instance. However, when you failover to a slave instance, all connections to the database are terminated.
Prerequisites
n
Verify that you have provisioned a vPostgres database within Data Director to replicate.
n
Create slave instances on different datastores assigned to different database groups.
To ensure fault tolerance, replicate slave instances on different datastores than that of the master instance.
Create slave instances in different database groups, where each group is assigned to a different resource
pool to ensure that slave instances have their own resources with which to operate in the event of a system
failure.
Procedure
1 Replicate a vPostgres Database on page 164
You can replicate a vPostgres database to provide an added degree of fault tolerance and redundancy
to your database environment.
2 Failover to a Standby vPostgres Database on page 165
You can manually failover by promoting a slave (or standby) database to take over from its master (or
primary) database. When you promote a slave database to take over from its master database, all other
slave instances are redirected to use the newly created master instance.
Replicate a vPostgres Database
You can replicate a vPostgres database to provide an added degree of fault tolerance and redundancy to your
database environment.
vPostgres replication requires that you create a slave database from the master database. The slave database
is a full clone of its master database.
Prerequisites
n
Provision a vPostgres master (or primary) database within Data Director from which to replicate slave (or
standby) instances.
n
Verify that the vSphere deployment hosting Data Director has two or more datastores on which to create
master and slave databases. The datastores must be on different physical hosts to ensure fault tolerance
in the event of physical hardware failure.
Procedure
1 Log in to Data Director as a system administrator.
2 Click the Organization tab, and click Manage and Monitor.
VMware vFabric Data Director Administrator and User Guide
164 VMware, Inc.