The BeyondRAID configuration seems to be stored on the disk pack. You don’t really need to think about the raid configuration yourself, as long as you keep the disk pack together.
Here’s my experience: I have two Drobo FS chassis. One has 5 2tb drives and it wouldn’t start due to file system corruption (the disks were fine, the data was fine, but the Linux file structure got damaged due to power-outage).
My second Drobo FS chassis I bought on eBay expecting to want to use it for additional expansion… but I’m not actually using it to store anything yet, so I used it for experiments. I created a 2 disk “disk pack” first. that worked fine. Then, I pulled those out (powered down) , powered up the drobo, and inserted a third test disk. The drobo complained, so I did a reset, and it created a 1 disk “disk pack” with that drive. After that, I was able to switch back and forth (powered down) those two “Disk packs” freely, and the data changed back and forth as I expected… So, one Drobo FS was able to seamlessly swap between two disk packs without loosing or corrupting any data. Then, I took my 2 disk “disk pack” and I put it into my main drobo (after removing my big disk pack and setting it aside)… and powered up… now the 2 disk “disk pack” was running in my main drobo as it did while in the test chassis. So, this proves that one disk pack can swap back and forth between two drobo units without any issues. The shares config and user config seemed to follow the disk pack, but the name of the drobo and the network configuration stayed with the chassis.
At no point during any of this did I need to touch, configure, or even think about the RAID configuration. Just treat the disks as a pack, and NEVER insert or remove any drive while the power is on unless you intend to erase that drive’s data.
I didn’t have to do any soldering… this was all software work.
if you install the dropbear droboapp, the SSH server is on port 22. I used PuTTY on my windows machine to connect using the IP of the drobo and port 22.
When using Dropbear, the SSH is installed on the disk pack… so if you remove the disk pack, it removes the SSH server as well. There’s a method of moving the SSH startup commands from the disk pack to the flash memory area of the Drobo, but it’s tricky, and requires manually editing some of the config files in the flash memory area.
I had to the procedure in order to use dropbear to fix my corrupt disk pack because the disk pack would not mount - and as such, I couldn’t put dropbear onto that disk pack. I had to use a test disk pack, copy to the settings from the disk pack down to the flash memory, then swap the packs, then I was able to SSH into the drobo even when the disk pack wouldn’t start.
I hope that information helps to answer some of your questions.