A backup schedule is one of the most crucial elements of a backup plan. It defines the frequency of backup performance in a monthly, weekly, daily, or hourly manner so you can indicate what days and time range your backup plan should be executed due to your development pipeline and organization needs.
You can choose between two types of rotation schemes:
Basic is using two backup cycles for:
- Full copy - made every month by default,
- Incremental - commonly made daily.
To make your start with GitProtect.io easier, once you assign your GitHub, GitLab, or Bitbucket organization account, a default backup plan for all repositories and metadata will be automatically launched to make sure your data are immediately protected and recoverable.
- 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).
Among backup schedule settings you also have control over retention scheme (keep infinitely, by time or by a number of copies), and other settings like backup windows, delayed start, and not suspending while performing a backup.
This wide range of backup schedule settings and options gives you full control over the number and time of copies stored on your storage and the backup execution manner.