Advice on Nexcloud structure

My case scenario is exactly the same: two people cutting ties from Google Photos/Drive and updating all phone photos straight to Nextcloud on a RPi4 4Gb armhf (soon to change to 8Gb aarch64) with OS on a SSD but all running docker containers are on a 500Gb USB external HDD (ext4).

Nextcloud is really fast (not before you tune it properly with several things that are on macomexcelent guide) (I'm also trying to make a small "RPi4 running Nextcloud on steroids" type of guide, WIP ).

So, to answer your questions (and this is my experience up until now)

1. Instead of "moving", make a verbatim copy of both "data" and "config" folders of Nextcloud from the SSD to the HDD.

In order to do this in a safe way, you have to bring down your stack (and maybe, stop docker so no access is being done to the files, especially on the DB, or you might end with corrupted DB, trust me, it happens )

2. I never ran it on SSD but, for me, speed is amazing (for a server on a SBC serving 2 users and on USB HDD.) (There are no miracles)

Again, only after doing some tuning with info on the web. (Hint: "pm ondemand vs dynamic", "app preview generator", and some other's )

Have a look on the guide mentioned above and read through for some tips and tricks. Then there's also The Q&A for the guide that answers a lot of things, if you care to read ALL of them (28 pages and counting, )

3. Shouldn't the question be: "Is it ok to turn ON the spin down"???

Why not??? If there is no access to the server (during the night, for eg.), it makes no sense to have the drives spinning needlessly.

Unless you want to power down the server most of the time.

Only issue is, when the drive(s) are spinned down, when access is "requested", there's some lag spinning them up but then, it's full throttle until they're not needed anymore.

4. Login to Nextcloud as "admin" (or the user you created with admin rights) and activate the "external storage app".

There's some posts here (will have to search for them) that explain how to access those shares via Nextcloud. No need for fancy configs on the OMV,

Zitat von metRo_

I don't expect config folder to grow very quickly, Am I wrong?

No it won't but backup backup backup (in this case all the configs of the containers that are part of the stack: nextcloud, mariadb, etc..)

Zitat von metRo_

I was thinking of "moving" only data. Is rsync ok make a verbatim copy?

You can move only the data and then alter the volume on the docker-compose.yml.

Like I said above--^^^^ bring down the stack before doing it to prevent locked files (especially if you have a lot of files already in "data")

[no root user but privileged sudo] I make my rsync backup with sudo rsync -aAXv /srv/dev-disk-by-label-DATA/appdata/ /home/pi/docker/backup_`date +"%Y%m%d"`/ to "clone" all that is bellow appdata (all containers configs and data)

Of course, this is not "moving" to use it on another drive, I'm backing it and also adding a date at the same time to the folder to know when it was done.

But this may give you an ideia of how to do it (in your case, something like: sudo rsync -aAXv /srv/dev-disk-by-label-OS/appdata/nextcloud/data /srv/dev-disk-by-label-DATA/Nextcloud/ <<---first path ends with data and the second path ends with Nextcloud/

Just remember, don't rsync before bring down the stack or, at least Nextcloud and MariaDB.