Migrate to Exadata Database

1. From the AWS console, navigate to Storage Gateway.
2. Click on the Create gateway button.
3. In the Set up gateway section, enter the following information.
   1. Enter a descriptive name in the Gateway name field. The name must be between 2 and 255 characters and cannot include a slash (\ or /).
   2. From the dropdown list, select the Gateway time zone. Choose the local time zone based on where you want to create your gateway.
   3. From the Gateway options section, choose the Amazon S3 File Gateway option.
   4. From the Platform options section, choose the Amazon EC2 as the host platform.
   5. Choose the Use default settings if you want to create an EC2 instance with default settings. Alternatively, you can click on Customize your settings to select the EC2 instance size and shape .
   6. From the dropdown list, select the Virtual private cloud (VPC) network.
   7. From the dropdown list, select the VPC subnet.
   8. From the Key pair dropdown list, select the existing key pair. If you do not have an existing one, select the Create new key pair link to create one.
   9. Select the Launch instance button to launch the EC2 instance with default settings. If you select the Customize your settings option, the instance will be launched in EC2 instance console.
   10. Select the Next button to proceed.
   
4. In the Connect to AWS section, enter the following information.
   1. From the Connection options section, choose the IP address option.
   2. The IP address automatically populates from the previous step where you created an EC2 instance.
   3. From the Service endpoint section, choose either the Publicly accessible option or VPC hosted option.
   4. Select the Next button to continue the creation process or select the Previous button to go back.
   
5. In the Activate gateway section, enter the following information.
   1. Review the Gateway details and Connection details, and then click on the Activate gateway button to continue the creation process or select the Previous button to go back.
   
6. In the Configure gateway section, enter the following information.
   1. From the Configure cache storage section, allocate one or more disks.
   2. From the CloudWatch log group section, choose either the Create a new log group option or the Use an exsiting group option. The Deactive logging option is not recommended.
   3. From the CloudWatch alarms section, choose the Create Storage Gateway's recommended alarms option.
   4. Based on your requirements, you can add Tags by selecting the Add new tag button.
   5. Select the Configure button.
   
7. Once your gateway is created, the status will change to Running.

1. From the AWS console, navigate to Storage Gateway.
2. From the Storage resources section, select File shares.
3. Select the Create file share button, and then complete the following substeps.
   1. From the Create file share page, select the Gateway that you created previously.
   2. From the File share protocol section, choose the NFS option.
   3. From the S3 bucket dropdown list, select your existing S3 bucket. If you do not have one, you can create one by clicking the Create a new S3 bucket button.
   4. Select the Create file share button.
   

1. Use the following bash commands in the database EFS instance and mount the S3 bucket as NFS mount points. The NFS parameters used are specific to Oracle AI Database and RMAN.
2. Create a directory with the required mount name. For example, the s3_mount directory was created.
3. Run the following command.

   mount -t nfs -o nolock,hard [ip-address]:/demo19c-backup /s3_mount/

You can now use the NFS file share that is mounted on the database server to take backups on either using Oracle Data Pump or RMAN. For this example, RMAN is being used.

Oracle Recovery Manager provides a robust utility for backing up Oracle AI Databases. When storing backups in Amazon S3, ensure that the db_recovery_file_dest parameter is set to the NFS mount point established in previous steps. Additionally, to enforce a strict storage limit, define the db_recovery_file_dest_size parameter, which controls the maximum space allocated for files within the recovery destination. For more information about RMAN backup types and best practices, see RMAN basic concepts.

1. Set the parameter db_recovery_file_dest to point the NFS share mounted in the previous steps, and define tge db_recovery_file_dest_size by using the following command.

   alter system set db_recovery_file_dest='' scope=both;
   alter system set db_recovery_file_dest_size='<size limit for nfs share mount point>' scope=both;

2. This is an example output after setting up the parameters db_recovery_file_dest and db_recovery_file_dest_size.

   alter system set db_recovery_file_dest='/s3_mount' scope=both;
   alter system set db_recovery_file_dest_size='1000G' scope=both;

3. Run RMAN backup on the database server using the following command:

   rman target / <<EOFrun {CONFIGURE DEFAULT DEVICE TYPE TO DISK;CONFIGURE DEVICE TYPE DISK PARALLELISM 3;BACKUP DATABASE PLUS ARCHIVELOG;}EOF

For Oracle AI Database backups utilizing parallel processing via RMAN or Data Pump, configuring multiple cached disks in Amazon S3 File Gateway significantly improves performance. Instead of relying on a single disk, distributing the workload across multiple cache disks enhances throughput by leveraging parallelism, optimizing storage efficiency and backup speed.

All the backup files are uploaded into Amazon S3 in the background as the Storage Gateway writes the files to the shares. Transport Layer Security encryption protects the data while in transit and Content-MD5 headers are used for data integrity.

Depending on the backup file size and network bandwidth between your Amazon S3 File Gateway and AWS, the backup file can take time to transfer from the local cache of Amazon S3 File Gateway to Amazon S3 bucket. You can use CloudWatch metrics to monitor the traffic.

1. Follow the steps from above to create a S3 file gateway in the AWS VPC which is peered to the Exadata using ODB peering.
2. When you create the file share make sure you are using the same S3 bucket that you have used for the RMAN backups.

1. Enter the following bash commands in the database EC2 instance and mount the S3 bucket as NFS mount points. The NFS parameters used are specific to Oracle AI Database and RMAN.
2. Create a directory with the required mount name in this case we created the s3_mount directory.

   mount -t nfs -o nolock,hard [ip-address]:/demo19c-backup
       /s3_mount/

3. After the NFS is mounted, the RMAN backup will be available on Exadata Database.

Using RMAN restore, databases can be restored on the same server or different server. RMAN backups can be used for disaster recovery scenarios across different regions in AWS as well.

1. Use the following command to complete the restore on Exadata Database:

   sqlplus / as sysdba<<EOFstartup mountexitEOF rman target / <<EOFrun {CONFIGURE DEFAULT
         DEVICE TYPE TO DISK;CONFIGURE DEVICE TYPE DISK PARALLELISM 3;RESTORE DATABASE;RECOVER
         DATABASE;alter database open;}EOF

1. Run the validation steps to ensure the RMAN restore completed successfully.

   Table 1-1 Validation Commands

   Check Area	Command	Expected Result
   RMAN Log	-	No errors, restore complete
   DB Status	select status from v$instance;	OPEN
   Datafiles	select * from v$datafile;	All ONLINE
   Tablespaces	select * from dba_tablespaces;	All ONLINE
   Alert Log	Tail the alert log	Opened successfully
   Application Data	select count(*) from known tables	Returns rows