通过SQL备份. SQL Server VSS写入 [英] SQL backup via. SQL Server VSS Write

问题描述

大家好.

我有一个安装了SQL Server实例的蔚蓝虚拟服务器.我已经在SQL Server代理中配置了一个备份例程，该例程或多或少地像这样运行.

每个星期天0100满额
除周日0100以外每天都是DIFF
每小时记录一次

但是在我的备份历史记录中，我每天都看到完整备份的新条目.

通常，physical_device_name列将显示到备份文件存储位置的路径.但是在这种情况下，我只会看到显示的值.

我希望它可以作为备份.由整个虚拟azure计算机的一般快照启动的卷影副本. Windows管理员指出只能启用或禁用计算机的快照，因此我们可能必须继续使用 这些庞大的数据库备份.

我想知道是否有一种方法可以防止Azure服务器的快照包括备份.

停止 SQL Server VSS编写器服务是否有帮助?

解决方案

您可以安全地停止VSS编写器服务，但这会导致备份失败.因此，在执行此操作之前，您需要咨询安装了此TP工具的任何人以进行快照备份.一定要通过还原来检查备份，因为某些工具的快照备份会摆弄 使用LSN链，可能会使其他备份失效.

Hi all. 

I have virtual server in azure with a SQL server instance installed on. I have configured a backup routine in the SQL server agent that runs more or less like this. 

FULL every sunday at 0100
DIFF every day except sunday at 0100
LOG every hour 

But in my backup history I see new entries of full backups daily. 

Normally the physical_device_name column would show a path to the destination where the backup file has been stored. But in this case I only see the values shown. 

I expect it to be a backup taken via. volume shadow copy initiated by the general snapshot of the entire virtual azure machine. The windows admin states that the snapshot of the machine can only be enabled or disabled, and therefore we might have to live with these rouge backups of the databases. 

I am wondering if there is a way to prevent the snapshot of the Azure server to include the backup. 

Would it help to stop the SQL Server VSS Writer service ? 

解决方案

You can safely stop VSS writer service but that would cause backups to fail. So before doing that you need to consult whoever has installed this TP tool for snapshot backup. Do check your backups by restoring because snapshot backups for some tools fiddles with LSN chain and may render other backups useless.

这篇关于通过SQL备份. SQL Server VSS写入的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！