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
File Based Conventions
During the ingestion and refresh process, coordinate your operations with external programs, such as third
party backup software, or with manual operations. Familiarize yourself with the backup files, and observe
these file based conventions.
n
Backup files for each ingestion or refresh operation should have their own directory. The directory should
be beneath the exported directory.
n
For a golden clone ingestion and golden clone refresh, you must supply a LIST file that contains
information about the backup. The naming convention for a LIST file is database.LIST, where database is
the name of the database. The content of the LIST file is a series of key-value pairs, as in this example LIST
file.
controlfile=o1 mf_s_774019590_71hv06jn_.bkp
pfile=sales.pfile
NOTE The level value, required in previous versions of Data Director, is no longer needed. The agent
automatically checks the bakup level during ingestion and refresh. The optional catalogstart property
specifies the location to load the backup files. This means the control file directory and the catalog start directory
can be different. The value of catalogstart is a directory relative to the LIST file. If no catalogstart is provided,
the directory of the LIST file is used. When you upgrade from Data Director 2.0, make sure your old LIST file
works as expected. Otherwise, provide a catalogstart value.
In this LIST file, the controlfile field specifies the control backup file in the backup set. The value is a file
relative to the LIST file. It can be in the same directory as the LIST file, or in another directory. Other backup
files must be in the same directory as the control backup file.
The pfile field is optional.
To illustrate how to organize the LIST file, a pfile, and backup files, assume that you take a level 0 backup on
Sunday and a level 1 backup on all other days. In this case, you would create a backup directory with a LIST
file and a pfile in it, for example, sales.LIST and sales.pfile. Also in that directory, you would create
subdirectories for each day of the week, with a backup file, LIST file and pfile in each of them.
On Sunday, the sales.LIST file will look like this.
controlfile=Sun/o1_mf_s_774019590_7lhv06jn_.bkp
catalogstart=Sun
pfile=sales.pfile
level=0
NOTE For backwards compatibility, you can retain the level value, as shown for Sunday.
On Monday, the sales.LIST file will look like this.
controlfile=Mon/o1_mf_s_774002607_7lhbfhrm_.bkp
catalogstart=Mon
pfile=sales.pfile
level=1
Ensure that the level information in the LIST file is correct. Information at the wrong level will result in failure
of the refresh process. If you retain the level value for backwards compatibility, set it as shown for Monday.
In the directory containing the backup files, a LOCK file is generated during the ingestion and refresh processes
to coordinate the operation with external programs. The LOCK file uses the same naming convention as the
LIST file. If the LOCK exists at the beginning of an ingestion or refresh process, the process aborts.
Chapter 9 Managing Databases
VMware, Inc. 111