Question about changing data DIR?

[killmasta93]

Hi
I was wondering what would be the correct steps on changing a currently directory?
I checked on the wiki
which this part says to pay close attention, but if i would need to change the directory, would i need to edit something in particular?
I know normally i would change the config.php on a nextcloud installation but not sure in this case what would be?
Attention: It is very important to change the datadir before Nextcloud is installed/started the first time and not to change it afterwards!

Thank you

[szaimen]

I guess the simplest way would be stopping all containers from the aio interface, creating a backup, use rsync to sync the files from the old datadir (in your case probably /var/lib/docker/volumes/nextcloud_aio_nextcloud_data/_data/ into e.g. /mnt/ncdata) and then removing and recreating the mastercontainer with -e NEXTCLOUD_DATADIR="/mnt/ncdata" and also starting the containers again from the aio interface.

Another solution would be stopping all containers from the aio interface, creating a backup, removing and recreating the mastercontainer with -e NEXTCLOUD_DATADIR="/mnt/ncdata" then restore the most recent backup and afterwards starting the containers again from the aio interface. In that case you should then delete the content of /var/lib/docker/volumes/nextcloud_aio_nextcloud_data/_data/ manually since the data would be duplicated otherwise.

Hope it helps!

[heshunme]

I think I've found another simple way. You just need to move the volume folder of nextcloud-aio-nextcloud-data to /example directly and then create a soft link using the "ln -s" command.

[killmasta93]

hi @heshunme very interesting, so lets say you want to move the container to another VM how would you do that? without using borg? so create first the containers or first create the softlinks?

[heshunme]

I apologize for realizing that my response was somewhat hasty after seeing your question. I find that this method may not be suitable for everyone.
My situation may be somewhat unique because I am deploying instances for home use on a Raspberry Pi. Therefore, I haven't considered migrating to other virtual machines. In fact, this is my first attempt at using Nextcloud-aio. Prior to this, I directly deployed Nextcloud on a physical machine. The reason for this re-deployment is that the TF card of the Raspberry Pi got damaged, resulting in the inability to boot the system, and the previously deployed Nextcloud instance was lost. However, the data was preserved on an external disk. In this re-deployment, since it is a home service with only a small number of accounts, I chose to forego migrating the database. Instead, I manually created new accounts and moved the files from the old instance to the data volume of the new instance. Then, I used 'occ files:scan --all' to rebuild the database.

[Javex]

This answer really helped me, too: Following the steps in the first paragraph worked like a charm, thank you!

[Softbox44]

@heshunme thanks! worked for me. Indeed a very elegant solution!

[mikebakke]

Hi - I tried this for moving the data dir and it comes up ok, but the Borg directory showing is still pointing to my original (custom) location. How can I amend the Borg archive location? I don't see any option to change it in the admin panel in the master container backup section.

[szaimen]

Hi, thw datadir is not the backup dir. Lets handle this in #1614

[mikebakke]

OK - I will hop over there for Borg. However - While testing I reverted to my original file data file location and created a new file, then switched to the new location and in the GUI I see the new file created which I assumed I should not. It is not in the disk directory though. While in the new directory, I created a new file and that one is in the correct disk location and not in the old.

When I switch the data dir between two mount-points, is the database always the same? I had assumed (dangerous) that the DB files were in the datadir hierarchy but thinking on it, they are in the nextcloud-database container which was only stopped?

I really think AIO is the way to go for the future, but it is very different to get used to ;-)

Bottom line - excluding the Borg question, what I did changing datadir in master contain is in fact safe so long as I after that I restrict all activities to the new location?

Thank you for the support - much appreciated.

[Henrijo]

Hi

I want to use minio as my primary object storage with nextcloud aio . How to proceed

[zupy666]

Hi,
I tried to perform the procedure mentioned above, but unfortunately it was unsuccessful. I wanted to move the entire persistent volume nextcloud_aio_* from /var/lib/docker/volumes/ to another folder, for example /opt/neixtcolu-aio/.

Is it even possible to define in docker-compose.yml that it should use a different path for everything?

Thank you for your support and feedback.

[szaimen]

Hi, see https://github.com/nextcloud/all-in-one?tab=readme-ov-file#how-to-store-the-filesinstallation-on-a-separate-drive

[patman-cp]

@szaimen But how do I store only the nextcloud AIO persistent volumes in a different location?

I don't want all my docker images in a different location, I already have that setup special but I do want the the persistent volumes stored elsewhere - in my case, so I can use a location with more storage, with RAID-1, and then I might use snapshots for backups rather then the AIO backup / restore method.

I see how to store the nextcloud_aio_nextcloud_data volume elsewhere, but how do I do that for the other AIO docker volumes?

[SingerJonathan]

@szaimen I see how to store the nextcloud_aio_nextcloud_data volume elsewhere, but how do I do that for the other AIO docker volumes?

I'm looking to do the same, specifically for the nextcloud_aio_database container. As far as I'm concerned, this container contains important user data and should be treated as such, not stored alongside replicable data like nextcloud itself and apache binaries.

I'd like all user data (including the database) to be on my RAID-1 filesystem, rather than in /var/lib/docker on my OS drive which has no redudancy. However, I'd much prefer not to move all docker containers, or even all nextcloud all-in-one containers. I only need to be able to move the ones containing important configuration and user data.

@szaimen Is this a possibility?

[patman-cp]

I'll probably sym link or bind mount them to point to my RAID-1 btrfs storage:

• backup or cross fingers
• Stop AIO
• rsync / cp files from /var/lib/docker/volumes/nextcloud_aio_* to /somewhere/else
• add symlinks or bind mount /var/lib/docker/volumes/nextcloud_aio_* to /somewhere/else
• restart AIO

[SingerJonathan]

That sounds like a good workaround, if it works. Hopefully we'll eventually get an environment variable like NEXTCLOUD_DATADIR for each individual container, or at least the database.