Data Director includes database templates to help administrators streamline resource allocation and standardize database setup and backup setup. Templates help database administrators to quickly provision a database and to select a backup process.

Data Director supports base DB templates, resource templates, and backup templates. Included with Data Director are several optimized templates. When system administrators create an organization, they must assign base DB templates to the organization. Data Director copies the system-defined templates, resource templates, and backup templates to the new organization. Organization administrators can modify only the resource and backup template instances or configure new templates.

You can enable base DB templates, create DB parameter groups associated with base DB templates, and create resource templates and publish them immediately or publish them later. When a template is not published, you can view or manage it, but you cannot use it for provisioning or for other purposes.

System administrators prepare base DB templates. The templates are not visible to organizations until system administrators assign them to the resource bundles of underlying organizations. When the base DB templates become visible, organization administrators must enable them on the resource bundles before database users can provision database from them.

DB parameter groups are associated with base DB templates and contain the database configuration settings used to provision database instances. DB parameter groups specify database configurations that vary from db engines. For vFabric Postgres, this includes parameters such as connection, memory, IO, WAL, checkpoint, logging, and so on. When organization administrators enable a base DB template, they can use the default DB parameter group for the template. They can also create a new DB parameter group or copy from another template, so that database users can choose a parameter group based on actual need when provisioning databases.

Database Resource templates define the computing and storage resources for creating a database, the database parameter group, and the high availability settings.

Resource Settings

When you create a template, you can specify the number of virtual CPUs, memory size, and recommended database storage allocation. You can enable high availability for the template and all corresponding databases. You can also choose the CPU and memory priority, which affects the allocation of resources for all databases in the database group. The levels (high, medium, and low) give certain databases higher priority than other databases in the same database group. The CPU reservation and Memory reservation text boxes let you reserve resources for each database that you create from the template.

If you make changes to a template, databases that are already created from the template are not affected.

You can create different templates for different situations. For example, you can define a resource template for engineering with a small memory size and have high availability disabled. You can define the resource template for QA with a larger memory size and with high availability enabled.

Backup templates define backup settings for databases. You can associate a backup template with a database when you create the database, or you can associate a backup template with a database at a later time. See Select a Database Backup Template.

You can use one of the predefined backup templates for consistency across your organization. See Backup Template Settings.

You can also clone and customize an existing template and associate the custom template with your database. You can customize frequency, start time, and retention for snapshots and for external backup. You can also enable and customize point-in-time recovery, and you can specify a backup label. See Create a Backup Template.