Cloning SAP HANA database backups using PowerShell cmdlets

The clone workflow includes planning, performing the clone operation, and monitoring the operation.

Before you begin

You must have prepared the PowerShell environment to execute the PowerShell cmdlets.

About this task

The SnapCenter cmdlet help and the cmdlet reference information contain more information about PowerShell cmdlets.

SnapCenter Software 4.0 Windows Cmdlet Reference Guide

Steps

  1. Initiate a connection session with the SnapCenter Server for a specified user by using the Open-SmConnection cmdlet.
    Example
    Open-SmConnection  -SMSbaseurl  https:\\snapctr.demo.netapp.com:8146/
    
  2. Retrieve the backups to perform the clone operation by using the Get-SmBackup cmdlet.
    Example

    This example shows that two backups are available for cloning:

     C:\PS> Get-SmBackup
           
            BackupId                      BackupName                    BackupTime                    BackupType
            --------                      ----------                    ----------                    ----------
             1                     Payroll Dataset_vise-f6_08... 8/4/2015 11:02:32 AM          Full Backup
             2                     Payroll Dataset_vise-f6_08... 8/4/2015 11:23:17 AM
    
    
  3. Initiate a clone operation from an existing backup and specify the NFS export IP addresses on which the cloned volumes are exported.
    Example

    This example shows that the backup to be cloned has an NFSExportIPs address of 10.232.206.169:

    New-SmClone -AppPluginCode hana -BackupName scsccore1_sccore_test_com_hana_H73_scsccore1_06-07-2017_02.54.29.3817 -Resources @{"Host"="scsccore1.sccore.test.com";"Uid"="H73"}  -CloneToInstance shivscc4.sccore.test.com -Suffix '_c12' -mountcommand 'mount 10.232.206.169:%hana73data_Clone /hana83data' -preclonecreatecommands '/home/scripts/scpre_clone.sh' -postclonecreatecommands '/home/scripts/scpost_clone.sh'
    Note: If NFSExportIPs is not specified, the default is exported to the clone target host.
  4. Verify that the backups were cloned successfully by using the Get-SmCloneReport cmdlet to view the clone job details.
    You can view details such as clone ID, start date and time, end date and time.
    Example
    PS C:\> Get-SmCloneReport -JobId 186
    
        SmCloneId           : 1
        SmJobId             : 186
        StartDateTime       : 8/3/2015 2:43:02 PM
        EndDateTime         : 8/3/2015 2:44:08 PM
        Duration            : 00:01:06.6760000
        Status              : Completed
        ProtectionGroupName : Draper
        SmProtectionGroupId : 4
        PolicyName          : OnDemand_Clone
        SmPolicyId          : 4
        BackupPolicyName    : OnDemand_Full_Log
        SmBackupPolicyId    : 1
        CloneHostName       : SCSPR0054212005.mycompany.com
        CloneHostId         : 4
        CloneName           : Draper__clone__08-03-2015_14.43.53
        SourceResources     : {Don, Betty, Bobby, Sally}
        ClonedResources     : {Don_DRAPER, Betty_DRAPER, Bobby_DRAPER, Sally_DRAPER}
        SmJobError          :