需要建议：SQL Server 2008 Express 的冷备份？
为运行单个数据库的 SQL Server Express 实例实现冷备份服务器有哪些选择？
我有一个正在生产中的 SQL Server 2008 Express 实例，它当前代表我的应用程序的单点故障。我的安装中还有第二个物理盒子，目前什么也没做。我想以某种方式将我的数据库近乎实时地复制（少量数据丢失是可以接受的）到第二个盒子。数据库很小，资源利用率很低。
如果生产服务器挂掉了，我会手动重新配置我的应用程序以指向备份服务器。
虽然 Express 不支持日志传送，但我认为我可以手动编写一个穷人版本的脚本，其中我使用批处理文件来获取日志并通过网络复制它们，并以 5 分钟的间隔将它们应用到第二个服务器。
有谁对这在技术上是否可以实现，或者是否有更好的方法来完成我想做的事情有任何建议？
请注意，我希望避免为 SQL Server 的完整版本付费并配置镜像，因为我认为这对于该应用程序来说是一种过度的杀伤力。我知道其他数据库平台可能会提供合适的选项（例如 MySQL 集群），但出于本次讨论的目的，我们假设我们必须坚持使用 SQL Server。
What are my options for achieving a cold backup server for SQL Server Express instance running a single database?
I have an SQL Server 2008 Express instance in production that currently represents a single point of failure for my application. I have a second physical box sitting at the installation that is currently doing nothing. I want to somehow replicate my database in near real time (a little bit of data loss is acceptable) to the second box. The database is very small and resources are utilized very lightly.
In the case that the production server dies, I would manually reconfigure my application to point to the backup server instead.
Although Express doesn't support log shipping, I am thinking that I could manually script a poor man's version of it, where I use batch files to take the logs and copy them across the network and apply them to the second server at 5 minute intervals.
Does anyone have any advice on whether this is technically achievable, or if there is a better way to do what I am trying to do?
Note that I want to avoid having to pay for the full version of SQL Server and configure mirroring as I think it is an overkill for this application. I understand that other DB platforms may present suitable options (eg. a MySQL Cluster), but for the purposes of this discussion, let's assume we have to stick to SQL Server.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我还建议使用基于脚本的日志传送。毕竟，这就是日志传送的开始方式。您所需要的只是一个基于时间的代理来安排脚本（即任务计划程序< /a>），以及智能（er）文件副本（
I would also advise for a script based log shipping. After all, this is how log shipping started. All you need is a time based agent to schedule the scripts (ie. Tasks Scheduler), and a smart(er) file copy (robocopy).