SnapProtect - Configuration - MySQL iDataAgent

Configuration

The following sections provide the necessary steps required to create and configure the components for a first SnapProtect backup of a MySQL database.

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.

Configuring an Instance
  1. From the CommCell Browser, navigate to Client Computers | <Client>.

    Right-click MySQL, point to All Tasks, and then click New MySQL Server.

  2. In the Server Name box, type the MySQL server name.

  3. In the SA User Name box, type the MySQL administrator user name.

    In the Account Password box, type the account password for the administrator user account.

    In the Confirm Password box, retype the password.

  4. In the Binary Directory box, type the path to the directory where the MySQL application files are stored.

    For example:

    /usr/bin

    Alternatively, click Browse to select the location.

  5. In the Log Data Directory box, type the directory name where the log files are stored.

    For example:

    /var/lib/mysql

    Alternatively, click Browse to select the location.

  6. In the Config File box, type the path to the configuration file.

    For example:

    /etc/my.cnf

    Alternatively, click Browse to select the location.

  7. For Unix, type the path to the socket file.

    Alternatively, click Browse to select the location.

  8. In the Log Backup Storage Policy box, select the storage policy name.

  9. Click OK.
  10. From the CommCell Browser, navigate to Client Computers | <Client> | MySQL | <Instance>.

    Right-click the default Subclient, and then click Properties.

  11. Click the Storage Device tab.

    In the Storage Policy box, select a storage policy.

    Click OK.

    If you do not have Storage Policy created, follow step 14 to create a storage policy.

    From the Subclient Properties dialog box,

    Click the SnapProtect Operations tab.

    Select the SnapProtect option.

    Select a Snap Engine from the available list.

    From the Use Proxy list, select the MediaAgent where SnapProtect and backup copy operations will be performed.

    When performing SnapProtect backup using proxy, ensure that the operating system of the proxy server is either same or higher version than the client computer.

    Click OK.

    For clustered environments, ensure the proxy you want to select is not part of a cluster setup.

    • The SnapProtect backup operation backs up the data of the entire server (entire datadir).
    • For an SnapProtect subclient, the Content tab is disabled, hence the content cannot be discovered or configured.

  12. From the Subclient Properties dialog box,

    Click the Storage Device tab.

    If you do not have Storage Policy created, follow the step given below to create a storage policy.
    1. Click Create Storage Policy.
    2. Follow the prompts displayed in the Storage Policy Wizard. The required options are mentioned below:
      1. Select the Storage Policy type as Data Protection and Archiving and click Next.
      2. Enter the name in the Storage Policy Name box and click Next.
      3. From the Library list, click the name of a disk library to which the primary copy should be associated and then click Next.

        Ensure that you select a library attached to a MediaAgent operating in the current release.

      4. From the MediaAgent list, click the name of a MediaAgent that will be used to create the primary copy and then click Next.
      5. For the device streams and the retention criteria information, click Next to accept default values.
      6. Select Yes to enable deduplication for the primary copy.
      7. From the MediaAgent list, click the name of the MediaAgent that will be used to host the Deduplication database (DDB).

        In the Location box, type the name of the folder in which the DDB must be located or click the Browse to select the folder, and then click Next.

      8. Review the details and click Finish to create the Storage Policy.

 

Skip this section if not using Solaris.

Enable SnapProtect Backups on Solaris Zone

Follow the steps given below to enable SnapProtect backups on each of the non-global zone clients containing the application data.

  1. From the CommCell Console, navigate to Client Computers | <Client>
    • Right-click the client and select Properties.
    • Click Advanced.
  2. In the Advanced Client Properties (General) tab
    • Select the Global zone host name from the drop-down list.
    • Click OK.

      • We support disks on a global zone mounted using loopback File System on a non global zone.
      • This option need not be enabled if you are using a NFS share. This is because when using NFS mount paths, the operations are limited to the non-global zone and does not use the global zone.

  3. Click OK and repeat the above steps on all the non-global zone clients containing the application data.

Skip this section if you already created a snapshot copy, and continue to the next page.

Create a Snapshot Copy

The following section provides step-by-step instructions for creating a Snapshot Copy for a 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. Specify the following to create a Snapshot Copy:
    1. Type the Copy Name in the Copy Name box.
    2. From the Library list, select the name of Library.
    3. From the MediaAgent list, select the name of a MediaAgent.
    4. From the Drive Pool list, select the name of a Drive Pool.
    5. From the Scratch Pool list, select the name of the Scratch Pool.

      Drive Pool and Scratch Pool are not applicable for disk libraries.

    6. Click OK.

The newly created Snapshot Copy can be associated with the subclient from which the snap backup is performed. In this case, the Snapshot Copy acts as the primary copy and therefore will contain only the metadata information associated with the snapshot Backup.