Due to issues with Docker and my cache drive (see here) I had to switch from using Docker with a directory to using it with the default BTRFS vDisk. I had originally used a directory due to Nextcloud AIO using volumes and storing its database and such there.

 

Now, obviously, with a vDisk the location of volumes has changed. I've been trying to locate the new location for the past two days to copy my exisiting data to.

 

Has anyone had to go through this before and knows more than I was able to find out? Thanks a lot!

I don't really understand your question.

If you followed the guide for setting up aio your data are on a share outside of docker file.

probably /mnt/user/aio/data

The best way would probably be to restore your borg backup. 

I had to restore once. After setting up the mastercontainer you restore the backup. I don't think you can reinstall all dockers with your data and databses without using borg.

17 hours ago, caplam said:

If you followed the guide for setting up aio your data are on a share outside of docker file.

probably /mnt/user/aio/data

In terms of installing, all I did originally was install the AIO docker. I left everything on default. This created several volumes in `/mnt/user/system/docker/docker/volumes`. That was with using a directory instead of a vDisk (meaning there were other folders such as `/mnt/user/system/docker/docker/btrfs`. 

Now, I'm using a vDisk and have that in `/mnt/user/system/docker/docker.img`. What I don't have is a `volumes` folder next to it into which I could copy my existing files from the original install.

Edited April 29, 20242 yr by DesertCookie

I think your best bet is to recreate the data volume paying attention to permissions, reinstall mastercontainer and then restore the lastbackup.

Assuming of course you have the backup and the password associated.

When i installed aio i followed this : https://myunraid-ru.translate.goog/nextcloud-aio/?_x_tr_sl=auto&_x_tr_tl=en&_x_tr_hl=de&_x_tr_pto=wapp

 

 

15 hours ago, caplam said:

When i installed aio i followed this : https://myunraid-ru.translate.goog/nextcloud-aio/?_x_tr_sl=auto&_x_tr_tl=en&_x_tr_hl=de&_x_tr_pto=wapp

Thanks. However, as far as I can see, the guide does not mention how to change the volume locations. There actually is a comment by `dude` asking my very question. You may be confusing the `NEXTCLOUD_DATADIR` with the volumes of the database, redis, talk, etc. as that is the only data location that is actively changed in the linked guide and is what you refered to as `/mnt/user/aio/data` earlier.

Edited April 29, 20242 yr by DesertCookie

Do you have a backup and associated password ?

If so don't bother with volumes other than the one i mentionned. 

Setup mastercontainer, restore the backup and you are done. See here the backup part. 

The whole point of aio is to build a whole instance of nextcloud without dealing with interaction between containers.

Before aio i was using separated containers. I always failed to add fulltextsearch or redis and each update was a nightmare (50% of time nextcloud stayed in maintenance mode or there was an update error). Not to mention multiple errors as "/.well-known/caldav" i was never able to solve.

You certainly loose control over certains things but with aio you spend considerably less time making it work.

4 minutes ago, caplam said:

Do you have a backup and associated password ?

 

I do not have an AIO backup. As with every other Docker container, I simply automatically back up the volumes on a nightly basis. I was assuming AIO would be able to deal with that, as any other container does.

Imho in unraid, docker data you want to back up need to be bind mounted to a host directory.

Aio doesn't support modification of volumes except for data and backup directories.

If you use a docker.img file it's mounted to a loop device when docker engine is started.

In theory after installing aio you could try to start docker engine with all containers stopped and browse volumes inside.

By default aio create named volumes so they could more easily identified. You could install portainer for locating these volumes. But i seriously doubt it's possible to restore your data in that way.