I understand the security concern around immutability.
But today immutability also applies to GFS restore points, which in our case are kept for up to 10 years. This makes rebalancing almost impossible.
Maybe there could be an option where immutability only applies to the last X days (e.g. 14). Then during rebalancing Veeam would just duplicate those recent restore points, and clean them up automatically once the immutability window expires after e.g. 14 days.
This way immutability is still fully enforced where it matters, but long-term GFS data would not block practical repository management.?
But today immutability also applies to GFS restore points, which in our case are kept for up to 10 years. This makes rebalancing almost impossible.
Maybe there could be an option where immutability only applies to the last X days (e.g. 14). Then during rebalancing Veeam would just duplicate those recent restore points, and clean them up automatically once the immutability window expires after e.g. 14 days.
This way immutability is still fully enforced where it matters, but long-term GFS data would not block practical repository management.?
Statistics: Posted by mv@cloudio.dk — Aug 20, 2025 5:59 pm
