SnapManager contains a Clone wizard that provides a convenient interface for performing the following cloning operations:
Cloning the backup of a database is probably the most commonly used cloning feature. The cloned database can serve as a baseline for developing new applications, or to isolate application errors that occur in the production environment. It could also be used for recovery from soft database errors.
Step | Action |
---|---|
1 | In the SnapManager console root, select a server. |
2 | In the Actions pane, click Clone Wizard. |
3 | In the Start page, click Next. |
4 | In the Clone Type page, select Clone Databases from existing Backup Set and click Next. |
5 | In the Backup Selection page, double-click the backup from which you want to create the clone and then click Next. Note: The first time you select a database that resides on a LUN, SnapManager automatically selects all other databases on
the same storage. You can then de-select any databases that you do not
want to be cloned.
|
6 | In the Restore Settings page, do the following and click Next:
For more information about these options, see Types of SnapManager restore operations. |
7 | Click Next. |
8 | SnapManager displays the list of databases to be cloned. By default, SnapManager provides the same name to the clone as the original database. You should rename the cloned database. Click Next. |
9 | In the Restore Settings page, specify the clone database name and click Next. |
10 | In the Clone to Server page, specify the clone server name, choose whether you will use a letter drive or a mount point, and click Next. If you choose a mount point, specify the mount point directory or accept the default. If you specify a mount point, make sure the directory is empty. If there is a database in the directory, after the mount the database will be in an invalid state. For more information about mount point settings, see Database integrity verification options |
11 | In the Verification Settings page, you can choose to do the following:
|
12 | In the Restore Settings page, do any of the following and click Next:
|
13 | In the Clone Life Cycle Management page, you can choose to resynchronize the clone and to automatically delete the clone. For more information about these options, see Understanding cloned database lifecycles. |
14 | In the Restore Settings page, select the state of the database you want after restore and click Next. If you select "Leave the database in read-only mode and available for restoring additional transaction logs, the "Undo file directory" option activates. Note: The default path for the SnapInfo directory
in the "Undo file directory" option is that of the source host.
|
15 | If you want to run a command or script prior to performing the clone operation or after the clone operation finishes, select the "Run Command Settings" option and click Next. Result If you select this option, SnapManager displays the Run Command dialog box. For more information, see Pre-command and post-command script settings. |
16 | Click Finish. Result The Clone Status window is displayed that shows the Clone task list and the Clone Report. |
17 | Click Start Now to start cloning. The operation is performed, and each item in the Clone Task List is checked off as the task is complete. A message appears indicating the successful completion of the cloning operation. |
The clone of a database that is in production is used when a new application or function has to be tested with the latest database content as the final step before the application is taken into production.
A current database that is in production must be selected for cloning. Cloning a current database involves two steps. The first step is creating the backup of the selected database and the second step is to restore the database from the just created backup set. The whole cloning process is managed by the Cloning wizard. Options made visible by the Cloning wizard are similar to options available in the Backup and Restore wizard.
Step | Action |
---|---|
1 | In the SnapManager console root, select a server. |
2 | In the Actions pane, click Clone Wizard. |
3 | In the Start page, click Next. |
4 | In the Clone Type page, select Clone Active Production Datbases and click Next. Note: If you select "Run Through Clone
QuickStart Wizard", the wizard applies default options for most of the settings.
|
5 | In the Database Selection page, double-click the backup from which you want to create the clone and then click Next. Note: The first time you select a database that resides on a LUN, SnapManager automatically selects all other databases on
the same storage. You can then de-select any databases that you do not
want to be cloned.
|
6 | Continue with the next steps, as instructed in the wizard. |
7 | If you want to rename the new database clone's paths based on the name of the new database, select the appropriate check box in the wizard. Note: You cannot specify database paths for a clone.
|
8 | To perform a clone on a SnapMirror destination volume, select the "Clone on available SnapMirror destination volumes" check box. |
9 | If you want to run a command or script prior to performing the clone operation or after the clone operation finishes, select the "Run Command Settings" option. Result: If you select this option, SnapManager displays the Run Command dialog box. For more information, see Pre-command and post-command script settings. |
10 | The wizard takes you to the final option that displays the SnapManager clone task list. Click Start Now to begin the specified tasks. Result: The operation is performed, and each item in the Clone Task List is checked off as the task is complete. A message appears indicating the successful completion of the cloning operation. |
Step | Action | |
---|---|---|
1 | Review the list in Understanding SnapManager Restore. |
|
2 | Ensure that all Windows Explorer windows are closed on the SQL Server computer that is running SnapManager. |
|
3 | Disable any SnapManager operations that are scheduled to run against the SQL Server data you are restoring, including any jobs scheduled on remote management or remote verification servers. |
|
4 | In the SnapManager console root, click the SQL Server you want to perform the restore operation on. |
|
5 | In the Scope pane, click Restore. Result It enables you to navigate the backup sets. |
|
6 | In the Results pane, double-click to select the backup set that you want to clone. |
|
7 | In the Actions pane, click Clone. Result The SnapManager for SQL Server-Clone window appears. |
|
Specify the destination | ||
8 | If you want to clone a database on a server other than the original server, follow these steps:
|
|
9 | If you want to clone a database with a different name, follow these steps:
Note: When you have completed viewing the data,
detach the database and dismount the Snapshot copy.
|
|
Specify the restore type | ||
10 | If... | Then... |
You want to restore to a point-in-time backup |
Note: A point-in-time restore halts the restoration
of transaction log entries that were recorded after the specified date
and time.
|
|
You want to restore to a marked transaction |
|
|
11 | To start the clone operation, click Clone. Result SnapManager begins to clone your databases from the backup you selected. SnapManager Clone completes each task and checks it off the list shown in the Restore Task List view. You can switch back and forth between the task check-off list and the progress report using the Switch buttons on either window. If the clone is successful, the Task window shows the check-off list with the tasks completed, and a dialog box reports that the restore was successful. Note: If Notification
is enabled, email is sent to the specified address. Events are
posted to the Windows event log even if notification is not enabled.
|
|
12 | After all the restore tasks are finished, click OK. Result Your restore is complete and your SQL Server computer comes back online. |
You can delete a cloned database that has outlived its purpose. Deleting the cloned database implies disconnecting the Snapshot copy. To delete cloned databases automatically as part of clone lifecycle management, see "Configuring automatic clone deletion in the Clone wizard" in Understanding cloned database lifecycles.
To delete a cloned database, complete the following steps:
Step | Action |
---|---|
1 | If you have not already done so, start SnapManager for SQL Server by accessing the Windows Start menu, and selecting Program Files > NetApp > SnapManager for SQL Server. Result: The SnapManager for SQL Server console appears. |
2 | In the Scope pane, double-click SnapManager for SQL Server. Result: SnapManager displays the SQL Server database servers running. |
3 | Click the SQL Server database server that you want to configure. Result: SnapManager displays the Status dashboard in the Result pane. |
4 | In the Actions pane, click Clone Wizard. Result: The Clone wizard launches and the Welcome window appears. |
5 | Click Next. Result: SnapManager displays an option for selecting the operation that you want to perform. |
6 | Select the operation you want to perform, and click Next. Result: SnapManager displays the Database to clone window listing the available cloned databases. Select the cloned databases that you want to delete. |
7 | In the Delete clone summary screen, verify the settings selected in the previous steps and click Finish. |
8 | This takes you to the final option that displays the Delete clone task list. Click start now to begin the specified tasks. Result: The operation is performed, and each item in the Clone Task List is checked off as the task is complete. A message appears indicating the successful completion of the delete clone operation. |
9 | Click Close to close the Clone Status dialog box. |
You can also delete clones through Delete Clone in the Actions pane.