简体繁体 English

为什么要备份本地或地理冗余的azure存储帐户？

[英]Why backup azure storage account if it's locally or geo redundant?

原文 2016-02-26 22:37:37 2 2 azure/ backup/ azure-storage/ azure-storage-blobs

So I've come across this AzCopy tool, and multiple tutorials that say it's good for backing up my storage blobs and whatnot. 因此，我遇到了这个AzCopy工具，还有多个教程说它们对备份存储Blob和其他内容非常有用。

Isn't Azure Storage automatically backed up? Azure存储不是自动备份吗？ Isn't that what locally redundant means? 这不是本地冗余的意思吗？

I just want to make sure I'm not missing something and putting my application in jeopardy by not running some external backup. 我只想确保我不会丢失任何东西，并且通过不运行某些外部备份来使我的应用程序处于危险之中。

2 个解决方案

Redundancy is different from back-ups. 冗余与备份不同。 Redundancy means that all your changes are replicated to another location. 冗余意味着您的所有更改都将复制到另一个位置。 In case of a failover your slave can theoretically function as a master and serve the (hopefully) latest state of your file system. 在发生故障转移的情况下，从站理论上可以充当主站，并服务（希望）文件系统的最新状态。 However, the fact that everything is replicated also means that your accidental delete actions, file corruptions, etc. are replicated. 但是，复制所有内容的事实也意味着复制了您的意外删除操作，文件损坏等。 Back-ups are meant to prevent this. 备份是为了防止这种情况。 In case you accidentally mess something up and perform some delete requests, you still have the back-ups and you can usually go back to any point in time (if you made a backup at that time of course). 万一您不小心弄乱了某些东西并执行了一些删除请求，您仍然可以进行备份，并且通常可以回到任何时间点（当然，如果您当时进行了备份）。

And of course it's not a bad idea to be not fully dependent on Azure. 当然，不完全依赖Azure也不是一个坏主意。

The most important thing about any backup policy is that before you create it you decide what you are protecting against, and what sort of data are you backing up. 任何备份策略最重要的是，在创建备份策略之前，您要确定要保护的对象以及要备份的数据类型。

If the data you backing up is an offsite backup of working data. 如果您备份的数据是工作数据的异地备份。 If access to that data is restricted to admin personnel and they all know what the data is. 如果只有管理员可以访问该数据，并且他们都知道数据是什么。 Then replication could well be all you need to protect from a hardware failure on Azure. 这样，复制就可以成为保护Azure上硬件故障所需的全部。

If however you are backing up customer data, or file data that fred in accounts randomly deletes when he falls asleep at the keyboard then you have a different threat model and you should consider your backups accordingly. 但是，如果您正在备份客户数据，或者帐户中流失的文件数据在他睡在键盘上时被随机删除，那么您将具有不同的威胁模型，应相应考虑备份。

Where you back it up is very much a matter of personal requirements and philosophy. 备份的位置在很大程度上取决于个人要求和理念。 I have known customers who will keep backups on Azure and AWS (even though their only compute workload was Azure) If in your threat model you want to protect against MS going bust and selling all of their kit on ebay one morning, then it makes sense to back up elsewhere. 我知道有一些客户会在Azure和AWS上保留备份（即使他们唯一的计算工作负载是Azure）。如果在您的威胁模型中，您想要防止MS崩溃并有一天早上在ebay上出售其所有套件，那么这很有意义备份到其他地方。 Or you can decide that you trust Azure to go bust and just split data across multiple regions. 或者，您可以决定相信Azure可以破产，而只是将数据拆分到多个区域。