Skip to content

Doc update - borg restore for long restore processes - #8421

Draft
steveroot wants to merge 2 commits into
nextcloud:mainfrom
steveroot:main
Draft

steveroot wants to merge 2 commits into
nextcloud:mainfrom
steveroot:main

Conversation

@steveroot

Copy link
Copy Markdown

Long running restores can be interrupted by new backups starting.

Summary

  • [ n/a - it's a doc update] The PR was tested and verified that it works locally
  • Sign-off message is added to all commits
  • [ n/a ] Tests (playwright if possible) are included
  • [ n/a] Screenshots before/after for front-end changes
  • [Y ] Documentation has been updated or is not required
  • Labels added where applicable (ex: bug/enhancement, 3. to review, feature component)
  • [ n/a] Milestone next added

AI (if applicable)

  • [ No, all my own work] The content of this PR was partly or fully generated using AI

steveroot added 2 commits July 6, 2026 00:33
workaround is to turn off daily backup

Signed-off-by: Steve Root <steve@rkbb.co.uk>
Add note about long borg restore clashing with new backups
@steveroot

Copy link
Copy Markdown
Author

I'm new to this, I'm not sure how to add labels.
Probably got something else wrong too - I hope it's useful!

@pabzm pabzm added 3. to review Waiting for reviews documentation Improvements or additions to documentation labels Jul 18, 2026
@pabzm pabzm added this to the soon milestone Jul 18, 2026

@pabzm pabzm left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you very much for the contribution, it definitely is useful!

I've got two comments, please have a look at them.

Comment thread readme.md
---
### Restoring a borg backup ###
Beware that a long running restore process may be interuprted by the start of a new backup process.
See [https://github.com/nextcloud/all-in-one/blob/main/docker-ipv6-support.md](https://github.com/nextcloud/all-in-one/issues/8414))

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Showing one URL but linking to another smells a little bit strange. Is that on purpose? If so, why?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not on purpose, that would be me struggling to work out how to do this :-)
Thanks for spotting, leave it with me and I'll resubmit and learn from doing it.
Thanks for reviewing

Comment thread readme.md

---
### Restoring a borg backup ###
Beware that a long running restore process may be interuprted by the start of a new backup process.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's a typo here:

Suggested change
Beware that a long running restore process may be interuprted by the start of a new backup process.
Beware that a long running restore process may be interrupted by the start of a new backup process.

@pabzm pabzm modified the milestones: soon, next Jul 18, 2026

@szaimen szaimen left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of documenting the workaround we should rather try to fix the underlying problem imho.

@szaimen
szaimen marked this pull request as draft July 30, 2026 11:29
@szaimen szaimen added 2. developing Work in progress and removed 3. to review Waiting for reviews labels Jul 30, 2026
@szaimen szaimen removed this from the next milestone Jul 30, 2026
@steveroot

Copy link
Copy Markdown
Author

I'm on holiday next week so plan to fix the pull request and resubmit.
I agree on the fix rather than just document work around, but that's probably beyond my skill set right now :-)

@szaimen

szaimen commented Aug 3, 2026

Copy link
Copy Markdown
Collaborator

I'm on holiday next week so plan to fix the pull request and resubmit. I agree on the fix rather than just document work around, but that's probably beyond my skill set right now :-)

All good! There is an open PR for this now here: #8514

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

2. developing Work in progress documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants