Supporting existing Oracle RMAN agent backups with
PowerProtect Data Manager
The Oracle RMAN agent 19.1 introduced the capability to onboard existing stand-alone deployments, including their existing backups, to
PowerProtect Data Manager. Existing backups are Oracle RMAN agent backups that you performed before you have integrated the Oracle RMAN agent with the
PowerProtect Data Manager software and added an asset to a
PowerProtect Data Manager protection policy.
NOTE
Retention lock is not supported for discovered existing backups in
PowerProtect Data Manager.
Onboarding of DD Boost-over-FC backups is not supported.
With the onboarding capability,
PowerProtect Data Manager provides the following centralized features:
Visibility of both existing backups and any new self-service or
PowerProtect Data Manager policy-driven backups of onboarded assets.
Retention management of all backups. The retention time of existing backups can be set during the
PowerProtect Data Manager registration.
Automatic configuration of target protection storage based on the
PowerProtect Data Manager protection policies that are used for your database.
All the other functionality that is provided for
PowerProtect Data Manager protection policies.
Self-service operations use the DD backup host and storage unit managed by
PowerProtect Data Manager
With Oracle RMAN agent 19.1 or later, you can provide the DD backup host and storage unit in the RMAN scripts. After you use
PowerProtect Data Manager to add an asset to the protection policy, you might want to keep using the existing RMAN scripts instead of or along with scheduling backups through
PowerProtect Data Manager.
When you create a protection policy, the
PowerProtect Data Manager software can either create or reuse a storage unit on the specified DD system backup host, subject to limitations. All subsequent backups of assets in that protection policy go to this storage unit. This implementation overrides the backup host and storage unit information from the script with the backup host and storage unit information from
PowerProtect Data Manager.
NOTE
If any asset on the host is being managed by
PowerProtect Data Manager, only the delete operations performed through
PowerProtect Data Manager are supported. Self-service delete operations through
rman delete or
ddutil delete are not supported.
If you plan to manage all assets on a host by using the stand-alone RMAN agent and not the
PowerProtect Data Manager, ensure that the hidden files
.app.settings and
.ddbmcon.gatherinfo are removed from the
$RMAN_AGENT_HOME/settings directory.
On a host where at least one asset is being managed by
PowerProtect Data Manager, do not remove the hidden files
.app.settings and
.ddbmcon.gatherinfo. In this case, the file removal will result in unexpected behavior.
Setting and reporting the retention time for existing backups
With Oracle RMAN Agent 19.1 or later, any backups that are performed before you add an asset to a
PowerProtect Data Manager protection policy are considered existing backups. You can set the retention time for existing backups during registration with the
PowerProtect Data Manager server by using the
configureAddOn.sh script with version 19.5 or later. This retention time is reported to
PowerProtect Data Manager during backup discovery.
Data is not available for the Topic
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: <>()\