For Amazon RDS for Oracle
Backup and restore support for full, differential incremental, and archive redo log type protection.
Oracle 21c and 19c CDB are supported. The 19c non-CDB version is also supported.
CDB databases with multi-tenant and single-tenant container databases, and non-CDB databases are supported.
Oracle Enterprise and Standard Editions are supported.
Backup and restore are both supported for S3 as the staging path.
Backup and restore are not supported for TDE-enabled RDS Oracle instances or read replicas.
For credential validation, IAM is not supported for Amazon RDS Oracle. You can use the username and password method.
The option group attached to RDS Oracle must have the same database engine version and the same database engine name.
Restore is supported using the S3 staging path only, including manual recovery from the Instant access database tab.
EFS support as a staging location is discontinued from NetBackup 11.0.0.1 release. Use S3 as a staging location for RDS Oracle backups.
You must manually clean up the EFS mounts that were previously used as staging locations. Any staging cleanup job run from the NetBackup UI, only removes the location from the NetBackup database.
Before running the archive log backup, set the retention period in the protection plan. See the Knowledge-base article: https://support.cohesity.com/s/article/article-100059038
Do not take external backups using the RDS rman APIs on the instance to maintain data consistency.
The recovery script supports EC2 or on-premises VMs.
NetBackup enforces full backups in these three cases:
If a backup cancellation or failure occurs. NetBackup tracks such events by keeping a flag in the previous DBPaaS statefile.
If you schedule the first backup as an incremental or archive log backup.
If you take multiple incremental or archive backups, beyond the threshold value. The threshold value refers to the number of recovery points of incremental and archive log backups.