Is borg-ui the best tool for me?

[RudiOnTheAir]

Hello

I'm not sure if my use of Borg is appropriate here. I have an external Borg backup server (rsync.net) and several servers backed up with borgmatic. My idea was to use the borg-UI to more easily maintain an overview and to be able to save restores locally to any other machine via a web interface. This means the docker container with the Borg-UI runs on a server that has nothing to do with the backups. Now I don't understand if or how I can specify a local path for saving the restore, which is neither on the backup source nor on the borg-UI machine.??

[karanhudia]

Borg UI can help with part of that setup, but there are boundaries.

If the rsync.net repositories are normal Borg repositories, you can import them as observe-only/remote repositories and use Borg UI to browse archives and start restores. The restore destination still has to be somewhere Borg UI can write: a path visible to the Borg UI container, a configured Remote Machine/SSH target, or a Managed Agent machine.

It cannot restore directly to an arbitrary third machine that is not connected to Borg UI in one of those ways, and it will not manage existing borgmatic schedules unless you recreate that workflow in Borg UI or add an agent-backed workflow.

So: good for central visibility and guided restores from existing Borg repos; not a drop-in controller for independent borgmatic clients without adding a Borg UI-managed connection/agent.