Can't seem to change back up path to volume

Nextcloud version (eg, 20.0.5): Nextcloud AIO v7.6.2
Operating system and version (eg, Ubuntu 20.04): Debian 12
Apache or nginx version (eg, Apache 2.4.25): N/A
PHP version (eg, 7.4): N/A

The issue you are facing:

I added a volume for backups (and restarted the container) as I want them stored on my raid array and not my much smaller nvme drive. Clearly I am doing something wrong, any help is appreciated.

    volumes:
      - nextcloud_aio_mastercontainer:/mnt/docker-aio-config # This line is not allowed to be changed as otherwise the built-in backup solution will not work
      - /var/run/docker.sock:/var/run/docker.sock:ro 
      - /media/btrfs_raid/nextcloud_backups:/mnt/backup

The AIO interface shows:

Backups get created in the following directory on the host: /mnt/backup/borg

Is this the first time you’ve seen this error? (Y/N): Y

Steps to replicate it:

  1. Set the back up path via the AIO interface
  2. Run a back up and monitor logs
  3. Back up directory is empty
Performing backup...
Starting the backup...
Creating archive at "/mnt/borgbackup/borg::20231116_195414-nextcloud-aio"
------------------------------------------------------------------------------
Repository: /mnt/borgbackup/borg
Archive name: 20231116_195414-nextcloud-aio
Archive fingerprint: 4a195f0416a75f9615455f00b63592c25658657886ddfd1c678c184eab19d9dd
Time (start): Thu, 2023-11-16 19:54:15
Time (end):   Thu, 2023-11-16 19:54:21
Duration: 6.87 seconds
Number of files: 36009
Utilization of max. archive size: 0%
------------------------------------------------------------------------------
                       Original size      Compressed size    Deduplicated size
This archive:               15.13 GB             14.37 GB             14.65 MB
All archives:               30.23 GB             28.74 GB             14.09 GB

                       Unique chunks         Total chunks
Chunk index:                   37611                81732
------------------------------------------------------------------------------
BORG_PRUNE_OPTS are --keep-within=7d --keep-weekly=4 --keep-monthly=6
Pruning the archives...
------------------------------------------------------------------------------
                       Original size      Compressed size    Deduplicated size
Deleted data:                    0 B                  0 B                  0 B
All archives:               30.23 GB             28.74 GB             14.09 GB

                       Unique chunks         Total chunks
Chunk index:                   37611                81732
------------------------------------------------------------------------------
Compacting the archives...
Backup finished successfully on 16.11.2023 - 19:54:23 (00 hours 00 minutes 09 seconds).

It appears that /media/btrfs_raid/nextcloud_backups is the mount point on your host (not /mnt/backup). I assume /media/btrfs_raid/nextcloud_backups is already set-up, can be accessed from your host, and configured to be automatically mounted (i.e. after reboots)? If so, that’s the directory you want to configure in AIO as the backup directory.

Remove this. This tries to mount /media/btrfs_raid/nextcloud_backups within a Docker container and have it appear at /mnt/backup. That shouldn’t be necessary and won’t work for your purposes. AIO will take care of integrating the host volumes used for things like backups or data as long as they’re specified correctly in the AIO interface.

See the “How to do the above step for step” section of Backup solution.

1 Like