locked
How to regain access to previous version of files in WHS shares RRS feed

  • General discussion

  • User Kariya21 has found a long time ago that previous versions of files in shares are in some instances no longer accessible and posted a bug report on WHS Connect Feedback site. Ken Warren describes this problem in detail in the FAQ section.

     

    The three of us now have found a relatively simple way to regain access to previous versions that appear to be no longer accessible.

     

    PLEASE NOTE:

    • We have tested this method on various installs (RTM, PP1, OEM or PP1 in virtual machine) and we think there are no major pitfalls. However,  this method is UNSUPPORTED and should as such be considered a hack. If you make any errors you might break your WHS install.
    • The method does NOT require shares to be duplicated, and should work for any configuration with more then one disk added to the storage pool.
    • If your WHS has only one disk there is NO need to use this method.
    • Use the method only if you have no access to previous version of your shares (If you try to open or copy a file from a specific previous version you get an error "Invalid File Handle" Or "File or Folder not Accessible" or something similar)

      Now here's the method:

     

    1. Log on to your WHS using  Remote Desktop (RDP)
    2. Open Explorer Window, browse to C:\fs\
    3. You will find your secondary drives listed there as drive letters or numbers.
    4. For each of the secondary drives (C:\fs\X, where X is drive letter or number) do:
      1. Browse to C:\fs\X\DE\shares\someshare ("someshare" = Software, or  Public, or ….)
      2. Share a single folder within this share (right click, sharing and security). On each disk please share another folder!
      3. Assign a logical name to each of the shares, for example name the share for the folder shared in C:\fs\X\someshare “Fix_VSS_X”. This will help you to identify them in the next step.
    5. Acces the WHS shares from the shortcut on the WHS desktop or from windows explorer on a client (\\server\shares for WHS RTM default install, \\hpserver\shares for HP Mediasmart default install) 
    6. Right click each of the newly made shares and select properties.
    7. Select the previous versions tab.
    8. Now you should have full access to all existing previous versions for all WHS shares
      1. Advice: Please do no use the restore function, instead use the copy or view function to copy or view the previous version you want, then store in another location.
    9. Disable the shares you created in 4b after you obtained the files you need.

     

    NOTE: On HP Mediasmart Server previous version are disabled by default. To enable this functionality you will need to edit the registry: PLEASE NOTE this "hack" is also unsupported, and you risk breaking your WHS install when make any error!!

    1. Log on to your WHS using  Remote Desktop (RDP)
    2. Do Start, Run, type regedit and Hit Enter
    3. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Storage Manager\Volumes\
    4. Select the Volume which represents the D partition (select volume key, value for mountpoint should be D)
    5. Edit or create the REG_DWORD key SnapPeriod. Decimal value for this key should be 43200000 (number of milliseconds between snaphots, you can also set this value to 21600000).
    6. Reboot to make effective. Check after 24h if snapshots are created (RDP into WHS, in explorer window right click drive letter, select shadow copies) 

    IF YOU WANT NORMAL ACCESS TO PREVIOUS VERSIONS RESTORED IN A FUTURE VERSION OF WHS PLEASE VOTE OVERHERE (Click on the stars top left in the post, select fifth star if you find this ver important)

    Wednesday, July 16, 2008 10:22 PM
    Moderator

All replies

  • I would like to emphasize the points brubber makes about being careful here. If we don't understand WHS storage as well as we believe, then this "how to" has a possibility of hosing up your server pretty severely. Permanent data loss severely.

    In particular, Microsoft has warned us that using the Previous Versions restore functionality may not work as intended, because of the number of moving pieces in Windows Home Server. And it is very important not to leave the shares you create in place after you're done, as doing so may have unexpected consequences.

    Please be careful if you need to use this technique.
    Thursday, July 17, 2008 1:40 AM
    Moderator
  • Additional comment:
    I would recommend, if trying this method, always to share the DE\shares folder on each disk. This simplifies the access to all subsequent folders.
    Also attach a $ sign to each of the share names, i.e.
    sharesA$ for the first disk in fs, sharesB$ for the second and so on (instead of A you could also use the volume mountpoint letter in c:\fs to identify the disk in the share name).
    So these shares are not listed in the shortcut Shared folders on server, and nobody without knowledge of their existence can access them. The benefit is, that you can leave them in place instead of having to remove them after recovery of the wanted files.

    If you need access to previous versions, click Start\Run on a client PC (or on the server desktop), enter a command like  \\server\shareA$ (and other of these hidden share names created, adjust server name and share names to meet your configuration) and navigate down until you see the folder which contained the file you wish to recover from previous versions.
    Right click the file, select Properties and use the Previous Versions tab, as stated in the original guide.
    Not each single of these shared folders will contain the previous versions you need, since these are only on the disks, which stored the shared folders originally or as duplicate.

    Best greetings from Germany
    Olaf
    Sunday, October 19, 2008 8:50 AM
    Moderator
  • Olaf Engelke said:

    Additional comment:
    I would recommend, if trying this method, always to share the DE\shares folder on each disk. This simplifies the access to all subsequent folders.
    Also attach a $ sign to each of the share names, i.e.
    sharesA$ for the first disk in fs, sharesB$ for the second and so on (instead of A you could also use the volume mountpoint letter in c:\fs to identify the disk in the share name).
    So these shares are not listed in the shortcut Shared folders on server, and nobody without knowledge of their existence can access them. The benefit is, that you can leave them in place instead of having to remove them after recovery of the wanted files.

    If you need access to previous versions, click Start\Run on a client PC (or on the server desktop), enter a command like  \\server\shareA$ (and other of these hidden share names created, adjust server name and share names to meet your configuration) and navigate down until you see the folder which contained the file you wish to recover from previous versions.
    Right click the file, select Properties and use the Previous Versions tab, as stated in the original guide.
    Not each single of these shared folders will contain the previous versions you need, since these are only on the disks, which stored the shared folders originally or as duplicate.

    Best greetings from Germany
    Olaf


    Olaf,

    While I understand the logic in what you are saying, MS has already told us very specifically do not leave the shares at all.  Plus, once you "activate" (mount) each drive using brubber's method (then unshare each one when complete), you now have the ability to use Shadow Copies just like any other Server 2003 machine (instead of guessing which drive had the appropriate file with your method).

    I use a batch file that I created which semi-automates the process (the only manual part is right click on each share, select Properties, then select Cancel).  I've been using it for 3 months and it continues to work every time after a reboot. :)
    Sunday, October 19, 2008 1:22 PM
    Moderator
  • Because of the issues around getting Previous Versions to work even as well (or poorly) as it presently does, and because I don't see any real hope that Microsoft will devote the resources required to change VSS functionality in Windows Server 2003 to fully support Drive Extender (c'mon, who thinks the storage team is going to go back and revisit VSS in 2003? :) ), I have to admit that I think the only reasonable thing to tell people is to not rely on Previous Versions functionality at all.
    I'm not on the WHS team, I just post a lot. :)
    Monday, October 20, 2008 7:56 PM
    Moderator
  • Well, even though I don't like your conclusion, but I have to be realistic and agree with you.  I only hope, that Microsoft DOES indeed have these things on the "must-to-do" list. Otherwise, I am going to be VERY disappointed. :) .

    Also, I believe that "previous version" functionality can be simulated by a server backup functionality.   I one adds one extra HD to the server and copies the shares, a previous will be preserved. The question remains, can one automate the server backup to the "out-of-storage-pool" disk?
    • Edited by Boggy Monday, October 27, 2008 5:04 AM
    Monday, October 27, 2008 5:00 AM
  • Hello,
    you can create a Scheduled task, which does that job ny executing a batch file in the wanted time frame.
    This batch could contain commands like
    robocopy /mir \\server\fotos e:\backup\fotos
    for each share.
    Robocopy is part of the Windows Server 2003 resource kit, which can be downloaded from microsoft.com.
    Best greetings from Germany
    Olaf
    Monday, October 27, 2008 8:52 AM
    Moderator
  • I tried these steps and I don't think it's working for me - what am I doing wrong?

    I have 4 drives

    I go to c:\fs\X

    Then I create a new folder within music: C:\fs\DE\shares\Music\new folder <-- the I right click and network shareit.

    I do this for all 4 drives, then when I return to WHS desktop, I see the new shares however the is no previous tab for any of the new shares?

    what am I doing wrong?

    Wednesday, July 29, 2009 6:14 PM
  • Do you have an HP MediaSmart Server? What client OS are you using?
    I'm not on the WHS team, I just post a lot. :)
    Wednesday, July 29, 2009 7:06 PM
    Moderator
  • Not an Media smart server - I built it myself.  WHS is OEM and has PP3 installed... Client is Win7 7600.
    Wednesday, July 29, 2009 7:52 PM
  • Not an Media smart server - I built it myself.  WHS is OEM and has PP3 installed... Client is Win7 7600.

    (Haven't seen this thread in a while. By the way, for those that are keeping score, I've been doing this for a full year now and it's still working.  :)  )

    What version of 7?  (And by the way, it's probably not a good idea to be announcing you have the RTM version of the product when it's not officially available anywhere yet.)
    Thursday, July 30, 2009 3:35 AM
    Moderator
  • Ultimate
    Thursday, July 30, 2009 12:46 PM
  • I would really like to get back files I accidently errased...what an I doing wrong?
    Thursday, July 30, 2009 2:19 PM
  • Not an Media smart server - I built it myself.  WHS is OEM and has PP3 installed... Client is Win7 7600.
    Hmm. Do you see a "previous versions" tab for pre-existing shares? For files/folders within those shares? And please note that you should be trying to access previous versions of files/folders from a client PC, not from the server...
    I'm not on the WHS team, I just post a lot. :)
    Thursday, July 30, 2009 3:48 PM
    Moderator
  • I do I see previous versions for existing tabs. I think previous version tab was on the client for the new shares but it was blank... not sure, does that make sense?
    Thursday, July 30, 2009 6:43 PM
  • Okay, then you haven't done anything wrong. If a share has never had anything in it (i.e. it's empty now, and has always been) you won't see anything for previous versions. And if there are no snapshots of a particular share (as there will not be just after it's created) you won't see the tab at all.

    Now you need to go find the files you want to restore...

    I'm not on the WHS team, I just post a lot. :)
    Thursday, July 30, 2009 9:35 PM
    Moderator
  • I'm trying to recover my music folder... I accidently erased the music files in it...however on the client when I right click on the shared music folder in network I can see the files in previous version, when I try to copy the files it says: Device not connected, is there any way around this?
    Thursday, July 30, 2009 10:27 PM
  • I'm trying to recover my music folder... I accidently erased the music files in it...however on the client when I right click on the shared music folder in network I can see the files in previous version, when I try to copy the files it says: Device not connected, is there any way around this?

    Umm, that was the point of brubber's first post in this thread....
    Friday, July 31, 2009 4:34 AM
    Moderator
  • I know... but I'm doing something wrong because it's not working for me.

    But I decided last night to format and reinstall WHS...as I was having too many problems and PP3 was not working properly. now everything is running super good and PP3 is working as well, so all is good. I will just re-rip all my music as I own all of it on CDs... I don't download music.
    Friday, July 31, 2009 12:58 PM
  • I bumped into this thread from the comment on the Time Traveler post on mswhs.  I went ahead and read through it even though it's over a year old (hey, with four MVP / Moderators chiming in it has to be good, right? :P )

    A couple questions:

    According to the bug on connect (circa July 2008) "[VSS not working] ...will continue to be tracked in our system and we will aim to address it in the near future via KB article."  Was a KB article ever published? 

    Is this a one-time fix?  Or do the steps detailed need to be repeated each time you add another disk to your drive pool?

    tomf
    WHS OEM, 14 drives ~8.4 TB
    Saturday, December 5, 2009 5:05 AM
  • You do it every time you reboot, and I very strongly doubt that it will be addressed at all with a patch or update to Windows Home Server. I don't know if it will be addressed in a future version of the product...
    I'm not on the WHS team, I just post a lot. :)
    Saturday, December 5, 2009 2:41 PM
    Moderator
  • You do it every time you reboot, and I very strongly doubt that it will be addressed at all with a patch or update to Windows Home Server. I don't know if it will be addressed in a future version of the product...
    I'm not on the WHS team, I just post a lot. :)
    Yikes!  What a pain.  So you'd really want a script / executable to run automatically on system startup in order to always have VSS previous versions available.

    Yeah, I wasn't expecting that MS would patch it.  The Connect feedback item is closed and marked as "won't fix". Hope it is fixed when WHS moves on from Server 2003.
    Saturday, December 5, 2009 10:09 PM
  • Hi Kariya

    Is this still working post PP3? I've tried it and it doesn't work for me. I get no previous versions available when I access any of the new shares from a Win 7 client. Previous Versions are available on the existing shares, but are inaccessible after reboot, as per bug. I'm using a self-build WHS.

    For now, I'm turning off Automatic Updates so the chances of a reboot are minimised. Pity the product forces you into a choice of risky behaviours to try to protect your data. It might be worthwhile suggesting to the product team that some kind of workaround for this would be welcome (I've read the 'Won't Fix' connect response) Even the ability to schedule a nightly backup to external media would be perfectly adequate. I've been trying to achieve this with a macro recorder, but can't get that working either.

    Ewan


    If you have found this post helpful, please click the 'Vote as Helpful' link (the green triangle and number on the top-left).

    If this post answers your question, click the 'Mark As Answered' link below. It helps others who experience the same issue in future to find the solution.
    Thursday, January 14, 2010 9:18 PM
  • As I said elsewhere in this thread, it's normal for a new share to have no previous versions visible until after the first snapshot is taken.

    As for a workaround, look up. Brubber's post is your workaround.

    I'm not on the WHS team, I just post a lot. :)
    Thursday, January 14, 2010 9:30 PM
    Moderator
  • Hi Kariya

    Is this still working post PP3? I've tried it and it doesn't work for me. I get no previous versions available when I access any of the new shares from a Win 7 client. Previous Versions are available on the existing shares, but are inaccessible after reboot, as per bug. I'm using a self-build WHS.

    For now, I'm turning off Automatic Updates so the chances of a reboot are minimised. Pity the product forces you into a choice of risky behaviours to try to protect your data. It might be worthwhile suggesting to the product team that some kind of workaround for this would be welcome (I've read the 'Won't Fix' connect response) Even the ability to schedule a nightly backup to external media would be perfectly adequate. I've been trying to achieve this with a macro recorder, but can't get that working either.

    Ewan


    If you have found this post helpful, please click the 'Vote as Helpful' link (the green triangle and number on the top-left).

    If this post answers your question, click the 'Mark As Answered' link below. It helps others who experience the same issue in future to find the solution.
    Yes, it still works.
    Saturday, January 16, 2010 12:30 AM
    Moderator
  • Hi Ken

    I'm clearly missing something, so sorry if I'm labouring this.

    If a new share has no previous versions, then what is the purpose of this thread? My reading (and this must be where I'm missing something), is that this is the workaround to enable users to access a pre-existing VSS snapshot indirectly, because there's a bug in the product which prevents you from accessing it normally. If there are no VSS snapshots on the new C:\FS\etc shares, why are we creating them?

    Also, as I've said, Brubbers method doesn't work for me, so doesn't qualify as a workaround... I've tried it multiple times after several reboots. Of course, this is on the basis that I'm expecting to see VSS versions on the new shares, which might be where I'm going wrong.

    My call for a workaround from the product team stands - not for a hack like this, but for an alternative, supportable, method for protecting file history. Automating the server backup to external media seems to me like an imperfect, but easily implementable alternative. Since it might be a while until we see a W2008 based WHS.

    Thanks

    Ewan


    If you have found this post helpful, please click the 'Vote as Helpful' link (the green triangle and number on the top-left).

    If this post answers your question, click the 'Mark As Answered' link below. It helps others who experience the same issue in future to find the solution.
    Sunday, January 17, 2010 9:48 PM
  • Oky, I need some help with this.   First off, I have an HP Mediasmart server, so some things maybe a little more difficult.   I was adding some pictures to my shared folders and I noticed that one of my directories was missing, then I noticed it was in another folder, which seemed strange.  So I moved it back out to my root directory and it only moved 3 sub folders(Out of 15), and the others were gone.  I don't seem to be having any hard drive failures.  It seems like some pointer just got screwed up.  From what I have read, it looks like the previous version stuff is off by default on the Media smart servers, is that true?

    So if I have not enabled it, are the files gone for good?   I tried following the steps above.  

    I remote desktoped into my server and located the C:\fs\F\DE\shares\Photos.   When I look at it the directory stucture is exactly the same.  

    I right clicked on the "Photos" directory and selected "File and Security", I clicked the Radio button to share the folder and put the share name as "photoback" and clicked okay.

    I then when to Windows Explorer on my windows 7 machine and looked at the share \\hpserver\photoback and clicked on Previous version and it says "There are no previous versions available"

     

    When I read the comments above it says "NOTE: On HP Mediasmart Server previous version are disabled by default. To enable this functionality you will need to edit the registry" Before I go into the registry and enable it, will it do me any good now?  Seems like it needed to be enabled before I ran into this problem.

    Any help would be appreciated!!!

     

    Friday, September 30, 2011 2:19 AM
  • Editing the registry now (after the fact) will not help you; if previous versions aren't turned on before an accidental change, there are no snapshots of previous states to go back to.

    Do you use the backup functionality built into the product to take backups of your shares?


    I'm not on the WHS team, I just post a lot. :)
    Friday, September 30, 2011 1:25 PM
    Moderator
  • I back up my PC's.   I have not done anything to back up my shared folders through the home server.  Stupid on my part, I just assumed that I have 2 drives that it would have been smart enough to have some kind of recovery.   After reading posts last night, it does not look like it does that.    Unbelievably Stupid design.  Home server had the potential to be a block buster product but not having this right out of the box is really one of the dumbest things I have ever seen.

     

    Luckily I have a copy of my files from a year ago, when I started putting stuff on my server, so I don't think I have lost much.  I just spent hours organizing them and removing duplicate files.  I certainly know that I need to back up my server to an external drive or duplicate the shared folders on the server once a month.

     

    The thing that gets me, is I never hit delete.  I was looking at the folders and noticed my main picture folder was listed under another directory, when I did a drag and drop back to where it was originally, it only moved 3 directories.

    Friday, September 30, 2011 5:07 PM
  • Unfortunately, people have an unrealistic idea of what RAID and RAID-like technologies like Drive Extender (which is similar conceptually to mirroring) really do for them. RAID wasn't conceived as a data protection technology. All RAID protects you from is the loss of a single disk. It doesn't protect against any sort of user or software error which damages data (the damage will, in all probability, be propagated immediately to the mirror volume in a RAID 1 array, or will be baked in to the parity calculations for RAID levels that use parity), and it doesn't protect against any disaster which affects more than one disk (including "Acts of God" like fire, flood, etc.). For actual data protection, nothing substitutes for regular backups.
    I'm not on the WHS team, I just post a lot. :)
    Friday, September 30, 2011 6:27 PM
    Moderator