数据库备份/恢复过程 [英] Database Backup/Restore Process
问题描述
sql server上的大型数据库或数据库集合的备份和恢复过程对于灾难和灾难恢复非常重要。恢复目的。然而，我没有找到一个可靠的解决方案，将保证整个过程尽可能高效，100％可靠，易于维护和可配置跨多个服务器。
The backup and restore process of a large database or collection of databases on sql server is very important for disaster & recovery purposes. However, I have not found a robust solution that will guarantee the whole process is as efficient as possible, 100% reliable and easily maintainable and configurable accross multiple servers.
Microsft的维护计划似乎不足。我使用的最佳解决方案是手动创建多个作业，每个数据库在源服务器（备份）和目标服务器（恢复）上运行许多步骤。作业使用存储过程进行备份，复制&恢复。此操作每天运行一次（完全备份/还原），并每5分钟（日志传送）进行日内。
Microsft's Maintenance Plans doesn't seem to be sufficient. The best solution I have used is one that I created manually using many jobs with many steps per database running on the source server (backup) and destination server (restore). The jobs use stored procedures to do the backup, copying & restoring. This runs once a day (full backup/restore) and intraday every 5 mins (transaction log shipping).
虽然我目前的流程工作，并通过电子邮件报告任何工作失败，我知道整个过程是不是很可靠，不能轻易地维护/配置在所有的服务器上非数据库管理员没有对过程的深入了解。
Although my current process works and reports any job failures via email, I know the whole process isn't very reliable and cannot be easily maintained/configured on all our servers by a non-DBA without having in-depth knowledge of the process.
我想知道其他人是否有同样的备份/恢复过程，以及其他人如何克服这个问题。
I would like to know if others have this same backup/restore process and how others overcome this issue.
推荐答案
您的问题的关键部分是备份解决方案由非DBA管理的能力。因为备份脚本需要T-SQL知识。
The key part of your question is the ability for the backup solution to be managed by a non-DBA. Any native SQL Server answer like backup scripts isn't going to meet that need, because backup scripts require T-SQL knowledge.
因为这个原因，你想向前看第三方解决方案像米奇小麦提到的。我为Quest（LiteSpeed的制造商）工作，所以当然我偏偏那个 - 很容易展示给非DBA。在我离开我的最后一家公司之前，我有一个十分钟的会议，向系统管理员和开发人员展示LiteSpeed控制台如何工作，就是这样。他们以前没有调用过。
Because of that, you want to look toward third-party solutions like the ones Mitch Wheat mentioned. I work for Quest (the makers of LiteSpeed) so of course I'm partial to that one - it's easy to show to non-DBAs. Before I left my last company, I had a ten minute session to show the sysadmins and developers how the LiteSpeed console worked, and that was that. They haven't called since.
另一种方法是使用与商店其他部分相同的备份软件。 TSM，Veritas，Backup Exec和Microsoft DPM都具有SQL Server代理，可让您的Windows管理员以不同程度的易用性管理备份过程。如果你真的想要一个非DBA来管理它，这可能是最简单的方法来做到这一点，虽然你牺牲了许多SQL特定的备份工具给你的性能。
Another approach is using the same backup software that the rest of your shop uses. TSM, Veritas, Backup Exec and Microsoft DPM all have SQL Server agents that let your Windows admins manage the backup process with varying degrees of ease-of-use. If you really want a non-DBA to manage it, this is probably the most dead-easy way to do it, although you sacrifice a lot of performance that the SQL-specific backup tools give you.
这篇关于数据库备份/恢复过程的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
