borg2: the description of the s3: schema is incorrect

[tve]

The s3 schema is described as:

    (s3|b2):[profile|(access_key_id:access_key_secret)@][schema://hostname[:port]]/bucket/path

but looking at the regexp in the code the @ is required after a profile, thus it should be:

    (s3|b2):[(profile|(access_key_id:access_key_secret))@][schema://hostname[:port]]/bucket/path

It's also not clear what 'schema' is. Is it https/http/htt2/... or something else?

[infectormp]

'schema' means s3/file/rclone/sftp and etc.

[ThomasWaldmann]

I didn't write the s3/b2 code and also I don't use it, but I would suspect that schema is usually https there.

[yodatak]

Same for me i cannot find simple exemple that work with s3 with garage https://garagehq.deuxfleurs.fr/ i try multiples command and it failed with invalid repo or create a local folder on my computer

a post i find that document rclone with hetzner but cannot find blog that explain s3
https://pelle.io/posts/borg2-hetzner/

./borg.exe repo-create --repo s3://borg-test/mytestrepo --encryption=repokey-aes-ocb
./borg.exe repo-create --repo s3:s3://borg-test/mytestrepo --encryption=repokey-aes-ocb
./borg.exe repo-create --repo s3:s3://192.168.1.168:3900/borg-test/mytestrepo --encryption=repokey-aes-ocb
./borg.exe repo-create --repo s3://192.168.1.168:3900/borg-test/mytestrepo --encryption=repokey-aes-ocb
/borg.exe repo-create --repo s3:KEYID:SECRETID@s3://192.168.1.168:3900/borg-test/mytestrepo --encryption=repokey-aes-ocb

borg.exe repo-create: error: argument -r/--repo: Invalid location format: "s3://borg-test/mytestrepo"

thanks to make borg object storage with solution like garage its awsome but i lack documentation

[yodatak]

exemple i found in code echo "BORG_TEST_S3_REPO=s3:minioadmin:minioadmin@http://127.0.0.1:9000/borg/s3-repo" >> $GITHUB_ENV

borg/.github/workflows/ci.yml

Line 260 in a8f1ed9

echo "BORG_TEST_S3_REPO=s3:minioadmin:minioadmin@http://127.0.0.1:9000/borg/s3-repo" >> $GITHUB_ENV

and more here

borg/src/borg/testsuite/helpers/parseformat_test.py

Line 153 in a8f1ed9

def test_s3(self, monkeypatch, keys_dir):

even when using info from this i got the error borgstore.backends.errors.BackendURLInvalid: Invalid or unsupported Backend Storage URL:

Details

yodatak /t/d/b/borg-dir> ./borg.exe repo-create --encryption=repokey-aes-ocb --debug
using builtin fallback logging configuration
17 self-tests completed in 0.06 seconds
Error: Invalid or unsupported Backend Storage URL: s3:minioadmin:minioadmin@http://127.0.0.1:9000/borg/s3-repo

Error:

Error: Error: Invalid or unsupported Backend Storage URL: s3:minioadmin:minioadmin@http://127.0.0.1:9000/borg/s3-repo

If reporting bugs, please include the following:

Traceback (most recent call last):
  File "borg/repository.py", line 161, in __init__
  File "borgstore/store.py", line 63, in __init__
borgstore.backends.errors.BackendURLInvalid: Invalid or unsupported Backend Storage URL: s3:minioadmin:minioadmin@http://127.0.0.1:9000/borg/s3-repo

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "borg/archiver/__init__.py", line 669, in main
  File "borg/archiver/__init__.py", line 546, in run
  File "borg/archiver/_common.py", line 110, in wrapper
  File "borg/archiver/_common.py", line 43, in get_repository
  File "borg/repository.py", line 163, in __init__
borg.helpers.errors.Error: Error: Invalid or unsupported Backend Storage URL: s3:minioadmin:minioadmin@http://127.0.0.1:9000/borg/s3-repo

Platform: Linux pcfixamd.home 6.17.7-ba22.fc43.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Dec 31 05:41:30 UTC 2025 x86_64
Linux: Unknown Linux  
Borg: 2.0.0b20  Python: CPython 3.11.14 msgpack: 1.1.2 fuse: llfuse 1.5.2 [mfusepy,pyfuse3,llfuse]
PID: 2596352  CWD: /tmp/d/borg-linux-glibc235-x86_64-gh/borg-dir
sys.argv: ['./borg.exe', 'repo-create', '--encryption=repokey-aes-ocb', '--debug']
SSH_ORIGINAL_COMMAND: None

[ThomasWaldmann]

is everybody here using 2.0.0b20?

[Julien-Blanc-tgcm]

2.0.0b19 here, with the same issue (borg2 keeps trying to create a file instead of using the s3 storage). This is the version coming from debian repo (trixie), not from pip. python3-boto3 is installed as well, but did not came as a dependency of borgbackup2, so this may be debian specific in my case.

[ThomasWaldmann]

See #9274.

I am wondering if you all really have the issue described in the top post. If not, please re-read the docs and open a separate issue if you can't get it working with a correct s3 URL.

[ThomasWaldmann]

There was one related change in borgstore, which will be in next release of borgstore:

borgbackup/borgstore@c7c1879