It could be an operating system issue or even a network transfer issue that can lead to missing bits or bytes, then unexpected results. Software Errors: There will always be a bug here or there at any level of the software being engaged.Despite numerous precautions, there can always be a slip that can put you in a tight spot. Try running a drop table command and then stop it from replicating. Human Error: This one spreads quickly across replicas.This can lead to unavailability of the whole datacentre which leads into all running instances being unavailable, and would require the cluster to be rebuilt from a backup. Device Failure: This is a very common situation.Even if you have multiple replicas available it is very likely that the corruption can spread (much quicker than you think) across the replicas making them redundant for running any kind of production. Data Corruption: The most important and critical one.There can be many reasons for data loss, but here are a few that we all may have encountered in our careers: However, we never study our own environment, which is unique for everyone, for how a data loss can happen. The reason why we have backups or plan for backups is to prevent data loss and ensure continuity. In short, planning is key to backup and recovery. Every environment has its own challenges even if we have multiple database clusters in the same organizations, the backup requirements for may vary. We need to list the situations we might need to recover from and then discuss the available solutions. We don’t try to understand what situations led to those recommendations and how they might be different from what we’re facing. Backups are often taken based on the suggestions and recommendations of the person we believe knows best.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |