Wo ist mein (Borg-)Backup?

Moin,
ich habe NextCloud AIO (Nextcloud 26.0.2.1) über Docker v 4.17.1 auf Windows 10 laufen.
Gestern frisch aufgesetzt und eingerichtet. Funktioniert alles, bis auf das Borg-Backup.

Als Pfad für das Backup habe ich
/run/desktop/mnt/host/y/AIO_Backup
angegeben.

Y:\ ist eine NAS in meinem LAN.
Wenn das Backup durchgeführt wird, erhöht sich der Speicherbedarf auf Laufwerk C:.
Allerdings landet nichts im angegebenem Laufwerk Y:\AIO_Backup.
Ein Fehler wird nicht ausgegeben, der Order AIO_Backup\borg ist im Laufwerk Y:\ vorhanden bleibt aber leer.

Habe ich den Pfad für das Backup falsch angegeben?
Wie kann ich den Pfad im Nachhinein ändern?
Ich wüsste schon gerne, wo das Backup liegt…?!

Zur Info; ich bin Windows Benutzer und kein Computer-Experte. Ich habe es geschafft die NextCloud zum laufen zu bringen, aber in der Konsole/Terminal/Datenbank/Config-Dateien etwas zu ändern, könnte leicht frustrierend für mich werden.

Anbei Logs und Screenshots (leider nur 2).

initializing repository…
using builtin fallback logging configuration
33 self tests completed in 0.45 seconds
Initializing repository at “/mnt/borgbackup/borg”
Key in “<Repository /mnt/borgbackup/borg>” created.
Keep this key safe. Your data will be inaccessible without it.
check_free_space: few segments, not requiring a full free segment
check_free_space: calculated working space for compact as 0 bytes
check_free_space: required bytes 169138, free bytes 1026046414848
security: previous location file /root/.config/borg/security/xxxxxxxxxxxxxxxxxxx/location not found
security: manifest timestamp file /root/.config/borg/security/xxxxxxxxxxxxxxxxxxx/manifest-timestamp not found
security: determined newest manifest timestamp as
security: remembering previously unknown repository
security: saving state for xxxxxxxxxxxxxxxxxxx to /root/.config/borg/security/xxxxxxxxxxxxxxxxxxx
security: current location /mnt/borgbackup/borg
security: key type 5
security: manifest timestamp 2023-05-27T11:46:07.645884
security: repository checks ok, allowing access
Synchronizing chunks cache…
Archives: 0, w/ cached Idx: 0, w/ outdated Idx: 0, w/o cached Idx: 0.
Verified integrity of /mnt/borgbackup/borg/index.1
Done.
security: saving state for xxxxxxxxxxxxxxxxxxx to /root/.config/borg/security/xxxxxxxxxxxxxxxxxxx
security: current location /mnt/borgbackup/borg
security: key type 5
security: manifest timestamp 2023-05-27T11:46:07.645884

By default repositories initialized with this version will produce security
errors if written to with an older version (up to and including Borg 1.0.8).

If you want to use these older versions, you can disable the check by running:
borg upgrade --disable-tam /mnt/borgbackup/borg

See Important notes — Borg - Deduplicating Archiver 1.2.7 documentation for details about the security implications.

IMPORTANT: you will need both KEY AND PASSPHRASE to access this repo!
If you used a repokey mode, the key is stored in the repo, but you should back it up separately.
Use “borg key export” to export the key, optionally in printable format.
Write down the passphrase. Store both at safe place(s).

Repository successfully initialized.
Performing backup…
Starting the backup…
Creating archive at “/mnt/borgbackup/borg::20230527_114610-nextcloud-aio”

Repository: /mnt/borgbackup/borg
Archive name: 20230527_114610-nextcloud-aio
Archive fingerprint: xxxxxxxxxxxxxxxxxxx
Time (start): Sat, 2023-05-27 11:46:11
Time (end): Sat, 2023-05-27 12:01:05
Duration: 14 minutes 54.56 seconds
Number of files: 40867
Utilization of max. archive size: 0%

                   Original size      Compressed size    Deduplicated size

This archive: 31.00 GB 29.91 GB 28.60 GB
All archives: 31.00 GB 29.91 GB 28.60 GB

                   Unique chunks         Total chunks

Chunk index: 47228 51088

Pruning the archives…

                   Original size      Compressed size    Deduplicated size

Deleted data: 0 B 0 B 0 B
All archives: 31.00 GB 29.91 GB 28.60 GB

                   Unique chunks         Total chunks

Chunk index: 47228 51088

Compacting the archives…
Backup finished successfully on 27.05.2023 - 12:01:10 (00 hours 15 minutes 00 seconds)

Checking the backup integrity…
Starting repository check
finished segment check at segment 63
Starting repository index check
Index object count match.
Finished full repository check, no problems found.
Starting archive consistency check…
Starting cryptographic data integrity verification…
Finished cryptographic data integrity verification, verified 47229 chunks with 0 integrity errors.
Analyzing archive 20230527_114610-nextcloud-aio (1/1)
Archive consistency check complete, no problems found.
Check finished successfully on 27.05.2023 - 12:38:41 (00 hours 07 minutes 26 seconds)

Unbenannt7

Nach einem Neustart des ganzen Systems, schlägt die Überprüfung des Backups fehl:

The repository is empty. cannot perform check or restore.

in der Anleitung steht ausdrücklich, dass unter Windows auf diese Art bisher ausschließlich interne Laufwerke angesprochen werden können.

Möglicherweise ist das der Hintergrund für dein Problem.