Backup target migration

Server
1

Hello everyone,

I would like to migrate my current backup target to a larger storage.
UrBackup runs on a Docker container.
backups_2 is the old/current storage location
backups_1 is the new location
Both folders can be read and written to (tested in the console)

I have entered the file “migrate_storage_to” the new backup target. “/backups_1”
After the restart, the migration does not start.
It is not visible under the logs and also nothing in the Activities tab.
Have I forgotten something or done something wrong?

services:
urbackup:
image: uroni/urbackup-server:latest
container_name: urbackup
restart: unless-stopped
environment:
- PUID=1000
- PGID=100
- TZ=Europe/Berlin
volumes:
- /srv/dev-disk-by-uuid-303f4187-7321-4829-93bf-dcf00722e646/Docker/urbackup_config:/var/urbackup
- /srv/dev-disk-by-uuid-d7ce89a8-49c5-47fd-a8fa-ea688b95634b/UrBackup:/backups_1
- /srv/dev-disk-by-uuid-6BACCBE4571F1D62/Backup:/backups_2
network_mode: “host”

2

Checked permissons? urbackup:urbackup should have rw!

3

Did you solve this?
I am in the very same situation and it is very difficult to find any guidance to how to manage this in a Docker-environment.

I would expect that there can be a problem with the
Settings > Server > Backup storage path:
as it seems to hold only one single path, on my case “/backups”, which is also what i have in my Docker-file:

    volumes:
      - "/srv/dev-disk-by-uuid-0ece5f82-42fd-4cab-aae8-bdbe1f3a200b/Backups/urbackup_client_files:/backups"

The open question, not comment on by the forum, is whether there can be two different host volume entries (/srv/dev-disk…) mapping to the same Docker-client entry (/backups), or if the target needs to be separated.