Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[6.3.5] How to best migrate to a new server?

Featured Replies

Hey all,

 

Right now I have a dual E5-2670 setup which is quite loud, noisy, big and power hungry and overkill so i am looking to step down (also picked up some new drives) so i need to figure out how to best move over to the new setup.

 

The 'new' setup if this will be ok is a desktop that i was planning on re-purposing to unraid duty. It is an AMD Ryzen 5 1600 (6c/12t) 16GB DDR4 and i picked up 5x 8TB WD Reds (Was thinking Unraid6 this time around).

 

The media data that lives on the mechanical drives right now (about 13TB on the current setup) i was just gonna copy over the network but the docker apps and vms i was hoping to some how just move to the new server so i dont have to re set them up (all of the SSD's that they live on will be moving to the new server).

 

Could i do a trial version on the new server, copy the data over, then remove the old drives from the old pool, move the flash drive from the old server to the new server and add the new drives (with the data on them)?

Edited by Blindsay

  • Author

Any thoughts?

Unfortunately you seem to want the hard things easy and the easy things hard. Data copying is easy and straightforward, probably be quicker to move all the drives intact from the old to the new box, then migrate data internally either by upgrading the drives one at a time from parity or using UD or adding the drives to the array then removing all the old drives after you are done.

 

Migrating dockers shouldn't be TOO bad, they''ll probably just start back up if you move all your drives over at once.

 

VM's, however, may require resetting up the XML.

  • Author
On 12/22/2017 at 2:52 PM, jonathanm said:

Unfortunately you seem to want the hard things easy and the easy things hard. Data copying is easy and straightforward, probably be quicker to move all the drives intact from the old to the new box, then migrate data internally either by upgrading the drives one at a time from parity or using UD or adding the drives to the array then removing all the old drives after you are done.

 

Migrating dockers shouldn't be TOO bad, they''ll probably just start back up if you move all your drives over at once.

 

VM's, however, may require resetting up the XML.

 

 

Yeah unfortunately moving everything over is a bit of a pain. My current setup, the onboard storage controller died so i threw in a controller i had but it didnt support jbod so the drives are technically individual raid 0 arrays (terrible i know)

 

Would this work,

 

Move the usb stick along with the SSD's (since they have all the VM's) over to the new server (will it tolerate the change in cpu and mobo ok?). Setup the new mechanical pool on the new server.

 

Put a trial version of unraid on another flash drive and put that in the old server (Will it recognize the old array?) then copy all of the data from the pool to the new server.

4 hours ago, Blindsay said:

Move the usb stick along with the SSD's (since they have all the VM's) over to the new server (will it tolerate the change in cpu and mobo ok?). Setup the new mechanical pool on the new server.

Unraid will probably tolerate the change ok, with the proviso that you are aware of all the little things that are still works in progress with Ryzen. Your VM's, however, probably won't, especially if you are passing through any hardware. If you aren't passing hardware, then you will probably be able to set up new VM's using the existing disk images and they should work fine.

4 hours ago, Blindsay said:

Put a trial version of unraid on another flash drive and put that in the old server (Will it recognize the old array?) then copy all of the data from the pool to the new server.

If you assign all the array data drives exactly as they are currently, it should come up just fine. You should be given the option to tell it parity is already valid, then when you start it, do a parity check immediately.

  • Author
18 hours ago, jonathanm said:

Unraid will probably tolerate the change ok, with the proviso that you are aware of all the little things that are still works in progress with Ryzen. Your VM's, however, probably won't, especially if you are passing through any hardware. If you aren't passing hardware, then you will probably be able to set up new VM's using the existing disk images and they should work fine.

If you assign all the array data drives exactly as they are currently, it should come up just fine. You should be given the option to tell it parity is already valid, then when you start it, do a parity check immediately.

 

Thanks! Not passing through any hardware on the VM's, just curious why you think the VM's wouldnt work after being moved? (The VM's are running Ubuntu if that matters).

 

When i go to setup the old pool with the trial flash drive, im guessing i should make sure to note which drive is the parity drive (or would unraid recognize which one was)

3 hours ago, Blindsay said:

just curious why you think the VM's wouldnt work after being moved?

The generated XML's include specific RAM and CPU core assignments, I don't know, and don't have the systems up to compare whether an XML generated on such different bases would still come up ok. It certainly is possible they would just work, but given how closely tied virtual machine technology is to the specific platform, I doubt it would be seamless over such a differing base. Pure speculation on my part, I hope I'm wrong.

3 hours ago, Blindsay said:

When i go to setup the old pool with the trial flash drive, im guessing i should make sure to note which drive is the parity drive (or would unraid recognize which one was)

Yes, before you kill the old array, make a note of the serial numbers of all the data drive positions, and duplicate it on the new setup. As long as everything matches, it should come up fine. If anything shows up unformatted, STOP, download diagnostics and post them here for help. Whatever you do don't format anything.

  • Author
12 minutes ago, jonathanm said:

The generated XML's include specific RAM and CPU core assignments, I don't know, and don't have the systems up to compare whether an XML generated on such different bases would still come up ok. It certainly is possible they would just work, but given how closely tied virtual machine technology is to the specific platform, I doubt it would be seamless over such a differing base. Pure speculation on my part, I hope I'm wrong.

Yes, before you kill the old array, make a note of the serial numbers of all the data drive positions, and duplicate it on the new setup. As long as everything matches, it should come up fine. If anything shows up unformatted, STOP, download diagnostics and post them here for help. Whatever you do don't format anything.

 

Cool, thanks for your help. 

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.