March 17, 20188 yr I've been using unRAID Pro for a few months now and I love it - I've been talking it up with another tech savvy friend and he wants to duplicate my set up on his hardware. I don't feel like I'm an expert yet, so I thought I'd post here and find out what the easiest/best way to clone my system would be, then I can get him a license key and then tweak his specific set up from there. I was thinking something like this: - Copy all files on flash drive to new flash drive except my license key - Run the make bootable script on new flash drive - Boot into unRAID on new server - get a trial key - start up array with his disks - Tweak shares if necessary - Copy over docker/VM images and app data and bring them online - Tweak everything else from there Does that sound about right or did I miss something? Thanks!
March 17, 20188 yr Community Expert 2 minutes ago, chris_b_chicken said: get a trial key Trial key doesn't work with an existing config, you need to start fresh or use a licensed flash drive.
March 17, 20188 yr Author So I would either have to configure everything from scratch with a trial key, or have him pay for a license and then I could copy over my config to his licensed flash drive? Does the level of license have to be the same (ie I have Pro but he'll probably only want Plus or Basic)?
March 17, 20188 yr Community Expert 2 minutes ago, chris_b_chicken said: So I would either have to configure everything from scratch with a trial key, or have him pay for a license and then I could copy over my config to his licensed flash drive? Correct. 3 minutes ago, chris_b_chicken said: Does the level of license have to be the same No
March 17, 20188 yr Community Expert When we are moving drives to a new system we will typically just use the same flash drive on the new system. unRAID figures out the hardware it is running on during boot so the specific hardware isn't usually a problem when moving to another system. But you are talking about copying your setup to another. The key is tied to a specific flash drive and won't work on another. And super.dat in the config folder is the exact disk assignments by serial number so that obviously won't work with other drives. Many of the other things may work assuming you have identically named user shares and you only reference user shares and not disks in docker mappings, etc. And some things may not work on another system depending on their settings, such as network settings. It might be better to just use the settings on your system as a guide to configuring his system, rather than actually copying the setup.
March 17, 20188 yr Community Expert If you do want to try to copy things, I think I would assign the disks first, then shut down and try to copy some of the other things in config (not key and super.dat of course).
March 17, 20188 yr Community Expert If you plan to set these up on the same LAN (at least initially) then DHCP should get you going for the network, but you still need to make sure you have different server names. If you boot into GUI mode then it might be simpler to apply any tweaks needed, especially if there are network conflicts between the 2 servers, since the webUI in GUI mode is just going to localhost.
March 17, 20188 yr Author Thank you both for the input. I guess I'm more of a noob than I thought These servers will initially be set up on the same network, so I think in the long run it'll be best if I just do it from scratch and use my server's settings a baseline rather than try to directly copy anything (besides media files on my shares), even if it takes me a bit longer.
Archived
This topic is now archived and is closed to further replies.