Understanding the Oracle Data Protection Gap
For many, snapshots are the go to data protection method for protecting Oracle databases. They can provide efficient, rapid protection from database corruption with high data integrity. But snapshot data protection has its limitations. First, snapshot copies can become corrupted if there is an application corruption issue. Secondly, snapshots will be lost if the storage system fails. And then of course there are retention limitations with maintaining snapshot data on primary storage as most systems only support around 250 snapshot copies. Therefore data has to be copied to another device that is independent of the primary storage device.
Consequently, many organizations have come to rely on a combination of point-in-time snapshots along with traditional backups to satisfy their various data protection requirements. The problem is that these backups often take too long to complete, can impact application performance and can be too far out of sync from the production data set to provide value in recovery. As a result, there is a gap in protection between snapshots and traditional backup that needs to be filled.
To read the complete article, CLICK HERE
NOTE: This column was originally published in the Storage Switzerland Weekly Newsletter.