Did integrating Data Domain into the Ready Node for SAP HANA meet our goals in protecting the SAP HANA database?
- Faster backups―Using Data Domain with DDBEA delivered faster backups. The first full data backup took 36.8 minutes while our second and third backups took, respectively, 12 minutes and 12.7 minutes, a time savings of 3X compared to our first backup.
- Minimal CPU usage―The additional average CPU usage never went above 3.3 percent on our Ready Node. The results show that DDBEA had a minimal CPU impact during our backups.
- Low network throughput―The first full data backup took an average of 507 MB/s, while the throughput dropped to 109 MB/s and 80 MB/s for the second and third backups. DDBEA client-side deduplication offers a substantial network throughput savings.
- Data Domain compression―The first full data backup provided a savings of 201 MB on the Data Domain appliance. However, the value of Data Domain compression is highlighted with the second and third backups, which took 81 MB and 62 MB respectively.
- Total compression ratio―The higher the TCR, the greater the increase in space savings on Data Domain. The first full data backup had a total compression ratio of 1.3, while the second and third backups showed the ongoing value of Data Domain with ratios of 19 and 30.4.
- Fast SAP HANA recovery―Dell EMC engineers were able to recover the 1.43 TB SAP HANA database in 23 minutes using Data Domain with SAP HANA Studio. Fast database recovery minimizes the impact of the unplanned outage to the organization.
Data Domain protection provides a substantial benefit to data protection operations because it can back up new SAP HANA databases quickly and provides long-term benefits by lowering network throughput and delivering a significant space savings through deduplication and compression.