Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products

PowerProtect Data Manager 19.10 SAP HANA User Guide

Add a protection policy for SAP HANA database protection

Use the PowerProtect Data Manager UI to add a protection policy to protect the SAP HANA databases.

Prerequisites

  • When you create the protection policies for SAP HANA multinode databases, ensure that all nodes in the multinode environment are powered on. Register each node, one after the other, with an interval of a few minutes between each node. Otherwise the protection might fail.
  • You cannot add assets from a single SAP HANA host in two or more protection policies with the same DD. You must add additional protection policies for a different DD. This requirement pertains to issue PPDM-39456.
  • Before you perform a backup on a weekly or monthly schedule from the protection policy, ensure that the PowerProtect Data Manager time zone is set to the local time zone. If the PowerProtect Data Manager time zone is not set to the local time zone, the weekly or monthly backup still runs but is triggered based on the PowerProtect Data Manager time zone.

The PowerProtect Data Manager Administration and User Guide provides more information about working with storage units, such as the relationships between storage units and policies, and applicable limitations.

If applicable, complete all of the virtual network configuration tasks before you assign any virtual networks to the protection policy. The PowerProtect Data Manager Administration and User Guide provides more information.

NOTE PowerProtect Data Manager does not recognize the SAP HANA System Replication systems. When a replication site is registered to the same PowerProtect Data Manager as a primary site, PowerProtect Data Manager considers the replication site assets to be different assets than the primary site assets. When the primary site is down, PowerProtect Data Manager does not automatically send the backup request to the replication site. In that case, you must manually change the protection policy to use the replication site assets, which are the new primary site assets.

Steps

  1. In the left navigation pane, select Protection > Protection Policies.
    The Protection Policies window appears.
  2. Click Add.
    The Add Policy wizard appears.
  3. On the Type page, specify the new protection policy group fields, and then click Next:
    • Name—Type a descriptive name for the protection policy, for example, SAP HANA Prod Databases.

      NOTE The name that you specify becomes part of the DD MTree entry.
    • Description—Type a short description for the protection policy, for example, SAP HANA Prod Daily Backups.
    • Type—Select SAP HANA.
  4. On the Purpose page, select from the following options to indicate the purpose of the new protection policy group, and then click Next:
    • Centralized Protection—The backup is triggered according to the schedule. PowerProtect Data Manager manages all protection centrally.

    • Set Credentials—Click this option to specify the credentials. The Set Credentials dialog appears.

      NOTE

      Policy-level credentials are mandatory. Credentials that you set at the asset level take precedence over the credentials that you set at the protection policy level. Asset-level credentials have the highest precedence.

      An SAP HANA instance can have one system database SYSTEMDB and multiple tenant databases. The SYSTEMDB database and each tenant database can have its own credentials. A tenant database can be backed up with either its own credentials or the SYSTEMDB credentials. Both the SYSTEMDB database and tenant databases support two types of credentials:

      • SAP HANA Database credentials, for which you must specify the database username and password.
      • SAP HANA Userkey credentials, for which you must specify the user key (created with hdbuserstore command) and OS username of the SAP HANA instance.

      In the Set Credentials dialog, the drop-down list includes all the credentials created for SAP HANA. You can select from the existing credentials or you can create new credentials.

      To create new credentials, click Create New to open the Add Credentials dialog, where you can set the authentication type as either User Name/Password or User Key and then specify the credential values. For a tenant database, you can specify the credentials of either the SYSTEMDB database or the tenant database itself. When you specify the SYSTEMDB credentials for a tenant database, select the System Database check box; otherwise, clear the System Database check box.

    • Self-Service Protection—You trigger the backup manually from the SAP HANA server. PowerProtect Data Manager creates a protection policy and manages extra stages.

    • Exclusion—Select this option when the protection policy contains SAP HANA assets that you want to exclude from data protection operations.
  5. On the Assets page, select the unprotected assets that you want to add to the backup of this protection policy group. The window enables you to filter by asset name to locate the required assets.
    You can also change the assets view to display all assets discovered by PowerProtect Data Manager or a hierarchical view with the assets in a tree structure underneath the application host. For example, a hierarchical view might be helpful when you have added multiple SAP HANA databases, so that you can more easily identify which assets belong to which database.
  6. Click Next.

    If you selected Exclusion on the Purpose page, the Summary page appears. Proceed to the final two steps.

    If you selected Centralized Protection or Self-Service Protection on the Purpose page, the Objectives page appears for creating the protection policy backup configuration.

  7. Complete the required steps for the specified type of protection policy group:
    • For Centralized Protection:

      1. Click Add under Primary Backup.

        The Add Primary Backup dialog appears.

      2. On the Target pane of the Add Primary Backup dialog, specify the following fields:

        • Storage Name—Select a backup destination from the list of existing DD systems, or select Add to add a system and complete the details in the Storage Target dialog.
        • Storage Unit—Select whether this protection policy should use a New storage unit on the selected DD system, or select an existing storage unit from the list. Hover over a storage unit to view the full name and statistics for available capacity and total capacity, for example, testvmpolicy-ppdm-daily-123ab (300 GB/1 TB).

          When you select New, a new storage unit in the format policy name hostname unique identifier is created in the storage system upon policy completion, for example, testvmpolicy-ppdm-daily-123cd.

          NOTE The Space field indicates the total amount of space, and the percentage of available space, on the storage system.
        • Network Interface—Select a network interface from the list, if applicable.
        • Retention Lock—Move the Retention Lock slider to the right to enable retention locking for these backups on the selected system. PowerProtect Data Manager uses Governance mode for retention locking, which means that the lock can be reverted at any time if necessary. Toggling the Retention Lock slider on or off applies to the current backup copy only, and does not impact the retention lock setting for existing backup copies.

      3. On the Schedules pane of the Add Primary Backup dialog:

        1. To schedule the full backup of this protection policy, specify the following fields:

          • Create a Full backup every—Specify how often to create a full backup.
          • Retain for—Specify the retention period for the backup.

            You can extend the retention period for the earliest primary backup copy within the backup schedule by using the Extend Retention feature. For example, your regular schedule for daily backups can use a retention period of 30 days, but you can apply extended retention to keep the full backups taken on Mondays for 10 weeks. Step 8 provides instructions.

            NOTE For database backups, PowerProtect Data Manager chains the dependent backups together. For example, the incremental or transaction log backups are chained to their base full backup. The backups do not expire until the last backup in the chain expires. This ensures that all incremental and transaction log backups are recoverable until they have all expired.
          • Start and End—The activity window. Specify a time of day to start the full backup, and a time of day after which backups cannot be started.

            NOTE Any backups started before the End time occurs continue until completion.
        2. To add an incremental or differential backup, click Add backup and then specify the following fields to schedule the backup of this protection policy:

          NOTE When you select this option, the backup chain is reset.
          • Create a <backup_type> backup every—For <backup_type>, select Incremental or Differential from the drop-down list, and then specify the interval at which the backup job runs within the window that you specify. The backup interval depends on the backup interval of the full backup schedule:

            • If the full backup schedule is hourly or daily, the backup interval of subsequent backup levels can be between 1 and 12 hours or between 1 and 60 minutes.
            • If the full backup schedule is weekly or monthly, the backup interval of subsequent backup levels can be daily, between 1 and 12 hours, or between 1 and 60 minutes.
            NOTE

            An incremental backup backs up the data since the previous full, incremental, or differential backup.

            A differential backup backs up the data since the previous full backup.

            SAP HANA automatically performs the log backups and catalog backups. PowerProtect Data Manager refers to a catalog backup as an AUXILIARY BACKUP TYPE.

          • Retain for—Specify the retention period for the backup.

            CAUTION If you set a shorter retention period for an incremental or differential backup than for the corresponding full backup, then data loss might occur and you might be unable to recover the point-in-time copies.
            NOTE The retention time of the log backup is set to the retention time of the full backup.
          • Start and End—The activity window. Specify a time of day to start the backup, and a time of day after which backups cannot be started.

            NOTE Any backups started before the End time occurs continue until completion.
      4. Click Save to save the changes and return to the Objectives page.

        The Objectives page updates to display the name of the target storage system under Primary Backup.

        NOTE After completing the backup schedule, you can change any schedule details by clicking Edit under Primary Backup.
    • For Self-Service Protection:

      1. Click Add under Primary Retention.

        The Add Primary Retention dialog appears.

      2. On the Target pane of the Add Primary Retention dialog, specify the following fields:

        • Storage Name—Select a backup destination from the list of existing DD systems, or select Add to add a system and complete the details in the Storage Target dialog.
        • Storage Unit—Select whether this protection policy should use a New storage unit on the selected DD system, or select an existing storage unit from the list. Hover over a storage unit to view the full name and statistics for available capacity and total capacity, for example, testvmpolicy-ppdm-daily-123ab (300 GB/1 TB).

          When you select New, a new storage unit in the format policy name hostname unique identifier is created in the storage system upon policy completion, for example, testvmpolicy-ppdm-daily-123cd.

          NOTE The Space field indicates the total amount of space, and the percentage of available space, on the storage system.
        • Network Interface—Select a network interface from the list, if applicable.
        • Retention Lock—Move the Retention Lock slider to the right to enable retention locking for these backups on the selected system. PowerProtect Data Manager uses Governance mode for retention locking, which means that the lock can be reverted at any time if necessary. Toggling the Retention Lock slider on or off applies to the current backup copy only, and does not impact the retention lock setting for existing backup copies.

      3. On the Retention (Self Service) pane of the Add Primary Retention dialog, change any required retention times.

        CAUTION If you set a shorter retention period for an incremental or differential backup than for the corresponding full backup, then data loss might occur and you might be unable to recover the point-in-time copies.

        By default, all backup types have the same retention time. To change the retention times for specific backup types, clear Set the same retention time for all backup types and change the Retain <backup_type> For field values as required.

        NOTE The retention time of the log backup is set to the retention time of the full backup.
      4. Click Save to save the changes and return to the Objectives page.

        The Objectives page updates to display the name of the target storage system under Primary Retention.

        NOTE After completing the backup retention setting, you can change the setting by clicking Edit under Primary Retention.
  8. Optionally, extend the retention period for the earliest primary backup copy within the backup schedule by using the Extend Retention feature:
    Extended retention provides more information.
    1. Click Extend Retention next to Primary Backup or Primary Retention. An entry for Extend Retention is created below Primary Backup or Primary Retention.
    2. Under Extend Retention, click Add. The Add Extended Retention dialog appears.
    3. Extend the retention of a full primary backup copy every—Specify the preferred recurrence for the extended retention backup schedule.
    4. Repeat on—Depending on the frequency of the backup schedule, specify the day of the week, the date of the month, or the date of the year that the extended retention backup will occur.
    5. Retain for—Specify the retention period for the backup. You can retain an extended retention backup for a maximum of 70 years.
    6. Click Save to save your changes and return to the Objectives page.
  9. Optionally, you can extend the retention of a replicated copy:
    1. Click Replicate next to Primary Backup, Primary Retention, or Extend Retention. An entry for Replicate is created to the right of the primary or extended retention backup schedule.
      NOTE PowerProtect Data Manager supports extending the retention of a replicated backup only if the primary backup already has one or more replication stages. Also, for extending the retention of a replicated backup, you can only select the DDs that are used by the replication stages based on the primary stage.

      For example, if there are 6 DDs available (DD001-DD006), and the primary backup is on DD0001:

      • Replicate1 based on the primary backup is replicated to DD002
      • Replicate2 based on the primary backup is replicated to DD003
      • Extended retention backup is backed up to DD001
      • Replicate3 based on the extended retention backup must extend the retention of copies on DD002 or DD003.
    2. Under Replicate, click Add. The Add Replication dialog appears.
      NOTE To enable replication, ensure that you add a remote DD system as the replication location. Add protection storage provides detailed instructions about adding a remote DD system.
    3. Complete the schedule details in the Add Replication dialog.
      CAUTION If you set a shorter retention period for an incremental or differential backup than for the corresponding full backup, then data loss might occur and you might be unable to recover the point-in-time copies.

      By default, all replicated copies have the same retention time. To change the retention times for specific replicated copies, clear Set the same retention time for all replicated copies and click Edit to change the Retain for field values as required.

      NOTE The retention time of the log backup is set to the retention time of the full backup.

      Click Save to save the changes and return to the Objectives page.

      NOTE The schedule frequency can be every day, week, month, or x hours for replication of the primary backup, and every day, week, month, year, or x hours for replication of the extended retention backup. For daily, weekly, and monthly schedules, the numeric value cannot be modified. For hourly, however, you can edit the numeric value. For example, if you set Create a Full backup every 4 hours, you can set a value of anywhere 1 to 12 hours.
  10. Optionally, add a cloud stage for a primary, replication, or extended retention backup schedule for the purpose of moving backups from DD storage to cloud tier:
    1. Click Cloud Tier next to Primary Backup or Extend Retention or, if adding a cloud stage for a replication schedule that you have added, click Cloud Tier under Replicate. An entry for Cloud Tier is created to the right of the primary or extended retention backup schedule, or below the replication schedule.
    2. Under the entry for Cloud Tier, click Add.
      The Add Cloud Tier Backup dialog appears, with summary schedule information for the parent node to indicate whether you are adding this cloud tier stage for the primary backup schedule, the extended retention backup schedule, or the replication schedule.
    3. Complete the schedule details in the Add Cloud Tier Backup dialog, and then click Save to save your changes and return to the Objectives page.
      Add a cloud tier schedule to a protection policy provides detailed instructions for adding a cloud stage for a primary, replication, or extended retention backup schedule.
    NOTE In order to move a backup or replica to the cloud tier, schedules must have a retention time of 14 days or more. Also, discovery of a DD system configured with a cloud unit is required.
  11. Click Next.
    The Options page appears.
  12. On the Options page, select the additional option if required for the policy:
    • Troubleshooting—Select this option to enable the debug logs for troubleshooting purposes.

    When you set the troubleshooting option, ensure that you also set the DEBUG_LEVEL and DPRINTF parameters in the configuration file /usr/sap/<SID>/SYS/global/ppdmconfig/<SID>_<database_name>_data_user.utl, as described in Modify the configuration file parameter settings.

    To enable logging by the ddbmcon program, create the file /opt/dpsapps/dbappagent/tmp/.ddbmcon.debug.

  13. Click Next.
    The Summary page appears.
  14. Review the protection policy group configuration details. You can click Edit next to any completed window's details to change any information. When completed, click Finish.
    An informational message appears to confirm that PowerProtect Data Manager has saved the protection policy. When the new protection policy group is created, PowerProtect Data Manager automatically performs a full backup. Subsequent backups are performed according to the schedule specified.
  15. Click OK to exit the window, or click Go to Jobs to open the Jobs window to monitor the backup of the new protection policy group.

    You can monitor and view detailed information in the Jobs window for both centralized and self-service backups and restores of database application agents.

    NOTE

    The Cancel and Retry options are not available for self-service jobs that are created by database application agents.

    The Jobs window does not display the system database recovery statistics for an MDC configuration or the SDC recovery statistics because the databases are inaccessible during the restores.


Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\