SnapProtect – NetApp - MySQL iDataAgent

Overview Deployment - Unix Configuration Select Storage Array
Backup Vault or Mirror Copy Backup Copy Restore  

Prerequisites

Array License

Verify that the following licenses are installed:

  • SnapRestore license for revert operations (LUNs and NFS shares)
  • FlexClone license for mount operations on NAS, NFS, and CIFS data. For NFS and CIFS, the mount operation is done as part of backup and restore jobs.
  • FCP, iSCSI, CIFS, NFS licenses for features such as Fibre Channel Protocol, iSCSI protocol, CIFS file sharing, and NFS File Sharing. Use the appropriate license for the specific data types
  • HTTP/HTTPS licenses on the NetApp file server to allow communication
  • If you use SnapVault or SnapMirror, install the additional licenses:
    • NetApp Snap Management license
    • SnapMirror Primary and Secondary Licenses for disaster recovery operations
    • SnapVault Primary and Secondary Licenses for backup and recovery operations
  • For OnCommand Unified Manager, install the following licenses:
    • Operations Manager
    • Provisioning Manager
    • Protection Manager

Configure the iSCSI Initiator on the client and proxy computers to access the storage device. For Virtual Server Agent, configure the iSCSI Initiator if the agent is configured on a separate physical server and uses iSCSI data stores. There is no need to configure the iSCSI Initiator if the agent uses NFS data stores.

Array Software

  • To create SnapVault and SnapMirror copies of 7-Mode snapshots, OnCommand Unified Manager server running OnCommand Unified Manager 5.0, 5.1, or 5.2 is required.

    OnCommand Unified Manager 5.1 or 5.2 is required for ONTAP 8.1.

    To create SnapVault and SnapMirror copies of clustered Data ONTAP snapshot copies, use OnCommand Unified Manager 6.0, 6.1, 6.2, 6.3P1, 6.4P1, or 7.0. Refer to NetApp Interoperability Matrix Tool (IMT) to verify the latest support for your product configuration.

Set Up SnapVault or SnapMirror

Skip this section if you are not using SnapVault or SnapMirror.

Perform the following steps to set up the SnapVault or SnapMirror.

  1. On your source file server, use the license command to check that the sv_ontap_pri and sv_ontap_sec licenses are available for the primary and secondary file servers respectively.
  2. Enable SnapVault on the primary and secondary file servers as shown below:

    options snapvault.enable on

  3. On the primary file server, set the access permissions for the secondary file servers to transfer data from the primary as shown in the example below:

    options snapvault.access host=secondary_filer1, secondary_filer2

  4. On the secondary file server, set the access permissions for the primary file servers to restore data from the secondary as shown in the example below:

    options snapvault.access host=primary_filer1, primary_filer2

Once you have the environment setup for using SnapVault and SnapMirror, you need to configure the following before performing a SnapVault or SnapMirror operation.

If you plan to use SnapVault or SnapMirror, use the appropriate storage policy based on the type of snapshot, such as NetApp 7-Mode and Cluster-Mode snapshots. For NetApp 7-Mode snapshots, use storage policies associated with OnCommand Unified Manager 5.0, 5.1, or 5.2. For NetApp Cluster-Mode snapshots, use storage policies associated with OnCommand Unified Manager 6.0, 6.1, 6.2 6.3P1, 6.4P1, or 7.0.

Most capabilities of data ONTAP 7-Mode apply, however cascaded replication of primary to snapvault to snapmirror on a single policy is not supported.

Create Storage Policy

Use the following steps to create a storage policy.

  1. From the CommCell Browser, navigate to Policies.

    Right-click the Storage Policies node and click New Storage Policy.

  2. Click Next.

  3. Specify the name of the Storage Policy in the Storage Policy Name box.

    Select Provide the OnCommand Unified Manager Server Information.

    Click Next.

  4. In the Library list, select the default library to which the Primary Copy should be associated.

    It is recommended that the selected disk library uses a LUN from the File server.

    Click Next.

  5. Select a MediaAgent from the MediaAgent list.

    Click Next.

  6. Click Next.

  7. Provide the OnCommand Unified Manager server information.
    • If a OnCommand Unified Manager server exists, click Select to choose from the drop-down list.
    • If you want to add a new OnCommand Unified Manager Server, click Add and provide the OnCommand Unified Manager server information.

    Click Next.

  8. Click Finish.

    The new Storage Policy creates the following:

    • Primary Snap Copy, used for local snapshot storage
    • Primary Classic Copy, used for optional data movement to tape, disk or cloud.

Create a Secondary Snapshot Copy

After the Storage Policy is created along with the Primary Snap Copy, the Secondary Snap Copy must be created on the new Storage Policy.

  1. From the CommCell Browser, navigate to Policies | Storage Policies.

    Right-click the <Storage Policy> and click All Tasks | Create New Snapshot Copy.

  2. Type the Copy Name..

    Select the Library and MediaAgent from the drop-down list.

    Click Vault/Backup or Mirror protection type based on your needs.

    By default, if you click Vault/Backup, the Selective Copy option under Copy Information will become selected. You may clear the Selective Copy option or if you plan to use the selective copy, see the information on how to configure the selective copy for SnapVault on Configure Selective Copy for SnapVault.

    It is recommended that the selected disk library uses a CIFS or NFS share or a LUN on the File server.

  3. Click the Copy Policy tab.

    Depending on the topology you want to set up, click Specify Source for Auxiliary Copy and select the source copy.

    Copies can be created for the topologies listed in the following table:

    Topology

    Source Copy

    Primary-Mirror Primary
    Primary-Mirror-Vault Mirror
    Primary-Vault Primary
    Primary-Vault-Mirror Vault
    Primary-Mirror-Mirror Mirror

  4. Click the Provisioning tab.

    Click Refresh to display the entities.

    Select the Provisioning Policy from the drop-down list.

    OnCommand Manager Unified Manager has three pre-defined provisioning policies for SnapProtect.

    Such policies will be picked up automatically by SnapProtect and will be displayed in the Provisioning tab of the Snap Copy Properties dialog box.

    Policy

    Definition

    SnapProtect_RAID-DP Has RAID-DP (double disk failure) enabled which protects against double disk failures

    To use a provisioning policy from the OCUM server, prefix the provisioning policy name with the string "SnapProtect_".

    Select the Resource Pools available from the list.

    vFiler option will be shown on the provisioning tab only if the storage policy is associate with OnCommand Unified Manager 5.x.

    When Select vFiler option is selected, all vFilers on the selected resource pools will be displayed in the drop-down list. Resource pool members should be complete filers and not aggregates.

    Once a vFiler is selected, you cannot change your selection. The data will continue to be replicated to the vFiler volume even though this value can be edited in the drop-down list.

    New volumes on this storage policy copy will be provisioned under selected vFiler.

    Click OK to create the secondary snapshot copy.

  5. If you are using a Primary-Mirror-Vault (P-M-V) or Primary-Vault (P-V) topology on ONTAP version higher than 7.3.5 (except ONTAP 8.0 and 8.0.1), perform the following steps:
    • Connect to the storage device associated with the source copy of your topology. You can use SSH or Telnet network protocols to access the storage device.
    • From the command prompt, type the following:

      options snapvault.snapshot_for_dr_backup named_snapshot_only

    • Close the command prompt window.

    It is recommended that you perform this operation on all nodes in the P-M-V topology.

During snap copy creation, if you select the copy to be vault, the selective copy will be checked by default and the default selection rule will be "All Fulls".

If you do not want the vault copy to be selective, please uncheck the selective copy option during creation and proceed.

When the selective copy option is checked at the time of vault copy creation, mirror copy will be greyed out.

If you need to switch to mirror copy at the time of creation, uncheck selective copy and change the copy to mirror.

Once a snap copy is created as vault, you cannot change it to mirror and vice-versa.

Similarly, once a selective vault copy is selected, you cannot change it to non selective vault copy and vice-versa.

Configure Backup Copy

Follow the steps given below to configure Backup Copy for moving snapshots to media.

  1. From the CommCell Browser, navigate to Policies | Storage Policies.

    Right-click the <Storage Policy> and click Properties.

  2. Click the Snapshot tab.

    Select Enable Backup Copy checkbox to enable movement of snapshots to media.

    Click Yes in the Confirm dialog box.

  3. Select Specify Source for Backup Copy.

    From the drop-down list, select the source copy to be used for performing the backup copy operation.

    Click OK.

Set Up the Array Information

Only one array management entry should be specified for each NetApp array. Specify the array name or IP that will be used for sending snapshot management commands. If an array has multiple interfaces, a list of corresponding names is maintained for each array, so that the proper array management entry is always used.

The following section provides step-by-step instructions for setting up the array information.

  1. From the CommCell Browser, click the Storage tab and then click the Array Management icon.
  2. In the Array Management dialog box, click Add.
  1. Select NetApp from the Snap Vendor list.

    Specify the name of the primary file server in the Name field.

    The name of primary file server may be different in the OnCommand Unified Manager, CommServe, MediaAgent and other entities, but it should resolve to the same IP address. However, if you plan to create a Vault/Mirror copy, ensure the IP address of the primary file server resolves to the primary IP of the network interface and not to an alias.

    You can provide the host name, fully qualified domain name or TCP/IP address of the file server.

    Click Change and enter the access information of a user with administrative privileges in the Username and Password fields in Enter User Name and Password dialog box.

    • The user must have privileges to manage array artifacts like snapshots, volumes, LUNs, CIFS shares, NFS exports, and initiator groups.
    • For NetApp C-Mode, the user must have ONTAP and SSH capabilities.

    Select File Server, then click Primary checkbox for the array type.

    Use the Description field to enter a description about the entity. This description can include information about the entity's content, cautionary notes, etc.

  2. Click the Snap Configuration tab and configure the following:

    In the Initiator Group Name box, specify the name of the initiator group to be configured on the client computer and proxy computer to access the array.

    In the Mount Retry Count box, type or select the number of retry attempts for a mount operation.

    In the Mount Retry Interval (in seconds) box, type or select the time interval after which the next mount operation will be attempted.

    Select Skip busy LUN check to enable skipping busy LUN on the array. When enabled snap job will not go into pending if there is a mounted snapshot in the volume.

    Click OK.

  3. Click Add again to enter the information for the secondary array.

    Specify the name of the secondary file server in the Name field.

    The name of secondary file server may be different in the OnCommand Unified Manager, CommServe, MediaAgent and other entities, but it should resolve to the same IP address.

    Select File Server for the array type.

    Use the Description field to enter a description about the entity. This description can include information about the entity's content, cautionary notes, etc.

    Click OK.