alez_G
Cadet
- Joined
- Feb 25, 2019
- Messages
- 1
@Lighthouse Appreciate you combining the steps. Also curious if this would migrate the jails and VMs.
If you can affords replicating to another machine on the network, things would be almost easier.Hello folks. I am in a process of upgrading my storage very soon, and I found this very helpful guide, and I do see some additional information provided by other people in this thread. I am a bit slightly confused in procedures combining depasseg, alexr and CPLeyden1282's posts. So here is the completed procedures from my understanding.
1.) Move off the system dataset.
2) Create system config backup.
3) Create a snapshot of the dataset I'd like to move.
4) Replicate the dataset from the old one to the new one using CPLeyden1282's instruction. Using GUI for 11.2 ver.
5) Detach both old and new volumes.
6) Import & rename pools using CLI, then export them.
7) Use the GUI to import the renamed pools so FreeNAS can understand them.
8) Using the backup from 2, bring back the old share.
9) Fix the GUID so that I can detach/wipe the old volume without problem, using alexr's instruction.
10) Wipe out the old volume if I like.
Are these procedures correct?
Also, if I do this, does Jail get moved as well? Since I will be moving enitre data from one to other, I assume Jail datasets are being copied as well, or is it not? Do I have to follow the steps for moving Jail (mentioned in OP) separately?
If you can affords replicating to another machine on the network, things would be almost easier.
Export should work if your pool isn't encrypted.
Nothing better than the old CLI commands.So I finished initial HDD tests, backup the data, created the pool, backup the config, created snapshot.
However, as usual the GUI of web interface is bugged, thus I could not use CPLeyden1282's method; my old pool/snapshot just does not show up to be chosen as source. I know GUI is useless for many cases because of bugs but I really think the bugs have to be ironed out. Like, at least dashboard should be reliably displaying status of the file server, for instance. This is one of the reasons I was really thinking about ditching FreeNAS after all.
I used the command zfs send -R <old pool>@<name of snapshot> | zfs receive -F <new pool>, with the addition of '-F'. I have to give the command to overwrite the existing <new pool>.
Now the data is being copied from my old pool to new pool. I will keep posting as I find new problems and/or new symptoms. I will update my initial procedure post.
Edit : initial procedure post is here : https://www.ixsystems.com/community...ool-to-a-bigger-pool.40519/page-3#post-517319
Nothing better than the old CLI commands.
And because it will take time for the replication to take place and in the event your current pool/volume is still in use, I would take a recursive snapshot of the original pool when it as competed, followed by a recursive incremental snapshot to the new pool and then stop all jails, disable services related to shares and take one last recursive snapshot. At that point performing recursive replication shouldn't take too long and modification of the original volume be almost inexistant. Perform a last recusive replication and both original and new pool should be identical.
At that point you can export new pool to to the original name and possibly shut down server, remove the original pool and restart. Hopefully, you will not need importing the new volume as it should be picked up as if the old one.
Thanks for Updating it. :)Hello folks. I am in a process of upgrading my storage very soon, and I found this very helpful guide, and I do see some additional information provided by other people in this thread. I am a bit slightly confused in procedures combining depasseg, Snow and CPLeyden1282's posts. So here is the completed procedures from my understanding.
Edit (3-13-2019): With this procedure I successfully migrated my pool into bigger pool.
<old pool> = current pool's name
<new pool> = any tempory name for added pool.
1.) Move off the system dataset.
2) Create system config backup. May not be needed but just in case.
3) Create a snapshot of the dataset I'd like to move, which will be <name of snapshot>.
4) Replicate the dataset from the old one to the new one using CPLeyden1282's instruction. Using GUI for 11.2 ver.
Or with high chance GUI is bugged and not working, then use the commend "zfs send -R <old pool>@<name of snapshot> | zfs receive -F <new pool>"
***If you use remote ssh connection, when you close it the replication will stop. Use the command "zfs send -Rv <old pool>@<name of snapshot> | pv | zfs receive -Fdu <new pool>" provided by Snow.***
5) Detach both old and new volumes. When detaching the volume, do not select "destroy" and select to save share-related configs.
6) Import & swap the names of pools using CLI, then export them.
"zpool import <old pool> <new pool>" and "zpool import <new pool> <old pool>"
Then
"zpool export <old pool>" and "zpool export <new pool>"
7) Use the GUI to import the renamed pools so FreeNAS can understand them.
8) If something happened to share and not working, use the system config backup did on 2).
9) Wipe out the old volume if I like.