locked
Migration / Upgrade Challenges RRS feed

  • General discussion

  • Is it me, or do the migration / upgrade challenges present a significant roadblock to moving to V2?  Why is this being made so difficult?  My understanding is:

    - No real way to upgrade from 32 to 64 bit in place (understandable)

    - No tools (yet) to preserve and copy data to V2.  Someone posted steps to juggle the drives and manually copy from shares.

    - Due to new DE, can't plugin V1 drive into V2 without it wiping data

    - Even if I wanted to buy new hardware, I can't even run V1 and V2 side by side at the same time.

    I am an early adoptor and love to have the latest release of anything, for better or worse, but this seems above my pay grade.  I'm sure I will find a way when the product is GA to make it work, but please help me and those at my level make an easy move to V2.  I WILL buy it, and I WILL make an excuse to build a new box to run it, but you need to make it easier.  Please please please....  I advocate WHS everywhere I go, and have sold 2 of them for you, please take care of me :)

    Friday, April 30, 2010 8:05 PM

All replies

  • Juggling drives is tedious, but not difficult. It's your best option, and it can be implemented fairly easily as follows:

    • Purchase one (or two if you want to turn on duplication immediately, which I recommend) new drives for your server. Make them nice and big, 1.5 TB drives are looking sweet right now.
    • Shut down your server and remove all the drives.
    • Connect the one (or two) new drives, install, configure.
    • If you will need additional shares, create them now.
    • Shut your server down.
    • Connect as many old drives as you can be sure you'll empty. Note: don't connect the old system drive. Handle that from another computer at the end of the process.
    • Copy from each of the old drives (<drive>:\DE\Shares\etc.) to the new drives in your server. There will be one new "drive" per share, with an eponymous folder within.
    • Once you're done with all the old drives you've got hooked up, if you have no more drives, add them all to server storage. If you do have more drives, add the larger drives to server storage, then shut down and swap the smaller drives for the remaining drives from the old server.
    • Last step is to connect your old system drive to another computer and see if there's anything in <drive>:\DE\Shares\etc. on it's second (larger) partition.
    I honestly don't see Microsoft building a migration tool. Maybe some third party will.
    I'm not on the WHS team, I just post a lot. :)
    Friday, April 30, 2010 8:21 PM
    Moderator
  • Thanks Ken, I did see those instructions, and I'm sure I could probably make it work.  This just scares me a bit, and I would *prefer* to run V1 and V2 side by side and migrate at my leasure without risk of losing data with a Robocopy or RichCopy type tool.  I hope that they will find away to have both connectors running at the same time (supported), this would alleviate my concerns.  I would think this would be a sensible request and would allow users to migrate and bring V1 offline on their own timeframe once they are convinced V2 is stable.
    Friday, April 30, 2010 8:30 PM
  • Heh. For side-by-side, buy lots of disk space.
    I'm not on the WHS team, I just post a lot. :)
    Friday, April 30, 2010 8:49 PM
    Moderator
  • Hi deepcscuba,

    I've done this twice, once from my 'Beta' home made WHS to a HP MSS EX470, and back to the 'Upgraded' home made WHS, when the lack of RAM/Power got the better of me.  :o)

    I had both Boxes side by side and connected to the same router.
    Installed or Setup the OS, and configured the Users / Shares on the 'new' WHS.
    I then Installed SyncToy (via RDP) on the 'old' WHS, and set it sync up all the shares,
    i.e. 'old' Music to 'new' Music, 'old' Photos to 'new' Photos, and so on.


    After a couple of days, when I was sure that every thing was OK.
    I started re-installing the connector software on our PC's pointing them to the 'new' WHS.
    I kept the 'old' WHS handy for a while, but never needed to swap back. :o)

    Friday, April 30, 2010 11:27 PM
  • Side by Side doesn't necessarily have to take any more disk space than the disk swap upgrade - but it does require another motherboard/processor/ram/case.

     

    This is what I am planning for my upgrade to vail - I have a spare Athlon 64x2 motherboard I am going to use to set up vail side-by-side with 1 500GB drive. I'll move enough data over that I should be able to then remove a 1TB drive from my v1 server and add it to the vail server - etc, until all 6 disks are moved.

     

    This will have the added benefit of allowing me to create new backups of my machines under vail, while still having the v1 server up with the valid backups.

     

    I've done this before when I rebuilt my v1 server with the current mobo that it has... in this way, Vail should allow me a smoother path overall since as it's been described, vail will let me temporarily move the whole drive set to the "spare" mother board and then when I have all the data migrated to a DE v2 drive set, I'll be able to pop one drive back in the original WHS box and install a new copy of vail and then just move the storage drives back over to the "permanent" vail box and promote the drive set to be the storage pool.

     

    Saturday, May 1, 2010 12:18 AM
  • Thanks Ken, I did see those instructions, and I'm sure I could probably make it work.  This just scares me a bit, and I would *prefer* to run V1 and V2 side by side and migrate at my leasure without risk of losing data with a Robocopy or RichCopy type tool.  I hope that they will find away to have both connectors running at the same time (supported), this would alleviate my concerns.  I would think this would be a sensible request and would allow users to migrate and bring V1 offline on their own timeframe once they are convinced V2 is stable.
    You don't need any connector software installed on a client in order to access the shares (just a valid user name and password on each server).  Just set up a batch file (or whatever tool you want to use) and copy from one to the other.
    Saturday, May 1, 2010 2:22 AM
    Moderator
  • Thanks Ken, I did see those instructions, and I'm sure I could probably make it work.  This just scares me a bit, and I would *prefer* to run V1 and V2 side by side and migrate at my leasure without risk of losing data with a Robocopy or RichCopy type tool.  I hope that they will find away to have both connectors running at the same time (supported), this would alleviate my concerns.  I would think this would be a sensible request and would allow users to migrate and bring V1 offline on their own timeframe once they are convinced V2 is stable.
    You don't need any connector software installed on a client in order to access the shares (just a valid user name and password on each server).  Just set up a batch file (or whatever tool you want to use) and copy from one to the other.

    I didn't know that, I thought you had to have the connector.  Thank you!  This makes sense and will be my migration plan, and I will just repurpose my V1 machine.  Perfect.
    Saturday, May 1, 2010 4:27 AM
  • ... and I will just repurpose my V1 machine.  ...

    Please read the announcement at the top of this forum about Vail not being supported in a production environment.

    That means that you should not put the only copy of irreplaceable files on your Vail server!!

    I have all of my files on my trusty HP MediaSmart; when I have enough storage to put my Vail server into production, I will still have all my files on my MediaSmart, synced nightly to Vail using a robocopy command.


    I'm not on the WHS team, I just post a lot. :)
    Saturday, May 1, 2010 3:08 PM
    Moderator
  • Yes, understood.  I'm talking when Vail goes GA.  And it will probably take me that long to sell the wife on building a new machine :)
    Saturday, May 1, 2010 4:03 PM
  • I have to emphasize the beta nature of this version of Vail whenever I see what looks like someone about to ignore that announcement; I would hate for someone to lose important data, and I would hate more for someone to say "but nobody ever said I shouldn't!" because they failed to "look up".
    I'm not on the WHS team, I just post a lot. :)
    Saturday, May 1, 2010 10:01 PM
    Moderator
  • As my wife always reminds me that "It is grounds for divorce if I lose her pictures" (she is a photographer).  Hmmm.... maybe installing the beta in production isn't sounding so bad...  lol.  j/k

    Saturday, May 1, 2010 11:34 PM