2.7

Table Of Contents
Configuring IP Whitelists Settings for the Clone
You create IP whitelists to specify trusted IP addresses from which the clone accepts connection requests.
Prerequisites
Review information about IP Whitelists. See Chapter 6, “IP Whitelists,” on page 83.
Procedure
1 (Optional) In your organization, click IP Whitelists, and select IP whitelists to use for the clone.
2 (Optional) Click Custom IP Whitelists, and click the plus (+) icon to create IP whitelists for the clone.
What to do next
Review the settings in the Summary panel, or click Back to modify your settings.
Review the Clone Configuration Summary
The Summary panel lets you review the clone configuration before creating the clone.
Procedure
1 In the Summary panel of the Clone Database wizard, review the clone configuration settings, and click
Back to make changes.
2 Click Finish to complete clone setup.
Data Director creates a clone of the current database using the settings you specify.
What to do next
Monitor the creation progress in the task bar on the right, or check the database list for the database group to
verify that the clone was created.
Managing Post-Clone Scripts
Users with the Clone Administration privilege can designate SQL scripts to run on newly cloned databases.
Post-clone scripts automate common tasks such as removing sensitive user data or adding, updating, or
removing tables.
Data Director does not provide out-of-the-box SQL scripts. You develop, test, and maintain post-clone SQL
scripts.
You can associate multiple post-clone scripts with a database, but only one of the database's associated post-
clone scripts can be active. The active (default) post-clone script runs immediately following the clone database
operation. Users with the Clone Administration privilege can choose which post-clone script to run after a
particular clone operation.
Users with the Clone Administration privilege can choose a post-clone script failure action.
n
Delete the cloned database if the post-clone script fails and log an error, or
n
Allow the clone operation to finish and log a warning.
Users who do not have the Clone Administration privilege might not know that a post-clone script is
associated with a database unless an error occurs. These users cannot choose the script to run, and cannot
choose a post-clone script failure action. If the database has a default post-clone script, that script runs
automatically. If the post-clone script fails, the clone is deleted. The user receives a notice that the clone failed
because the post-clone script failed. The user is instructed to check with the database owner for details.
Chapter 10 Cloning Databases
VMware, Inc. 133