Supported backup data
Rewind Backups consist of the complete git repository, including all branches, plus GitHub-related metadata associated with the repository, such as issues, milestones, and more:
-
Git Repository
- refs
- branches
- commits
- tags
- objects
- logs
-
Commit comments
- comment text
- creation date
- creator
- status open/closed
- Releases *
- Labels
-
Milestones
- status open/closed
- description
- due date
- associated issues
-
Issues *
- description
- creation date
- creator
- status open/closed
- comments (without reactions)
- assignee
- assigned labels
- assigned milestones
-
Pull Requests *
- description
- creation date
- creator
- status open/closed
- review comments (without reactions)
- assignee
- assigned labels
- assigned milestones
- Wikis *
Limitations:
- *Pull Requests: Pull Requests are included in the backup, but can only be restored as issues due to limitations of the GitHub API.
- *Wikis: Wikis are included in the backup but cannot be automatically restored due to limitations of the GitHub API.
- File and image attachments: When you include an image or another attachment, such as ZIP files, the file is uploaded to GitHub’s CDN and then referenced by the URL in the issue or comment. The URL for the attachment is included in the backup, but the file itself is fetched from GitHub’s CDN.
FAQs
How do GitHub restores work?
Rewind restores GitHub data at the repository level.
When you initiate a restore:
- You choose a specific backup snapshot (date and time) from the Rewind dashboard.
- Rewind creates a new GitHub repository containing the restored data.
- Existing repositories are never overwritten during the restore process.
The restored repository includes the full Git history and the supported repository data captured at the time of the backup.
What naming convention does Rewind use for restored GitHub repositories?
To ensure each restore is uniquely named, Rewind appends a timestamp to the original repository name.
Naming format: <original-repo-name>-rewind-YYYY-MM-DD-HH-MM-SS-msec
The timestamp includes hours, minutes, seconds, and milliseconds to prevent naming collisions when multiple restores are performed in quick succession.
Can I change the frequency of the backups?
Rewind’s automatic backups are performed on a daily basis by default. When you need an additional backup, you can initiate it from your Rewind account using the “Backup Now” function.
How long do you keep the backup snapshots?
Rewind keeps the backup snapshots for 365 days, which are easily accessible through your Rewind account for export.
Do I need storage for the backup files?
No. Rewind Backups for GitHub includes unlimited cloud storage. You can access any backup version through the Rewind Vault by clicking versions and choosing a date from the calendar view.
Does Rewind back up Git LFS (Large File Storage) files?
Yes, Rewind can back up Git LFS files associated with your repositories.
Git LFS backups are not enabled by default. If your repositories use Git LFS and you want those files included in your backups, please contact Rewind Support to have Git LFS backups enabled on your account.
Once enabled, Git LFS files are backed up and restored as part of the repository-level restore process.