Can't specify just the hostname for the backup server #156

New Issue

Closed

opened 2019-03-25 14:42:05 +00:00 by dtu-compute · 5 comments

dtu-compute commented 2019-03-25 14:42:05 +00:00

Copy Link

The shortest possible remote path seams to be

repositories:
    - 'borg@backup.example.com:borgmatic'

where I would really like to not have the last borgmatic part, as I on the Borg backup server have

command="cd /tank/borg/repos/client.example.com; borg serve --restrict-to-path /tank/borg/repos/client.example.com",restrict ssh-rsa ...

in each public key. I.e

I would much prefer to use have

repositories:
    - 'borg@backup.example.com:'

so I on the Borg backup server have

/tank/borg/repos/client.example.com/

instead of

/tank/borg/repos/client.example.com/borgmatic/

The shortest possible remote path seams to be ``` repositories: - 'borg@backup.example.com:borgmatic' ``` where I would really like to not have the last `borgmatic` part, as I on the Borg backup server have ``` command="cd /tank/borg/repos/client.example.com; borg serve --restrict-to-path /tank/borg/repos/client.example.com",restrict ssh-rsa ... ``` in each public key. I.e I would much prefer to use have ``` repositories: - 'borg@backup.example.com:' ``` so I on the Borg backup server have ``` /tank/borg/repos/client.example.com/ ``` instead of ``` /tank/borg/repos/client.example.com/borgmatic/ ```

witten commented 2019-03-25 17:08:44 +00:00

Owner

Copy Link

Is there a particular error you're getting when you try to specify 'borg@backup.example.com:'? As far as I know, the repository string is passed directly to Borg. Thanks!

Is there a particular error you're getting when you try to specify `'borg@backup.example.com:'`? As far as I know, the repository string is passed directly to Borg. Thanks!

dtu-compute commented 2019-03-26 08:51:53 +00:00

Author

Copy Link

I get

Command '('borg', 'list', 'borg@backup.example.com:')' returned non-zero exit status 2.

and if I use

repositories:
    - 'borg@backup.example.com:borgmatic'

then a directory is created in current directory called borg@backup.example.com:borgmatic.

I get ``` Command '('borg', 'list', 'borg@backup.example.com:')' returned non-zero exit status 2. ``` and if I use ``` repositories: - 'borg@backup.example.com:borgmatic' ``` then a directory is created in current directory called `borg@backup.example.com:borgmatic`.

witten commented 2019-03-26 16:09:53 +00:00

Owner

Copy Link

Based on the borg list error you provided, this may just be a Borg limitation. Have you tried running the borg list borg@backup.example.com: command directly in your shell to see what Borg's output is like when borgmatic is not involved?

Based on the `borg list` error you provided, this may just be a Borg limitation. Have you tried running the `borg list borg@backup.example.com:` command directly in your shell to see what Borg's output is like when borgmatic is not involved?

dtu-compute commented 2019-03-27 09:32:00 +00:00

Author

Copy Link

Ok, it is a Borg limitation. Closing.

Ok, it is a Borg limitation. Closing.

dtu-compute closed this issue 2019-03-27 09:32:00 +00:00

witten commented 2019-03-27 16:30:08 +00:00

Owner

Copy Link

If you file a Borg ticket on this, please link to it here. Thanks!

If you file a Borg ticket on this, please link to it here. Thanks!

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

spot-check

1.8.10

1.8.9

1.8.8

1.8.7

1.8.6

1.8.5

1.8.4

1.8.3

1.8.2

1.8.1

1.8.0

1.7.15

1.7.14

1.7.13

1.7.12

1.7.11

1.7.10

1.7.9

1.7.8

1.7.7

1.7.6

1.7.5

1.7.4

1.7.3

1.7.2

1.7.1

1.7.0

1.6.6

1.6.5

1.6.4

1.6.3

1.6.2

1.6.1

1.6.0

1.5.24

1.5.23

1.5.22

1.5.21

1.5.20

1.5.19

1.5.18

1.5.17

1.5.16

1.5.15

1.5.14

1.5.13

1.5.12

1.5.11

1.5.10

1.5.9

1.5.8

1.5.7

1.5.7.dev0

1.5.6

1.5.5

1.5.4

1.5.3

1.5.2

1.5.1

1.5.0

1.4.22

1.4.21

1.4.20

1.4.19

1.4.18

1.4.17

1.4.16

1.4.15

1.4.14

1.4.13

1.4.12

1.4.11

1.4.10

1.4.9

1.4.8

1.4.7

1.4.6

1.4.5

1.4.4

1.4.3

1.4.2

1.4.1

1.4.0

1.3.26

1.3.25

1.3.24

1.3.23

1.3.22

1.3.21

1.3.20

1.3.19

1.3.18

1.3.17

1.3.16

1.3.15

1.3.14

1.3.13

1.3.12

1.3.11

1.3.10

1.3.9

1.3.8

1.3.7

1.3.6

1.3.5

1.3.4

1.3.3

1.3.2

1.3.1

1.3.0

1.2.18

1.2.17

1.2.16

1.2.15

1.2.14

1.2.13

1.2.12

1.2.11

1.2.10

1.2.9

1.2.8

1.2.7

1.2.6

1.2.5

1.2.4

1.2.3

1.2.2

1.2.1

1.2.0

1.1.15

1.1.14

1.1.13

1.1.12

1.1.11

1.1.10

1.1.9

1.1.7

1.1.6

1.1.5

1.1.4

1.1.3

1.1.2

1.1.1

1.1.0

1.0.3

1.0.2

1.0.1

1.0.0

0.1.8

0.1.7

0.1.6

0.1.5

0.1.4

0.1.3

0.1.2

0.1.1

0.1.0

0.0.7

0.0.6

0.0.5

0.0.4

0.0.3

0.0.2

Labels

Clear labels   

bug

  

data loss

  

design finalized

  

good first issue

  

new feature area

  

question / support

  

security

  

waiting for response

No Label

bug

data loss

design finalized

good first issue

new feature area

question / support

security

waiting for response

Milestone

Clear milestone

No items

No Milestone

Assignees

Clear assignees

No Assignees

2 Participants

Notifications

Subscribe

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: borgmatic-collective/borgmatic#156

No description provided.