Hello.
I think I have a similar problem like this one: https://www-secure.symantec.com/connect/forums/bac...
System: W2008 R2 Enterprise, Hyper-V, Failover-Cluster, DNS, BackupExec 2010 R3 Media Server, Dell R710
Errors while the backup runs:
Log Name: Application
Source: VSS
Date: 06.12.2012 13:03:50
Event ID: 8193
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer:
Description:
Volume Shadow Copy Service error: Unexpected error calling routine Cannot find anymore diff area candidates for volume \\?\Volume{3291399f-d579-11e0-8a79-806e6f6e6963}\ [0]. hr = 0x8000ffff, Catastrophic failure
.
Operation:
Automatically choosing a diff-area volume
Processing EndPrepareSnapshots
Context:
Volume Name: \\?\Volume{3291399f-d579-11e0-8a79-806e6f6e6963}\
Execution Context: System Provider
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="VSS" />
<EventID Qualifiers="0">8193</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-12-06T12:03:50.000000000Z" />
<EventRecordID>63545</EventRecordID>
<Channel>Application</Channel>
<Computer></Computer>
<Security />
</System>
<EventData>
<Data>Cannot find anymore diff area candidates for volume \\?\Volume{3291399f-d579-11e0-8a79-806e6f6e6963}\ [0]</Data>
<Data>0x8000ffff, Catastrophic failure
</Data>
<Data>
Operation:
Automatically choosing a diff-area volume
Processing EndPrepareSnapshots
Context:
Volume Name: \\?\Volume{3291399f-d579-11e0-8a79-806e6f6e6963}\
Execution Context: System Provider</Data>
<Binary>2D20436F64653A20535052414C4C4F4330303030313137342D2043616C6C3A20535052414C4C4F4330303030303739302D205049443A202030303030363036342D205449443A202030303030353530302D20434D443A2020433A5C57696E646F77735C53797374656D33325C737663686F73742E657865202D6B2073777072762D20557365723A204E616D653A204E5420415554484F524954595C53595354454D2C205349443A532D312D352D313820</Binary>
</EventData>
</Event>
-------------
Log Name: Application
Source: VSS
Date: 06.12.2012 13:03:50
Event ID: 12293
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer:
Description:
Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details EndPrepareSnapshots({448c7306-4098-46ce-a1d8-dd5f9b3b7871}) [hr = 0x80042302, A Volume Shadow Copy Service component encountered an unexpected error.
Check the Application event log for more information.
].
Operation:
Executing Asynchronous Operation
Context:
Current State: DoSnapshotSet
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="VSS" />
<EventID Qualifiers="0">12293</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-12-06T12:03:50.000000000Z" />
<EventRecordID>63546</EventRecordID>
<Channel>Application</Channel>
<Computer></Computer>
<Security />
</System>
<EventData>
<Data>{b5946137-7b9f-4925-af80-51abd60b20d5}</Data>
<Data>EndPrepareSnapshots({448c7306-4098-46ce-a1d8-dd5f9b3b7871})</Data>
<Data>0x80042302, A Volume Shadow Copy Service component encountered an unexpected error.
Check the Application event log for more information.
</Data>
<Data>
Operation:
Executing Asynchronous Operation
Context:
Current State: DoSnapshotSet</Data>
<Binary>2D20436F64653A20434F52534E50534330303030313632342D2043616C6C3A20434F52534E50534330303030313630352D205049443A202030303030343735362D205449443A202030303030353839322D20434D443A2020433A5C57696E646F77735C73797374656D33325C76737376632E6578652020202D20557365723A204E616D653A204E5420415554484F524954595C53595354454D2C205349443A532D312D352D313820</Binary>
</EventData>
</Event>
--------------
Part of the BackupExec job error:
Backup- C:Directory C:\ClusterStorage was not found, or could not be accessed.
None of the files or subdirectories contained within will be backed up.
Backup - AOFO: Initialization failure on: "Shadow?Copy?Components". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
V-79-10000-11226 - VSS Snapshot error. The Microsoft Volume Shadow Copy Service (VSS) snapshot provider selected returned: "Unexpected provider error". Ensure that all provider services are enabled and can be started. Check the Windows Event Viewer for details.
- AOFO: Initialization failure on: "System?State". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
V-79-10000-11226 - VSS Snapshot error. The Microsoft Volume Shadow Copy Service (VSS) snapshot provider selected returned: "Unexpected provider error". Ensure that all provider services are enabled and can be started. Check the Windows Event Viewer for details.
----------------------
This seems to be only when this external usb disk is connected. This one is used as B2D target.
This is fsutil output from this disk:
NTFS Volume Serial Number : 0x2e907d05907cd535
Version : 3.1
Number Sectors : 0x000000001d1c0680
Total Clusters : 0x000000001d1c0680
Free Clusters : 0x0000000011556155
Total Reserved : 0x0000000000000000
Bytes Per Sector : 4096
Bytes Per Physical Sector : <Not Supported>
Bytes Per Cluster : 4096
Bytes Per FileRecord Segment : 4096
Clusters Per FileRecord Segment : 1
Mft Valid Data Length : 0x0000000002a00000
Mft Start Lcn : 0x00000000000c0000
Mft2 Start Lcn : 0x000000000e8e0340
Mft Zone Start : 0x00000000000c2a00
Mft Zone End : 0x00000000000cc900
RM Identifier: F7608656-1D12-11E2-B773-BC305BE4F7E1
All tests are ok with b2dtest.exe with this drive. With other USB disks with 512 cluster size there is no problem.
I tried the solution from https://www-secure.symantec.com/connect/forums/bac...
(9) C:\>VSSADMIN ADD SHADOWSTORAGE /FOR=Z: /ON=F: /MaxSize=UNBOUNDED
(10) C:\>VSSADMIN ADD SHADOWSTORAGE /FOR=F: /ON=F: /MaxSize=UNBOUNDED
where Z: is the 100mb system reserved partition and F: is the USB drive.
Here are some information before the shadowstorage for Z: and F: was created:
MOUNTVOL
Possible values for VolumeName along with current mount points are:
\\?\Volume{3291399e-d579-11e0-8a79-806e6f6e6963}\
*** NO MOUNT POINTS ***
\\?\Volume{d4adfa87-d57b-11e0-9cad-bc305be4f7e1}\
D:\
\\?\Volume{f7608653-1d12-11e2-b773-bc305be4f7e1}\
F:\
\\?\Volume{db1d6621-386e-11e2-84b7-bc305be4f7e1}\
Q:\
\\?\Volume{3291399f-d579-11e0-8a79-806e6f6e6963}\
C:\
\\?\Volume{329139a2-d579-11e0-8a79-806e6f6e6963}\
E:\
WRITERS
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Writer name: 'SCVMM Express Writer'
Writer Id: {7aaa9b7b-e652-4f37-9057-a9627141b420}
Writer Instance Id: {2ddd390f-34de-455e-8d5b-d7ae5eee0b80}
State: [1] Stable
Last error: No error
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: {c463b230-6933-4df5-9023-15f06a1b521d}
State: [1] Stable
Last error: No error
Writer name: 'Microsoft Hyper-V VSS Writer'
Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
Writer Instance Id: {98582205-7f30-45cf-93aa-c4090f19a376}
State: [7] Failed
Last error: Timed out
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {e339f280-77b4-41b6-ba1c-db8e389dd2b9}
State: [7] Failed
Last error: Timed out
Writer name: 'SqlServerWriter'
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {aa495a55-2973-4d10-8896-b3843de7113d}
State: [1] Stable
Last error: No error
Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id: {21ad42fe-e006-45d9-9ecd-1327aa248678}
State: [7] Failed
Last error: Timed out
Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {2f1f5aa7-f5f2-4490-9fda-34c9c3be67f5}
State: [1] Stable
Last error: No error
Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {f1f08548-1411-4295-801c-f3b2c70e53b3}
State: [7] Failed
Last error: Timed out
Writer name: 'NTDS'
Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
Writer Instance Id: {5f0d242d-f311-4959-840d-f2c7634579d8}
State: [7] Failed
Last error: Timed out
Writer name: 'DFS Replication service writer'
Writer Id: {2707761b-2324-473d-88eb-eb007a359533}
Writer Instance Id: {be1a8f5d-2b4e-4f0b-9e95-4cd992b0b3ce}
State: [7] Failed
Last error: Timed out
Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {e0708a13-1fb0-4d2a-8243-b217fc458ff8}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {e42a2db3-ce1d-43b4-b2d6-28411693b378}
State: [1] Stable
Last error: No error
Writer name: 'Cluster Database'
Writer Id: {41e12264-35d8-479b-8e5c-9b23d1dad37e}
Writer Instance Id: {7c8b16aa-df76-466d-ac76-58c48b92392a}
State: [7] Failed
Last error: Timed out
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {63ed6de4-cdbf-488a-9a61-ff1a16e2cea2}
State: [1] Stable
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {ce8e8e5d-b632-4ce8-9d90-30601ffb791e}
State: [7] Failed
Last error: Timed out
Any idea how to get the backup to work with the 4K cluster USB disk?
Thanks for help,
Michael