J
JoyCThomas
We recently expanded one of our Volumes to 64 TB. Backups are ( Veeam Backups) failing on that volume with VSS error.
Backups were OK till we expanded the drive. Also, backups are OK for the other volumes ( 20-30 TB) on the same system. So.. no issues with Veeam.
We are getting following error in the Application log.
Log Name: Application
Source: VSS
Date: 5/29/2019 3:30:36 AM
Event ID: 8194
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: xxxxxx
Description:
Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005, Access is denied.
. This is often caused by incorrect security settings in either the writer or requestor process.
Operation:
Gathering Writer Data
Context:
Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Name: System Writer
Writer Instance ID: {a761636d-65ce-4d75-87b2-f5110f5580b6}
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="VSS" />
<EventID Qualifiers="0">8194</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2019-05-29T07:30:36.000000000Z" />
<EventRecordID>124494</EventRecordID>
<Channel>Application</Channel>
<Computer>xxxx</Computer>
<Security />
</System>
<EventData>
<Data>0x80070005, Access is denied.
</Data>
<Data>
Operation:
Gathering Writer Data
Context:
Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Name: System Writer
Writer Instance ID: {a761636d-65ce-4d75-87b2-f5110f5580b6}</Data>
<Binary>2D20436F64653A20575254575254494330303030313239352D2043616C6C3A20575254575254494330303030313234392D205049443A202030303030303434382D205449443A202030303030333931322D20434D443A2020433A5C57696E646F77735C73797374656D33325C737663686F73742E657865202D6B204E6574776F726B53657276696365202020202020202D20557365723A204E616D653A204E5420415554484F524954595C4E4554574F524B20534552564943452C205349443A532D312D352D3230</Binary>
</EventData>
</Event>Log Name: Application
Source: VSS
Date: 5/28/2019 11:11:07 PM
Event ID: 12289
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: xxxxxx
Description:
Volume Shadow Copy Service error: Unexpected error DeviceIoControl(\\?\Volume{c4e61cad-42e7-4095-9c39-b0f93aab7285} - 0000000000000274,0x0053c008,000000E54EAF3910,0,000000E54EAF08E0,4096,[0]). hr = 0x8007001f, A device attached to the system is not functioning.
.
Operation:
Processing EndPrepareSnapshots
Context:
Execution Context: System Provider
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="VSS" />
<EventID Qualifiers="0">12289</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2019-05-29T03:11:07.000000000Z" />
<EventRecordID>124474</EventRecordID>
<Channel>Application</Channel>
<Computer>xxxxx</Computer>
<Security />
</System>
<EventData>
<Data>DeviceIoControl(\\?\Volume{c4e61cad-42e7-4095-9c39-b0f93aab7285} - 0000000000000274,0x0053c008,000000E54EAF3910,0,000000E54EAF08E0,4096,[0])</Data>
<Data>0x8007001f, A device attached to the system is not functioning.
</Data>
<Data>
Operation:
Processing EndPrepareSnapshots
Context:
Execution Context: System Provider</Data>
<Binary>2D20436F64653A20494E434943484C4830303030303532312D2043616C6C3A2053505251534E504330303030303137342D205049443A202030303030343235322D205449443A202030303030333031322D20434D443A2020433A5C57696E646F77735C53797374656D33325C737663686F73742E657865202D6B2073777072762D20557365723A204E616D653A204E5420415554484F524954595C53595354454D2C205349443A532D312D352D313820</Binary>
</EventData>
</Event>
System Log showing following error.
Log Name: System
Source: volsnap
Date: 5/28/2019 11:11:07 PM
Event ID: 5
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: xxxxxx
Description:
The shadow copy of volume E: could not be created due to insufficient non-paged memory pool for a bitmap structure.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="volsnap" />
<EventID Qualifiers="49158">5</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2019-05-29T03:11:07.154365500Z" />
<EventRecordID>813851</EventRecordID>
<Channel>System</Channel>
<Computer>xxxxxx</Computer>
<Security />
</System>
<EventData>
<Data>\Device\HarddiskVolumeShadowCopy147</Data>
<Data>E:</Data>
<Binary>000000000200300000000000050006C001000000010000C07B000000000000000000000000000000</Binary>
</EventData>
</Event>
I have read some Microsoft articles, which says the Volume shadow copy does not work with Volumes more than 64 TB.
Based on that, our only option is to Shrink the volume to 63 TB or 62 TB. We do have the space to shrink the volume.
Anybody have tried to shrink a volume at that size? How long does it take, say .. to shrink by 2 TB.
Any I/O performance impact? Can we attempt to do it during our normal business hours?
Any suggestions?
Continue reading...
Backups were OK till we expanded the drive. Also, backups are OK for the other volumes ( 20-30 TB) on the same system. So.. no issues with Veeam.
We are getting following error in the Application log.
Log Name: Application
Source: VSS
Date: 5/29/2019 3:30:36 AM
Event ID: 8194
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: xxxxxx
Description:
Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005, Access is denied.
. This is often caused by incorrect security settings in either the writer or requestor process.
Operation:
Gathering Writer Data
Context:
Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Name: System Writer
Writer Instance ID: {a761636d-65ce-4d75-87b2-f5110f5580b6}
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="VSS" />
<EventID Qualifiers="0">8194</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2019-05-29T07:30:36.000000000Z" />
<EventRecordID>124494</EventRecordID>
<Channel>Application</Channel>
<Computer>xxxx</Computer>
<Security />
</System>
<EventData>
<Data>0x80070005, Access is denied.
</Data>
<Data>
Operation:
Gathering Writer Data
Context:
Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Name: System Writer
Writer Instance ID: {a761636d-65ce-4d75-87b2-f5110f5580b6}</Data>
<Binary>2D20436F64653A20575254575254494330303030313239352D2043616C6C3A20575254575254494330303030313234392D205049443A202030303030303434382D205449443A202030303030333931322D20434D443A2020433A5C57696E646F77735C73797374656D33325C737663686F73742E657865202D6B204E6574776F726B53657276696365202020202020202D20557365723A204E616D653A204E5420415554484F524954595C4E4554574F524B20534552564943452C205349443A532D312D352D3230</Binary>
</EventData>
</Event>Log Name: Application
Source: VSS
Date: 5/28/2019 11:11:07 PM
Event ID: 12289
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: xxxxxx
Description:
Volume Shadow Copy Service error: Unexpected error DeviceIoControl(\\?\Volume{c4e61cad-42e7-4095-9c39-b0f93aab7285} - 0000000000000274,0x0053c008,000000E54EAF3910,0,000000E54EAF08E0,4096,[0]). hr = 0x8007001f, A device attached to the system is not functioning.
.
Operation:
Processing EndPrepareSnapshots
Context:
Execution Context: System Provider
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="VSS" />
<EventID Qualifiers="0">12289</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2019-05-29T03:11:07.000000000Z" />
<EventRecordID>124474</EventRecordID>
<Channel>Application</Channel>
<Computer>xxxxx</Computer>
<Security />
</System>
<EventData>
<Data>DeviceIoControl(\\?\Volume{c4e61cad-42e7-4095-9c39-b0f93aab7285} - 0000000000000274,0x0053c008,000000E54EAF3910,0,000000E54EAF08E0,4096,[0])</Data>
<Data>0x8007001f, A device attached to the system is not functioning.
</Data>
<Data>
Operation:
Processing EndPrepareSnapshots
Context:
Execution Context: System Provider</Data>
<Binary>2D20436F64653A20494E434943484C4830303030303532312D2043616C6C3A2053505251534E504330303030303137342D205049443A202030303030343235322D205449443A202030303030333031322D20434D443A2020433A5C57696E646F77735C53797374656D33325C737663686F73742E657865202D6B2073777072762D20557365723A204E616D653A204E5420415554484F524954595C53595354454D2C205349443A532D312D352D313820</Binary>
</EventData>
</Event>
System Log showing following error.
Log Name: System
Source: volsnap
Date: 5/28/2019 11:11:07 PM
Event ID: 5
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: xxxxxx
Description:
The shadow copy of volume E: could not be created due to insufficient non-paged memory pool for a bitmap structure.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="volsnap" />
<EventID Qualifiers="49158">5</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2019-05-29T03:11:07.154365500Z" />
<EventRecordID>813851</EventRecordID>
<Channel>System</Channel>
<Computer>xxxxxx</Computer>
<Security />
</System>
<EventData>
<Data>\Device\HarddiskVolumeShadowCopy147</Data>
<Data>E:</Data>
<Binary>000000000200300000000000050006C001000000010000C07B000000000000000000000000000000</Binary>
</EventData>
</Event>
I have read some Microsoft articles, which says the Volume shadow copy does not work with Volumes more than 64 TB.
Based on that, our only option is to Shrink the volume to 63 TB or 62 TB. We do have the space to shrink the volume.
Anybody have tried to shrink a volume at that size? How long does it take, say .. to shrink by 2 TB.
Any I/O performance impact? Can we attempt to do it during our normal business hours?
Any suggestions?
Continue reading...