Back up Oracle resources

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

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

Steps

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

  2. In the Resources page, select Database from the View list.

  3. Click filter icon, and then select the host name and the database type to filter the resources.

    You can then click filter icon to close the filter pane.

  4. Select the database that you want to back up.

    The Database-Protect page is displayed.

  5. On the Resource page, perform the following actions:

    For this field…​ Do this…​

    Use custom name format for Snapshot copy

    Select this 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.

    Exclude archive log destinations from backup

    Specify the destinations of the archive log files that you do not want to back up.

  6. On the Policies page, perform the following steps:

    1. Select one or more policies from the drop-down list.

      Note You can also create a policy by clicking add policy from resourcegroup.

      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 window, configure the schedule, and then click OK.

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

      The configured schedules are listed in the Applied Schedules column.

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

    1. Click Load locators to load the SnapMirror or SnapVault volumes to perform verification on secondary storage.

    2. Click add policy from resourcegroup in the Configure Schedules column to configure the verification schedule for all of the schedule types of the policy.

    3. 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, and then select the schedule type from the drop-down list.

      Note In a Flex ASM setup, you cannot perform verification operation on Leaf nodes if the cardinality is less than the number nodes in the RAC cluster.
    4. Select Verify on secondary location to verify your backups on secondary storage.

    5. Click OK.

      The configured verification schedules are listed in the Applied Schedules column.

  8. 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 backup operation performed on the resource, and then select Attach Job Report.

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

    The database topology page is displayed.

  10. Click Back up Now.

  11. 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. Click Backup.

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

After you finish

  • In AIX setup, you can use the lkdev command to lock and the rendev command to rename the disks on which the database that was backed up was residing.

    Locking or renaming of devices will not affect the restore operation when you restore using that backup.

  • If the backup operation fails because database query execution time exceeded the timeout value, you should change the value of the ORACLE_SQL_QUERY_TIMEOUT and ORACLE_PLUGIN_SQL_QUERY_TIMEOUT parameters by running the Set-SmConfigSettings cmdlet:

    After modifying the value of the parameters, restart the SnapCenter Plug-in Loader (SPL) service by running the following command /opt/NetApp/snapcenter/spl/bin/spl restart

  • If the file is not accessible and the mount point is unavailable during the verification process, the operation might fail with error code DBV-00100 specified file. You should modify the values of the VERIFICATION_DELAY and VERIFICATION_RETRY_COUNT parameters in sco.properties.

    After modifying the value of the parameters, restart the SnapCenter Plug-in Loader (SPL) service by running the following command /opt/NetApp/snapcenter/spl/bin/spl restart

  • 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