Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

4. To save your changes, click Modify.

AWS RDS RMAN GI

...

First configuration screen

On the first configuration screen choose AWS RDS Oracle and the source server (it should have Oracle Database software installed - same version as the RDS database)

...

Second configuration screen

On the second configuration screen enter AWS parameters

...


AWS authentication

The AWS authentication can be either via access key or via IAM role.

AWS Credentials

Use this mode in case you have prepared a dedicated user in AWS and generated access key for it. How to do it

...

A secret key that pairs with your Access Key ID for request authentication and authorization. This key should be generated when creating a new Access Key ID and kept confidential.

IAM role

Use this mode if you have applied an IAM role to the source server. How to do it


AWS Backup Details

Backup Directory Name:

Specify the storage location within AWS for AWS Oracle directory on the RDS Oracle database backupsinstance.
E.g.: DATA_PUMP_DIR

Compress Backup (Y/N):

Option to compress backup files, which helps in reducing storage space. Choose 'Y' to enable compression, reducing backup size, or 'N' to store backups in their original size.

...

Provide the S3 bucket name used for storage that will be used to copy of Oracle backups in AWS. between RDS and the source server. How to create it
E.g. : rds-ora19


Local Mount Path:

The designated path for mounting the S3 bucket locallyon the source server. This allows agent access to to access the backups that are stored on the S3 bucket backup content.. The path should reference an existing, empty directory.
E.g. : /home/oracle/s3_backups


S3 Bucket Prefix (Subfolder).

Subfolder within the S3 bucket for organizing data, for managing different data categories efficiently. Use prefixes to differentiate data backup categories.

...

Click Next and continue to create Test Data Environment , as described in https://accelario.atlassian.net/wiki/spaces/DVPD/pages/2176975966/Oracle+Initial+Setup#To-create-a-test-data-environment-from-a-AWS-RDS-Oracle-GI%3A where the RDS backups will be stored. Do not use any slashes.

E.g. : ora19-folder

Third configuration screen

On the third configuration screen enter the connection details to the RDS Oracle database

...

Make sure that the RDS Oracle user will have the following permissions:

Code Block
GRANT dba TO acc_rman_user;
GRANT EXECUTE ON RDSADMIN.RDSADMIN_UTIL TO acc_rman_user;
GRANT EXECUTE ON RDSADMIN.RDSADMIN_RMAN_UTIL TO acc_rman_user;
GRANT EXECUTE ON RDSADMIN.RDSADMIN_MASTER_UTIL TO acc_rman_user;
GRANT EXECUTE ON RDSADMIN.RDSADMIN_S3_TASKS TO acc_rman_user;
GRANT EXECUTE ON rdsadmin.rds_file_util TO acc_rman_user;
GRANT READ, WRITE ON DIRECTORY DATA_PUMP_DIR TO acc_rman_user;

Forth configuration screen

On the forth configuration screen enter details of the staging database on the source server (beware that it is different from the RDS Oracle)

...

Some of the fields are not required, since they are derived automatically from previous screens

Test Data Environment (TDE)

...