Skip to main content

Use a host backup system to protect a LUN on your ONTAP storage system

Contributors netapp-aherbin netapp-aaron-holt netapp-dbagwell
PDFs

You can use a cloned LUN from a snapshot as source data for the host backup system.

Before you begin

A production LUN must exist and be mapped to an igroup that includes the WWPN or initiator node name of the application server. The LUN must also be formatted and accessible to the host

Steps

  1. Save the contents of the host file system buffers to disk.

    You can use the command provided by your host operating system, or you can use SnapDrive for Windows or SnapDrive for UNIX. You can also opt to make this step part of your SAN backup pre-processing script.

  2. Create a snapshot of the production LUN.

    volume snapshot create -vserver <SVM_name> -volume <volume_name> -snapshot <snapshot> -comment <comment> -foreground false

  3. Create a clone of the production LUN.

    volume file clone create -vserver <SMV_name> -volume <volume> -source-path <path> -snapshot-name <snapshot> -destination-path <destination_path>

  4. Create an igroup that includes the WWPN of the backup server.

    lun igroup create -vserver <SVM_name> -igroup <igroup> -protocol <protocol> -ostype <os_type> -initiator <initiator>

  5. Map the LUN clone you created in Step 3 to the backup host.

    lun mapping create -vserver <SVM_name> -volume <volume_name> -lun <lun_name> -igroup <igroup>

    You can opt to make this step part of your SAN backup application's post-processing script.

  6. From the host, discover the new LUN and make the file system available to the host.

    You can opt to make this step part of your SAN backup application's post-processing script.

  7. Back up the data in the LUN clone from the backup host to tape by using your SAN backup application.

  8. Take the LUN clone offline.

    lun modify -vserver <SVM_name> -path <path> -state offline

  9. Remove the LUN clone.

    lun delete -vserver <SVM_name> -volume <volume> -lun <lun_name>

  10. Remove the snapshot.

    volume snapshot delete -vserver <SVM_name> -volume <volume> -snapshot <snapshot>