{"id":26723,"date":"2019-12-12T15:33:52","date_gmt":"2019-12-12T15:33:52","guid":{"rendered":"https:\/\/home.apeconsulting.co.uk\/adrian\/?p=26723"},"modified":"2019-12-31T10:02:45","modified_gmt":"2019-12-31T10:02:45","slug":"freenas0-config-1-not-so-long","status":"publish","type":"post","link":"https:\/\/home.apeconsulting.co.uk\/adrian\/freenas0-config-1-not-so-long\/","title":{"rendered":"FreeNAS0 – Config 1 (not so long)"},"content":{"rendered":"\n

Version 1 of this blog was going to be a long and winding affair that went through re-configuring FreeNAS0 with all the config from FreeNAS1, MANUALLY<\/strong>. The more I thought about what needed to be changed, the more I began to think saving the config from FreeNAS1 and uploading to FreeNAS0 was the right approach. Sure, I knew this would cause some problems (such as networking and passwords) but I decided it was the lesser of two evils, a bit like my vote in today’s General Election!<\/p>\n\n\n\n\n\n\n\n

The first thing I’d done, which I covered in the Build 2 blog<\/a>, was to create the pool, which I named APEpool0 (APE Consulting Ltd is the name of my company) and is consistent with the other 2 builds.  Next, I’d configured the networking, adding an interface and assigning a fixed IP address.  <\/p>\n\n\n\n

I then disabled all of the existing replication tasks from FreeNAS1 to FreeNAS2. There were several, as these were created for specific datasets rather than the whole pool, partly due to size restrictions on FreeNAS2, but also to allow different properties for each dataset (I keep snapshots of pictures and documents longer than media files).<\/p>\n\n\n\n

Next, I needed to enable the SSH service, and after a few failed attempts, eventually got the replication from FreeNAS1 to FreeNAS0 started.  Although I\u2019d used Google and found a few helpful guides, the manual <\/a>is actually your best friend here. Another useful tip is to try SSH’ing to each other using the appropriate passwords (at this point I also reset the root password on FreeNAS0, which I\u2019d just set as root during the installation \u2013 it\u2019s now something much more secure!).  Also, using the semi-automatic settings is a big help and something that wasn’t there the last time I set all this up. The last thing I had to do was move the system dataset from the pool onto the boot device.  I might leave it there, or move it back once everything has transferred.<\/p>\n\n\n\n

The way I\u2019ve actually done this is to create a periodic snapshot of APEpool1, including recursive datasets, and then to create a replication task to send this from FreeNAS1 to FreeNAS0, as below:<\/p>\n\n\n