2.5
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
- 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
- Building DBVMs and Base DB Templates
- Database Virtual Machine OVA Files
- Deploy a DBVM OVA File
- Build a SLES and Oracle Base Database Virtual Machine
- Build a Custom RHEL and Oracle Database Template
- Deploy the base database VM into the System Resource Pool
- Repackage the Linux ISO Image
- Install Linux on a Blank Virtual Machine
- Initialize the Virtual Machine to Make It Oracle and Data Director Compliant
- Install Oracle 11g R2 Software
- Convert a Base DBVM into a Base DB Template
- Validate a Base DB Template
- Assign a Base DB Template to a Resource Bundle
- Install the Operating System and Database Software in a Blank DBVM
- Requirements for the Kickstart File
- 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
- Recover a Database
- Import Backups
- 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
- 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
- Index
External Backups
External backups are full copies of the database saved to a datastore separate from the database. This section
describes the pros and cons of using external backups.
External backups use about the same amount of storage as the database itself. Because they reside on a separate
disk from the database, external backups provide resiliency and benefits such as the following.
n
External backups protect against data loss due to failure of the primary data storage device.
n
External backup storage is more cost effective than using the primary data storage for backups.
n
You can extend the data disk as needed.
The following are points to consider about using external backups.
n
External backups can take a long time. Large amounts of data must be copied across devices.
n
Each backup uses the full size of the data disk on the backup storage device.
Snapshot Backups
Snapshot backups capture the changes to the database after the snapshot is taken. Snapshots initially use less
storage than external backup files and take just a few minutes regardless of database size.
Snapshot backups are stored in files called delta files or delta disks on the same data store as the database.
The following are points to consider about using Snapshot backups.
n
Because snapshots reside on the same data store as the database, they do not protect against data loss due
to failure of the data storage.
n
As the database changes, the changes require more and more space on the virtual disk. That space is
generally more expensive than backup storage.
n
The recovery process from snapshots is not faster than the recovery process from an external backup.
n
If you have snapshots, you cannot extend the data disk.
Point-In-Time Recovery
If point-in-time recovery (PITR) is enabled, a write-ahead log (WAL) continuously records every change made
to the database while the database is running. In the event of a failure, you can replay the WAL to restore the
database to its state at a point in time within the retention period of the database backups.
The WAL logs are archived and are subject to a retention period that you set. The time range for point-in-time
recovery is from the time of your oldest backup to the present. The oldest backup can be an external backup
or a snapshot.
By default, PITR is disabled. If you enable PITR, consider the following points.
n
Because every change to the database is recorded, PITR requires additional storage. Depending on how
large your database is and how many transactions occur during the WAL archive retention time, the
amount of storage needed can be large.
n
PITR has a performance impact on the database and on Data Director as a whole. The impact depends on
the size of the database and the volume of database activity.
Start with a conservative storage allocation. You cannot decrease the storage allocation, but you can increase
it. Monitor the size of the PITR logs until you understand the workload and storage needed, and adjust the
storage amount.
You can specify whether to suspend the database or automatically increase the log retention period if PITR
runs out of space.
Chapter 12 Safeguarding Data
VMware, Inc. 131