Previous Shadow Copies

In accessing the PREVIOUS VERSIONS, I only see the last Shadow Copy that was ran at 5:30 this morning.  This runs every morning at 5:30AM M-F and I was trying to figure out why the other previous sets are not shown.  

There appears to be limits on shadow copies that would cause the oldest one to be deleted, but I have not reached those limits.
1)  If you reach your max allowed (mine is 28,552mb, used is 2,457mb).
2) More than 64 versions, I only show one version.

* So why am I not retaining the previous versions?

* Is there an option to say purge prior versions, that I may have turned on somewhere? If so I have been unable to locate it.

Thanks for your assistance.
HCSHAWAsked:
Who is Participating?
 
DonNetwork AdministratorCommented:
0
 
HCSHAWAuthor Commented:
Interesting, I am doing some research on those events.   In the mean time, I am posting the events that I am seeing.  The timing of these events is during the nightly backup.  

Event Type:      Error
Event Source:      VolSnap
Event Category:      None
Event ID:      34
Date:            4/24/2010
Time:            12:54:16 AM
User:            N/A
Computer:      PNS-TERMSVR
Description:
The shadow copies of volume C: were aborted because of a failure to ensure crash dump or hibernate consistency.

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 22 00 06 c0   ...."..À
0010: 02 00 00 00 0e 00 00 c0   .......À
0018: 01 00 00 00 00 00 00 00   ........
0020: 00 00 00 00 00 00 00 00   ........

---and---
Event Type:      Error
Event Source:      VolSnap
Event Category:      None
Event ID:      25
Date:            4/24/2010
Time:            12:57:28 AM
User:            N/A
Computer:      PNS-TERMSVR
Description:
The shadow copies of volume C: were deleted because the shadow copy storage could not grow in time.  Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied.

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 19 00 06 c0   .......À
0010: 03 00 00 00 00 00 00 00   ........
0018: 02 00 00 00 00 00 00 00   ........
0020: 00 00 00 00 00 00 00 00   ........

 
0
 
HCSHAWAuthor Commented:
First attempt will be to move the Diff Area (snapshot location) to the E: Drive.  Currently it is on the same drive where the snapshot is being taken.

Ref Tech Bullentin:
http://technet.microsoft.com/en-us/library/cc734469(WS.10).aspx

I will post the results.
0
 
HCSHAWAuthor Commented:
It appears moving the Diff Area to the other drive has fixed the problem.   I am seeing previous versions now, and no errors in the event log.

I don't think this is related to a defrag issue as much as a BU Exec issue when the drive is being backed up.  I based this on when the events are getting logged.     Only time will tell if this is the final fix.   Thanks for the great links.  
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.