** Forgive if this has been Covered** Looking to copy everything to new hardware (drives, MB, enclosures ETC) from one to another box


Wiseone001

7 posts in this topic Last Reply

Recommended Posts

upon looking (quickly mind you) i want to completely copy one unraid server to another. Can not transfer physical drives(different size, current 3.5 moving to 2.5 enclosures) but moving from 500GB to 1TB enterprise units (16 of them) :)

My thoughts on this was to configure a test box, install all of my dockers and copy the file structure over as it sits on my current unraid system (recently new Pro user and extremely noob) but picking it up fast. 

is there a documented way to accomplish this and then when all said and done, decommission old hardware and move usb to new hardware and invoke my current license?

 

Again I'm sure being a noob to unraid, I'll take the heat :P  (insert spoon feed answers here <-- )

Thanks

Bill (Wiseone001)

Link to post

I doubt there is a guide that would fit as it is a specific request. Generally people tend to change MB, CPU etc. but keep the drives.

 

However, I am sure we can provide answers and guidance on this use case.

 

As base information, I think we would need :

  • your diagnostics (Tools/Diagnostics) as it provides tons of information on your actual system
  • an idea of your file structure
  • what the system is used for, the dockers/VMs you run, ...

I am sure I forget stuff, but we can build a plan from that.

Link to post

Sounds like a solid plan (set up new server with trial license temporarily).

 

Do you have a way to physically connect the new drives one or more at a time to the current box?

 

If so, then you could mount and format the new data drives in UD, rsync each drive, then physically install in new server fully populated. Run it up, assign and build parity, that would take care of the parity data array.

 

Migrating the containers might be a tad more complex, where do you have container appdata set right now?

Link to post
3 hours ago, ChatNoir said:

I doubt there is a guide that would fit as it is a specific request. Generally people tend to change MB, CPU etc. but keep the drives.

 

However, I am sure we can provide answers and guidance on this use case.

 

As base information, I think we would need :

  • your diagnostics (Tools/Diagnostics) as it provides tons of information on your actual system  (Will Supply as soon as I get a new system up and hope that will be tonight maybe tommorow) I know you will want for both systems.
  • an idea of your file structure
  • what the system is used for, the dockers/VMs you run, ...   (Please see comment under)

I am sure I forget stuff, but we can build a plan from that.

As above, I will get this information for you as soon as i construct the second box, hopefully that is today..

file structure? how many disk's and how big the storage arrays are? i can tell you i plan on making it double parity, (2 1TB hard drives), Double cache Drives 2x 120Gig SSD) and the remainder of the 12 hd's will be set up as my array at 12 TB..

My use is multi platform, i have dockers for usenet, for VPN access, i will be running VM's for my active directory domain, my exchange and my PXE services, on top there should eventually be FTP and some sort of media service for movies/TV and Jukebox service.  

This is the simple down and dirty config for my unraid.. I know as a noob I will expand but i already know how i want it to work. i just to gain the experiance with it to make it do the things i want it to do like pxe boot a desktop pc into a virtual enviroment all from within a server 2019 DC VM... i want to store my physical servers as a vm and decommision my old hardware. 

3 hours ago, jonathanm said:

Sounds like a solid plan (set up new server with trial license temporarily).

 

Do you have a way to physically connect the new drives one or more at a time to the current box? (no) but original Server Still active and Backup services running daily

 

If so, then you could mount and format the new data drives in UD, rsync each drive, then physically install in new server fully populated. Run it up, assign and build parity, that would take care of the parity data array.

 

Migrating the containers might be a tad more complex, where do you have container appdata set right now? (in its current default folder. i do have it backed up but it is mostly stock under the hood. tried not to deviate as i wanted and thought i may have to rebuild from scratch.)

unfortunately, I can not maintain structure as the hard drives are different form factors.. im increasing in storage size but decreasing physically size of the hard drive.. going from 3.5 SATA to 2.5 SAS,  now keep in mind its a fully functional unraid right now and loaded up as i built this using the trial period, now have the pro license, i want to build(more like copy) everything as it is to the new hard ware platform and then use my legit pro key to turn it up. then decom the old one.

 

 

Link to post

One plan would be not to install the parity drives until you have populated the array with the data from the old server.   (That will increase the write speed to the array by a factor of two or more!) 

 

I would then consider just copying the data over the network.  It sound like you have less than 12TB of data which means the copy time would be about 36-40 hours (if my math is correct!)

Edited by Frank1940
Link to post

You are correct I probably have less then 4 gig of data on a gig back bone Network. With a true switch. File copy shouldn't take that long with 4 gig connections running from one box to another. But that seems like a good idea. Configure without parity, then add parity. Ok

Now for the USB with the pro key on it. Just move it to the new server? Or is there a file structure I need to copy from the new box to the old key so I keep my settings, configs etc.

Sent from my SM-N986U using Tapatalk

Link to post
11 minutes ago, Wiseone001 said:

Now for the USB with the pro key on it. Just move it to the new server? Or is there a file structure I need to copy from the new box to the old key so I keep my settings, configs etc.

Depends. Remember the cardinal rule that the *.key file is paired with the specific USB stick, so if you get the new box up and running exactly the way you like it all things included on a trial key, then you would copy the config folder from the trial key, delete the *.key file that goes with that trial stick, delete the config folder on your current licensed stick making sure to keep a backup, restore the new server config folder to your licensed key, copy the *.key file that goes with that stick back into the config folder, done.

 

The config folder holds all your customizations, and 99% of the files in there are text files, so browse around and get familiar, you might figure some stuff out.

Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.