-
|
Hi everyone, I'm using Nextcloud AIO together with rsync.net for remote Borg backups. I recently got an email from rsync.net saying that, starting May 1st 2025, they will remove the default borg binary on their servers. From that date, users will be required to call a specific Borg version using --remote-path, for example: --remote-path=borg14They wrote
So far I haven’t seen any way to configure this in AIO. The My question: Let me know what you think – and if someone has already found a workaround, thank you. |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 9 replies
-
Hi, I fear there is no way to do so. I think the best way forward would be that you write a mail to the rsync.net service if it would be possible to use borg14 as default if --remote-path is not specified as this breaks the usage with Nextcloud AIO. |
Beta Was this translation helpful? Give feedback.
-
|
Well, I think this is a standard feature supported by borg and accessible in a similar way (through env exports) as backup location. So there is in no way need to let backup storage providers change theirs systems. I created a PR at #6687 that lets users configure the remote path and propagate / export it to the backupscript.sh in the borgbackup container. |
Beta Was this translation helpful? Give feedback.
-
|
Oh that's sad. I just signed up with rsync.net not realizing this would be a problem. |
Beta Was this translation helpful? Give feedback.
-
|
adding "BORG_REMOTE_PATH=borg14" as env in the containers.json file temporary fixes this until the masterconbtainer is recreated, would a PR adding this env to the mastercontainer (which redirects it to the borg container) be accepted? |
Beta Was this translation helpful? Give feedback.
-
|
I see it like @Zoey2936: A general mechanism to pass additional environment variables to AIO containers would be very helpful and flexible in general. Borg is very nice in this regard, so users with advanced configurations would be able to customize the process easily. It might also be a nice to have option for other containers. |
Beta Was this translation helpful? Give feedback.
-
@szaimen (sorry for the ping), but would one of these two ideas be something that has a chance of being merged? |
Beta Was this translation helpful? Give feedback.
-
|
I am not sure honestly. I would as always rather keep the complexity down and not add this. As the problem in this discussion seems to only be a problem with this one provider, I don't see the need for adding this - at least for now... The correct fix for this discussion is in my opinion still that rsync.net adds borg14 as default if not remote-path was set... |
Beta Was this translation helpful? Give feedback.
-
|
They wrote this E-Mail last night:
So I asked them how their workaround looks like and got this response:
So I think this can be closed: ssh [email protected] borg -V
borg9 1.2.8
ssh [email protected] borg1 -V
borg1 1.2.8
ssh [email protected] borg12 -V
borg12 1.2.8
ssh [email protected] borg14 -V
borg14 1.4.1
ssh [email protected] borg0 -V
borg0 0.29.0 |
Beta Was this translation helpful? Give feedback.
-
|
Ok, good to know, thanks! |
Beta Was this translation helpful? Give feedback.
-
|
If anyone is interested, I created a shell script that will keep injecting the workaround from @Zoey2936 into the mastercontainer. Can be run standalone or as a systemd unit to keep backups running after a mastercontainer upgrade: https://gist.github.com/ict/960ab27f6db18b6ad633c9817cd0e6fb |
Beta Was this translation helpful? Give feedback.
Hi, I fear there is no way to do so.
I think the best way forward would be that you write a mail to the rsync.net service if it would be possible to use borg14 as default if --remote-path is not specified as this breaks the usage with Nextcloud AIO.