![]() ![]() However, the principles of diversifying and spreading out your backup data and distancing it from production, still applies. It may be much less likely that you would lose your data stored in a public cloud environment due to the same reasons as an on-premises disaster. Public cloud environments such as Google’s G Suite environment and Microsoft’s Office 365, already have impressive mechanisms in place that may replicate your data behind the scenes between various nodes, pods, or other mechanisms that help to protect your data. You want to diversify the locations in which these are stored. The results of this could be catastrophic! By diversifying both the location and backup media types on which backup data is stored, you greatly reduce the risk of losing all copies of your backup data.īackups of cloud environments are very similar when considering the advantages of separating your production data from backup data. Well, the same disaster that may take down or destroy the production equipment and workloads would have equal risk of destroying the backups of the data as well. Why is this important? When we think about a disaster that may affect an entire site such as a natural disaster, you don’t want to have your only copy of your production backups stored at that site to only be stored at the same site as production. ![]() This rule helps to create both redundancy in backups as well as diversity in storage locations and media, which are data backup best practices. The 3-2-1 rule recommends having (3) backups stored on (2) different kinds of media, with at least (1) copy stored off-site. What is the 3-2-1 backup methodology that is used as a backup best practice? In thinking about cloud data backup best practices when it comes to backup methodologies, there is an industry-wide backup best practice methodology know as the 3-2-1 rule that helps to create resiliency and redundancy from a backup perspective. Efficient, Effective Use of Cloud-to-cloud Backup.Snapshot Backup – Use in Backup Technologies.Different Backup Types, Terms and Use Cases. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |