Case #07502718 - VSS failure

[NetAdHHRI]

Using VAW to back up physical file server, volume mode, to VB&R repository; been backing up D:\without problem for months. Made a change today to add E:\ to the job and it failed:

Creating VSS snapshot Error: Failed to create snapshot: Backup job failed. Cannot create a shadow copy of the volumes containing writer's data. VSS asynchronous operation is not completed. Operation: [Shadow copies commit]. Code: [0x80042306].
Error: Failed to create snapshot: Backup job failed. Cannot create a shadow copy of the volumes containing writer's data. VSS asynchronous operation is not completed. Operation: [Shadow copies commit]. Code: [0x80042306].

Interestingly, it couldn't back up D: or E:, but when I removed E: from the backup job config, the backup runs again. D:\ is a 14TB slice of a RAID1 array; E:\ is a 114TB (not a typo) RAID5 array, which I know is a weird config, but I had to set it up that way to prepare for some big data sets coming in. Could it just be too big for VSS to work? Or, what else can y'all suggest as issues?

Error in the Windows Application Log is:
Log Name: Application
Source: VSS
Date: 11/13/2024 11:14:08 AM
Event ID: 12289
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: FILES1.mrf.lan
Description:
Volume Shadow Copy Service error: Unexpected error DeviceIoControl(\\?\Volume{9cdb730d-8b5d-4a13-bdaa-9fa3b5e42b28} - 00000000000002E0,0x0053c008,0000023D00247E40,0,0000023D00248E50,4096,[0]). hr = 0x80070057, The parameter is incorrect.
.

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="2024-11-13T17:14:08.766510300Z" />
<EventRecordID>16941</EventRecordID>
<Channel>Application</Channel>
<Computer>FILES1.mrf.lan</Computer>
<Security />
</System>
<EventData>
<Data>DeviceIoControl(\\?\Volume{9cdb730d-8b5d-4a13-bdaa-9fa3b5e42b28} - 00000000000002E0,0x0053c008,0000023D00247E40,0,0000023D00248E50,4096,[0])</Data>
<Data>0x80070057, The parameter is incorrect.
</Data>
<Data>

Operation:
Processing EndPrepareSnapshots

Context:
Execution Context: System Provider</Data>
<Binary>2D20436F64653A20494E434943484C4830303030303532312D2043616C6C3A2053505251534E504330303030303137322D205049443A202030303030393236342D205449443A202030303031313038342D20434D443A2020433A5C57696E646F77735C53797374656D33325C737663686F73742E657865202D6B2073777072762D20557365723A204E616D653A204E5420415554484F524954595C53595354454D2C205349443A532D312D352D313820</Binary>
</EventData>
</Event>

[david.domask]

Hi Barry,

https://helpcenter.veeam.com/docs/agent ... tml?ver=60

I suppose it's probably this limitation of VSS:

Microsoft Windows FAT32/exFAT, NTFS, ReFS file systems are supported.

The supported file system must reside on a volume that is 64 TB or smaller, because Veeam Agent uses the Microsoft Software Shadow Copy Provider to create a volume shadow copy during the backup. To learn more about the limitation, see Microsoft documentation.

So if the E:\ volume is really over 64 TiB, then VSS won't work here. What kind of data is on the volume? Is it perhaps like a file server or something where our Unstructured Data Backup (File Server backup) would be feasible?

[NetAdHHRI]

Yep, that's it. Fortunately, there wasn't a lot of data on the partition yet; I was able to copy data elsewhere, destroy the partition, recreate two smaller partitions, and then all was well. Thanks for your help.

[david.domask]

Great, glad to hear that we caught it "early" and you were able to reconfigure without too much hassle.

Glad to be able to help!