looking for advice on having 90 consecutive days of file level recovery. The user has almost 30 TB of free space on their onsite backup repository and doesn't want to store anymore than 30 days offsite for cost reasons.
We're currently using reverse incrementals with monthly health checks, weekly synthetic fulls, no active fulls scheduled. If I did 90 days on the backup job I'd have 1 vbk every week and 6 dailies for 90 days total.
Another option is some sort of backup copy job option to keep the backup chain short but it would duplicate the first 30 days to accomplish this.
Any concerns with such a long retention period? They did reiterate they don't want weekly's only after 30 days but 90 actual days to recover from. Another option is some sort of previous versions built into Windows OS. But we have 3 days of every 4 hours turned on for that right now. Not sure of implications of having 1 a day for 90 days in there instead of in Veeam.
rntguy wrote:
Any concerns with such a long retention period? They did reiterate they don't want weekly's only after 30 days but 90 actual days to recover from. Another option is some sort of previous versions built into Windows OS. But we have 3 days of every 4 hours turned on for that right now. Not sure of implications of having 1 a day for 90 days in there instead of in Veeam.
90 days with weekly fulls is not a long retention / backup chain at all - go with it.
VSS previous version is a nice feature and easy to use. But please don't name it a backup!
Shadow Copy wouldn't be reliable enough to ensure 90 days retention.
You could activate deduplication on your repository if you have Windows Server 2016 ( or 2012R2 if you're in the limits) or use ReFS (only 2016).
thanks all. i'm upping it to 90 days with weekly SF's. will monitor for space usage and consider enabling dedupe if needed. a bit concerned about corruption and sluggishness so going to wait and see if it's needed.
Got it, indeed, 90 days is not actually a long retention. I'd also consider less frequent fulls or switching to forever forward incremental mode, if space is a concern.
