In Data Director, database lifecycle includes preparing base database templates from database virtual machines, database creation and resource allocation, managing the database schema and data, performing backup and recovery tasks, ingesting databases into Data Director, and decommissioning databases. System administrators, database administrators, and application developers perform the database lifecycle tasks.

For information about backup and recovery tasks, see Safeguarding Data.

Prepare base database templates

Base database templates (base DB templates) reside at the Data Director system level. They provide the virtual hardware, operating system, database software, and other required files and configuration information needed to create databases in Data Director. System administrators create database virtual machines (DBVMs) at the system level, convert them to base DB templates, assign the base DB templates to one or more resource bundles, and assign the resource bundles to organizations. Organization administrators must enable at least one base database template in their organization resource bundle(s) to allow organization users to create databases. See Building DBVMs and Base DB Templates.

Create databases

Create and allocate resources to a new database using base database templates, database resource templates, and parameter groups. Database resource templates specify resource limits. Parameter groups specify sets of database parameters, such as maximum connections allowed, encoding, and checkpoint timeout. Application developers can perform do-it-yourself database creation using the predefined base database templates, resource templates, and parameter groups. See Requirements for Creating Databases.

Administrators can grant permissions to their users to create databases from resource templates, but not allow users to modify the resource templates or change the default resource allocations. This restriction provides resource limit enforcement and allows administrators to retain control of resource and security policies. See Managing Database Templates.

Manage schema

Manage vFabric Postgres database schemas and add data. You can create tables, designate primary and foreign keys and indexes, and create views, sequences, triggers, and other database entities.


Data Director supports managing schemas for vFabric Postgres databases only.

Backup and restore

Safeguard your data by taking regular backups and testing your backups. See Safeguarding Data.

Update database

Choose the database version to update within Data Director to meet IT policies or application requirements.


Ensure access to consistent, yet isolated databases by cloning the database for specific purposes such as development or quality assurance. See Cloning Databases.

Scale up

Dynamically increase the database size as required during the development, test, and production phases.

Monitor performance and usage

Use the Data Director user interface to monitor resource usages, recent alarms, tasks and events. See Monitoring the Data Director Environment.

Stop and restart the database

Stop and restart, for example, to perform maintenance tasks.

Decommission the database

Disable and then delete databases. Free up the resources when they are no longer needed.

Add databases to the organization catalog

Add any Data Director database to the organization catalog. Organization users can create databases using the catalog databases when they need a database with known characteristics and preloaded data, for example, for testing SQL scripts or usage scenarios.

Ingest external databases into Data Director

Ingest a backup of an external database into Data Director. You can ingest a one time clone, or you can refresh an existing database from an external database. Ingested databases are accessible only from the organization database catalog and can be refreshed only by an additional backup from the source database. You cannot use ingested databases directly in Data Director.

Perform common operations and schedule tasks in batches

Perform common tasks and schedule database operations to run on multiple databases in a database group, for example, run restart, stop, repair, enable, and add whitelists tasks, and schedule upgrade and backup operations on multiple databases.

Every database requires an administrator account that can perform all schema management operations. This account is specific to the database and cannot log in to Data Director. You can add database owner accounts after database creation. Data Director database users must log in with their database-specific credentials to view the database, its entities, and its data or to perform database management tasks.

Database administrators and application developers can manage databases only if they have appropriate permissions and roles granted to them by the organization administrator. The administrator must grant permissions and roles on the database group or on the database. These permissions and roles apply only within the organization in which they are granted.