Most backups are relatively small because they only contain changes made (at a file or, even better, a block level) since the last backup. But while you’re backups are busy grabbing the latest and greatest, some files simply don’t change very often and are, therefore, overlooked. For example, take an organizational chart—it is important, but won’t change daily.
Now add to this the fact that your default retention of backups may only be, say, 30 days, with a few archives at monthly and quarterly intervals. So, those critical files that change infrequently may only have one iteration saved within the 30 -day retention period.
If you think about an RPO for a specific file that changes infrequently, it may be defined not so much in terms of a date or time, but in terms of a version. For example, if the version of the org chart you work with today is missing information, you need to recover to the last version of that file—which may be 35 days old.
So, how can you provide recovery of files that infrequently change with a more frequent retention time?