将 SQL Server 备份到 Rackspace 云文件

发布于 2024-12-10 05:36:26 字数 57 浏览 0 评论 0原文

从 SQL 进行每日或每小时备份,然后将它们自动上传到 Racksapce 云文件的最佳方法是什么?

What is the best way to take daily or hourly backups from SQL and then have them automatically upload to Racksapce Cloud Files.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

吃兔兔 2024-12-17 05:36:26

您可以执行每日完整备份和定期差异备份,但假设您的数据库使用完整恢复模式,您可能需要考虑使用事务日志备份。通过日志备份,您可以每天或每周发送一次完整备份,然后每小时发送一次日志备份。每次发送新的完整备份时,您都可以删除所有旧的日志备份。只要您有完整备份和所有日志,您就可以将数据恢复到最后一个日志点;您基本上会在不应用日志的情况下进行日志传送。

您还需要决定如何从 rsync/robocopy/其他方式获取文件,并确保您有足够的带宽来跟上传输速度。并确保在失败时有一些通知流程。

如果您正在寻求灾难恢复,请记住更多地关注恢复计划而不是备份计划。估计时间要求并记录恢复过程需要在灾难发生之前完成和实践,而不是在灾难发生期间。

You could do daily full backups and periodic differential backups, but you may want to look at using transaction log backups instead, assuming your database is using FULL recovery mode. With log backups you could send a full backup once a day or week, then send log backups every hour. Each time you send a new full backup, you could delete all the older log backups. As long as you have a full backup and ALL the logs, you can restore the data up to the point of the last log; you would basically be doing log shipping without applying the logs.

You'll also need to decide how to get the files there, rsync/robocopy/other, and make sure you have the bandwidth to keep up with the transfers. And make sure you have some notification process if it fails.

If you're looking for disaster recovery, remember to focus on the the plan to restore more than the plan to backup. Estimating the time requirements and documenting the process to restore needs to be done and practiced before a disaster, not during.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文