Define a cloning strategy for SQL Server
Defining a cloning strategy enables you to clone your database successfully.
Review the limitations related to clone operations.
Decide the type of clone you require.
Limitations of clone operations
You should be aware of the limitations of clone operations before you clone the databases.
If you are using any version of Oracle from 184.108.40.206 to 220.127.116.11, the clone operation will be in hung state when you run the renamedg command. You can apply the Oracle patch 19544733 to fix this issue.
Cloning of databases from a LUN that is directly attached to a host (for instance, by using Microsoft iSCSI Initiator on a Windows host) to a VMDK or an RDM LUN on the same Windows host, or another Windows host, or vice versa, is not supported.
The root directory of the volume mount point cannot be a shared directory.
If you move a LUN that contains a clone to a new volume, the clone cannot be deleted.
Types of clone operations
You can use SnapCenter to clone either a SQL Server database backup or a production database.
Clone from a database backup
The cloned database can serve as a baseline for developing new applications and help isolate application errors that occur in the production environment. The cloned database can also be used for recovery from soft database errors.
You can use SnapCenter to schedule recurring clone jobs that will occur when the production database is not busy.