borgbase/docs.borgbase.com

Documentation around BorgBase.com. Learn about backup strategy, setup and automation.

docs.borgbase.com's Issues

Icon instructions are out of date, development notes are hidden away

src/vorta/assets/icons/dark/ and src/vorta/assets/icons/light/ no longer exist as of borgbase/vorta#475, yet are still mentioned in documentation. Should be changed to something like

New icons are first added to src/vorta/assets/icons, and can be gotten with the get_colored_icon function

Currently, the Notes for Developers and Style Guide/Glossary are hidden in the Translation link, even though they contain information that a developer not working on translations needs to know, most importantly this:

In Qt (sub)classes, use self.tr(“English string”), scope will be the instance class name.
Elsewhere use vorta.i18n.translate(“scopename”, “English string”)
To only mark for string extraction, but not immediately translate, use vorta.i18n.trans_late function. Later, to translate, use vorta.i18n.translate (giving same scope).

Synology: Does the suggested setup store the borg cache in /root?

We had borgmatic set up on one of our Synologies, but I can't remember which method we set it up with. Long story short, Synology only provides VERY little space on /. Borg was running fine for months, but its cache was being written to /root/.borg (Or something like that) and so, a time came when / had no space available, so Synology stopped functioning correctly. We had to SSH in to figure out what was going on and to remove the cache. I haven't had a chance to reinvestigate yet, but if the setup instructions are indeed allowing Borg to write to /, they should be adjusted to cause Borg to write its cache to the shared folder location.

Can't get backup working using Synology instructions

I've been following the steps in your Synology guide here with a few minor alterations to the but haven't been able to get the backup working. I think this is because I have set the SSH key with a passphrase, which I then can't enter via the Synology task scheduler interface. This is the gist of the error message.

Task: BorgBase backup
Start time: XXX
Stop time: XXX
Current status: 1 (Interrupted)
Standard output/error:
ssh://[[email protected]/./repo](http://[email protected]/repo): Error running actions for repository
Connection closed by remote host. Is borg working on the server?
Command 'borg prune --keep-weekly 4 --keep-monthly 12 --keep-yearly 2 --prefix {hostname}- ssh://[[email protected]/./repo](http://[email protected]/repo)' returned non-zero exit status 2.
/root/borgmatic/config.yml: Retrying... attempt 1/5
/root/borgmatic/config.yml: Sleeping 5s before next retry
ssh://[[email protected]/./repo](http://[email protected]/repo): Error running actions for repository
Remote: [[email protected]](mailto:[email protected]): Permission denied (publickey,gssapi-keyex,gssapi-with-mic).

I'd rather not have a passphrase-free SSH key, so how do I provide the Synology interface with the means to get the key to work? Or should I just remove the passphrase and go with that key? Or am I looking at some other problem and not noticing it?

procedure to migrate borg 1.x repo to borg 2.x

I guess that the way is to:

• export the repo
• remove the repo on borgbase
• convert it locally with borg transfert
• import the 2.0 repo

https://docs.borgbase.com/setup/import/
https://www.borgbackup.org/releases/borg-2.0.html

Expand the "Restore" section with Borgmatic

Hello! I believe it would be beneficial to expand the Restore section with steps to restoring your backups with Borgmatic, as I find it to be a bit easier to use and friendlier than the plain borg syntax--and the other sections as well as the main website go into detail on configuring it.

Here is a short sample write-up:

Step 5 - Restoring with Borgmatic (optional)

If you use Borgmatic for your regular backups, it may be easier to use the Borgmatic syntax, provided you have a correctly configured configuration file.

Assuming that you have Borgmatic correctly configured and making backups, you would first need to find the backup you need to restore by listing the archives.

$ borgmatic -l

After choosing the backup, you would then add it to the borgmatic -x command

$ borgmatic -x server-2020-04-01T12:11:41

Make sure you are in the directory you would like to restore to, as it will extract the files into it.

If you would only like restore a particular directory from a backup, its as easy as adding --restore path to the command, along with the directory or file you would like to restore (minus the first /).

For example, if you would like to only restore /mnt/catpics from the same archive, the full command would be:

$ borgmatic -x server-2020-04-01T12:11:41 --restore-path 'mnt/catpics'

Synology: Initializing repo via one-off task doesn't work

... and will never work, because the BorgBase ssh key has to be added to root's known keys.

I suggest removing that info from https://docs.borgbase.com/setup/synology/ and telling the user that the repository has to be initialized from the command line on the disk station.

Troubleshooting section

Hi,

I am sorry if this is not the right place, but I cannot find an answer on docs.borgbase.com, and the doc does not have a common error that relates to my problem.

I am stuck with an error, and everything I find on the internet points to solutions to implement on the server side; the error message points to a server side error too.

I have no idea where to turn to try and solve it. I do have a few simple ssh keys setup like github for example that works well.

I created an ssh key pair, copied the public key on my borgbase account, so far everythnig seems to be ok.

$ borg init -e repokey-blake2 ssh://[email protected]/./repo

Remote: [email protected]: Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
Connection closed by remote host. Is borg working on the server?

I tried to change the borg version on my account to make sure it matches the one installed on my laptop.
My ssh config is as follows but I tried many changes there for consistently the same error message:

Host *
  AddKeysToAgent yes
  IgnoreUnknown UseKeychain
  UseKeychain yes

Host borgbase
  HostName xxx.repo.borgbase.com
  User xxx
  IdentityFile ~/.ssh/borgbase
  IdentitiesOnly yes

Any help would be greatly appreciated, thanks in advance.