Explanations
This is where we will put extra information, our considerations and architectural decisions. Why did we pick a particular sofware for a piece of this system?
Let us know if there’s anything you’d like us to add here.
This is where we will put extra information, our considerations and architectural decisions. Why did we pick a particular sofware for a piece of this system?
Let us know if there’s anything you’d like us to add here.
Operation error when trying to create a backup repository?If you see something like this:
Operation error
[unknown] failed to init repo: init failed: command “/root/.local/share/backrest/restic init –json –option rclone.program=ssh jane@backups.backupscale…” failed: command “/root/. local/share/backrest/restic init –json –option rclone.program=ssh jane@backups.backupscale…” failed: exit status 1
Output:
Fatal: create repository at rclone:europe:backupscalee/jane/repository1 failed: Fatal: unable to open repository at rclone:europe:backupscalee/jane/repository1: error talking HTTP to rclone: signal: killed
It probably means that your requested operation was invalid.
Repository paths must be something like
europe:backupscale/jane/REPOSITORY_NAME, where REPOSITORY_NAME consists
of lowercase letters, numbers or dashes (but not at the beginning or end),
and the maximum length is 63 characters.
To confirm, you can log into your dashboard account, and review your request logs. There will be request-specific information posted there.
In this example, backupscalee was spelled wrong, which is an invalid name
for the storage container.
signal: killed when trying to run a backup?If you see something like this:
Failed to schedule backup: [unknown] failed to get snapshots for plan: get snapshots for plan “my-backup-plan”: command “/root/.local/share/backrest/restic snapshots –json –option rclone.program=ssh jane@backups.backup…” failed: exit status 1 Output: Fatal: unable to open repository at rclone:europe:backupscale/jane/repository1: error talking HTTP to rclone: signal: killed
It probably means that your account has been disabled. To confirm, you can log into your dashboard account, and review your request logs. There will be request-specific information posted there.
If you account has indeed been disabled, check the billing for your subscription plan, and ensure it’s up-to-date.