Identificando e resolvendo erros com serviços do Volume de Copia de Sombra (VOLUME SHADOW COPY).
Para identificarmos o problema, podemos usar o comando vssadmin.
Sintaxe do vssadmin:
vssadmin list {shadows [/set= [shadow copy set GUID]] | writers | providers}
vssadmin delete shadows /for=<ForVolumeSpec> [/oldest | /all | /shadow=<ShadowID>] [/quiet]
Visualizando o problema:
Para listar os serviços, podemos utilizar o comando vssadmin list writers.
C:Windowssystem32>vssadmin list writers
vssadmin 1.1 – Volume Shadow Copy Service administrative command-line
(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: ‘System Writer’
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {86ed6b7e-4533-4b61-ad77-8908ae546093}
State: [7] Failed
Last error: Timed out
Writer name: ‘IIS Config Writer’
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id: {b3b29c93-c7e5-4128-94ea-42884d22b802}
State: [7] Failed
Last error: Timed out
Writer name: ‘ASR Writer’
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {60ea7ad7-3a15-4457-be25-2f01c0fae980}
State: [7] Failed
Last error: Timed out
Writer name: ‘WMI Writer’
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {7f853611-7476-4a79-9e7a-42999c869034}
State: [7] Failed
Last error: Timed out
Writer name: ‘Registry Writer’
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {fa8a22fc-3fc6-4ec2-bed5-a17434d58979}
State: [7] Failed
Last error: Timed out
Writer name: ‘BITS Writer’
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {c188c55e-929c-4110-9edb-919ea5a0e708}
State: [1] Stable
Last error: No error
Writer name: ‘COM+ REGDB Writer’
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {d3342d08-8020-4c65-8b96-bbcfaad86a39}
State: [7] Failed
Last error: Timed out
Writer name: ‘Shadow Copy Optimization Writer’
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {13af788a-d807-4e48-958c-8a2cae38add4}
State: [7] Failed
Last error: Timed out
Writer name: ‘Microsoft Exchange Writer’
Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
Writer Instance Id: {f3583bf7-0517-411c-adb5-a460c81928a1}
State: [7] Failed
Last error: Retryable error
Writer name: ‘IIS Metabase Writer’
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {77d700ec-b9f0-4e4d-9bae-b97c60e4552f}
State: [7] Failed
Last error: Timed out
Resolvendo o problema:
Podemos notar que o State de alguns serviços se encontra Failed.
Utilizando a tabela abaixo, podemos identificar o serviço responsável pelo Writer Name. Com base nos dados, basta acessar o MMC Serviços (services.msc) e reiniciar os serviços.
VSS Writer | Service Name | Service Display Name |
---|---|---|
ASR Writer | VSS | Volume Shadow Copy |
BITS Writer | BITS | Background Intelligent Transfer Service |
COM+ REGDB Writer | VSS | Volume Shadow Copy |
DFS Replication service writer | DFSR | DFS Replication |
IIS Config Writer | AppHostSvc | Application Host Helper Service |
IIS Metabase Writer | IISADMIN | IIS Admin Service |
Microsoft Exchange Writer | MSExchangeIS | Microsoft Exchange Information Store |
Microsoft Hyper-V VSS Writer | vmms | Hyper-V Virtual Machine Management |
Registry Writer | VSS | Volume Shadow Copy |
Shadow Copy Optimization Writer | VSS | Volume Shadow Copy |
System Writer | CryptSvc | Cryptographic Services |
WMI Writer | Winmgmt | Windows Management Instrumentation |
Latest posts by Flavio Ferreira (see all)
- Esse é o fim para o Wiki do Microsoft Teams. E está proximo! - 17 de maio de 2023
- WEEK 365 - 24 de janeiro de 2023
- Treinamentos e Eventos Microsoft Gratis - 12 de janeiro de 2023
- MVPConf LATAM 2021 - 10 de dezembro de 2021
- Fui voluntário no BizAppsLATAMSummit - 3 de dezembro de 2021
0 comentário