I've been chasing down a problem with Shadow Copies on our file server for a few months now. The server is a member server 2003 SP1 and is up to date with all MS patches and updates.
Every night around 1:00 AM I would receive the series of errors related to Shadow Copy service in my event log.
The errors would start like this:
**************
Event Type: Information
Event Source: VolSnap
Event Category: None
Event ID: 33
Date: 5/25/2006
Time: 12:47:10 AM
User: N/A
Computer: WCNAS
Description:
The oldest shadow copy of volume D: was deleted to keep disk space usage for shadow copies of volume D: below the user defined limit.
***************
and end like this:
***************
Event Type: Warning
Event Source: VolSnap
Event Category: None
Event ID: 24
Date: 5/25/2006
Time: 1:39:51 AM
User: N/A
Computer: WCNAS
Description:
There was insufficient disk space on volume C: to grow the shadow copy storage for shadow copies of D:. As a result of this failure all shadow copies of volume D: are at risk of being deleted.
*****************
Event Type: Error
Event Source: VolSnap
Event Category: None
Event ID: 35
Date: 5/25/2006
Time: 1:47:24 AM
User: N/A
Computer: WCNAS
Description:
The shadow copies of volume D: were aborted because the shadow copy storage failed to grow.
*******************
After these errors occur all the copies are deleted from the storage volume.
I received the hotfixes from MS to fix the known problem with volsnap errors in the event log. However, because I was already running SP1, they would not install.
The shadow copy service stores all the copies on a separate volume which has more than enough drive space to accomodate.
My volume shadow copy schedule is M - F at the default times, 9AM and 2 PM.
I've performed some testing by creating multiple copies and watching the event log for the errors I've posted above, but I'm unable to recreate the problem.
No backups are running during the time these events take place.
The only thing that is going on at the server during the time these events are taking place is a Symantec virus scan. I'm going to run the scan at a different time of the day to pinpoint that this is the cause. Does anyone else have any experience with this problem and how did you resolve it?
TIA
Heather
Every night around 1:00 AM I would receive the series of errors related to Shadow Copy service in my event log.
The errors would start like this:
**************
Event Type: Information
Event Source: VolSnap
Event Category: None
Event ID: 33
Date: 5/25/2006
Time: 12:47:10 AM
User: N/A
Computer: WCNAS
Description:
The oldest shadow copy of volume D: was deleted to keep disk space usage for shadow copies of volume D: below the user defined limit.
***************
and end like this:
***************
Event Type: Warning
Event Source: VolSnap
Event Category: None
Event ID: 24
Date: 5/25/2006
Time: 1:39:51 AM
User: N/A
Computer: WCNAS
Description:
There was insufficient disk space on volume C: to grow the shadow copy storage for shadow copies of D:. As a result of this failure all shadow copies of volume D: are at risk of being deleted.
*****************
Event Type: Error
Event Source: VolSnap
Event Category: None
Event ID: 35
Date: 5/25/2006
Time: 1:47:24 AM
User: N/A
Computer: WCNAS
Description:
The shadow copies of volume D: were aborted because the shadow copy storage failed to grow.
*******************
After these errors occur all the copies are deleted from the storage volume.
I received the hotfixes from MS to fix the known problem with volsnap errors in the event log. However, because I was already running SP1, they would not install.
The shadow copy service stores all the copies on a separate volume which has more than enough drive space to accomodate.
My volume shadow copy schedule is M - F at the default times, 9AM and 2 PM.
I've performed some testing by creating multiple copies and watching the event log for the errors I've posted above, but I'm unable to recreate the problem.
No backups are running during the time these events take place.
The only thing that is going on at the server during the time these events are taking place is a Symantec virus scan. I'm going to run the scan at a different time of the day to pinpoint that this is the cause. Does anyone else have any experience with this problem and how did you resolve it?
TIA
Heather