I often use the integrated VSS feature on Windows files servers, to allow users to restore themselve some files. This also allow IT team to do the job fast when few files are involved, which is the most frequent problem.
For example I take one VSS per working hour (10 per day), and retain them during 4 weeks (5 working days per week) --> total = 200 VSS for 4 weeks
I'd like to use some "flexible" retention policy:
For example keeping each hourly VSS during 3 working days, then 4 VSS per day for the next 7 working days, then 2 VSS per day during the next 10 working days --> total = 78 VSS for 4 weeks
The space occupied by the VSS in both cases should be similar.
My point is not to save space. It is to extend the number of weeks during VSS are kept. But as NTFS can have a maximum of 512 VSS, then hourly VSS is not sustainable more than 10 weeks. And this is a huge number.
Question: do you think I should write a PowerShell script to manage the VSS retention policy? Or can I use something already done (script or software)?
You can just adapt this simple script to your needs:
You should have actual offline backups to other media for long-term data recovery needs. Shadow copies are fantastic for short-term, user-facing restores, but will not (and should not) be your entire data protection tool.