- Notes, cautions, and warnings
- Preface
- Getting started
- Enabling the Oracle RMAN agent
- Review Oracle data protection and replication requirements
- Protecting a standalone Oracle server
- Protecting Oracle RAC environments
- Install and configure the Oracle RMAN agent
- Install the Oracle RMAN agent and PowerProtect Data Manager agent on AIX or Linux
- Install the Oracle RMAN agent and PowerProtect Data Manager agent on Windows
- Integration with PowerProtect Data Manager software
- Installation requirements for Oracle Incremental Merge
- Uninstall the Oracle RMAN agent and PowerProtect agent service on AIX or Linux
- Uninstall the Oracle RMAN agent and PowerProtect Data Manager agent on Windows
- Update in an Oracle RAC environment on AIX or Linux
- Update the Oracle RMAN agent on AIX or Linux
- Update the PowerProtect agent
- Update the application agent in the PowerProtect Data Manager UI
- Enable a disabled 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
- PowerProtect Data Manager support of Oracle active/passive RAC systems
- PowerProtect Data Manager support of Oracle RMAN agent with Oracle 21c
- Enable multistream backups for Oracle protection policy
- Enable the app-optimized compression for Oracle backups
- Enable the deletion of Oracle audit logs
- Oracle Data Guard protection with Oracle RMAN agent
- Oracle Incremental Merge protection with Oracle RMAN agent
- Oracle Exadata protection with Oracle RMAN agent
- Parallel discoveries in an Oracle environment
- Parallel backups in an Oracle environment
- Managing storage, assets, and protection
- Add protection storage
- Enable an asset source
- Delete an asset source
- Discover an Oracle application host
- Add and remove the credentials for Oracle assets
- Assign a preferred node in Oracle RAC environment
- Protection policies for Oracle database protection
- Supported protection policy purposes
- Supported protection policy objectives
- Replication triggers
- Roadmap for planning an Oracle database protection policy
- Before you add a protection policy for Oracle database protection
- Add a protection policy
- Select a protection policy type
- Select a protection policy purpose
- Select protection policy asset groups
- Select protection policy assets
- Add protection policy objectives
- Configure protection policy options
- Add pre-script and pre-script (optional)
- Review the protection policy summary
- Clone a protection policy
- Viewing protection policy jobs
- Asset-level configuration for protection policies
- Extended retention for protection policies
- Protection rules
- Cancel a Microsoft Exchange, Oracle, or SAP HANA application agent protection job
- Edit the retention period for backup copies
- Delete backup copies
- Generate alerts for missing dependent logs
- Host CPU throttling
- Disable DD Boost write compression for encrypted Oracle backups
- Enable the use of pre-scripts and post-scripts with backups
- Enable the multistream parallel backups in an Oracle RAC environment
- Enable the Oracle RMAN agent after Oracle RMAN hostname change
- Enable the Oracle RMAN agent after Oracle RMAN host IP address change
- Reregister the agent after a PowerProtect Data Manager server hostname or IP address change
- Enable the Oracle RMAN agent after migration to a different host
- Enable the Oracle RMAN agent after Oracle application update
- Enable the Oracle RMAN agent after reusing IP address from non-Oracle host
- Enable the use of an existing asset in a modified environment
- Delete backup copies from RMAN catalog with ddutil command
- Manage the PowerProtect agent service
- About the PowerProtect agent service
- Start, stop, or obtain the status of the PowerProtect agent service
- Register the PowerProtect agent service to a different server address on AIX or Linux
- Register the PowerProtect agent service to a different server address on Windows
- Recovering the PowerProtect agent service from a disaster
- Manage the cloud tier operations with PowerProtect Data Manager for application agents
- Cyber Recovery solution for PowerProtect Data Manager
- Performing self-service backups and restores of Oracle databases
- Performing centralized restores of Oracle backups
- Centralized restore and recovery of Oracle backups
- Considerations for centralized Oracle restore and recovery
- Performing centralized Oracle restore and recovery of an online database
- Performing centralized Oracle restore of archive logs
- Performing centralized disaster recovery of an Oracle database or group
- Performing centralized instant access recovery of an Oracle database
- Quick recovery
- Best practices and troubleshooting
- Glossary
PowerProtect Data Manager 19.17 Oracle RMAN User Guide
Root certificate authority expiration
The PowerProtect Data Manager root certificate authority (CA) expires five years after PowerProtect Data Manager has been deployed. If the root CA is not renewed, PowerProtect Data Manager and its components no longer protect any assets.
NOTE:PowerProtect Data Manager issues critical alerts about root CA expiration at intervals of 30, 15, and 7 days before the expiration date. A critical alert is also issued on the same day that the root CA is due to expire.
To prevent any interruption to protection, perform the following steps on or before the expiration date:
- Update all application agents to version 19.17 or later.
NOTE:Any application agent at version 19.16 or earlier must be manually reregistered after the root CA is renewed.
- Renew the root CA. For more information, see the PowerProtect Data Manager Security Configuration Guide.
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: <>()\