2.7

Table Of Contents
Virtual Disk Provisioning
Types
Data Director supports the following disk provisioning profiles:
Eager Zeroed
Thick Provision
A type of thick virtual disk that supports clustering
features such as Fault Tolerance. Space required for
the virtual disk is allocated at creation time. In contrast
to the flat format, the data remaining on the physical
device is zeroed out when the virtual disk is created.
Eager Zeroed Thick Provision disks provide superior
performance for applications supporting I/O intensive
operations.
Thin Provision
Use this format to save storage space. For the thin disk,
you provision as much datastore space as the disk
would require based on the value that you enter for
the disk size. However, the thin disk starts small and
at first, uses only as much datastore space as the disk
needs for its initial operations.
If the thin disk needs additional space, it can grow to
its maximum capacity and occupy the entire datastore
space provisioned to it. Also, you can manually
convert the thin disk into a thick disk.
Minimum Storage Size
You can specify a minimum storage size to use for each disk that you create.
Carefully consider how much storage space you have available, and how much
you will need for your data and log usage.
NOTE Determining log disk storage requirements depends upon several
factors. Refer to your database vendors documentation for information on log
storage capacity planning for your particular database.
Table 4-1. Minimum Storage Size for Data Disks
Database Minimum Size of Data Disk
MySQL 1 GB
Oracle 2 GB
SQL Server 1 GB
vPostgres 1 GB
Build an Oracle, SQL Server, or Empty Base DBVM
You can create a base DBVM and install the operating system and database software required to provision
databases.
You can create an Oracle, SQL Server, or empty base DBVM which you can then use to create base DB templates.
You can create a base DBVM using either Oracle or SQL Server databases with the standard operating systems
supported by Data Director as guest operating systems within a DBVM.
To build a base DBVM with a customized operating system (using a specific set of patches and system
configurations configured for use in your IT environment), you must create an empty base DBVM. The empty
base DBVM contains the structure for installing an operating system and database software combination not
provided by preconfigured base DBVMs. See “Build a Base DBVM with a Custom Operating System,” on
page 63.
VMware vFabric Data Director Administrator and User Guide
50 VMware, Inc.