Hello,

I have a server with a pro key.

Array has 5 data drives + 2 parity

There is also a 2 ssd btrfs pool and 1 ssd xfs pool.

The server is a power hungry HP Z620 with a 9207-8e hba and a das attached.

Backups are made on unassigned drives (btrfs) and on a external usb (exfat) attached to my macbook air.

I moved and now my server is in the basement not very accessible. I have no ipmi and intel amt vpro is not very convenient (no kvm) on the Z620.

For power savings purpose i've just bought a minisforum ms01 and a unraid plus key to run my unraid server. 

The plus key is enough for my arraid and pools.

I plan to repurpose the Z620 as backup server.

The Z620 has 128Gb ram.

The ms01 will have 64Gb ram and also a 9300-8e hba.

What is the best way to set-up the ms01 to make it my principal server ?

 

edit: in the Z620 i have a nvidia P400 used for transcoding in plex and tdarr

in the ms01 i will use quicksync.

I want my vm and dockers to be configured from the 1st server.

So in these conditions what's best?

-configure the ms01 as new server with new key, the later reconfigure backup server 

-use the actual usb key for the new server

Edited February 23, 20242 yr by caplam
more details

Few answers here. I will rephrase.

 

I have 3 vm, 50 dockers, 6 disks and 3 ssd to move from one server to another.

Hardware is quite different. I will come from a bi xeon E5-2650V2 with quadro P400 to minisforum MS-01 with i9-12900H.

I have 2 license keys: 1 pro from the old server and 1 plus not yet installed. I'd rather keep the ip of the old server for the new one so i have not to reconfigure everything.

I will use the old server as backup server.

What is the best way to do this?

What about disks for the new server?  (It is not clear weather you are moving the disks from the old server to the new server or purchasing new disks for the new server.)

 

1 hour ago, caplam said:

I'd rather keep the ip of the old server for the new one so i have not to reconfigure everything.

 

This is a problem.  I would hope you realize that you should not have two devices on your LAN with the same IP address.  (The same advice applies to computer/server names.)  I would think you would want to start with the new server having a new IP address and server_name until you get it setup properly.  You can then change the IP address and server_name on the old server to something new.  Then configure the new server to have the old server's IP address and server_name.

 

You also didn't say what data is going to be on the new server.  (One might assume that you want all of the data from the old server.  But is that true?)   Figure that 2-3 hours per TB of data will be required.  

 

I understand that VM can be a problem area that has to be considered. Also if you are passing any hardware through to a Docker. 

 

My approach would be to set up the new server and get it basically running with its new license. Don't install any plugins or Dockers at this point.  Then make a backup of your flash drive and have it safely stored on another computer. 

 

Most of the time, Plugins and Dockers are hardware agnostic and you can just copy the /config folder from the old server over.  (I would stop all Dockers and VMs before I did this.)  You will have to replace the .KEY file with the one from the flash drive backup that you made.   Then find the section of the manual about reinstalling Docker containers.   Make sure everything works.  Then tackle the VMs...

26 minutes ago, Frank1940 said:

Most of the time, Plugins and Dockers are hardware agnostic and you can just copy the /config folder from the old server over.  (I would stop all Dockers and VMs before I did this.)  You will have to replace the .KEY file with the one from the flash drive backup that you made.  

 

I forgot one thing.  If you do this the new server will now have the old server IP address (if it is static) and server_name.  You should shut the old server down before you restart the new server.  As soon as it is up, change the IP address and server_name (until you have everything working properly on the new server) and reboot the new server again.  In the mean time, you can restart the old server so that it can provide service until you have the new one working the way you want.

 

PS---  You can actually login to the new server files from any Windows computer by the usual way using either server_name or IP address for the new server.  If there is a limit to the number of servers that a Windows client can be attached, it is very high (like, >64?).  So you can test things out before you make the final switch.  You can even use the same user name and password on both servers!

My plan is to move all disks and ssds from the old server to the new. The new server is going to replace the old; so normally i have not to transfer data across the network.

I want to keep everything (shares, dockers, vms,...). I have to deal with different hardware for docker (plex and tdarr use quadro p400 on the old server for hardware encoding and it will be quicksync on the new one). I have no hardware passed through to the vms.

On the old server parity, disks 1,2&3 are on internal sata ports; the others in a sas enclosure. 

On the new servers all spinners will be in a external sas enclosure.

Then later configure the old as a backup server with other disks probably as unassigned drives.

Of course i'm aware i can't have 2 servers with same ip (i have dhcp reservation on the router). I don't need both servers to run at the same time.

 

Assuming no RAID controllers on old or new system, Unraid should recognize all disks just as before and just boot up as if nothing had changed.

just hbas: lsi9207-8e in the old and lsi 9300-8e in the new.

For now i'm fighting with the minisforum ms-01. It's tricky to have it running as i want.