# Configuration for Amazon RDS for Oracle

Configuration for protecting Amazon RDS for Oracle with Commvault includes deploying an EC2 access node and configuring the Amazon RDS for Oracle database instance.

Depending on the backup staging requirement, the RDS instance can be configured to use Amazon EFS or Amazon S3 as the RMAN staging location. Using Amazon EFS generally requires less operational management than Amazon S3.

## Prerequisites

### RMAN integration with Amazon EFS

Note

Use hosted infrastructure option does not support Amazon EFS as the RMAN staging location.

1. Configure the following on the EFS file system:

   - Create an Amazon EFS file system in the same VPC and Region as the Amazon RDS for Oracle instance with mount targets enabled across all RDS availability zones.

   - Create an EFS access point with a root directory such as `/commvault`.

   - Configure POSIX ownership and permissions that permit RMAN operations from Amazon RDS for Oracle.

   - The minimum required permissions must allow read and write access to the directory (for example, mode `0755`).

   - Configure the EFS file system policy to allow RDS IAM role and EC2 access with `ClientMount`, `ClientWrite`, and `ClientRootAccess` permissions. For information, see .

   - Configure the EFS security group to allow TCP 2049 access from RDS and EC2 security groups.

2. Configure the following on RDS:

   - Make sure that the Amazon EFS integration configuration is completed, and verify that the connectivity from Amazon RDS to efs is fine.

   - Ensure that the Amazon RDS instance has:

     - Network connectivity to EFS mount targets

     - An associated IAM role with required EFS permissions

   - Configure a new option group with Amazon EFS integration enabled and associate it with the Amazon RDS for Oracle instance. For information, see option groups.

3. Configure the following on Amazon EC2:

   - Install EFS utilities using `amazon-efs-utils`.

   - Mount the EFS file system using the access point or by mounting the root of the EFS file system to the desired directory.

### RMAN integration with S3

1. Verify that you have sufficient space on Amazon RDS to backup RMAN dumps. For full backup of the RMAN, you must have:

   - Same amount of space which is of RDS database size (1x) on the local Amazon RDS storage

   - Space to accommodate the archive logs

2. Configure the trust relationship policy at IAM role level. For more information, see the sample trust relationship policy JSON.

3. Make sure that the Amazon S3 integration configuration is completed, and verify that the connectivity from Amazon RDS to S3 bucket is fine.

4. Configure a new options group with S3 integration as the option and associate it to the Amazon RDS for Oracle instance. For information, see option groups.

## Backup optimization

By default, RMAN backup optimization is disabled, so every backup includes all datafiles and archived logs. To optimize backups, enable the OptimizeLogBackups additional setting. RMAN then skips unchanged datafiles that have already been backed up.

×

Loading...