I have experienced each of those points, so I understand them. That said, I have a few concerns. First, if retention is to be logically associated with the backups themselves, then configuration of said retention needs to be associated with the backups themselves too. For example, I should have been able to right-click the "orphaned" backup set and selected "Configure Retention" which would have provided a dialog box similar to the one available through the deleted job. Frankly, based on the logic you have presented, this should be available for all backup sets going forward, i.e. retention configuration available through the job (legacy) and directly against the backup set itself. (Feature request?) Second, I think Veeam's previous policy of preservation of the last point is still the best policy (and presents the least liability) for Veeam. The online manual is the best online manual for any product I have ever seen, but even I have not read ever page of it, nor kept up to date on it. Veeam should assume users will not know precisely how retention works and should "fail safe" in any kind of destruction process, whether this is an actively used chain, an "orphaned" chain, or some other kind of chain. There can always be an option in advanced settings somewhere that reverses this decision for those users who want it. That said, is this "fail safe" policy still in place for an active backup chain? If not, I really need to know since this was a trust factor between me and the product for many years. Third, I do appreciate the trend towards day based retention over point based retention. I always had to explain how point based retention worked to clients. I experienced other minor negative oddities that I can only vaguely recall now and that were resolved by switching the jobs to day based retention. This was usually the more sensible option, though we did have a few clients who wanted intra-daily backups.
Statistics: Posted by TitaniumCoder477 — Apr 12, 2025 3:46 pm
