Skip to main content
NetApp Backup and Recovery
All cloud providers
  • Amazon Web Services
  • Google Cloud
  • Microsoft Azure
  • All cloud providers

Clone Microsoft SQL Server workloads using NetApp Backup and Recovery

Contributors netapp-mwallis
PDFs

Clone Microsoft SQL Server application data to a VM for development, testing, or protection with NetApp Backup and Recovery. Create clones from instant or existing snapshots of your SQL Server workloads.

Choose between the following types of clones:

  • Instant snapshot and clone: You can create a clone of your Microsoft SQL Server workloads from an instant snapshot, which is a point-in-time copy of the source data that is created from a backup. The clone is stored in an object store in your public or private cloud account. You can use the clone to restore your workloads in case of data loss or corruption.

  • Clone from an existing snapshot: You can choose an existing snapshot from a list of snapshots that are available for the workload. This option is useful if you want to create a clone from a specific point in time. Clone to either primary or secondary storage.

You can accomplish the following protection goals:

  • Create a clone

  • Refresh a clone

  • Split a clone

  • Delete a clone

Required NetApp Console role
Storage viewer, Backup and Recovery super admin, or Backup and Recovery backup admin role. Learn about NetApp Console access roles for all services.

Create a clone

You can create a clone of your Microsoft SQL Server workloads. A clone is a copy of the source data that is created from a backup. The clone is stored in an object store in your public or private cloud account. You can use the clone to restore your workloads in case of data loss or corruption.

You can create a clone from an existing snapshot or from an instant snapshot. An instant snapshot is a point-in-time copy of the source data that is created from a backup. You can use the clone to restore your workloads in case of data loss or corruption.

Steps

  1. From the NetApp Backup and Recovery menu, select Clone.

  2. Select Create new clone.

  3. Select the clone type:

    • Clone and database refresh from existing snapshot: Choose a snapshot and configure clone options.

    • Instant snapshot and clone: Take a snapshot now of the source data and create a clone from that snapshot. This option is useful if you want to create a clone from the latest data in the source workload.

  4. Complete the Database source section:

    • Single clone or bulk clone: Select whether to create a single clone or multiple clones. If you select Bulk clone, you can create multiple clones at once using a protection group that you already created. This option is useful if you want to create multiple clones for different workloads.

    • Source database host, instance, and name: Select the source database host, instance, and name for the clone. The source database is the database from which the clone will be created.

  5. Complete the Database target section:

    • Target database host, instance, and name: Select the target database host, instance, and name for the clone. The target database is the location where the clone will be created.

      Optionally, select Suffix from the target name drop-down list and add a suffix to the cloned database name. If you do not add a suffix, the cloned database name is the same as the source database name.

    • QoS (max throughput): Select the quality of service (QoS) maximum throughput in MBps for the clone. The QoS defines the performance characteristics of the clone, such as the maximum throughput and IOPS.

  6. Complete the Mount section:

    • Auto-assign mount point: Automatically assign a mount point for the clone in the object store.

    • Define mount point path: Enter a mount point for the clone. The mount point is the location where the clone will be mounted in the object store. Select the drive letter, enter the data file path, and enter the log file path.

  7. Select Next.

  8. Select the restore point:

    • Existing snapshots: Select an existing snapshot from the list of snapshots that are available for the workload. This option is useful if you want to create a clone from a specific point in time.

    • Instant snapshot and clone: Select the latest snapshot from the list of snapshots that are available for the workload. This option is useful if you want to create a clone from the latest data in the source workload.

  9. If you chose to create Instant snapshot and clone, choose the clone storage location:

    • Local storage: Select this option to create the clone in the local storage of the ONTAP system. The local storage is the storage that is directly attached to the ONTAP system.

    • Secondary storage: Select this option to create the clone in the secondary storage of the ONTAP system. The secondary storage is the storage that is used for backup and recovery workloads.

  10. Select the destination location for the data and logs.

  11. Select Next.

  12. Complete the Advanced options section.

  13. If you chose Instant snapshot and clone, complete the following options:

    • Clone refresh schedule and expiration: If you chose Instant clone, enter the date when to begin refreshing the clone. The clone schedule defines when the clone will be created.

      • Delete clone if schedule expires: If you want to delete the clone upon the clone expiration date.

      • Refresh clone every: Select how often the clone should be refreshed. You can choose to refresh the clone hourly, daily, weekly, monthly, or quarterly. This option is useful if you want to keep the clone up to date with the source workload.

    • Prescripts and postscripts: Optionally, add scripts to run before and after the clone is created. These scripts can do extra tasks, such as setting up the clone or sending notifications.

    • Notification: Optionally, specify email addresses to receive notifications about the clone creation status along with the Job report. You can also specify a webhook URL to receive notifications about the clone creation status. You can specify whether you want success and failure notifications or only one or the other.

    • Tags: Select labels to help you search for resource groups later and select Apply. For example, if you add "HR" as a tag to multiple resource groups, you can later find all resource groups associated with the "HR" tag.

  14. Select Create.

  15. When the clone is created, you can view it in the Inventory page.

Refresh a clone

You can refresh a clone of your Microsoft SQL Server workloads. Refreshing a clone updates the clone with the latest data from the source workload. This is useful if you want to keep the clone up to date with the source workload.

You have the option to change the database name, use the latest instant snapshot, or refresh from an existing production snapshot.

Steps

  1. From the NetApp Backup and Recovery menu, select Clone.

  2. Select the clone you want to refresh.

  3. Select the Actions icon Actions option > Refresh clone.

  4. Complete the Advanced settings section:

    • Recovery scope: Choose whether to recover all log backups or log backups until a specific point in time. This option is useful if you want to recover the clone to a specific point in time.

    • Clone refresh schedule and expiration: If you chose Instant clone, enter the date when to begin refreshing the clone. The clone schedule defines when the clone will be created.

      • Delete clone if schedule expires: If you want to delete the clone upon the clone expiration date.

      • Refresh clone every: Select how often the clone should be refreshed. You can choose to refresh the clone hourly, daily, weekly, monthly, or quarterly. This option is useful if you want to keep the clone up to date with the source workload.

    • iGroup settings: Select the iGroup for the clone. The iGroup is a logical grouping of initiators that are used to access the clone. You can select an existing iGroup or create a new one. Select the iGroup from the primary or secondary ONTAP storage system.

    • Prescripts and postscripts: Optionally, add scripts to run before and after the clone is created. These scripts can do extra tasks, such as setting up the clone or sending notifications.

    • Notification: Optionally, specify email addresses to receive notifications about the clone creation status along with the Job report. You can also specify a webhook URL to receive notifications about the clone creation status. You can specify whether you want success and failure notifications or only one or the other.

    • Tags: Enter one or more labels that will help you later search for the resource group. For example, if you add "HR" as a tag to multiple resource groups, you can later find all resource groups associated with the HR tag.

  5. In the Refresh confirmation dialog box, to continue, select Refresh.

Skip a clone refresh

Skip a clone refresh to keep the clone unchanged.

Steps

  1. From the NetApp Backup and Recovery menu, select Clone.

  2. Select the clone you want to skip the refresh for.

  3. Select the Actions icon Actions option > Skip refresh.

  4. In the Skip refresh confirmation dialog box, do the following:

    1. To skip only the next refresh schedule, select Only skip the next refresh schedule.

    2. To continue, select Skip.

Split a clone

You can split a clone of your Microsoft SQL Server workloads. Splitting a clone creates a new backup from the clone. The new backup can be used to restore the workloads.

You can choose to split a clone as independent or long-term clones. A wizard shows the list of aggregates that are part of the SVM, their sizes, and where the cloned volume resides. NetApp Backup and Recovery also indicates whether there is enough space to split the clone. After the clone is split, the clone becomes an independent database for protection.

The clone job is not be removed and it can be reused again for other clones.

Steps

  1. From the NetApp Backup and Recovery menu, select Clone.

  2. Select a clone.

  3. Select the Actions icon Actions option > Split clone.

  4. Review the split clone details and select Split.

  5. When the split clone is created, you can view it in the Inventory page.

Delete a clone

You can delete a clone of your Microsoft SQL Server workloads. Deleting a clone removes the clone from the object store and frees up storage space.

If a policy protects the clone, both the clone and its job are deleted.

Steps

  1. From the NetApp Backup and Recovery menu, select Clone.

  2. Select a clone.

  3. Select the Actions icon Actions option > Delete clone.

  4. In the clone Delete confirmation dialog box, review the deletion details.

    1. To delete the cloned resources from SnapCenter even if the clones or their storage is not accessible, select Force delete.

    2. Select Delete.

  5. When the clone is deleted, it is removed from the Inventory page.