restoring config file, still need to set...

[nojohnny101]

so i am very familiar with the process of restoring a previous system after a fresh install by uploading the config file...

but does the config file really restore everything? i think i read somewhere that passwords have to be reset is that correct?

so my question basically is, what does the config file NOT restore.

I have a few jails, 6-8 datasets, 4-5 users, and nothing else special. i use SSH, SMART, CIFS, and AFP series. that's it.

thanks!

 

[danb35]

To the best of my knowledge, the only thing it doesn't cover is the disk encryption keys, if you're using encryption. I know that when I restored my 9.3.1 config file on 9.10, all my passwords were set as before.

 

[nojohnny101]

@danb35 ok thanks. i do not use encryption so i'm good there. i just did a fresh install of 9.10 and restored a 9.10 config file and everything seems to be there. mysteriously, the GUI shows no SSH public key for any of the accounts but when checking through the CLI, the key is in its proper place. probably just a GUI bug.

if i find anything else missing over the next day or so i'll report back.

 

[SweetAndLow]

If uploading to the same system it was taken from it will have everything.
Encryption keys are the exception but they are downloaded from the gui in the same way the config is so it's important to backup those just like the config.

 

[nojohnny101]

well reporting back after a few days of the systems (main FreeNAS box and the back FreeNAS box that the main one replicates to) running their normal stuff....

two things failed:

1) the replication task failed because the replication key for the PUSH account was not saved in the root user on PULL (the account I use for replication). clearly this was working and the key was there before the fresh install and restore of the config files. don't know how that got lost.

2) the email account that i setup FreeNAS to use in order to send emails was missing a password as well. all other settings were intact, just the password was missing so i got an error when i woke up this morning about that.

fairly easy fixes but i suspected some minor things like this would happen after a clean install and restore of config. I guess this thread is just more of an FYI for others worried about what the config files doesn't cover. Granted, I do not have a complex setup and don't come close to covering all likely scenarios.

Also in the spirit of be thorough, here is exactly how I did the wipe and restore.
1) manually saved a config file to the desktop of local machine on the network
2) downloaded latest ISO from freenas website and created bootable flash drive
3) restart the box and then booted to install media
4) installed FreeNAS on mirrored USB flash drives (previously FreeNAS was installed on single flash drive)
5) made sure to choose "fresh install" because the installer detected a previous installation
6) installation completed
7) logged into the FreeNAS GUI and immediately uploaded config file

that's it. strange how the email password got lost and the SSH key for replication. bug maybe or something I missed?

 

[Robert Trevellyan]

bug maybe or something I missed?

Is (was) your system dataset on your boot pool or your data pool?

 

[nojohnny101]

Is (was) your system dataset on your boot pool or your data pool?

on my main FreeNAS box, the system dataset is located on the pool
on my backup FreeNAS box, it is located on the freenas-boot

 

[Robert Trevellyan]

on my backup FreeNAS box, it is located on the freenas-boot

That might be why PULL forgot the authorized key for PUSH.
EDIT: but probably not, according to what I see on my FreeNAS.

 

[nojohnny101]

That might be why PULL forgot the authorized key for PUSH.
EDIT: but probably not, according to what I see on my FreeNAS.

yea I was following your train of thought initially and almost included that observation in my last post but the system dataset is required to be located elsewhere on the target machine. replication requires that.

maybe someone with deeper knowledge of the underpinnings can chime in.

 

[JoelN]

I also have had password issues after uploading a config file. Not sure why. I usually check the following whenever I upload a config:

1. Make sure System > Email is working properly by sending a test mail.
2. Sometimes my UPS doesn't initialize properly so I go to the UPS service and enter Monitor User and Monitor password. One or both may be missing.
3. Make sure S.M.A.R.T. service has email address. Not sure if this is necessary but I check anyway.

 

[Mirfster]

Good Info, it was mentioned in a different thread where this stuff would be a great resource to have available.

Maybe if we are lucky an Admin might see this and make such a thing... /Hint Hint, Wink Wink