Home > Storage > PowerFlex > White Papers > Dell APEX Block Storage for AWS: Backup and Recovery using DDVE and DD Boost Oracle RMAN Agent > Backup time and efficiency tests using Oracle RMAN Agent
In this test case, we instantiated the Amazon EC2 c5n.9xlarge instance type that is used as the PowerFlex SDC instance with six PowerFlex volumes. The Amazon EC2 i3en.9xlarge instance type with NVMe SSDs is used as the PowerFlex SDS instance. The Amazon EC2 compute optimized instance running Oracle database is populated with 1 TB of application data. The initial backup of Oracle database is 1 TB in size, and subsequent backups included a data change in a range of 10 percent (approximately 100 GB).
We obtained test results under the following categories:
The following figure shows the duration times of the four-backup procedure. The initial backup of the full database took 109 minutes to complete reading the entire volumes. The subsequent incremental database backup completed in 28 minutes because it includes only 10 percent of data change.
Figure 26. Backup time using Oracle RMAN agent
The following figure shows that the initial backup of the Oracle database used 60 percent of the DD system on average. The initial backup is the most resource-intensive because the entire Oracle database data is transferred and protected on the DD system. The DD system CPU usage fell in all subsequent incremental backups to a range between 45 to 50 percent. This change occurs because the Oracle RMAN agent processes only the unique data in each incremental backup, freeing up CPU cycles for other operations.
Figure 27. CPU usage on the DD system
The following figure shows that the initial Oracle database full backup network bandwidth was on average 220 Mbps. Because all the data had to be sent to the DD system, the entire Oracle database data was considered as unique data to be protected on the DD system. The subsequent incremental backup network bandwidth falls significantly, by a range between 160 Mbps to 170 Mbps, because the Oracle database data was already protected and only the unique data had to be transferred.
Figure 28. Network bandwidth on the DD system using Oracle RMAN agent
The following figure shows that the initial size of the Oracle database backup on a DD system was 1125 GB. After the Oracle database data transfer to the DD system, physical storage consumption was reduced to 406 GB due to deduplication and compression algorithms. After the subsequent incremental database backup transfer to the DD system, physical storage consumption was reduced to 56 GB. The amount was lower than the initial backup because deduplication became the dominant factor for the incremental backups.
Figure 28. DD system pre-compression and post-compression values
The following figure shows that the initial Oracle database full backup consists of unique data and had the lowest total compression factor (2.8x). The subsequent incremental backups were similar in the amount of unique data and compression factor, and their reduction percentage is small.
Figure 30. Deduplication and compression savings