How to migrate preexisting borg backups when switching to remote borg backup?

[michaelfliegner]

As of now I can only configure a new instance for backup to BorgBase.
Switching from preexisting local backups I would have to borg transfer my local backups to BorgBase. Thereafter I could remote restore from the new instance. But restoring the instance from a preexisting archive implies returning to local backups, right?

How to handle that?
Shouldn't the solution be extended to include

• import of preexisting archives and
• change of backup location?

Then restoring from a preexisting archive would entail only

• upgrading to AIO >= v10
• toggle back to remote backup.

[szaimen]

@timdiels do you have some ideas how to do the above?

[michaelfliegner]

so we're actually getting somewhere quite soon!

[archont00]

I have my own borg backup server. That's how I migrated from local repo path to remote repo path:

1. Stop all containers (from AIO interface).
2. Move borg.config (in nextcloud-aio-mastercontainer volume) to a temporary location.
3. Move all files from existing borg repo location to a new location managed by remote borg server. (I did it manually by moving the files and correcting ownership of all files - because my borg backup server runs on the same machine.)
4. Restore borg.config from temporary location back to nextcloud-aio-mastercontainer volume).
5. Re-create AIO master container (in my case: docker-compose down, change to "beta" channel to get v10.0.0 and docker-compose up -d)
6. In AIO interface, click on Reset backup location and enter the remote URL.
7. In AIO interface, click on Create backup - it fails due to authentication error. Copy the displayed SSH pub key to the borg backup server's authorized_keys.
8. In AIO interface, click on Create backup again. It should work now.

I did not test to restore the remote backup.

P.S. It would be good if the entry field in AIO interface for remote URL displays ssh://user@host:port/path_to_repo hint.

EDIT: Sorry, I have misunderstood the title of the issue How to migrate preexisting borg backups when switching to remote borg backup?. Yet it might help some to solve a similar use case as mine.

[michaelfliegner]

I did not test to restore the remote backup.

My question was just that: what happens after restoring from remote?

And it has been answered by @timdiels .

[timdiels]

Ah one other thing, we need a way to set the encryption password when resetting in this case. I think now it just generates a new password which doesn't match the existing repo's password.

[timdiels]

Although we already know the password, if it just keeps using the existing one after we reset, we should be fine