1

I'm trying to setup backup scripts on WinXP to use Volume Shadow Sets. I downloaded the VSS 7.2 SDK from MSFT, and used the include vshadow.exe to create a shadow set:

vshadow -script=vss-setvar.cmd f:

(note that I've tried both f: and c:)

vshadow executes just find, giving no errors, reporting the shadow is created. However, executing

vshadow -q

as the very next command results in "There are no shadows on the system" and, indeed, if I use dosdev to try and map the Shadow set named in vss-setvar.cmd, it will not work.

Am I missing a step?

Kara Marfia
  • 7,892
  • 5
  • 32
  • 56
Jeff Leyser
  • 682
  • 6
  • 19

2 Answers2

1

Based on the web page at: http://blogs.msdn.com/adioltean/archive/2005/01/05/346793.aspx , when vshadow is run on an XP system, the Shadow Volume is deleted when the command finishes running. To be able to use the shadow volume, you must use a callback script (add -exec=Callback-script.cmd to your command line and put the actions to preform on the shadow volume in that scipt.

Walter
  • 1,047
  • 7
  • 14
0

Double check that the place where you are creating the shadow copy is NTFS, and not FAT16/FAT32.

You can double check this by right click the parition/drive and going to properties.

Also you may wish to see if that tool is supported under Windows XP. You may need to upgrade to either Windows Server line or possibly Vista, but I don't have details on that.

Never mind, according to the tool download Windows XP is supported.

Also to create a shadow copy the command is

vssadmin create shadow /for=c:

You may wish to look at the MSDN support documents about the VSS tools.

Scott Markwell
  • 722
  • 1
  • 6
  • 13
  • Yep, c: and f: are NTFS. There is no vssadmin.exe anywhere in the VSS SDK that I've downloaded (and that you've linked to), however. – Jeff Leyser Aug 03 '09 at 22:57
  • I've linked to more information about vshadow, and some diagnostic tools for VSS that may give you some more insight into what's going on. – Scott Markwell Aug 04 '09 at 17:25