• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 268
  • Last Modified:

Windows 2003 Shadow Copies aborted during power outage

We have Shadow copies configured on our servers.  Data is stored on a Windows 2003 server (Win02), with a shared drive on Win02 (Drive F:) connected to our SAN.  We have shadow copies configured to take snapshots 4 times a day.  It's been working fine.

I went to restore a previous version today, and all the previous versions show up as "white" icons of an "unspecified" type.  No dates are associated with any.  If I try to restore it, it says the previous version no longer exists.

This is only happening on the data we have stored on the SAN.  All other previous versions on Win02 that are stored locally on that server are working.

If I go to where I configure the shadow copies and select "create now", it seems to create it.  But I get the same behavior when I try to restore it -- it doesn't exist.

I do see an error in the event viewer from when we had a power outage two weeks ago.  The event ID 14, Sourse VolSnap, says "copies of volume F were aborted because of an IO failure on Volume F."  How do I get these started again?  I've since rebooted the server.

I realize I probably have lost the previous snapshots but I'd like to get this running again.  The service is running, but the snapshots it is making are "invalid".  Thank you.
0
CMCo
Asked:
CMCo
1 Solution
 
BiniekCommented:
I suppose, that can be problem with VSS hardware provider for the SAN

You should install the VSS hardware provider for the SAN.

There is some examples of hardware VSS provider (The table  contains the list of VSS hardware provider tested to be compatible with DPM, but it will be helpful)
http://blogs.technet.com/b/dpm/archive/2010/07/08/tested-hardware-vss-provider-table.aspx

Some interesting information about VSS:

http://technet.microsoft.com/en-us/library/ee923636(v=ws.10).aspx
http://blogs.technet.com/b/josebda/archive/2007/10/10/the-basics-of-the-volume-shadow-copy-service-vss.aspx
0
 
CMCoAuthor Commented:
The fix was related to this.  Our SAN support tech resolved it.  Thanks!
0

Featured Post

The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now