Hello everyone,
I'm planning on expanding my current storage (4x4TB raidz2 to 6x4TB raidz2) very soon. I fully understand that I will have to destroy my pool and start from scratch and am ok with that since I have a backup solution to store all my data during the transition.
However, I'd like to make this process as easy as possible (duh) and I am wondering what the exact steps would be to achieve this goal.
So my questions are :
I was thinking of simulating the whole process with a VM at some point anyway (better be safe than sorry), but I would really appreciate a better understanding of all this from you guys.
Thanks for the help
I'm planning on expanding my current storage (4x4TB raidz2 to 6x4TB raidz2) very soon. I fully understand that I will have to destroy my pool and start from scratch and am ok with that since I have a backup solution to store all my data during the transition.
However, I'd like to make this process as easy as possible (duh) and I am wondering what the exact steps would be to achieve this goal.
So my questions are :
- Is the config backup useful in any way for this use case (destroying / creating new pool) ? Can it be used to restore the storage "layout" (I want to keep the way I organized my datasets, just expand their size) ? Basically I'm not sure what is stored in the config backup and what it can be used for, other than recovering from a failed boot drive...
- How can I backup my jails to restore them once the new pool is created ? The data is not a problem as it is just a matter of copying files from the backup to the new pool. But I have some jails that I spent time to set up and I would like to transfer them "as-is". I found this topic but am not sure that it's the right way to do it as it's kind of a hack.
I was thinking of simulating the whole process with a VM at some point anyway (better be safe than sorry), but I would really appreciate a better understanding of all this from you guys.
Thanks for the help