Enabling the SAP HANA Agent

21

Table 6. Parameters that you can modify for SAP HANA operations (continued)
FALSE (default) = The software does not generate debug messages. TRUE = The software writes debug messages in the debug log. The DEBUG_LEVEL setting determines the level of the
debug messages.
Parameter: PARALLELISM
Specifies the parallelism value for self-service SAP HANA backups. The parallelism value controls the number of parallel streams that the SAP HANA agent uses to write the backup data to DD.
NOTE: For centralized backups, you must set the parallelism value in the PowerProtect Data Manager UI as described in Enable multi-stream backups for SAP HANA protection policy.
Valid values:
1 (default) = The software does not use parallel streams for the self-service backups. 2 or greater = The software uses the specified number of parallel streams for the self-service backups.
Enable the discovery of database application agent backups
To enable the PowerProtect Data Manager to discover the SAP HANA backups that were performed by the database application agent, you must update a specific configuration file.
About this task Restore an SAP HANA application host provides more details about the recovery of SAP HANA backups that were performed by the database application agent. To enable the discovery of the database application agent backups, perform the following steps.
Steps 1. In the PowerProtect Data Manager UI, ensure that the assets are visible. 2. In the directory /opt/dpsapps/dbappagent/saphana/brownfield, rename the file
sap_hana_brownfield_ddbda.utl as brownfield.utl. 3. Open the file /opt/dpsapps/dbappagent/saphana/brownfield/brownfield.utl in an editor and complete the
following settings: Set the DDBOOST_USER parameter to the username of the DD Boost user configured on the DD system. Set the DEVICE_HOST parameter to the hostname (as the fully qualified domain name) of the DD system where the
backups are stored. Set the DEVICE_PATH parameter to the top-level directory name of the storage unit (without the /data/col1 prefix)
on the DD system. Set the DISCOVERY_DAYS parameter to the number of days to be used for discovery. The PowerProtect Data Manager
will discover the database application agent backups that were performed within the specified past number of days. Set the RETENTION_DAYS parameter to the number of days that the PowerProtect Data Manager will keep the
database application agent backups after discovery. 4. Save the file /opt/dpsapps/dbappagent/saphana/brownfield/brownfield.utl.
NOTE: Ensure that the RETENTION_DAYS parameter is set correctly. When RETENTION_DAYS is set to 0 or is unspecified, all copies from the database application agent that are discovered in PowerProtect Data Manager will have the retention value set to 30 days from the backup creation date. For copies from the database application agent that PowerProtect Data Manager discovers, the retention value is set based on the copy creation date, not on the date when the copies are discovered.
Results The PowerProtect Data Manager will discover the database application agent backups during the subsequent backup discovery operations.

22

Enabling the SAP HANA Agent

Configure support of SAP HANA 2.0
The SAP HANA 2.0 user documentation provides a complete list of all the backup and recovery features, including details about how to enable and configure the features. The following list highlights several of the features: SAP HANA 2.0 SPS 00 supports data encryption in the persistence layer for both data and log volumes. SAP HANA volume
encryption can impact the deduplication rates on the DD systems. SAP HANA 2.0 SPS 00 supports the user-configurable interval mode for log backups. The interval mode enables the creation
of log backups after the service-specific timeout is reached, instead of when the log segment becomes full. A log backup can include multiple log segments. The interval mode setting limits the number of log backups in high-transaction databases, which reduces the impact on the databases. You can configure the interval mode by setting the following parameter in the SAP HANA global.ini file:
log_backup_interval_mode = service
Configure automatic backups of SAP HANA logs
The SAP HANA database server automatically performs periodic backups of the redo logs for a database. PowerProtect Data Manager does not perform any log or catalog backups. You cannot perform the log backups with any backup commands.
NOTE: Since the log backups and catalog backups are automatically triggered by SAP HANA, these backups continue to be performed even when the PowerProtect Data Manager protection policy is disabled.
You can use the SAP HANA Studio GUI to configure the frequency of automatic log backups and whether the Backint interface is used for the log backups. To configure the automatic backups of SAP HANA redo logs, complete the required settings in SAP HANA Studio. On the Configuration tab of the Backup editor, complete the settings in the Log Backup Settings group box: Select Enable Automatic Log Backup. For Destination Type, select Backint. For Backup Interval, specify the log backup interval. Type the numeric value in the text box, and then select the unit of
time, such as Minutes, from the menu.
NOTE: The recommended log backup interval is 30 minutes.
The following figure shows a configuration example in SAP HANA Studio.

Figure 1. Configuring automatic log backups in SAP HANA Studio

Enabling the SAP HANA Agent

23

Configure the SAP HANA parallel backup setting
The streams usage by the storage unit during an SAP HANA backup varies, depending on the number and type of parallel operations that are performed at a given time. You can set the SAP HANA parameter parallel_data_backup_backint_channels to specify the number of channels to use for the backup.
The SAP HANA agent requires one DD stream for each backed-up pipe. For example, if an SAP HANA scale-out system has 12 running services, then 12 streams are required to back up the data. Starting with SAP HANA SPS 09, each service can also back up multiple logs for each backup, as controlled by the database parameter max_log_backup_group_size.
For a multistream backup with SAP HANA SPS 11 or later, the SAP HANA agent can use multiple SAP HANA channels to write the backup data for each service. The SAP HANA agent uses a separate channel to write each stream of data to the DD system. To specify the number of channels to use for the backup, up to a maximum of 32 channels, you can set the SAP HANA parameter parallel_data_backup_backint_channels. SAP HANA opens the corresponding number of pipe files for the backup, and the agent saves each stream as a separate save set.
For example, if the parallel_data_backup_backint_channels parameter is set to 12 on the SAP HANA database server, then 12 streams are used for the backup, which produces 12 save sets.
A restore uses the same number of streams as the backup, and ignores the parallel_data_backup_backint_channels parameter setting.
During an SAP HANA backup or restore, the storage unit typically uses the following number of streams:
Number of services x max_log_backup_group_size
Due to the design of SAP HANA log backups, an SAP HANA system cannot wait until a stream is available because waiting can negatively affect the database performance.
If the DD system runs out of streams during a backup, the backup fails (although not immediately) with the following error message in the operational log:
153004:hdbbackint: Unable to write to a file because the streams limit was exceeded. The error message is: [5519] [16805] [140261664245536] Tue May 10 06:45:23 2016
ddp_write() failed Offset 0, BytesToWrite 317868, BytesWritten 0 Err: 5519Exceeded streams limit
If the DD system runs out of streams during a restore, then the restore fails (although not immediately) with the following error message in the operational log:
163971 11/28/2016 06:55:59 AM hdbbackint SYSTEM critical Unable to read from a file because the streams limit was exceeded. The error message is: [5519] [60299] [140167084230432] Mon Nov 28 06:55:59 2016
ddp_read() failed Offset 192, BytesToRead 262144, BytesRead 0 Err: 5519-nfs readext remote failed (nfs: Resource (quota) hard limit exceeded)
Enable multi-stream backups for SAP HANA protection policy
To enable multi-stream SAP HANA backups for a centralized protection policy, you can set the parallelism value in the PowerProtect Data Manager UI. The parallelism value controls the number of parallel streams that the SAP HANA agent uses to write the backup data to DD.
The preceding topic describes the SAP HANA parameter parallel_data_backup_backint_channels that you can set in SAP HANA Studio to control the number of data pipes provided by SAP HANA.
NOTE:
As a SAP requirement to enable multiple streams for SAP HANA databases, the protected data size must be 128 GB or greater. You must also enable the multi- stream SAP HANA backups with PowerProtect Data Manager and configure the parallel streams in SAP HANA. The SAP HANA documentation provides the latest information about the requirement for multiple streams.
For self-service backups, you must set the parallelism value through the PARALLELISM parameter as described in Modify the configuration file parameter settings.
Use the following guidelines to set the parallelism value in the PowerProtect Data Manager UI:

24

Enabling the SAP HANA Agent

Set the parallelism to a value that is equal to or very close to the parallel_data_backup_backint_channels parameter setting. When the two settings are equal or almost equal, the SAP HANA agent can take full advantage of the parallelism provided by SAP HANA.
Set the parallelism to a value that is not more than the maximum number of connections provided by DD. Set the parallelism to a value that is at least 3 less than the maximum number of connections provided by DD. Reserve 3
connections for the log backups. For example, when DD can provide a maximum of 10 connections, set the parallelism value to 7 (10 minus 3).
In the PowerProtect Data Manager UI, perform the following steps to set the parallelism for multi-stream backups:
1. Select Infrastructure > Assets > SAP HANA. 2. Select the SAP HANA asset. 3. Select More Actions > Set Stream Count. 4. Set the stream count for each backup level as a value between 1 and 28 in the Full, Differential, and Incremental fields. 5. Click Save.

Deploy the SAP HANA agent in Microsoft Azure environment

When you deploy the PowerProtect Data Manager with the SAP HANA agent in a Microsoft Azure environment and you use the Azure provided DNS service, you must add the required entry in the /etc/hosts file.
To enable the SAP HANA operations in the Azure environment, add an entry in the /etc/hosts file for the fully qualified domain name (FQDN) of the Azure virtual machine that hosts the SAP HANA agent. For example, add the following type of entry in the /etc/hosts file on the SAP HANA agent host:

10.6.0.12

host123.internal.cloudapp.net

host123

If you do not add this type of entry in the /etc/hosts file, the SAP HANA backup and restore operations might fail.
NOTE:
In a multinode environment, ensure that you add the FQDN of every node in the /etc/hosts file on every host. For example, in an SAP HANA multinode environment with two nodes, N1 and N2:
In the /etc/hosts file on node N1, add the FQDN of both N1 and N2. In the /etc/hosts file on node N2, add the FQDN of both N1 and N2.
The PowerProtect Data Manager Azure Deployment Guide on Customer Support provides more details about the deployment requirements and procedures in an Azure environment.

Manage the SAP HANA application agent
You can use the PowerProtect Data Manager UI to add an SAP HANA application agent for data protection, approve and reject pending agent requests, and edit and delete existing agents.
Steps 1. Select Infrastructure > Application Agents.
The Application Agents window appears. NOTE: If the PowerProtect agent service was able to register during the installation, the SAP HANA host is already listed and does not need to be added.
2. In the Application Agents window, click Add. 3. Select one of the following options:
Select Add FQDN or CSV Filename. If you select Add FQDN, perform the following steps: a. Type the fully qualified domain name (FQDN) for the application agent. b. Specify the date until which the application agent is preapproved. c. Click Save.

Enabling the SAP HANA Agent

25

If you select CSV Filename, perform the following steps: a. Click the Choose File icon.
NOTE: The contents of the .csv file must be in the following format, for example:
“ppdm.dell.com” “ppdm2.emc.com” “ppdm.dellemc.com”
The Explorer window appears.
b. Select the .csv file, and then click Open.
The file appears in the window.
c. Select the date until which the application agent is preapproved. d. Click Save. If you have disabled Auto Allow List, perform the following steps:
NOTE: The Auto Allow List option is disabled by default. When Auto Allow List is enabled, all preapproved application agents are automatically approved.
a. Select the required application agent. b. Select one of the following options:
Approve Reject Edit, and then make the required changes. Remove c. Click Save.
Next steps Discover an SAP HANA application host describes how to set the host credentials before you schedule a backup.
View application agent details
Use the Application Agents window in the PowerProtect Data Manager UI to monitor the registration and update status of application agents, and view details for individual application agents. To view application agent details, from the left navigation pane, select Infrastructure > Application Agents. Agent registration status displays the total number of application agents that are awaiting approval, approved, registered, or rejected. Agent update status displays the total number of application agents that are up-to-date, available, scheduled, in progress, or failed.
NOTE: If the update of an application agent fails for any reason, the agent host is counted as available. The host is included in the total number of available applicant agents.
At the end of the Agent update status row, you can click the arrow to view information about scheduled updates. The Schedules table appears and displays the following information: Update/Precheck Name Date and Time Schedule Status Host Count Actions The lower table in the Application Agents window displays information about individual application agents. The following table describes the available information.

26

Enabling the SAP HANA Agent

Table 7. Application agent information

Column

Description

Details

Click in the Details column to view details and summary information for the application agent, including registration status.

Host Name

The name of the application agent host.

IP

The IPv4 or IPv6 address of the application agent host.

Registration Status

The registration status of the application agent:
Awaiting Approval Pending Approval Registered Approved Rejected Expired Accepting Certificates Failed

OS

The operating system of the application agent host.

Agent Type

The application agent type.

Current Version

The current version of the application agent.

Update Status

The update status of the application agent host:
Available–The PowerProtect Data Manager release is 19.12 and the application agent release is 19.10 or 19.11.
In Progress–The update of the application agent is in progress. Up to Date–The PowerProtect Data Manager release and the application agent
release are both 19.12.
Scheduled–The application agent is scheduled for an update. Failed–The update of the application agent failed. Not Supported–The PowerProtect Data Manager release is 19.12 and application
agent release is earlier than 19.10.

Filter and sort information

Use the filtering and sorting options to find specific application agents, and to organize the information that you see.

You can filter and sort the information that appears in table columns. Click a table column, or click a table column heading to sort that column.

in the column heading to filter the information in

Use the Search field to filter application agents based on a search string. When you type a keyword in the Search field, the PowerProtect Data Manager UI filters the results as you type. To clear the search filter, remove all keywords from the Search field.

Export application agent data
To export the data that is shown in the table to a .CSV file, click Export All. For more information about the Export All functionality, see the PowerProtect Data Manager Administration and User Guide.

Enabling the SAP HANA Agent

27

Managing Storage, Assets, and Protection

Topics:
· Add protection storage · Enable an asset source · Delete an asset source · Discover an SAP HANA application host · Add and remove the credentials for SAP HANA assets · Replication triggers · Add a protection policy for SAP HANA database protection · Cancel an application agent protection job · Extended retention (for protection policies created in PowerProtect Data Manager 19.11 and earlier) · Edit the retention period for backup copies · Delete backup copies · Enable the SAP HANA agent after hostname change · Manage the PowerProtect agent service · Manage the cloud tier operations with PowerProtect Data Manager
Add protection storage
Add and configure protection storage to use as a target for protection policies. Adding protection storage requires the Administrator role.
Prerequisites NOTE:
When adding a High Availability PowerProtect DD system, observe the following points:
Do not add the individual active and standby DD systems to PowerProtect Data Manager. In the Address field, use the hostname that corresponds to the floating IP address of the High Availability PowerProtect
DD system. The High Availability PowerProtect DD system is verified with the root certificate.
About this task The PowerProtect Data Manager Administration and User Guide provides more information about protection storage and related concepts: High availability options Smart Scale system pools, a single interface to a flexible group of pool members Working with protection storage Working with storage units
Steps 1. From the left navigation pane, select Infrastructure > Storage.
The Storage window appears. 2. In the Protection Storage tab, click Add. 3. In the Add Storage dialog box, select a storage system (PowerProtect DD System or PowerProtect DD Management
Center). For a system pool, select DDMC.

28

Managing Storage, Assets, and Protection

4. To add a High Availability PowerProtect DD system, select the checkbox. 5. Specify the storage system attributes:
a. In the Name field, specify a storage name. b. In the Address field, specify the hostname, fully qualified domain name (FQDN), or the IP address. c. In the Port field, specify the port for SSL communication. Default is 3009. 6. Under Host Credentials click Add, if you have already configured protection storage credentials that are common across storage systems, select an existing password. Alternatively, you can add new credentials, and then click Save. 7. If a trusted certificate does not exist on the storage system, a dialog box appears requesting certificate approval. Click Verify to review the certificate, and then click Accept. 8. Click Save to exit the Add Storage dialog and initiate the discovery of the storage system. A dialog box appears to indicate that the request to add storage has been initiated. 9. In the Storage window, click Discover to refresh the window with any newly discovered storage systems. When a discovery completes successfully, the Status column updates to OK. If DDMC is selected, all DD systems managed by the host will be listed after discovery. 10. To modify a storage system location, complete the following steps: A storage system location is a label that is applied to a storage system. If you want to store your copies in a specific location, the label helps you select the correct storage system during policy creation. a. In the Storage window, select the storage system from the table. b. Click More Actions > Set Location.
The Set Location window appears. c. Click Add in the Location list.
The Add Location window appears. d. In the Name field, type a location name for the asset, and click Save.
Results
PowerProtect Data Manager displays external DD systems only in the Storage window Name column. PowerProtect Data Manager displays PowerProtect DD Management Center storage types in the Managed By column.
View the storage unit password
PowerProtect Data Manager provides a script to retrieve the password for a storage unit that you configured as a backup target.
Prerequisites
This task requires the name of the protection storage system MTree where the storage unit resides.
Steps
1. Connect to the PowerProtect Data Manager console as an admin user. 2. Navigate to the /usr/local/brs/puppet/scripts directory. 3. Obtain the storage unit password by typing the following command:
python get_dd_mtree_credential.py MTree-name For example:
python get_dd_mtree_credential.py accounting-75914 ==============PowerProtect DD MTree credential============== Full MTree path: /data/col1/accounting-75914 User name: accounting-75914 Password: IwWXT#DC93m={XV+K

Managing Storage, Assets, and Protection

29

Enable an asset source
An asset source must be enabled in PowerProtect Data Manager before you can add and register the asset source for the protection of assets.
About this task Only the Administrator role can manage asset sources. In some circumstances, the enabling of multiple asset sources is required. For example, a vCenter Server and a Kubernetes cluster asset source must be enabled for Tanzu Kubernetes guest cluster protection. There are other circumstances where enabling an asset source is not required, such as the following: For application agents and other agents such as File System and Storage Direct, an asset source is enabled automatically
when you register and approve the agent host. For example, if you have not enabled an Oracle asset source but have registered the application host though the API or the PowerProtect Data Manager user interface, PowerProtect Data Manager automatically enables the Oracle asset source. When you update to the latest version of PowerProtect Data Manager from an earlier release, any asset sources that were previously enabled appear in the PowerProtect Data Manager user interface. On a new deployment, however, no asset sources are enabled by default.
Steps 1. From the PowerProtect Data Manager user interface, select Infrastructure > Asset Sources, and then click + to reveal
the New Asset Source tab. 2. In the pane for the asset source that you want to add, click Enable Source.
The Asset Sources window updates to display a tab for the new asset source.
Results You can now add or approve the asset source for use in PowerProtect Data Manager. For a vCenter server, Kubernetes cluster, SMIS Server, or PowerProtect Cloud Snapshot Manager tenant, select the appropriate tab in this window and click Add. For an application host, select Infrastructure > Application Agents and click Add or Approve as required.
NOTE: Although you can add a Cloud Snapshot Manager tenant to PowerProtect Data Manager in order to view its health, alerts, and the status of its protection, recovery, and system jobs, you cannot manage the protection of its assets from PowerProtect Data Manager. To manage the protection of its assets, use Cloud Snapshot Manager. For more information, see the PowerProtect Cloud Snapshot Manager Online Help.
Disable an asset source
If you enabled an asset source that you no longer require, and the host has not been registered in PowerProtect Data Manager, perform the following steps to disable the asset source.
About this task NOTE: An asset source cannot be disabled when one or more sources are still registered or there are backup copies of the source assets. For example, if you registered a vCenter server and created policy backups for the vCenter Server virtual machines, then you cannot disable the vCenter Server asset source. But if you register a vCenter server and then delete it without creating any backups, you can disable the asset source.
Steps 1. From the PowerProtect Data Manager UI, select Infrastructure > Asset Sources, and then select the tab of the asset
source that you want to disable. If no host registration is detected, a red Disable button appears. 2. Click Disable.
Results PowerProtect Data Manager removes the tab for this asset source.

30

Managing Storage, Assets, and Protection

Delete an asset source
If you want to remove an asset source that you no longer require, perform the following steps to delete the asset source in the PowerProtect Data Manager UI.
About this task Only the Administrator role can manage the asset sources.
Steps 1. From the PowerProtect Data Manager UI, select Infrastructure > Asset Sources, and then select the tab for the type of
asset source that you want to delete. 2. Select the asset source name in the asset source list, and then click Delete. 3. At the warning prompt that appears, click Continue.
The asset source is deleted from the list.
Results PowerProtect Data Manager removes the specified asset source in the Asset Sources window. Any associated assets that are protected by the protection policy are removed from the protection policy and their status is changed to deleted. These assets are removed automatically as part of daily PowerProtect Data Manager cleanup after all associated backup copies have been deleted. These assets can also be removed manually. The PowerProtect Data Manager Administration and User Guide provides details on how to remove assets from PowerProtect Data Manager. The copies of assets from the asset source are retained (not deleted). You can delete the copies from the copies page, if required. If the asset source deletion completes with an exception from PowerProtect Data Manager, you must manually decommission the SAP HANA client by running the command ./unregister.sh –full_decommission from the directory where the agent service is installed. After you decommission the SAP HANA client from PowerProtect Data Manager, the agent software binary remains on the client host. You can configure the client host as a stand-alone agent by following the instructions in the PowerProtect Database Application Agent Installation and Administration Guide. Information about the previous DD setup is located under the directory /usr/sap//SYS/global/ppdmconfig.
Discover an SAP HANA application host
After you register an application host with PowerProtect Data Manager, you can use the Asset Sources window to discover an application host and modify the application host credentials. For application hosts, discovery is required if you want to schedule a backup. You must add credentials to the SAP HANA database so that PowerProtect Data Manager can access the database to create backups.
About this task Perform the following steps to discover an SAP HANA application host as an asset source in the PowerProtect Data Manager UI.
Steps 1. Select Infrastructure > Asset Sources.
The Asset Sources window appears. 2. Select the SAP HANA tab. 3. If you are adding an SAP HANA database, select the host entry and click Edit Credentials.
The Edit Credential dialog appears. 4. If you select User Name/Password for Authentication, specify the SYSTEM user’s credentials. If the credentials belong
to the SYSTEMDB database, select the System Database check box. If you select User Key for Authentication, specify the credentials of the OS user associated with the database instance. If the credentials belong to the SYSTEMDB database, select the System Database check box.

Managing Storage, Assets, and Protection

31

The following figure shows the fields for adding the required credentials.

Figure 2. Adding the credentials for authentication
5. Click Save. An entry for the application host with the specified information appears as an entry in a table on the Asset Sources window. Discovery time is based on networking bandwidth. The resources that are discovered and those that are doing the discovery take a performance hit each time that you go through a discovery process. It might appear that PowerProtect Data Manager is not updating the Asset Sources data. NOTE: Click Discover at any time if any additions or other changes to your Asset Sources have taken place outside of the PowerProtect Data Manager environment. You can initiate a full discovery of assets by selecting the Initiate a Full Discovery option.
Results If the database is properly configured, the application hosts can now be added to a PowerProtect Data Manager protection policy.
Add and remove the credentials for SAP HANA assets
You can optionally add and remove the credentials for one or more SAP HANA database assets at the same time in the PowerProtect Data Manager UI. The asset-level credentials take precedence over policy-level credentials for SAP HANA databases. Asset-level credentials have the highest precedence.
About this task NOTE: You can only add the asset-level credentials when the SAP HANA host agent version is 19.8 or later. The SAP HANA agent does not support the asset source-level (host) credentials.
Use the following procedure to add or remove the credentials for the SAP HANA database assets.

32

Managing Storage, Assets, and Protection

Steps 1. In the PowerProtect Data Manager UI, select Infrastructure > Assets, and then click the SAP HANA tab. 2. Select one or more assets by clicking the checkbox next to each required asset name. 3. Select More Actions > Set Credential. 4. In the Set Credential dialog box, add or remove the credentials for the selected SAP HANA assets:
To add the credentials for the assets, select the appropriate value from the drop-down list in the Credential field: To create new credentials, select Create New. In the Add Credentials dialog box that appears, set the authentication type as either User name/Password or User Key, specify the credential values, and click Save.
To add existing credentials, select the credentials name from the credentials list. To remove the credentials for the assets, select Remove Credentials. 5. Click Save in the Set Credential dialog box.
Results After you add the credentials by using this procedure, the asset-level credentials are used for the selected assets during SAP HANA centralized backups, overriding the policy-level credentials.
Replication triggers
PowerProtect Data Manager orchestrates protection policy replication objectives independently of the primary backup. When you add a replication objective to a policy, select one of the available triggers.
The default replication trigger is a schedule window that you define by setting a recurrence period plus start and end times. Replication occurs during the defined window. For example, every day between 8 p.m. and 12 a.m.
You can also trigger replication immediately after the completion of the associated primary backup, whether scheduled or manual. At the start of the primary backup, PowerProtect Data Manager generates an associated replication job that remains queued until the end of the protection job. If the backup fails or completes with exception, the associated replication job is skipped. Restarting the protection job queues the associated replication job again.
When you create a replication objective, you can specify either scheduled replication or replication after backup completion, which is applicable to both centralized and self-service protection policies.
NOTE: For replication after backup completion, PowerProtect Data Manager 19.12 or later and application agents 19.10 or later are required. It is recommended that you update the application agents to the latest version.
Using a schedule can help you manage network traffic by replicating during off-peak hours. However, for larger backup sets, the primary backup may not finish before the start of the replication schedule, which creates a replication backlog. Replication after backup completion prevents a replication backlog from forming.
To prevent data loss, the replication after backup completion trigger replicates new backups from the primary objective and any outstanding backups that have not yet replicated.
A job status of Completed with Exceptions during replication
After a triggered replication job, you might see a job status message similar to the following:
Completed with Exceptions ABA0017: plc_linux_rac: Backup was successful for the ORACLE_DATABASE asset ORCLPP on the host blrv009d132.blr.lab.emc.com but the copy metadata information is currently unavailable.
The backup of this asset completed successfully but the copy metadata information has not yet been discovered by PowerProtect Data Manager. If the ‘Replicate immediately upon backup completion’ option is enabled for this protection policy, the replication job for the copy might appear in ‘Unknown’ or ‘Cancel’ state. Once the copy metadata is discovered by PowerProtect Data Manager, the copy will be replicated.
Review the backup copy details in the View Copies pane of the PowerProtect Data Manager UI Infrastructure > Assets window to determine when the discovery is complete.

Managing Storage, Assets, and Protection

33

If you see this message, the replication backup is not immediately available.
To correct this issue, either wait for the next automatic discovery or initiate a discovery.
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.
NOTE: PowerProtect Data Manager does not support the automatic retention lock (ARL) setting on the DD system. The option to create a storage unit during protection policy configuration does not support compliance mode retention locking, only governance mode. To use compliance mode retention locking, create and configure a storage unit before you configure an associated protection policy. If you enable retention locking and select a storage unit where the retention lock mode is None, the retention lock defaults to governance mode. The PowerProtect Data Manager Administration and User Guide provides more information.
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. From the left navigation pane, select Protection > Protection Policies.
The Protection Policies window appears. 2. In the Protection Policies window, click Add.
The Add Policy wizard appears. 3. On the Type page, specify the following fields, and then click Next:
Name–Type a descriptive name for the protection policy. Description–Type a description for the policy. 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.

34

Managing Storage, Assets, and Protection

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 objectives.
Exclusion–Select this type if there are assets within the protection policy that you plan 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:
a. Click Add under Primary Backup.
The Add Primary Backup dialog appears.
b. 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.
The retention lock mode setting comes from the configuration of the selected storage unit. When you enable retention locking, the Retention Lock Mode field displays the corresponding storage unit setting.
Setting a retention lock applies to the current backup copy only, and does not impact the retention lock setting for existing backup copies.
NOTE: Primary backups are assigned a default retention lock period of 14 days. Replicated backups, however, are not assigned a default retention lock period. If you enable Retention Lock for a replicated backup, ensure

Managing Storage, Assets, and Protection

35

that you set the Retain for field in the Add Replication dialog to a minimum number of 14 days so that the replicated backup does not expire before the primary backup. c. On the Schedules pane of the Add Primary Backup dialog:
i. 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.
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.
ii. 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 every–For , 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.
iii. Click Add Backup and repeat the procedure for creating full backups if you want to create additional backup copies at different intervals with different retention periods.
Within this protection policy, when a full schedule conflicts with another full backup schedule, a message appears, indicating that there is a conflict. Schedule occurrences can conflict with each other when the activity windows are identical or occur entirely within the same time range. To avoid full schedule conflicts in a policy, edit the activity windows. If you proceed with conflicting schedules, the backup of the lower priority schedule will be skipped. Schedule priority is ranked according to the following criteria:
Full schedules have a higher priority than Synthetic Full schedules. For schedules of the same backup type, the schedules that run less frequently have a higher priority than
schedules that run more frequently. For schedules with the same backup type and frequency, the schedule with the longest activity window has
the higher priority. If the activity windows are also identical, only one of these schedules will run.

36

Managing Storage, Assets, and Protection

NOTE: When a schedule conflict between full backups occurs, PowerProtect Data Manager retains the full backup with the longest retention period. d. 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.
After completing the objective, you can change any details by clicking Edit next to the objective.
For Self-Service Protection: a. Click Add under Primary Retention.
The Add Primary Retention dialog appears.
b. 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. The retention lock mode setting comes from the configuration of the selected storage unit. When you enable retention locking, the Retention Lock Mode field displays the corresponding storage unit setting.
Setting a retention lock applies to the current backup copy only, and does not impact the retention lock setting for existing backup copies.
NOTE: Primary backups are assigned a default retention lock period of 14 days. Replicated backups, however, are not assigned a default retention lock period. If you enable Retention Lock for a replicated backup, ensure that you set the Retain for field in the Add Replication dialog to a minimum number of 14 days so that the replicated backup does not expire before the primary backup. c. 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 For field values as required.
When a different retention time for all backup types is set, you can create additional full backup patterns with different retention times. For example, you can add a full backup pattern Retain full backups created every week on the Monday and Tuesday for 2 months.
NOTE: The retention time of the log backup is set to the retention time of the full backup.
d. 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.
After completing the objective, you can change any details by clicking Edit next to the objective.
8. Optionally, replicate the backups: NOTE:
To enable replication, ensure that you add remote protection storage as the replication location. The PowerProtect Data Manager Administration and User Guide provides detailed instructions about adding remote protection storage.
When creating multiple replicas for the same protection policy, it is recommended to select a different storage system for each copy. If you select a storage unit that is the target of another objective for the same policy, the UI issues

Managing Storage, Assets, and Protection

37

a warning. The PowerProtect Data Manager Administration and User Guide provides information about replicating to shared protection storage to support PowerProtect Cyber Recovery. Verify the storage targets and the use case before you continue.
When you create a replication objective, you can specify either scheduled replication or replication after backup completion.
NOTE: For replication after backup completion, PowerProtect Data Manager 19.12 or later and application agents 19.10 or later are required. It is recommended that you update the application agents to the latest version.
The retention time of the log backup is set to the retention time of the full backup.
a. Click Replicate next to Primary Backup or Primary Retention. An entry for Replicate is created to the right of the primary backup objective.
b. Under Replicate, click Add. The Add Replication dialog appears, with information in the left pane for each schedule that has been added for the primary backup objective of this protection policy. NOTE: Backups for all of the listed schedules will be replicated. You cannot select individual schedules for replication.
c. Select a storage target: Storage Name–Select a destination from the list of protection storage. Or, select Add to add a protection storage system and complete the details in the Storage Target window. Storage Unit–Select an existing storage unit on the protection storage system. Or, select New to automatically create a storage unit. 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 replicas. The retention lock mode setting comes from the configuration of the selected storage unit. When you enable retention locking, the Retention Lock Mode field displays the corresponding storage unit setting.
SLA–Select an existing replication service level agreement that you want to apply to this schedule from the list. Or, select Add to create a replication SLA within the Add Service Level Agreement wizard.
The PowerProtect Data Manager Administration and User Guide provides more information about replication targets, such as SLAs.
d. Select when to replicate the backups:
Replication triggers provides more information.
To replicate after the backup finishes, move the Replicate immediately upon backup completion slider to on. For scheduled replication, move the Replicate immediately upon backup completion slider to off, and then
complete the schedule details in the Add Replication dialog.
For replication of the primary backup, the schedule frequency can be every day, week, month, or x hours.
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 from 1 to 12 hours.
By default, all replicas of the primary backup objective inherit the retention period from the Retain For value of the synthetic full and full backup schedules.
e. To specify a different retention period for individual synthetic full and full replicas, clear Set the same retention time for all replicated copies, click Edit in the row of each schedule that you want to change, update the value in the Retain For field, and then click Save. CAUTION: Setting a retention period for the replicas of other backup types (such as log backups, incremental, and differential backups, where applicable) that is shorter than the retention period of the corresponding full backup may result in being unable to recover from those replicas.
f. Click Save to save your changes and return to the Objectives page. 9. Optionally, to move backups from protection storage to Cloud Tier, add a Cloud objective for the primary or replication
objective: NOTE: To move a backup or replica to Cloud Tier, objectives must have a retention time of 14 days or more. PowerProtect Data Manager also requires the discovery of protection storage with a configured Cloud unit.

38

Managing Storage, Assets, and Protection

a. Click Cloud Tier next to Primary Backup or Primary Retention. Or, if adding a Cloud objective for a replication objective that you have added, click Cloud Tier under Replicate. An entry for Cloud Tier is created to the right of the primary objective, or below the replication objective.
b. Under the entry for Cloud Tier, click Add. The Add Cloud Tier Backup dialog appears, with summary information for the parent objective to indicate whether you are adding this Cloud Tier objective for the primary objective or the replication objective.
c. Keep the All applicable full backups slider to the right if you want to tier the backups from all of the full primary backup or replication schedules of this policy. Otherwise, move the slider to the left and select the full schedule(s) that you want to tier. NOTE: If the retention period of a schedule is less than the minimum 14 days required before tiering occurs, or is less than the value in the Tier After field, you can still select this schedule for tiering. However, if you do not edit the retention period of this schedule or its backup or replication copy to a value greater than the Tier After field before the retention period of the copy expires, the backup or replication copy of this schedule will not be cloud tiered.
d. Complete the objective details in the Add Cloud Tier Backup dialog, and then click Save to save your changes and return to the Objectives page. The PowerProtect Data Manager Administration and User Guide provides detailed instructions for adding a Cloud objective for a primary or replication objective.
10. Click Next. The Options page appears.
11. 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 DEBUGLEVEL and DPRINTF parameters in the configuration file /usr/sap//SYS/global/ppdmconfig/_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.
12. Click Next. The Summary page appears.
13. 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.
14. 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.
When a backup fails or a backup is skipped, a particular backup job step appears as canceled, depending on which step failed or was skipped for a particular database. The backup job steps are displayed on the Step Log tab in the details section of the Job ID Summary window.
Cancel an application agent protection job
You can cancel an application agent protection job from the PowerProtect Data Manager UI. The job must be in a queued or running state. The protection job runs for a primary backup that is configured through an application agent protection policy.
About this task
You can perform two types of application agent job cancellations in the PowerProtect Data Manager UI:

Managing Storage, Assets, and Protection

39

Cancellation of a job group that includes one or more asset jobs. Cancellation of an individual asset job.
NOTE:
When a job completes before the cancel request reaches the application host, the status of the canceled job transitions to either success or failure.
You can cancel many other types of jobs, in addition to protection jobs. The PowerProtect Data Manager Administration and User Guide provides more information. Perform the following steps to cancel an application agent protection job in the PowerProtect Data Manager UI.
Steps 1. From the PowerProtect Data Manager UI left navigation pane, select Jobs > Protection Jobs.
The Protection Jobs window opens to display a list of protection jobs and job groups.
2. In the Protection Jobs window, perform the required type of job cancellation: To cancel a job group: a. In the Protection Jobs window, select the required job group and click Cancel. A job group warning prompt appears. b. Click OK at the prompt. You can monitor the job group cancellation in the Protection Jobs window. The job group status changes to Canceled when the cancellation of all the asset jobs is complete. To monitor the cancellation of individual asset jobs within the job group, click the job ID in the Protection Jobs window. The Job ID Summary window opens, where you can view the status of each asset job. To cancel an asset job: a. In the Protection Jobs window, click the job ID. The Job ID Summary window opens to display the job details of the assets in the job group. b. In the Job ID Summary window, select the required asset job and click Cancel. A job warning prompt appears. c. Click OK at the prompt.
You can monitor the asset job cancellation in the Job ID Summary window. The asset job status changes to Canceled when the job cancellation is complete.
NOTE: When the cancel request for a job cannot be completed, an informational alert is displayed.
Extended retention (for protection policies created in PowerProtect Data Manager 19.11 and earlier)
NOTE: This section applies to protection policies created in PowerProtect Data Manager 19.11 and earlier only. For protection policies created in PowerProtect Data Manager 19.12, instead of using the Extend Retention objective to extend the retention period of certain full copies, you can now add multiple full schedules for primary backup and replication objectives. When updating to PowerProtect Data Manager 19.12 from a previous release, any protection policies created in the earlier release with the Extend Retention objective will continue to be supported, however, you will not be able to edit existing extended retention objectives, or add new extended retention objectives, in these policies. The Knowledge Base article 000204454 at https://www.dell.com/support/ provides detailed information about specific Extend Retention objective migration scenarios when updating to PowerProtect Data Manager 19.12. For protection policies created in PowerProtect Data Manager 19.11 and earlier, the Extend Retention objective allows you to extend the retention period for the primary backup copy for long-term retention. For example, your regular schedule for daily

40

Managing Storage, Assets, and Protection

backups can use a retention period of 30 days, but you can extend the retention period to keep the full backups taken on Mondays for 10 weeks.
Both centralized and self-service protection policies support weekly, monthly, and yearly recurrence schedules to meet the demands of your compliance objectives. For example, you can retain the last full backup containing the last transaction of a fiscal year for 10 years. When you extend the retention period of a backup in a protection policy, you can retain scheduled full backups with a repeating pattern for a specified amount of time.
For example:
Retain full yearly backups that are set to repeat on the first day of January for 5 years. Retain full monthly backups that are set to repeat on the last day of every month for 1 year. Retain full yearly backups that are set to repeat on the third Monday of December for 7 years.
Preferred alternatives
When you define an extended retention objective for a protection policy, you define a set of matching criteria that select preferred backups to retain. If the matching criteria do not identify a matching backup, PowerProtect Data Manager automatically retains the preferred alternative backup according to one of the following methods:
Look-back–Retain the last available full backup that was taken before the matching criteria. Look-forward–Retain the next available full backup that was taken after the matching criteria.
For example, consider a situation where you configured a protection policy to retain the daily backup for the last day of the month to extended retention. However, a network issue caused that backup to fail. In this case, look-back matching retains the backup that was taken the previous day, while look- forward matching retains the backup that was taken the following day.
By default, PowerProtect Data Manager uses look-back matching to select the preferred alternative backup. A grace period defines how far PowerProtect Data Manager can look in the configured direction for an alternative backup. If PowerProtect Data Manager cannot find an alternative backup within the grace period, extended retention fails.
You can use the REST API to change the matching method or the grace period for look-forward matching. The PowerProtect Data Manager Public REST API documentation provides instructions. If there are no available backups for the defined matching period, you can change the matching method to a different backup.
For look-forward matching, the next available backup can be a manual backup or the next scheduled backup.
Selecting backups by weekday
This section applies to centralized protection policies. Self-service protection policies have no primary backup objective configuration.
When you configure extended retention to match backups by weekday, PowerProtect Data Manager may identify a backup that was taken on one weekday as being taken on a different weekday. This behavior happens where the backup window does not align with the start of the day. PowerProtect Data Manager identifies backups according to the day on which the corresponding backup window started, rather than the start of the backup itself.
For example, consider a backup schedule with an 8:00 p.m. to 6:00 a.m. backup window:
Backups that start at 12:00 a.m. on Sunday and end at 6:00 a.m. on Sunday are identified as Saturday backups, since the backup window started on Saturday.
Backups that start at 8:01 p.m. on Sunday and end at 12:00 a.m. on Monday are identified as Sunday backups, since the backup window started on Sunday.
Backups that start at 12:00 a.m. on Monday and end at 6:00 a.m. on Monday are identified as Sunday backups, since the backup window started on Sunday.
In this example, when you select Sunday backups for extended retention, PowerProtect Data Manager does not retain backups that were taken between 12:00 a.m. and 8:00 p.m. This behavior happens even though the backups occurred on Sunday. Instead, PowerProtect Data Manager selects the first available backup that started after 8:00 p.m. on Sunday for extended retention.
If no backups were created between 8:01 p.m. on Sunday and 6:00 a.m. on Monday, PowerProtect Data Manager retains the next alternative to extended retention. In this example, the alternative was taken after 6:00 a.m. on Monday.

Managing Storage, Assets, and Protection

41

Extended retention backup behavior

When PowerProtect Data Manager identifies a matching backup, automatic extended retention creates a job at the beginning of the backup window for the primary objective. This job remains queued until the end of the backup window and then starts. The following examples describe the behavior of backups with extended retention for centralized and self-service protection.
Centralized protection
For an hourly primary backup schedule that starts on Sunday at 8:00 p.m. and ends on Monday at 6:00 p.m. with a weekly extended retention objective that is set to repeat every Sunday, PowerProtect Data Manager selects the first available backup starting after 8:00 p.m. on Sunday for long-term retention. The following diagram illustrates the behavior of backups with extended retention for a configured protection policy. In this example, full daily backups starting at 10:00 p.m. and ending at 6:00 a.m. are kept for 1 week. Full weekly backups are set to repeat every Sunday and are kept for 1 month.

Figure 3. Extend retention backup behavior
Self-service protection
For self-service backups, PowerProtect Data Manager uses a default backup window of 24 hours. For a backup schedule that starts on Sunday at 12:00 p.m and ends on Monday at 12:00 p.m. with a weekly extended retention objective that is set to repeat every Sunday, PowerProtect Data Manager selects the first available backup that is taken between 12:00 p.m. on Sunday and 12:00 p.m. on Monday for long-term retention.
Replication of extended retention backups
You can change the retention time of selected full primary backups in a replication objective by adding a replication objective to the extended retention backup. The rules in the extended retention objective define the selected full primary backups. Review the following information about replication of extended retention backups. Before you configure replication of extended retention backups, create a replication objective for the primary backup. Configure the replication objective of the extended retention and match this objective with one of the existing replication
objectives based on the primary backup. Any changes to a new or existing storage unit in the extended retention replication objective or the replication objective of the primary backup is applied to both replication objectives. The replication objective of extended retention backups only updates the retention time of replicated backup copies and does not create any new backup copies in the replication storage.

42

Managing Storage, Assets, and Protection

Edit the retention period for backup copies
You can edit the retention period of one or more backup copies to extend or shorten the amount of time that backups are retained.
About this task You can edit the retention period for all asset types and backup types.
Steps 1. Select Infrastructure > Assets. 2. From the Assets window, select the tab for the asset type for which you want to edit the retention period. If a policy has
been assigned, the table lists the assets that have been discovered, along with the associated protection policy. 3. Select a protected asset from the table, and then click View Copies. The Copy Locations pane identifies where the
backups are stored. 4. In the left pane, click the storage icon to the right of the icon for the asset, for example, DD. The table in the right pane lists
the backup copies. 5. Select one or more backup copies from the table, and click Edit Retention. 6. Select one of the following options:
To select a calendar date as the expiration date for backups, select Retention Date. To define a fixed retention period in days, weeks, months, or years after the backup is performed, select Retention
Value. For example, you can specify that backups expire after 6 months. NOTE: When you edit the retention period for copies that are retention locked, you can only extend the retention period.
7. When satisfied with the changes, click Save. The asset is displayed in the list with the changes. The Retention column displays both the original and new retention periods, and indicates whether the retention period has been extended or shortened.
Delete backup copies
In addition to deleting backups after the retention period expires, PowerProtect Data Manager enables you to manually delete backup copies from protection storage.
About this task If you no longer require a backup copy and the retention lock is not enabled, you can delete backup copies prior to their expiration date. Starting with PowerProtect Data Manager version 19.6, you can perform a backup copy deletion that deletes only a specified part of a backup copy chain, without impacting the ability to restore other backup copies in the chain. When you select a specific backup copy for deletion, only that backup copy and the backup copies that depend on the selected backup copy are deleted: When you select to delete a full backup copy, any other backup copies in the chain that depend on the full backup copy are
also deleted.
NOTE:
You can delete a full backup copy only if an archive log exists and the previous full backup copy is available. If you delete a full backup of an incomplete chain, you cannot restore the whole chain until you perform the next full backup.
Deletion of the last remaining full backup from DD does not delete the entry for that backup in the SAP HANA catalog. This behavior applies to both scheduled deletion and manual deletion operations. When you select to delete an incremental backup copy, any incremental backup copies that depend on the selected incremental backup copy are also deleted. The whole backup chain is not deleted. When you select to delete a differential backup copy, any incremental backup copies that depend on the selected differential backup copy are also deleted. The whole backup chain is not deleted. When you select to delete a log backup copy, any other log backup copies that depend on the selected log backup copy are also deleted. The whole backup chain is not deleted.

Managing Storage, Assets, and Protection

43

NOTE: Deletion of log backups might affect a point-in-time restore that depends on those log backups.
Regarding expired copy deletion for a backup chain, the full backup expires last. The other incremental, differential, and log backups can be expired and deleted earlier: The full backup expires only when every other backup in the chain has expired. A differential backup expires only when all the incremental backups that depend on it have expired. An incremental backup expires when its retention time expires. A log backup expires only when all the log backups that depend on it have expired.
Steps 1. From the PowerProtect Data Manager UI, select Infrastructure > Assets. 2. From the Assets window, select the tab for the asset type for which you want to delete copies. If a policy has been
assigned, the table lists the assets that have been discovered, along with the associated protection policy. 3. Select a protected asset from the table, and then click View Copies. The Copy Locations pane identifies where the
backups are stored. 4. In the left pane, click the storage icon to the right of the icon for the asset, for example, DD. The table in the right pane lists
the backup copies. 5. Select one or more copies from the table that you want to delete from the DD system, and then click Delete.
A preview window opens and displays the selected backup copies.
NOTE: For assets with backup copies that are chained together such as SAP HANA databases, the preview window lists all the backup copies that depend on the specified backup copy. If you delete a backup copy, PowerProtect Data Manager deletes the specified backup copy and all backup copies that depend on the specified backup copy. 6. For all asset types, you can choose to keep the latest backup copies or delete them. By default, PowerProtect Data Manager keeps the latest backup copies. To delete the latest backup copies, clear the check box next

References

• Dell Technologies Developer
• Submit Form
• SAP Help Portal

Read User Manual Online (PDF format)

Read User Manual Online (PDF format)  >>

Download This Manual (PDF format)

Download this manual  >>