In this article:
Adding new plan
To create a new backup plan click on Add Plan button on the top bar in Plans tab.
After clicking on it new panel will be displayed in GitProtect web-console. First step is to define a name for the task in Backup plan name field and select Git as Backup type.
While creating a custom Git backup you can select one account from which repositories will be protected. Click on Repositories section and select the account.
At the bottom of organization list you can select to backup all available repositories by clicking on Protect all or select them manually by clicking Select repositories.
Choosing data to protect
This tab consists of two parts:
Select resources to backup - allows you to toggle between protecting only a repository or including metadata with it (issues, pull requests, actions / pipelines, wiki).
Worker - device listed in this part will be responsible for communication with Git services. More specifically it will be device that downloads the data from Git and then sends it to the storage.
Data storage is the location where backups are stored. GitProtect allows users to customize their backup policies with storage locations on per project basis.
Currently there are five types of storages that you can choose from:
- Local directory,
- Network location (SMB Share),
- Amazon Web Service storage,
- S3 compatible,
- Xopero Cloud.
To learn more about storage management see: Storage management
The last part of creating a backup plan is to set its frequency and retention. In Scheduler part of the form you can define the rotation scheme:
- Basic - is the simplest type of schedule.
- GFS (Grandfather-Father-Son) - policy dedicated for long-term archiving. It provides a possibility to store data over extended period of time while keeping a small amount of versions.
GFS is a multi-level scheme using multiple backup cycles for different time periods:
- Full copy ("Grandfather") made with greatest time interval (least often - monthly by default),
- Differential ("Father") performed more often than full copy (weekly),
- Incremental ("Son") most common with the smallest interval (daily).
Additional schedule settings
Backup window - time frame during which specific backup plan can operate. If the policy exceeds allowed timeslot, it will be automatically terminated.
Start delay - defines for how long GitProtect must wait before starting backup of the next repository / device in the list.
Don't suspend while performing a backup - prevents your device from going into suspended mode.
In Retention section allows you to define a data retention policy. You can set one of three rules to decide how long you want to keep your data on storage.
1) Keep infinitely - backup versions will never be removed.
2) By time - to set different time period for each kind of copy.
3) By number of copies - to set a number of versions that you want to keep.