...
A source host is a server that hosts the source databases. A test data environment includes access definition to one source database and a GI. This section describes how to create and manage a Source Host and a Test Data Environment.
There are 4 supported A Golden Image (GI) types:
Live GI
RMAN GI
RMAN Standby GI
RDS AWS RMAN
refers to a pre-configured template of a database environment. This template encapsulates a snapshot of the database including its schema, data, configurations, and associated applications. It serves as a master copy from which multiple instances of the database can be rapidly deployed, ensuring consistency, reliability, and quick scalability across different virtual environments.
Supported types of Golden Images for Oracle database
Each type of Golden Image for Oracle databases serves a specific set of needs, from real-time replication to disaster recovery and cloud-based management. The choice of GI should align with the operational objectives and the specific environment, whether it’s on-premises or cloud-based like AWS RDS.
1. Live Golden Image (Live GI)
A Live GI is a real-time replica of a production database, mirroring its current state including data and configurations.
2. RMAN Golden Image (RMAN GI)
An RMAN GI is a backup-based image created using Oracle Recovery Manager (RMAN). It includes all critical components of the database, such as data files, control files, and archived redo logs, captured at a specific point in time.
3. RMAN Standby Golden Image (RMAN Standby GI)
This GI is a variant of the RMAN GI, specifically designed for setting up Oracle standby databases. While it also uses RMAN, it includes additional elements necessary for creating and managing a standby database environment, such as standby redo logs and specific configurations for data guard.
4. RDS AWS RMAN Golden Image
The RDS AWS RMAN GI is exclusively for Oracle databases hosted on Amazon RDS. It combines the features of RMAN with optimizations for AWS cloud infrastructure.
To open the Source work area:
...
4. To save your changes, click Modify.
AWS RDS RMAN GI
Please enter AWS parameters during TDE creation.
...
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
Access Key ID:
This is a unique identifier provided by AWS, for accessing all AWS services. It's used for authentication. Obtain it from the IAM settings in your AWS account.
Secret Access Key:
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 Oracle directory on the RDS Oracle instance.
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.
AWS S3 Bucket Parameters
Name:
Provide the S3 bucket name that will be used to copy of Oracle backups 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 on the source server. This allows to access the backups that are stored on the S3 bucket. The path should reference an existing, empty directory.
E.g. : /home/oracle/s3_backups
S3 Bucket Prefix (Subfolder).
Subfolder within the S3 bucket 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)
...