Concepts
Clone workflow
Suggest changes
-
PDF of this doc site
-
Protect Microsoft SQL Server databases
-
Protect SAP HANA databases
-
Protect IBM Db2
-
Protect PostgreSQL
-
Collection of separate PDF docs
Creating your file...
The clone workflow includes performing the clone operation and monitoring the operation.
-
You can clone on the source IBM Db2 server.
-
You might clone resource backups for the following reasons:
-
To test functionality that has to be implemented using the current resource structure and content during application development cycles
-
For data extraction and manipulation tools when populating data warehouses
-
To recover data that was mistakenly deleted or changed
-
The following workflow shows the sequence in which you must perform the clone operation:
You can also use PowerShell cmdlets manually or in scripts to perform backup, restore, and clone operations. The SnapCenter cmdlet help and the cmdlet reference information contain detailed information about PowerShell cmdlets.
After cloning the automatically discovered Db2 resources, the cloned resource is marked as manual resource. Click Refresh resources to recover the cloned Db2 resource. When you delete the clone, the storage and the host also gets cleaned up.
If you do not refresh the resources after the clone operation and attempt to delete the clone, the storage and the host will not be cleaned up. You must delete the entries manually in fstab.