Backup Retention
Retention setup and how to meet your compliance?
There are organizations that need to keep their data for years. It may have different prerequisites: the type of the data organization keeps in its repositories, the period of time your company needs to keep those data, from what time those data should be restored or, even to meet international security standards, like SOC 2 Type II and ISO 27001.
By default, most service providers offer retention from 30 to 365 days, and it is definitely not enough if you have strict security requirements and need to keep your hot DevOps data or old unused repositories archived to meet your compliance.
Thus, keeping in mind that organizations may have different needs and requirements depending on their industry, GitProtect.io provides 3 retention rules. So, you can set retention:
- by time, so to say, how long your copy should be kept in storage. Depending on the backup schedule you have, you can set retention rules separately for the full, differential, and incremental backups.
- by number of copies, which means that you set the exact number of versions you keep in your storage.
- or choose unlimited retention: disable the rules and keep your copies infinitely, which is critical if you follow strict security policies or plan to keep your copies for archiving purposes.