备份 Windows Azure SQL Azure、Blob 和 SQL 的策略表数据
我很好奇其他开发人员如何成功实现在 SQL Azure、Azure 存储 Blob 和 Azure 存储表中备份 Windows Azure 数据的过程。
我知道有各种工具可以独立执行每个 Azure 服务的备份，但是有哪些有效的方法可以将所有这些都捆绑到一个执行所有备份和管理事务的系统中？
我考虑了两种可能的方法来完成此任务：
- 使用 CI 服务器（例如 Jenkins），可以设置计划作业来执行每个备份过程。在这种情况下，可能有 3 个计划作业，每个作业支持 1 个 Azure 服务，或者我可以使用 PowerShell 脚本之类的工具一次性备份所有 3 个 Azure 服务创建一个计划作业，
- 创建基于 Azure 计算的辅助角色来执行备份。单个辅助角色可以承担调用某些 PowerShell 脚本、第 3 方命令行工具或 Azure API 来备份 Azure 服务的任务。如果需要更高的性能，将来也可以扩展单一工作者角色。
如果您已经实施或考虑了其他选项，或者您对我上面描述的内容有一些反馈，我非常感谢对此进行一些讨论。有什么好处，有什么缺点……等等。
I am curious how other developers have successfully implemented a procedure for backing up Windows Azure data in SQL Azure, Azure Storage Blobs and Azure Storage Tables.
I know there are various tools out there that can perform backups of each Azure service independently but what would be some effective ways for tying this all together into a single system that performs all the backups and manages things?
I have thought about 2 possible ways to accomplish this:
- Use a CI Server (such as Jenkins) whereby scheduled jobs can be setup that perform each backup process. In this case there could be 3 schedule jobs each backing 1 Azure service OR I could have a single scheduled job using something like a PowerShell script to backup all 3 Azure services at once
- Create Azure Compute based worker roles to perform the backups. A single worker role can take on the task of invoking certain PowerShell scripts, 3rd party command line tools OR Azure APIs to backup the Azure services. That single worker role coud also be scaled out in the future if more performance was needed.
I'd very much appreciate some discussion about this if you have implemented or thought about other options or if you have some feedback for what I have described above. What are the benefits, what were the drawbacks... etc.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
无论哪种方式都会起作用。我最初可能会选择 CI 服务器，因为它的设置和维护速度会快得多。但它的扩展性或可靠性可能不如由 Azure Worker 角色负责。
Either way will work. I would probably go for the CI Server initially as it will be much quicker to set up and maintain. But it may not scale as well or be as reliable as having an Azure Worker role in charge of it.