Multiple Backup Policies
You may not need to back up all your critical data with the same scheduler. Some data needs more attention and requires more often backups because of frequent changes and its value, and some information is updated only occasionally, and thus doesn’t need so often backups.
With GitProtect.io you are not limited to one backup plan. You can create as many backup plans as your infrastructure needs and business requires. Your backup plans can vary with the frequency, rotation scheme, level of encryption, data to protect, scheduler, or compression.
What's more,
- you can set a replication plan assigning more storage destinations and defining a schedule to meet your legal and/or compliance requirements.
- your backup policy can be adapted to the company's real-time requirements: multiple teams in different time zones, different core hours and, therefore, different times of backup execution, etc.,
- you can set up an archived data scheduler for seldom backup performance to save your storage and meet compliance requirements,
- use a hot backup setup (it means that a backup is performed every hour to secure your projects in progress),
- get an independent backup plan with immutable storage as a backup store configured (for an extra security measure) and another plan for arching data with normal storage - cloud or on-premise,
- each of your backup plans can also have different retention settings, encryption levels, etc.
- and there are a lot of other scenarios to guarantee your data protection.
Thus, in case of a disaster, you can easily restore your critical data eliminating downtime and securing your business continuity.