- Notes, cautions, and warnings
- Preface
- PowerProtect Data Manager for Oracle RMAN Agent Overview
- Enabling the Oracle RMAN Agent
- Review Oracle data protection and replication requirements
- Protecting a stand-alone Oracle server
- Protecting Oracle RAC environments
- Install and configure the Oracle RMAN agent
- Install the Oracle RMAN agent
- Integration with PowerProtect Data Manager software
- Install the PowerProtect Data Manager agent
- Uninstall the Oracle RMAN agent
- Uninstall the PowerProtect agent service
- Update the Oracle RMAN agent
- Update the PowerProtect agent
- Recommission the Oracle RMAN agent
- How the Oracle RMAN agent communicates with PowerProtect Data Manager
- Verify the connectivity from ddbmcon
- Discover the storage units
- Manage the Oracle application agent
- Supporting existing Oracle RMAN agent backups with PowerProtect Data Manager
- Enable multi-stream backups for Oracle protection policy
- Enabling app-optimization for storage unit created by Oracle protection policy
- Managing Storage, Assets, and Protection
- Add protection storage
- Storage unit considerations
- Enable an asset source
- Delete an asset source
- Discover an Oracle application host
- Add and remove the credentials for Oracle assets
- Add a protection policy for Oracle database protection
- Cancel an application agent protection job
- Add a service-level agreement
- Extended retention
- Edit the retention period for backup copies
- Delete backup copies
- Enable the Oracle RMAN agent after hostname change
- Manage the PowerProtect agent service
- Manage the cloud tier operations with PowerProtect Data Manager
- Performing Self-Service Backups and Restores of Oracle Databases
- Oracle RMAN Best Practices and Troubleshooting
- Troubleshooting storage units
- Troubleshooting backup failures when credentials include a backslash character (\)
- Troubleshooting PowerProtect Data Manager UI display of localhost.localdomain hostname
- Troubleshooting agent registration
- Troubleshooting PowerProtect agent service operations
- Troubleshooting self-service backup error related to top-level pathname
- Troubleshooting self-service operations with data-in-flight encryption
- Troubleshooting Oracle self-service jobs that run indefinitely
- Troubleshooting an incorrect self-service backup report for different backup types in same session
- Troubleshooting an incorrect asset display after asset source deletion
- Troubleshooting an issue with AIX RAC cluster failover
- Troubleshooting RAC cluster failure due to active node issue
- Troubleshooting a missing duration value for centralized backup
- Troubleshooting an issue with onboarded backup copies
- Troubleshooting missing Oracle version with added protection rules
- Troubleshooting restore failure due to FORMAT specification
PowerProtect Data Manager 19.10 Oracle RMAN User Guide
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, 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. This retention time is reported to PowerProtect Data Manager during backup discovery.
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: <>()\