Often, backup strategies are inconsistent, poorly documented, and misunderstood. This misunderstanding stems from widespread expectations that backups must exist, must be readily available at a moment’s notice, and must be restored immediately, regardless of size. When backup and DR practices are not documented, management will believe that not only do they exist, but that they will be good, consistent, and that they are current (possibly up to the minute). It is therefore critical to document your organization’s backup strategy and practices.
Ultimately, you should protect the data according to business demands. However, consistency checking puts additional strain on both infrastructure and personnel. You must scale these resources according to the acceptable level of data loss based on business requirements.
Developing a sound backup and data retention procedures facilitates the safety of data, compliance with business needs for point-in-time recovery, and potentially regulatory compliance.
Most database technology includes the ability to restore after a disaster. As such, the performance of the database depends on understanding the way in which logging, and backups operate and impact performance. Improperly configuring backups can result in unanticipated outages and even loss of data if backups are corrupt.
To achieve the highest level of reasonable data retention and silent failure prevention, consider retaining two copies of the data at two geographically distinct locations. Perform weekly MD5 hash checks on the data primary set and monthly checks of the secondary. You can automate these tests and run them in addition to the initial consistency checks performed when the data was created.