Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Backup on Two Different WHS RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    I have been utilizing WHS v1 Beta, then RTM, then purchased OEM, then purchased HP MSS 485. I am now getting ready to install Vail on a Dell P4 3.6ghz with 4 gig of DDR2 Ram. Is there any resonable way to continue to back up on two different windows home servers as I know I can not count on Vail as my Production unit.
    Wednesday, April 28, 2010 8:41 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    No. You can only have a client connected to one Windows Home Server at a time.

    http://www.tomontech.com
    Wednesday, April 28, 2010 8:48 AM
    Moderator

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    No. You can only have a client connected to one Windows Home Server at a time.

    http://www.tomontech.com
    Wednesday, April 28, 2010 8:48 AM
    Moderator
  • Question
    Sign in to vote
    1
    Sign in to vote

    I am successfully running both WHS and VAIL.

    When VAIL setup tells you to remove the WNS Connector, do it-- and complete VAIL setup.

    Then go back and reinstall WHS Connector from Software Folder after VAIL is done setting up.

    Works for me.

    Friday, April 30, 2010 4:21 PM
  • Question
    Sign in to vote
    1
    Sign in to vote
    Please don't do this. There is a good reason why we blocked this in the v2 connector. Your backups may succeed (assuming the v1 and v2 times don't coincide) but you most likely will not be able to do restores on that client either from a v1 backup or from a v2 backup. This is a completely un-supported (read: untested) scenario and you are likely to run into weird problems.
    This post is "AS IS" and confers no rights.
    Friday, April 30, 2010 4:41 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Please don't do this. There is a good reason why we blocked this in the v2 connector. Your backups may succeed (assuming the v1 and v2 times don't coincide) but you most likely will not be able to do restores on that client either from a v1 backup or from a v2 backup. This is a completely un-supported (read: untested) scenario and you are likely to run into weird problems.
    This post is "AS IS" and confers no rights.

    Now I'm intrigued.  Exactly why would such a thing cause restore issues, and have any actually been found?  Backup does not modify the client PC in any way, and I am guessing the two connectors have no knowledge of each other once they are successfully installed.  Each backs up the client to its own backup service and is unlikely to interfere with the other's operation.  Restoring should be similarly independent since only one backup server would be involved and the other would not.

    Sorry, I am just very curious if you have any interesting stories to share, thanks.

     

    Friday, April 30, 2010 5:12 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Please give it a try and let us all know what happens. :)
    I'm not on the WHS team, I just post a lot. :)
    Friday, April 30, 2010 5:15 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    And I strongly suggest you do it on a PC that you’re happy to flatten anyways.  :)
     
    This post is "AS IS" and confers no rights.
     
    "Ken Warren" wrote in message news:e20ff6a4-a93a-44a1-a552-7f41fea34017...
    Please give it a try and let us all know what happens. :)
    I'm not on the WHS team, I just post a lot. :)
    Friday, April 30, 2010 5:55 PM
    Moderator
  • Question
    Sign in to vote
    1
    Sign in to vote

    No problem roddy_0 :)

    For one - the restore driver file for both v1 and v2 have the same name. We could have changed the name but then there were other issues that we would have to resolve - some known (eg. v1 and v2 engines backing up at the same time, etc) and potential unknowns as well in order to support this scenario. In the end, it came down to resources vs priority and so we decided to block this in the v2 connector install itself.

    This post is "AS IS" and confers no rights.
    Friday, April 30, 2010 5:57 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Adding onto what Imran says,
    (BTW, this is the same question as discussed on http://social.microsoft.com/Forums/en-US/whsvailbeta/thread/deb65bba-a77e-4732-ab20-518518e4a551)

    A Computer can only be connected to on Windows Home Server at any one time, this is version independent. The Connector included in the original release of Windows Home Server does not yet block on install if it sees a Vail Connector but it should.

    Your computer is likely now in an state where Connector uninstalls are not working as expected.

    This post is "AS IS" and confers no rights.
    Kind regards /Lennart
    Friday, April 30, 2010 6:08 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    No problem roddy_0 :)

    For one - the restore driver file for both v1 and v2 have the same name. We could have changed the name but then there were other issues that we would have to resolve - some known (eg. v1 and v2 engines backing up at the same time, etc) and potential unknowns as well in order to support this scenario. In the end, it came down to resources vs priority and so we decided to block this in the v2 connector install itself.

    This post is "AS IS" and confers no rights.

    That is very interesting, and makes sense now I think about it.  Thanks for the explanation.

     

    Friday, April 30, 2010 6:08 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    And I strongly suggest you do it on a PC that you’re happy to flatten anyways.  :)
     

    PC, he says.

    Use a darn virtual machine. With undo disks so you don't have to flatten it. That's how I do most of my "Kids, please don't try this at home!" stuff with Windows Home Server. :)

    But to follow on, I'm going to give this a try in a VM with undo disks turned on over the weekend, if I can remember. My bet is that there is no recovery short of flattening the machine, as Sean suggests.

    I'm not on the WHS team, I just post a lot. :)
    Friday, April 30, 2010 6:58 PM
    Moderator