# Backup "Files" to new node?

**URL:** <https://discuss.ipfs.tech/t/backup-files-to-new-node/7493>\
**Category:** Help\
**Created:** [March 17, 2020, 4:36am UTC](https://discuss.ipfs.tech/t/backup-files-to-new-node/7493 "2020-03-17T04:36:24Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![MidnightLightning](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/midnightlightning/32/2651_2.png) [@MidnightLightning](https://discuss.ipfs.tech/u/MidnightLightning)\
**Post date:** [March 17, 2020, 4:36am UTC](https://discuss.ipfs.tech/t/backup-files-to-new-node/7493/1 "2020-03-17T04:36:24Z")

</div>

I have an IPFS node that I’ve added files to over time using the web UI “Files” section (the “unixfs” virtual file system). I now need to rebuild the server it’s running on, and wish to back up all the files I’ve put there over time, to be able to re-add them to the rebuilt server after it’s complete. I can get the files one-by-one with `ipfs files read`, but that seems extremely tedious. Is there a way to mount the whole unixfs “files” tree as a virtual folder on the host machine? The `ipfs mount` command attempts to mount the entire IPFS global infrastructure as a directory mount point, which doesn’t work the best for this purpose.

---

<div class="post-metadata">

**Author:** ![hector](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/hector/32/178_2.png) [@hector](https://discuss.ipfs.tech/u/hector)\
**Post date:** [March 17, 2020, 9:36am UTC](https://discuss.ipfs.tech/t/backup-files-to-new-node/7493/2 "2020-03-17T09:36:25Z")

</div>

Does this help? [https://docs-beta.ipfs.io/how-to/move-ipfs-installation/#move-installation](https://docs-beta.ipfs.io/how-to/move-ipfs-installation/#move-installation)

---

<div class="post-metadata">

**Author:** ![MidnightLightning](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/midnightlightning/32/2651_2.png) [@MidnightLightning](https://discuss.ipfs.tech/u/MidnightLightning)\
**Post date:** [March 17, 2020, 11:59am UTC](https://discuss.ipfs.tech/t/backup-files-to-new-node/7493/3 "2020-03-17T11:59:10Z")

</div>

Thanks! That gets me started; that guide seems to be missing accomplishing that maneuver if running in Docker, but that at least gives me the files I should be targeting.

---

<div class="post-metadata">

**Author:** ![markg85](https://avatars.discourse-cdn.com/v4/letter/m/41988e/32.png) [@markg85](https://discuss.ipfs.tech/u/markg85)\
**Post date:** [March 18, 2020, 11:04pm UTC](https://discuss.ipfs.tech/t/backup-files-to-new-node/7493/4 "2020-03-18T23:04:43Z")

</div>

Note that the document talks about **moving**. If you **copy** instead of move you probably get the situation with 2 IPFS nodes with both the same peer id. The .ipfs folder contains not only the files you pinned but also the config you had.

What you want is probably some service that looks at all the files you have pinned and pin all those files on your new node too. I don’t think that exists other then going for ipfs-cluster (which would be overkill here). You might be best off by listing your pins `ipfs pin ls --type=recursive` and pinning all your files again on the new instance. You might be better off scripting that if you have a load of pins 😉

---

<div class="post-metadata">

**Author:** ![hector](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/hector/32/178_2.png) [@hector](https://discuss.ipfs.tech/u/hector)\
**Post date:** [March 19, 2020, 9:56am UTC](https://discuss.ipfs.tech/t/backup-files-to-new-node/7493/5 "2020-03-19T09:56:12Z")

</div>

> I’m surprised it doesn’t show you warnings.

You mean the second paragraph?

 ![image](https://us1.discourse-cdn.com/flex020/uploads/ipfs1/original/2X/e/e1188bb88197c1eabb727b378ac36cd8ced8ce67.png)

At the bottom there is a link to edit page or open an issue though, so the docs team would be super happy if you have suggestions for improvement.

---

<div class="post-metadata">

**Author:** ![markg85](https://avatars.discourse-cdn.com/v4/letter/m/41988e/32.png) [@markg85](https://discuss.ipfs.tech/u/markg85)\
**Post date:** [March 19, 2020, 10:05am UTC](https://discuss.ipfs.tech/t/backup-files-to-new-node/7493/6 "2020-03-19T10:05:55Z")

</div>

> [@hector](#):
>
> You mean the second paragraph?

I stand corrected 🙂  
I totally missed that one, sorry and thanks for pointing it out!

---

<div class="post-metadata">

**Author:** ![rennschnecke123](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/rennschnecke123/32/4381_2.png) [@rennschnecke123](https://discuss.ipfs.tech/u/rennschnecke123)\
**Post date:** [January 7, 2021, 4:57pm UTC](https://discuss.ipfs.tech/t/backup-files-to-new-node/7493/7 "2021-01-07T16:57:20Z")

</div>

Have a look here.  
with “backup2ipfs” it should be very easy to share/copy/move data from/to ipfs!

> **[rennschnecke123 - Overview](https://github.com/rennschnecke123)**
>
> rennschnecke123 has 5 repositories available. Follow their code on GitHub.
