超过1000个以上的分片单租户数据库的备份 [英] Backup of Sharded Single-Tentant Databases over 1000+

问题描述

如果存在单个租户类型为2000+的分片数据库，则这是建议的最佳备份和还原策略.除了Azure备份中的构建之外，我们还需要每日备份策略

Which is the best suggested backup and restore strategy if there is a single tentant type 2000+ sharded databases. A daily backup strategy is what we required other than the build in Azure Backup

当尝试使用Databae Import/Export RestAPI https://docs.microsoft.com/zh-cn/rest/api/sql/databases%20-%20import%20export/export

When tried out with Databae Import/Export RestAPIhttps://docs.microsoft.com/en-us/rest/api/sql/databases%20-%20import%20export/export

Powershell/.Net应用程序中的代码有时需要花费很长时间才能完成.其余api方法的问题是Microsoft仅在队列中添加备份请求并仅处理该请求，因此无法确保每日备份，因为somtimes MS会启动该备份请求. 仅在第二天备份(取决于队列).

from a Powershell/.Net application somtimes it taks long hours to complete. The problem with this rest api approach is Microsoft adds backup requests in a queue and process only, so it is not possible to ensure a daily backup, because somtimes MS starts the backup only by next day(Depending on the queue).

如果要对所有分片数据库进行每日备份，您有什么建议的建议策略吗?

Do you have any suggestions which is the recommended strategy if want to have a daily backup of all sharded database?

在此先感谢

推荐答案

我很好奇为什么会有问题.

I'm curious why this would be a problem.

我不知道备份请求可能要花24个小时才能完成，所以我理解了这个问题.

I didn't know that the backup requests might take 24 hours to fill, so I understand the issue.

但是，由于Azure数据库始终处于打开状态，并且可以通过时间点还原进行访问，因此安全性和安全性还不够，以至于您只能等待备份吗?

However, since Azure databases are Always-On and available via point-in-time restores, isn't that safe enough and good enough so you can just wait for your backups?

乔什

这篇关于超过1000个以上的分片单租户数据库的备份的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！