Move to a new SSD Disk with replication tasks

pete_mor

Cadet
Joined
May 13, 2014
Messages
4
Hi,

I have TrueNAS Core 13 and I want to move my boot SSD to a new one with different capacity. No datasets are on this disk

From searching the forums I found out that the best way is to backup config, install to new disk and restore config which is straight forward and an easy task

My question is that this system is my secondary one that stores the mirrored snapshots from my main Truenas Core 13 (of course on different disks). What happens to this mechanism after I install and restore the config? Will I have to recreate the jobs on my main system? Will the system recognise the already stored snapshots or start from the beginning?

Thanks
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
After the config restore, your system will behave (and essentially be) the same server that it was before the reinstall.

There should be no need to change anything.

Make sure you backup your ssh key files if you have those and put them back after.
 

pete_mor

Cadet
Joined
May 13, 2014
Messages
4
After the config restore, your system will behave (and essentially be) the same server that it was before the reinstall.

There should be no need to change anything.

Make sure you backup your ssh key files if you have those and put them back after.
Thanks for your answer.

Can you please direct me on how to backup my ssh keys? I have only found documentation about scale

Do you mean backup /root/.ssh ? I have only the authorized_keys file there. Is that it?
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
Do you mean backup /root/.ssh ? I have only the authorized_keys file there. Is that it?
Yes, that's the only thing that the config backup doesn't catch from the boot pool.

Well, maybe also the encryption keys (particularly if you have legacy GELI encryption), but I'm guessing you don't have that.
 

pete_mor

Cadet
Joined
May 13, 2014
Messages
4
Yes, that's the only thing that the config backup doesn't catch from the boot pool.

Well, maybe also the encryption keys (particularly if you have legacy GELI encryption), but I'm guessing you don't have that.
ok thanks a lot. It is clear
 
Top