Backups Overview
GitSec creates snapshots of your Git repositories. Each backup captures the data you choose and stores it in your configured storage, encrypted on GitSec Storage.
How Backups Work
When a backup runs, GitSec connects to your Git provider (GitHub, GitLab, or Bitbucket) using the access you granted when you connected it. For GitLab, this is either an OAuth connection (GitLab.com) or an access token (Self-Managed GitLab). GitSec then downloads the selected data scopes and stores the result as a backup snapshot. On GitSec Storage the snapshot is encrypted; in your own storage it is kept as regular files.
The contents of a snapshot never change once it is created. This ensures data integrity for compliance and recovery purposes. You can still give a backup a name, pin it, or delete it from Backup Snapshots. See Viewing Backups.
Backup Scopes
You can control what data is included in each backup. The scopes offered depend on the provider:
| Scope | GitHub | GitLab | Bitbucket | Description |
|---|---|---|---|---|
| Repository Metadata | ✓ | ✓ | ✓ | Repository settings and details. |
| Code & Commits | ✓ | ✓ | ✓ | All branches, tags, and full commit history. Always included. |
| Pull Requests (GitLab: Merge Requests) | ✓ | ✓ | ✓ | Pull requests or merge requests. On GitHub and Bitbucket, their comments are included. |
| Merge Request Comments | ✓ | Comments on merge requests, as a separate scope on GitLab. | ||
| Issues | ✓ | ✓ | Repository issues. | |
| Releases | ✓ | ✓ | Releases. On Bitbucket, tags come with the source code. | |
| Collaborators | ✓ | ✓ | Repository collaborators. |
Code & Commits is required and included in every backup, because a backup without source code cannot be restored. Wiki pages and project boards are not backed up.
Backup Triggers
There are three ways to trigger a backup:
| Trigger | Description |
|---|---|
| On Demand | Manually triggered from the repository detail page. |
| Scheduled | Automatically triggered by a scheduler at a configured interval. |
| Push Event | Automatically triggered on every git push when push event backups are enabled. |
Backup Storage
Backups are stored in either:
- GitSec Storage: Managed infrastructure with TR, US, and EU regions.
- BYOS (Bring Your Own Storage): Your own AWS S3, Azure Blob, Google Drive, Onedrive, or Huawei OBS bucket.
See Storage Overview for configuration details.