Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
I was planning to use rsync to ship several TB of stuff from my old NAS to my new one soon. Since we're already talking about rsync, I guess I may as well ask if this is right way to go?
It depends
rsyncis fine, but to clarify a little further...If you think you'll stop the transfer and want it to resume (and some data might have changed), then yep,
rsyncis best.But, if you're just doing a 1-off bulk transfer in a single run, then you could use other tools like
xcopy/scpor - if you've mounted the remote NAS at a local mount point - just plain oldcpThe reason for that is that
rsynchas to work out what's at the other end for each file, so it's doing some back & forwards communications each time which as someone else pointed out can load the CPU and reduce throughput.(From memory, I think Raspberry Pi don't handle large transfers over
scpwell... I seem to recall a buffer gets saturated and the throughput drops off after a minute or so)Also, on a local network, there's probably no point in using encryption or compression options - esp. for photos / videos / music... you're just loading the CPU again to work out that it can't compress any further.
It's just a one-off transfer, I'm not planning to stop the transfer, and it's my media library, so nothing should change, but I figured something resumable is a good idea for a transfer that's going to take 12+ hours, in case there's an unplanned stop.
One thing I forgot to mention:
rsynchas an option to preserve file timestamps, so if that's important for your files, then thst might also be useful... without checking, the other commands probably have that feature, but I don't recall at the moment.rsync -Prvt <source> <destination>might be something to try, leave for a minute, stop and retry ... that'll prove it's all working.Oh... and make sure you get the source and destination paths correct with a trailing
/(or not), otherwise you'll get all your files copied to an extra subfolder (or not)