We have a primary copy which uses a deduplicated WORM enabled cloud storage pool as a target.
Therefore we have frequent sealing of the DDB so the data can be aged and block references are cleaned up.
I just recently discovered a client which for some reason had not started a synthetic full backup for two months despite being assigned to a plan where a synthetic full is configured.
Because of that a whole DDB generation is now blocked from aging because of the cycle dependency.
Is there an option to fix these kind of situations afterwards?
I was thinking about a synthetic full backup which only uses incrementals up to a user defined time so the cycle stays short.
As we are currently still on 11.40: I also read that there are improvements in data aging on WORM enabled pools which would enable pruning on job level rather than a whole DDB.
Would this change already prevent my current situation in advance?
From my understanding the DDB would still stay but only the blocks referenced by this one client would be retained on disk.
