windows server 2008 - Shadow Copy - "Failed to retrieve volumes that are eligible" - 0x8004230f

07
2014-07
  • Joey

    We have a server running Windows Server 2008. The server is the file share server.

    Shadow copies look to have been set up previously, but now it isn't working at all.

    Upon right-clicking on the drive and going to "Configure Shadow Copies", The error message is all that is displayed.

    enter image description here

    When trying to view the previous versions from a Users PC, it searches and finds nothing.

    The Volume Shadow Copy service is running.

    I have looked at the registry key permissions and followed those instructions but hasn't worked.

  • Answers
    Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

    Related Question

    backup - Shadow copy to clone system volume on Windows XP
  • ARF

    I am looking for a program that uses shadow copy to copy the contents of a Windows XP system volume that is running.

    I.e. I want to clone the system volume with the following snags: (1) I want to be able to select which files to copy (i.e. not the entire file system) (2) This is probably implied by (1), but I also have to avoid sector-by-sector copies (3) I do not want to clone a file system into an image file and restore to a 3rd drive but want to do a filesystem to filesystem copy

    All the backup/clone utilities I looked into stumble on one of above points. Any ideas?


  • Related Answers
  • Hannes de Jager

    Hope I understand the question correctly. If so have a look at Hobocopy

  • ARF

    Since this problem seems to be somewhat obscure, I thought I explain the solution I found.

    To copy a Windows system volume using volume shadow copy service, the best program seems to be ViceVersa (Fully functional trial on http://www.tgrmn.com/). I also tried the freeware "Shadow Copy" by Runtime Software but this is very buggy and has an terribly limited GUI.

    Also note, for some reason shadow copying the current user's profile seems to fail on Windows XP. So copy while running as some temporary user whose user directory you can exclude from the copy.

    Before trying to boot from the new harddrive, one also has to modify the drive-letter assignements in the Windows registrs ON THE NEW DRIVE: for this, load the system registry hive from the new drive and rename in "Mounted Devices" key:

    "\DosDevices\D:" to "\DosDevices\C:"

    Assuming that D was the drive letter for the new drive and C the drive letter of the system volume. If this is not done, Windows will appear to load but freeze just before it reaches the login screen. Do not forget to unload the registry hive after you are done, otherwise you may run into problems when rebooting from the old drive.