Today, 04:01 AM
(Yesterday, 01:24 AM)Parallax Abstraction Wrote: So I've run into another odd problem. Per the suggestions here, I set my backup policy to Daily Incremental with the image retention policy simply being Full 15 days. I was told this would take the Full, do 14 days of Incrementals then delete the chain on the next run and create a fresh chain. It does seem to be doing that but I noticed that the image check I have set to run after every backup is failing. After the latest Full was created, I ran an image check and immediately got this:
Warning: The backup version 1 has been deleted, lost or corrupted.
Warning: The backup version 2 has been deleted, lost or corrupted.
Warning: The backup version 3 has been deleted, lost or corrupted.
Warning: The backup version 4 has been deleted, lost or corrupted.
Warning: The backup version 5 has been deleted, lost or corrupted.
Warning: The backup version 6 has been deleted, lost or corrupted.
Warning: The backup version 7 has been deleted, lost or corrupted.
Warning: The backup version 8 has been deleted, lost or corrupted.
Warning: The backup version 9 has been deleted, lost or corrupted.
Warning: The backup version 10 has been deleted, lost or corrupted.
Warning: The backup version 11 has been deleted, lost or corrupted.
Warning: The backup version 12 has been deleted, lost or corrupted.
Warning: The backup version 13 has been deleted, lost or corrupted.
Warning: The backup version 14 has been deleted, lost or corrupted.
Warning: The backup version 15 has been deleted, lost or corrupted.
Warning: The backup version 16 has been deleted, lost or corrupted.
It seems to be acting like it's expecting to see a full chain there, even though the retention policy is supposed to be resetting it. Is there something I maybe need to adjust in the settings?
Thanks.
This is normal and nothing to worry about. Your settings do not need any adjustment.
This warning is a direct result of the image retention policy using image deletion rather than image merging to improve efficiency. When the policy deletes old backups, the image check still expects those versions in the chain to exist, so it reports them as “deleted, missing, or corrupted.” However, this is only a warning; it does not indicate an actual problem with your remaining backup chain.
The integrity of the backup chain that still exists is unaffected, and restore operations are also unaffected. Backups in the current chain that have not been deleted can still be used normally for restore.
Therefore, your configuration is behaving as designed. The information you are seeing is simply the image check indicating those old versions that were intentionally removed by the retention policy.