Claim 350 GB space from AWS RDS by Backup table from AWS RDS DB amd move to S3 bucket

Implementation Steps:

 1. Bring down the application and make sure no db sessions are running. --> COMPLETED

2. Take AWS snapshot of the database. -->COMPLETED – 15 Minutes

3. Purge the data from the Cloned database using truncate statement --> COMPLETED – Table1 took 3 seconds and Table2 took 11 seconds

3a.  Check the Cloned database and keep note of the current stats specifically in terms of rewrite speeds and memory and performance. à here we will be monitoring sessions count, blocking sessions and parallel AWS cloud watch for IO and CPU utilization --> COMPLETED – DB is good.

4. Bring UP the service portal application --> COMPLETED

5. Restore the database with a new name (cloned DB) from the snapshot taken in step3. --> COMPLETED – 20 Minutes

6. After restore DB, check S3 bucket is attached to cloned DB. Otherwise request team to integrate S3 bucket to Cloned DB --> COMPLETED

7. Export Audit Table backup in RDS using AWS procedures --> COMPLETED – Table1 took 3 hours, 38 minutes and Table2 took 2 hours 52 minutes.

8. Move RDS tables Backed up files to S3 bucket using AWS procedures --> COMPLETED table1 took 5 mins and table2 took 4 mins.

9. check the claimed space logically and physically --> COMPLETED – 260 GB space claimed.

10. Statsgather and index rebuild to reset num_rows and blocks.

Rollback:

 1.       Create new cloned RDS DB.

2.       Move backup file from S3 to new cloned RDS server.

3.       Import backup file data into new cloned RDS DB.

4.       Statsgather and index rebuild to reset num_rows and blocks.