Cloning a Database

When cloning a database, you can create an identical database cluster. Cloning is equivalent to PITR to latest available time.

Any service data residing in the original database VM is also cloned. You can also choose to change database settings. The cloned database VM is owned by the user who clones the original database VM. The owner can perform typical database management operations on the cloned database. The owner also recieves email notifications for status change of the cloned database VM and failure of operations on the cloned database VM.

Prerequisites

• The version of the ESXi host of the Primary database should not be later than the version of the ESXi host of the cloned database VM.

Procedure

Perform the following procedure to clone a database:

1. Select Databases from the left navigation pane.

   This action displays the Databases view, a table that lists the provisioned database VMs.

2. Examine the database VMs listed in the table, identify the database VM that you wish to clone, and navigate to that table row.

3. Click in the Actions column, and select Clone from the pop-up menu.

   The Clone Database form displays.

4. Set the following properties for the new database VM:

   Property Name	Value
   Database Version	Use the dropdown menu to select from the available template versions of the database. Note: You can only increase the version of the database, but you cannot decrease it.
   Instance Name	Enter a unique name for the database cluster.
   Replica Mode	Configure the number of nodes. Switch between the following: Single Server - One node with no replicas. You can use vSphere HA. Single vSphere Cluster - Multiple nodes co-located on a single vSphere cluster providing non-disruptive upgrades. You can select a three-node or five-node topology.
   Topology	Specify configuration for the database nodes depending on the replica mode you selected.

5. Click CLONE NOW or NEXT is you want to continue changing parameters. Set the following items on the Infrastructure pane.

   Property Name	Value
   Infrastructure Policy	Select an infrastructure policy from the list of preconfigured policies.
   Storage Policy	From the list of storage policies associated with the infrastructure policy, select a storage policy for the database VM storage placement.
   VM Class	Depending on your database resource requirements for vCPU and memory, select an appropriate VM class.
   Disk Size	Set the disk size.

6. Click NEXT to continue and to expand the Backup and Maintenance pane.

   Set the following properties for the new database VM

   Property Name	Value
   Enable Backups	Use the slider to opt-in for automated backups. If you opt-in for automated backups, you have to set Backup Retention.
   Backup Retention	Specify the number of days to retain a backup on the selected storage location.
   Daily Backup Time	Use the dropdown menus to select the time of day to backup the database.
   Backup Schedule	Specify if you want to use default or customized backup schedule: Use Default Backup Schedule - Use the schedule provided by the system and set the start time. Add Customized Backup Schedule - Specify whether you want the backup to be full or incremental. Set up the start time and the frequency of the backup.
   Enable Maintenance Window	Use the slider to opt-in for automatic upgrade to the next minor versions during the maintenance window that you configure.
   Day of the Week	Use the dropdown menu to select the maintenance window's day of the week.
   Start Time	Use the dropdown menus to select the time of day in which to start the maintenance window.
   New Duration	Use the dropdown menu to specify the duration of the maintenance window (hours).

7. Click CLONE DATABASE.

   VMware Data Services Manager initiates a management operation of type CREATE DATABASE CLUSTER FROM EXISTING CLUSTER, and adds an entry for the new cloned VM in the Databases view table.

   Note: Cloning a database can take some time.

8. Monitor the progress of the operation in the Operations tab or in the Operations view.

   When the operation completes, the new cloned database displays the READY or ERROR status.