Remote backup integrity issues #403
Labels
No Label
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: borgmatic-collective/borgmatic#403
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I'm tryingt to remotely backup a database using borgmatic. My remote server is running borg, using rclone/s3 as a backend. With just borg, I can back up this client with no issues, but I have a need for database backup, hence borgmatic.
I'm receiving errors when doing integrity checks as such:
Advice is welcome
I unfortunately don't have a ton of insight here; my guess is there's a problem with the repository and/or the filesystem it's stored on that's causing segment file integrity issues. (I'm going by similar Borg tickets like this one.) When you say that you're using rclone/s3 as a backend, does that mean you're using a traditional filesystem on the server (ext4, etc.) and then running rclone to sync that to s3? Or are you doing something more exotic?
Closing due to inactivity. But feel free to reopen if you'd like to discuss further!