Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 28 Source: VolSnap
The shadow copy of volume <volume>: could not be created due to a failure in creating the necessary on disk structures.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is a shadow copy?
If server has been updated with SP2, there are newer hotfixes for VSS in ME967551 and ME979457.
We had the error Event ID 28 and 20 from Volume Shadow Copy Service on an Windows Server 2003 32-Bit Standard Edition wich has a 12, 8TB iSCSI connected Partition.
We tried to activate the VolumeShadowCopy but it terminates everytime with the following Error:
"Error 0x08007000e: For this ...."
As per Microsoft Online Support (found on a forum), he made the following Statement wich resolved our issue:
"Shadow Copy on your 12TB volume.
I would like to inform you that VSS has a limit of 5TB for 32 bit Operating System, which means if you want to make a snapshot of a volume larger than 5TB, you will get an error saying that not enough storage is available to complete this operation.
If your Operating System architecture is 64 bit, please take a look at the Application event log and check if any related error (usually Event Source is VolSnap) exists."
In my case i divided the drives into 3 parts each. Each part less than 5TB to enable the VSS.
Little Note: If you are using Backup Exec, also with Remote Agents, Bex tries to backup this partition with VSS. But BEX would fail!
See ME833167 for a Volume Shadow Copy Service (VSS) update package for Windows Server 2003. See ME887827 for a newer version on this package.
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated