Backup via restic limited to local/AWS

[AdminMichal]

v 3.1.1

Restic supports multiple repository targets ie. SFTP .
You don't.

Now it is somehow possible by entering repository path into backup_restic_repository
and setting backup_restic_aws to true.

And it will create repository on remote side and will works correctly

level=info msg="Command completed successfully: /srv/restic_log [init]" cluster=esrv module=restic type=log

But after restart from whatever reason it tries to init it again:

level=info msg="Starting command: /srv/restic_log [init]" cluster=esrv module=restic type=log
Fatal: create repository at sftp:ckup-ha-repman@10.10.90.1:/srv/backup/ha-repman/data/esrv failed: Fatal: unable to open repository at sftp:ckup-ha-repman@10.10.90.1:/srv/backup/ha-repman/data/esrv: config file already exists

Is it possible to use sftp with restic in replication-manager or AWS/minio is the only remote repository supported?

[sonkiee]

Hi! I'd like to work on extending backup support in replication-manager to properly handle additional restic repository targets like SFTP. I'm familiar with restic internals and can implement logic to prevent reinitialization errors by checking for existing repositories before running init.

I'll ensure clean support for SFTP and other restic-supported backends beyond local and AWS, and add proper handling for restarts. I can also contribute to improving config validation and related documentation if needed.

Let me know if you have any edge cases or preferred approach in mind

[svaroqui]

I Sonkiee thanks for choosing us, we have dev docker image with all the tools you need to build and use replication-manager.
I guess that it can help just give me a public key and i will give.back infos to you on how to use . It better you register an account at gitlab.signal18.io and come in our chat meet.signal18.io by signing using gitlab