Ilan

Restore Computer Backups After Server Reinstallation

7 posts in this topic

I remember reading on the forum that after the re-installation of the server the backed up computers will be listed in the the Windows Home server console and there being a way to re-associate the computers to there collective backups but I can't find that thread. Does anyone remember where it was located?

Share this post


Link to post
Share on other sites

Upgrade to a WGS Supporter Account to remove this ad.

If you restore the backups using the WHS BDBB add-in, the re-association will be automatic as it will put the PC's unique ID's back on the server. I have just done this moving from my home-brew Dell server to an HP X510.

I think I may have written what you were after, and if you can't get to where you need to be by restoring the backup database, post back and I'll give some more help.

Share this post


Link to post
Share on other sites

I am getting ready to move to WHS 2011 and am using a 2nd older system to build a new installation WHS v1 by using WHS BDBB to backup the BDB and then restore on the new WHS v1. This way I can reload current hardware with 2011. My added question to this thread is that do I need to re-install the connector on my workstations so they get added to WHS first or does the restore of the DBD recreate the clients in WHS? What is the order of restoring the DBD and adding clients to the new build of WHS v1?

Thanks

Share this post


Link to post
Share on other sites

Restore in BDBB recreates the clients, but it may be worth running discovery.exe on the clients to make sure (it is in the C:\Program Files\Windows Home Server folder). You should not need to reinstall the connector if the new server is up to the same patch level as the old one.

Restore BDBB before looking to see if you need to add the clients.

1 person likes this

Share this post


Link to post
Share on other sites

I am having trouble restoring a BDBB backup.

I was taking off-site backups every months and when a disk died I replaced it and did a restore but the BDBB was damaged and the repair failed. I retried twice and had the same issue.

There's not much point in taking off-sites if they can't be restored so I bought a second, identical Acer server since I din't want to mess with my "production" server. I backed up the BDBB and tried to restore it to the second Acer and got exactly the same problem.

The backup disk is on a computer and shared to the servers, there were no errors with the backup and it appeared to complete correctly.

I use version 1.0.3.3 of Alex Kuretz utility to do the backup and restore.

Is there a trick, this is very frustrating.

Any help will be appreciated.

Share this post


Link to post
Share on other sites

Have you tried manually restoring?

As in, stop the backup service, copy the files over (should be a bunch of .dat files), and then restart the service.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now



Upgrade to a WGS Supporter Account to remove this ad.



  • Posts

    • There's a post on problems re-installing WHS 2011 Connector software on Windows 10 with anniversary update here: http://forum.wegotserved.com/index.php?/topic/31019-whs-2011-and-windows-10/&_fromLogin=1#replyForm Doing a clean install of Windows 10 appears to work, but much simpler is creating the folder: C:\Windows\System32\Task\Microsoft\Windows\Windows Server  and then installing the Connector.
    • I found a solution to the Connector re-installation problem here: https://social.microsoft.com/Forums/en-US/09a41a60-1696-4341-85f8-a1373a46082e/windows-10-anniversary-update-breaks-whs-connector-install?forum=whs2011&prof=required Creating a folder named "Windows Server" in C:\Windows\System32\Tasks\Microsoft\Windows allowed the installation to complete in my Windows 10 that had been upgraded in place and then had the anniversary update. The Connector was still working after the anniversary update, but Lights-Out wasn't, so I needed to re-install. I was getting the installation error described above until I created the folder C:\Windows\System32\Tasks\Microsoft\Windows\Windows Server
    • What exactly did you do? Did you set up the shares as read for everyone then NTFS permissions for those with read/write? This is what I am currently struggling with. Trying to find the best setup for my Win10 shares.
    • The experience I have had with Storage Spaces has not been good. I had a disk go bad and even though I had redundant storage set up, the system did not rebuild all the stored folders completely and I had to resort to other backups that I kept on another server. Note that Storage Space data is not recoverable if the system goes bad. Drivepool still has the files fully readable just like the old duplication system in WHS V1. 
    • I get the above error dialogue when I run the connector on my Win 10 pro client.  Followed the issue resolution on TechNet which say start cert service in IIS on server but this was already running.   I've downloaded the Win 10 connector with no joy also.   Please help.
  • Popular Contributors