SayCyberOnceMore

To answer your question on where it’s used, have you seen https://providers.xmpp.net/ ?

(It might be worth testing your client against a few different servers…)

That’s where I found who to use, until I get to setting up prosody at home.

INHO never auto-upgrade anything.

Leave it a day / week or so, and then manually upgrade.

(And do a backup of application database(s) first.)

Ahh, ok. Thanks for clarifying.

Depends on which functions of NC you’re using.

Personally, I found thst no-one used the gallery, calendar or contacts apps in NC, so I replaced it all with radicale and syncthing.

But if you’re using all the collaboration stuff, then you’ll need to look into it a bit more.

For me, NC was way overkill, nightmare to maintain and an extra layer of software (ie vulnerabilities) exposed to the interwebs thst I didn’t need

I use Vivaldi’s built in calendar as the UI to Radicale.

Just a suggestion

I replaced NC with Radicale

One thing I forgot to mention: rsync has 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)

Ah… robocopy… that’s a great tool

Hardlinks need to be on the same filesystem, don’t they? I don’t see how that would work with a remote backup…?

It depends

rsync is 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, rsync is best.

But, if you’re just doing a 1-off bulk transfer in a single run, then you could use other tools like xcopy / scp or - if you’ve mounted the remote NAS at a local mount point - just plain old cp

The reason for that is that rsync has 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 scp well… 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.

Ah, but it’s how old you feel which is more important 😉

Maybe those statistics could be really interesting:

• How old do you feel when using proprietary software?
• How old do you feel when using FOSS?

I think that’s the point (.txt)