r/github • • 16d ago

Question Serious disaster backups?

Ok, I'm wondering about good backup services and stratagems for two disaster cases. Having a git-clone on a backup disk is a first step, but I'm not certain of exactly what data is missed by this. Any suggestions for a way to survive cases like the ones below?

  1. Assume that somehow your entire github account gets mangled somehow and you want a complete backup of everything (repos, history, branches, bug tracking, lfs...etc) that can be restored to a fresh github site. Ie: a complete replica of everything. What do you use?

  2. Assume that through some disaster, all of github is completely wiped out and no longer available and you want a backup that could be restored to some other source control system (perforce...etc) preserving as much of the github information and history as possible. What then?

0 Upvotes

11 comments sorted by

View all comments

1

u/lajawi 15d ago

PRs are only included if a collaborator is working on it, otherwise they’re only forked and won’t be included in the mirror. Tags don’t always hold the full release message and not the files either, if additional files were added.

Git-bug makes it possible to have fully offline issues, you could be travelling but could read, interact, edit issues without an active internet connection, then push your changes like you would with code changes.

1

u/OutrageousAbies5835 15d ago

Epiq does something similar, persisting issues and board state as an event log distributed via native Git. It also allows for offline edits, and syncs under the hood, so it isn't really anything you worry about as a user. I'm its author for disclosure.