Borg backup: Update for using diffrent ssh port #1782
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File need to be modified to use a different port for a remote borg backup. BORGBACKUP_PORT=<REMOTE PORT> need to be put in /etc/rear/local.conf
jsmeix
changed the title
|
@patlegu see also |
|
Superseded by #1785 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
File need to be modified to use a different port for a remote borg backup.
BORGBACKUP_PORT=<REMOTE PORT>need to be put in /etc/rear/local.confRelax-and-Recover (ReaR) Pull Request Template
Please fill in the following items before submitting a new pull request:
Pull Request Details:
Type: Bug Fix / New Feature / Enhancement / Other?
Enhancement
Impact: Low / Normal / High / Critical / Urgent
Low
Reference to related issue (URL):
How was this pull request tested?
On a new server with new installation and success of "
rear mkbackup"Brief description of the changes in this pull request:
I'm using a remote borg server with limited borg access (no deletion in repository), limited by the authorized_keys.
command="borg serve --append-only --restrict-to-path /backup/rear_test" ssh-ed25519 <CLIENT KEY>the borg server process is launch when the user connect on the server.