That's what I am finding in some searches. There is a hotfix I found... but have not really looked at it much yet.
http://support.microsoft.com/kb/826936 I am curious how many others are running in to this. It really hugs because I had to do a tape restore for something I could have quickly done on a shadow copy. Bob Fronk From: Joseph L. Casale [mailto:[email protected]] Sent: Thursday, May 07, 2009 11:21 AM To: NT System Admin Issues Subject: RE: Shadow Copies disappearing Yup, battle this often. IMHO, VSS is super flawed in this respect. When the volume your snapping undergoes high IO (and that is a matter of VSS's perspective, not mine) it gets its sh!t in a knot and dumps the whole freaking repository of snaps. It doesn't even have to be undergoing this so called high IO while snapping either... The best way to minimize it, because I can't get it to stop totally is to move the shadow copy storage to different controller and spindles. jlc From: Bob Fronk [mailto:[email protected]] Sent: Thursday, May 07, 2009 9:08 AM To: NT System Admin Issues Subject: Shadow Copies disappearing Something is killing my Shadow Copies on several servers. On one of them I am seeing "service control manager" events 7035 7036 over and over. (Shadow copy service entered stopped state / Shadow copy service was successfully sent a start control) Starting to Google, but wondering if anyone else has noticed similar events. Seems to have just started on several servers. Thanks. Bob Fronk ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
