# Hardware Migration Guide?

**URL:** <https://forum.storj.io/t/hardware-migration-guide/31239>\
**Category:** Node Operators\
**Tags:** truenas, move-node\
**Created:** [December 14, 2025, 7:54pm UTC](https://forum.storj.io/t/hardware-migration-guide/31239 "2025-12-14T19:54:17Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![trek-e](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/trek-e/32/1133_2.png) [@trek-e](https://forum.storj.io/u/trek-e)\
**Post date:** [December 14, 2025, 7:54pm UTC](https://forum.storj.io/t/hardware-migration-guide/31239/1 "2025-12-14T19:54:17Z")

</div>

I have an older TrueNAS Scale that is running the docker application that was released when the partner was announced a few years ago.

I need to migrate it to a newer bit of hardware and wanted to sanity check my thought process.

I’m snapshotting my identity and config folders which according to the configuration hold the identity and Storj data.

Then, stop the app (docker container) on the old node, rsync one more time to validate, and then start the app on the new node with the same settings pointed at the new replicated set on the new hardware, change the firewall to point the ports to the new one, start it up and good?

My question is, if I miss anything, I still have my original server sitting there and can always restart it, but how do I validate I have everything copied?

Or is that what repair is for and there might be some repair done by other nodes should something not gracefully copy?

I saw this topic: [Migrating from Windows Node to TrueNAS node, how to? - #8 by Alexey](https://forum.storj.io/t/migrating-from-windows-node-to-truenas-node-how-to/30264/8) but it’s windows to trueness so not quite apples to apples.

Thanks for any input.

---

<div class="post-metadata">

**Author:** ![snorkel](https://storj.bcdn.literatehosting.com/letter_avatar/snorkel/32/5_5575768a8748004e209b776fc1b2916d.png) [@snorkel](https://forum.storj.io/u/snorkel)\
**Post date:** [December 14, 2025, 9:05pm UTC](https://forum.storj.io/t/hardware-migration-guide/31239/2 "2025-12-14T21:05:27Z")

</div>

No repair is done to your node. If you loose data, you can get disqualified.

---

<div class="post-metadata">

**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\
**Post date:** [December 15, 2025, 1:46am UTC](https://forum.storj.io/t/hardware-migration-guide/31239/3 "2025-12-15T01:46:29Z")

</div>

> [@trek-e](#):
>
> rsync one more time to validate, and then start the app on the new node with the same settings pointed at the new replicated set on the new hardware

Correct, please note, the last rsync should be with the `--delete` option, otherwise your databases could be corrupted.

`rsync` should be enough to make sure that all data is copied.

You shouldn’t run the old node after the clone was online, it could end with a disqualification due to missing data.

@snorkel is correct, the repair traffic will go to other nodes, not the node, which lost data. And the node could be disqualified if it lost more than 4% of the data which it supposedly should have.