Unexpected results when replacing boot volume

[Todd Nine]

Hey All,
I recently was upgrading drives in server, and I accidentally smashed my USB drive that was my root volume (whoops). I created a new USB stick, booted it, and imported my volume "internal". I checked the system->dataset volume is set to "internal", my volume in my server, then rebooted. After my reboot, none of my jail settings are preserved, nor are any of my share settings preserved. I assumed these were stored in the system data set and would be retained if I replaced the system flash drive, is this not the case? Do I have a way to recover them, or will I need to manually redefine all my share and jail settings?

Thanks,
Todd

 

[dlavigne]

Which version of FreeNAS?

Did you reset the Jails -> Configuration to point to the dataset holding the jails?

Don't confuse the system dataset with the config db. If you haven't been saving the config db, you don't have any settings to import after a reinstall.

 

[DrKK]

What dlavigne said.

 

[danb35]

...but if your system dataset is in the same place, you probably have copies of your config database at /var/db/system. If you can find one from before you smashed your boot device, you should be able to upload it and move forward.

And perhaps you can use this as an opportunity to add another boot USB and mirror them.

 

[Todd Nine]

Hey guys,
Thanks for the reply. I'd saved my configuration before I started my migration process. I was able to restore it, update the root share mount points, and was rolling again. Thanks for the help!

A follow up question, is there a way I can do rolling config exports to a storage media via cron? This way I back up my config nightly to storage. I can sync that to something like dropbox for an offsite backup.

 

[DrKK]

Cyberjock and I do this exact thing, nightly. You will find a post in the forum on it if you strategically search. It's a simple matter of making a shell script.

 

[danb35]

...and though cyberjock's script doesn't copy the database off-system, it shouldn't be difficult to modify it to copy to some other mounted filesystem.

 

[DrKK]

...and though cyberjock's script doesn't copy the database off-system, it shouldn't be difficult to modify it to copy to some other mounted filesystem.

Indeed. I left that unsaid as an exercise to the reader. :)