Shadow Copy Service Not Working - Large Disks - XP/SP2

C

Chris

All-

I recently upgraded a PC and have 2xSATAII 250GB (500GB total) drives
striped as RAID 0, with a NTFS cluster size of 512 bytes. Previously
had a NTFS 250GB drive and no problems.

Now, I cannot backup using NTBackup because the volume shadow cannot get
created.

The event log states:

Event Type: Error
Event Source: VolSnap
Event Category: None
Event ID: 20
Date: 1/20/2006
Time: 11:10:44 PM
User: N/A
Computer: P4
Description:
The shadow copy of volume C: was aborted because of a failed free space
computation.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 02 00 58 00 ......X.
0008: 00 00 00 00 14 00 06 c0 .......À
0010: 00 00 00 00 9a 00 00 c0 ....?..À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

The backup log states:

"Backup Status
Operation: Backup
Active backup destination: File
Media name: "C Drive Backup.bkf created 1/21/2006 at 6:50 AM"

Error returned while creating the volume shadow copy:80042308
Reverting to non-shadow copy backup mode."

Listing providers provides:

"

vssadmin 1.0 - Volume Shadow Copy Service administrative command-line
tool
(C) Copyright 2001 Microsoft Corp.

Provider name: 'MS Software Shadow Copy provider 1.0'
Provider type: System
Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
Version: 1.0.0.7"

vssadmin naturally does not list any shadows, When I list the writers,
all statuses are stable.

I know that MS has a hotfix for Server 2003, but that isn't much help to
me running XP Professional SP2. It just seems like almost the exact
same problem.

Any ideas or help?

Thanks-

Chris.
 
R

Ronnie Jypore

Chris said:
All-

I recently upgraded a PC and have 2xSATAII 250GB (500GB total) drives
striped as RAID 0, with a NTFS cluster size of 512 bytes. Previously
had a NTFS 250GB drive and no problems.

Now, I cannot backup using NTBackup because the volume shadow cannot get
created.

The event log states:

Event Type: Error
Event Source: VolSnap
Event Category: None
Event ID: 20
Date: 1/20/2006
Time: 11:10:44 PM
User: N/A
Computer: P4
Description:
The shadow copy of volume C: was aborted because of a failed free space
computation.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 02 00 58 00 ......X.
0008: 00 00 00 00 14 00 06 c0 .......À
0010: 00 00 00 00 9a 00 00 c0 ....?..À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

The backup log states:

"Backup Status
Operation: Backup
Active backup destination: File
Media name: "C Drive Backup.bkf created 1/21/2006 at 6:50 AM"

Error returned while creating the volume shadow copy:80042308
Reverting to non-shadow copy backup mode."

Listing providers provides:

"

vssadmin 1.0 - Volume Shadow Copy Service administrative command-line
tool
(C) Copyright 2001 Microsoft Corp.

Provider name: 'MS Software Shadow Copy provider 1.0'
Provider type: System
Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
Version: 1.0.0.7"

vssadmin naturally does not list any shadows, When I list the writers,
all statuses are stable.

I know that MS has a hotfix for Server 2003, but that isn't much help to
me running XP Professional SP2. It just seems like almost the exact
same problem.

Any ideas or help?

Thanks-

Chris.

Hi Chris,

The error code : 80042308 means that the shadow copy went away during
the backup
process. The most probable reasons for this are :

1) If you run out of disk space,
2) If you have other applications that have intense I/O activity during
the
shadow copy lifetime.

The System event log should contain a VOLSNAP entry explaining the
reason of why the shadow copy went away.

Regards,

Naved
 
R

Ronnie Jypore

Chris said:
All-

I recently upgraded a PC and have 2xSATAII 250GB (500GB total) drives
striped as RAID 0, with a NTFS cluster size of 512 bytes. Previously
had a NTFS 250GB drive and no problems.

Now, I cannot backup using NTBackup because the volume shadow cannot get
created.

The event log states:

Event Type: Error
Event Source: VolSnap
Event Category: None
Event ID: 20
Date: 1/20/2006
Time: 11:10:44 PM
User: N/A
Computer: P4
Description:
The shadow copy of volume C: was aborted because of a failed free space
computation.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 02 00 58 00 ......X.
0008: 00 00 00 00 14 00 06 c0 .......À
0010: 00 00 00 00 9a 00 00 c0 ....?..À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

The backup log states:

"Backup Status
Operation: Backup
Active backup destination: File
Media name: "C Drive Backup.bkf created 1/21/2006 at 6:50 AM"

Error returned while creating the volume shadow copy:80042308
Reverting to non-shadow copy backup mode."

Listing providers provides:

"

vssadmin 1.0 - Volume Shadow Copy Service administrative command-line
tool
(C) Copyright 2001 Microsoft Corp.

Provider name: 'MS Software Shadow Copy provider 1.0'
Provider type: System
Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
Version: 1.0.0.7"

vssadmin naturally does not list any shadows, When I list the writers,
all statuses are stable.

I know that MS has a hotfix for Server 2003, but that isn't much help to
me running XP Professional SP2. It just seems like almost the exact
same problem.

Any ideas or help?

Thanks-

Chris.

Hi Chris,

The error code : 80042308 means that the shadow copy went away during
the backup
process. The most probable reasons for this are :

1) If you run out of disk space,
2) If you have other applications that have intense I/O activity during
the
shadow copy lifetime.

The System event log should contain a VOLSNAP entry explaining the
reason of why the shadow copy went away.

Regards,

Naved
 
C

Chris

Naved-

Thank you for your response.

However, if you read my original post, I did post the VolSnap message
from the system log file.

"The shadow copy of volume C: was aborted because of a failed free space
computation." The only thing I can find on this error message is that
there is a bug with Windows Server 2003 for large disk drives with small
cluster sizes. I have 2x250 GB disks with 512 clusters. Is this
related? The fix only appears to be patched for 2003. It is important
to note that this same configuration DID WORK with a single 250 GB
drive. It stopped working when the second drive was added.

Also:

1) The computer is not out of disk space. I have 89% free (415 GB Free
of 465 GB). 2) The CPU is idle except for the backup process. All
uneeded applications were stopped. There is no other significant IO
activity occuring per the task manager CPU and IO loads.

Any other ideas?

Chris.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top