![为什么 SQL Server 将数百个文件写入系统卷信息(所有文件都具有相同的名称)](https://linux22.com/image/561552/%E4%B8%BA%E4%BB%80%E4%B9%88%20SQL%20Server%20%E5%B0%86%E6%95%B0%E7%99%BE%E4%B8%AA%E6%96%87%E4%BB%B6%E5%86%99%E5%85%A5%E7%B3%BB%E7%BB%9F%E5%8D%B7%E4%BF%A1%E6%81%AF%EF%BC%88%E6%89%80%E6%9C%89%E6%96%87%E4%BB%B6%E9%83%BD%E5%85%B7%E6%9C%89%E7%9B%B8%E5%90%8C%E7%9A%84%E5%90%8D%E7%A7%B0%EF%BC%89.png)
我注意到 SQL Server 有大量的写入\System Volume Information\{guid1}{guid2}
当发生这种情况时,Sql Server 正在做什么?
在上图中,sqlsevr.exe的写入IO有一半用于系统卷信息写入。
这是在 Windows 7 Profressional 中运行的。
这是输出vssadmin list shadows
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Writer name: 'Task Scheduler Writer'
Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
State: [1] Stable
Last error: No error
Writer name: 'VSS Metadata Store Writer'
Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
State: [1] Stable
Last error: No error
Writer name: 'Performance Counters Writer'
Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
State: [1] Stable
Last error: No error
Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {6584bb82-094c-4896-9be2-880ff9fb4d80}
State: [1] Stable
Last error: No error
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {669bba38-6066-4bf6-99af-8d312f66648d}
State: [5] Waiting for completion
Last error: No error
Writer name: 'SqlServerWriter'
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {48de0d7f-b7a0-457e-8bab-fefe2089286e}
State: [1] Stable
Last error: No error
Writer name: 'MSSearch Service Writer'
Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
Writer Instance Id: {d5c4ab16-b67e-4476-976b-4dba610084d8}
State: [5] Waiting for completion
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {5e334911-6049-4d29-8d33-d9b230b46ec2}
State: [5] Waiting for completion
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {e9dde2da-5cee-4d65-ac50-45387be4b600}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {9825b95f-94a0-438b-a359-4111aa308a60}
State: [1] Stable
Last error: No error
Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {d23d67d3-c421-4e9a-9965-123ec802bfcc}
State: [1] Stable
Last error: No error
输出如下(vssout list shadows
太长,无法在此发布)
答案1
这是 Windows 对您的 E 驱动器进行的卷影复制。
(这对于 SQL 服务器的数据/日志驱动器来说是不正常的,它会极大地增加 I/O)。
编辑:或者,好吧..至少将其安排到某个合理的时间,例如每个人上班前一小时。
答案2
闻起来像 VSS 快照。
您是否有软件(可能是备份)告诉 SQL Server 创建 VSS 快照?
答案3
我的猜测是您正在备份服务器本身,或者使用 VSS 感知备份程序(Windows 备份、SQL 维护计划或 SQL 数据库备份作业,或第三方 VSS 感知备份软件)备份 SQL Server 数据库。
答案4
您还可以禁用数据库文件文件夹中的卷影复制: http://msdn.microsoft.com/en-us/library/aa819132(v=vs.85).aspx