Web应用程序的SQL Azure故障转移/备份策略 [英] SQL Azure failover / backup strategy for web app

问题描述

我正在使用Azure&构建Web应用程序； SQL Azure.我正在设置它，所以每个组织都有自己的数据库.每个客户组织的流量较低至中等.

我正在考虑将SQL Azure数据同步作为故障转移/备份计划的一部分，以便在SQL Azure发生故障时，我的应用程序可以切换到本地SQL Server(只读模式)./p>

我还可以在本地进行所有备份，而不是在云中进行备份，这会产生成本.

• 一个问题可能是试图将多个数据库数据同步到本地 sql server(不确定数据库数量的限制) 可以同步到一台服务器)

• 带宽可能是个问题，但我可能每天只会同步一次.

有人用这种方法看到任何其他问题吗?

解决方案

数据同步还可以，但由于它不是事务同步模型，因此可能适合或可能不适合您的特定灾难恢复计划.

要考虑的一个选项是制作数据库副本:

CREATE DATABASE destination_database_name
    AS COPY OF [source_server_name.]source_database_name

然后，您可以从此副本创建备份，将备份存储在blob存储中，以及(可选)删除数据库副本.尽管由于第二个数据库的存在，这确实增加了额外的成本，但是如果在创建备份并将其存储到Blob存储之后删除数据库实例，则可以将成本降至最低(请记住，数据库每天都要摊销). >

由于您的备份随后将存储在blob存储中，因此您可以将多个备份保留在blob存储中，并在需要时将备份拉到本地服务器上.

I'm building a web app using Azure & SQL Azure. I'm setting it up so each organization has their own database. Low to moderate traffic per customer organization.

I'm thinking about using SQL Azure Data Sync as part of a failover/backup plan, so that if SQL Azure goes down, my app can switch over to my on-premises SQL Server (read-only mode).

I would also be able to do all of my backups on-prem, instead of in the cloud which could incur costs.

• One issue may be trying to data-sync multiple databases to my on-prem sql server (not sure what the limit is on the number of databases that can be synced to one server)

• Bandwidth may be an issue, but I'll probably only sync daily.

Does anyone see any other problems with this approach?

解决方案

Data Sync is ok, but may or may not be good for your particular DR plan since it's not a transactional sync model.

One option to consider is making a database copy:

CREATE DATABASE destination_database_name
    AS COPY OF [source_server_name.]source_database_name

Then you can create a backup from this copy, store the backup in blob storage, and (optionally) delete the database copy. While this does add an additional cost due to a second database being live, you can keep that cost to a minimum if you delete the database instance after creating a backup and storing to blob storage (remember that databases are amortized daily).

Since your backups would then be in blob storage, you could keep multiple backups in blob storage, and pull a backup to your on-premises server if needed.

这篇关于Web应用程序的SQL Azure故障转移/备份策略的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！