Skip to main content
SnapCenter Software 6.0

Clone a IBM Db2 backup

Contributors netapp-nsriram
PDFs

You can use SnapCenter to clone a backup. You can clone from primary or secondary backup.

Before you begin

  • You should have backed up the resources or resource group.

  • You should ensure that the aggregates hosting the volumes should be in the assigned aggregates list of the storage virtual machine (SVM).

  • For pre clone or post clone commands, you should check if the commands exist in the command list available on the plug-in host from the following paths:

    For Windows: C:\Program Files\NetApp\SnapCenter\Snapcenter Plug-in Creator\etc\allowed_commands.config

    For Linux: /opt/NetApp/snapcenter/scc/etc/allowed_commands.config

Note If the commands do not exist in the command list, then the operation will fail.
About this task

  • For information about clone split operation limitations, see ONTAP 9 Logical Storage Management Guide.

  • For ONTAP 9.12.1 and below version, the clones created from the SnapLock Vault Snapshots as part of restore will inherit the SnapLock Vault expiry time. Storage admin should manually cleanup the clones post the SnapLock expiry time.

Steps

  1. In the left navigation pane, click Resources, and then select the appropriate plug-in from the list.

  2. In the Resources page, filter resources from the View drop-down list based on resource type.

    The resources are displayed along with information such as type, host, associated resource groups and policies, and status.

  3. Select the resource or resource group.

    You must select a resource if you select a resource group.

    The resource or resource group topology page is displayed.

  4. From the Manage Copies view, select Backups either from the primary or secondary (mirrored or vaulted) storage systems.

  5. Select the data backup from the table, and then click clone icon.

  6. In the Location page, perform the following actions:

    For this field…​ Do this…​

    Clone server

    Choose a host on which the clone should be created.

    Target Clone Instance

    Enter the target Db2 clone instance ID to clone from the existing backups.

    This is applicable only for ANF storage type resource.

    Target Clone Name

    Enter the name of the clone.

    This is applicable only for Db2 database resource.

    NFS Export IP Address

    Enter IP addresses or the host names on which the cloned volumes will be exported.

    This is applicable only to NFS storage type resource.

    Capacity Pool Max. Throughput (MiB/s)

    Enter the maximum throughput of a capacity pool.

  7. In the Scripts page, perform the following steps:

    Note The scripts are run on the plug-in host.

    1. Enter the commands for pre clone or post clone that should be run before or after the clone operation, respectively.

      • Pre clone command: delete existing databases with the same name

      • Post clone command: verify a database or start a database.

    2. Enter the mount command to mount a file system to a host.

      Mount command for a volume or qtree on a Linux machine:

      Example for NFS:

      mount VSERVER_DATA_IP:%VOLUME_NAME_Clone /mnt
      Note For pre and post commands for quiesce, Snapshot, and unquiesce operations, you should check if the commands exist in the command list available on the plug-in host from the /opt/snapcenter/snapenter/scc/allowed_commands.config path for Linux and C:\Program Files\NetApp\SnapCenter\Snapcenter Plug-in Creator\etc\allowed_commands.config for Windows.

  8. In the Notification page, from the Email preference drop-down list, select the scenarios in which you want to send the emails.

    You must also specify the sender and receiver email addresses, and the subject of the email.

  9. Review the summary, and then click Finish.

  10. Monitor the operation progress by clicking Monitor > Jobs.

After you finish

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.