Back up SQL resources

Contributors netapp-nsriram netapp-asubhas Download PDF of this page

If a resource is not yet part of any resource group, you can back up the resource from the Resources page.

About this task

  • For Windows credentials authentication, you must set up your credential before installing the plug-ins.

  • For SQL Server instance authentication, you must add the credential after installing the plug-ins.

  • For gMSA authentication, you must setup gMSA while registering the host with SnapCenter in the Add Host or Modify Host page to enable and use the gMSA.

  • If the host is added with gMSA and if the gMSA has login and system admin privileges, the gMSA will be used to connect to the SQL instance.

Steps

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

  2. On the Resources page, select Database ,or Instance, or Availability Group from the View drop-down list.

    1. Select the database, or instance, or availability group that you want to back up.

      When you take a backup of an instance, the information about the last backup status or the timestamp of that instance will not be available in the resources page.

      In the topology view, you cannot differentiate whether the backup status, timestamp, or backup is for an instance or a database.

  3. On the Resources page, select the custom name format for Snapshot copy check box, and then enter a custom name format that you want to use for the Snapshot copy name.

    For example, customtext__policy_hostname or resource_hostname. By default, a timestamp is appended to the Snapshot copy name.

  4. On the Policies page, perform the following tasks:

    1. In the Policies section, select one or more policies from the drop-down list.

      You can create a policy by clicking add policy from resourcegroup to start the policy wizard.

      In the Configure schedules for selected policies section, the selected policies are listed.

    2. Click add policy from resourcegroup in the Configure Schedules column for the policy for which you want to configure a schedule.

    3. In the Add schedules for policy policy_name dialog box, configure the schedule, and then click OK.

      Here policy_name is the name of the policy that you have selected.

      The configured schedules are listed in the Applied Schedules column.

    4. Select the Use Microsoft SQL Server scheduler, and then select the scheduler instance from the Scheduler Instance drop-down list that is associated with the scheduling policy.

  5. On the Verification page, perform the following steps:

    1. Select the verification server from the Verification server drop-down list.

      You can select multiple verification servers (local host or remote host).

      Note The verification server version should be equal or above the version of the edition of the SQL server that is hosting the primary database.
    2. Select Load secondary locators to verify backups on secondary to verify your backups on secondary storage system.

    3. Select the policy for which you want to configure your verification schedule, and then click add policy from resourcegroup.

    4. In the Add Verification Schedules policy_name dialog box, perform the following actions:

      If you want to…​ Do this…​

      Run verification after backup

      Select Run Verification after Backup.

      Schedule a verification

      Select Run scheduled verification.

      Note If the verification server does not have a storage connection, the verification operation fails with error: Failed to mount disk.
    5. Click OK.

      The configured schedules are listed in the Applied Schedules column.

  6. On 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. If you want to attach the report of the operation performed on the resource group, select Attach Job Report.

    Note For email notification, you must have specified the SMTP server details either using the GUI or PowerShell command Set-SmSmtpServer.
  7. Review the summary, and then click Finish.

    The database topology page is displayed.

  8. Click Back up Now.

  9. On the Backup page, perform the following steps:

    1. If you have applied multiple policies to the resource, from the Policy drop-down list, select the policy that you want to use for backup.

      If the policy selected for the on-demand backup is associated with a backup schedule, the on-demand backups will be retained based on the retention settings specified for the schedule type.

    2. Select Verify after backup to verify your backup.

    3. Click Backup.

      If the policy selected for the on-demand backup is associated with a backup schedule, the on-demand backups will be retained based on the retention settings specified for the schedule type.

      An implicit resource group is created. You can view this by selecting respective user or group from the User Access page. The implicit resource group type is “Resource”.

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

After you finish

  • In MetroCluster configurations, SnapCenter might not be able to detect a protection relationship after a failover.

  • If you are backing up application data on VMDKs and the Java heap size for the SnapCenter Plug-in for VMware vSphere is not large enough, the backup might fail. To increase the Java heap size, locate the script file /opt/netapp/init_scripts/scvservice. In that script, the do_start method command starts the SnapCenter VMware plug-in service. Update that command to the following: Java -jar -Xmx8192M -Xms4096M.

Find more information