Active Full & Forward Incremental Forever

[thomas.biesmans]

Case ID: 01908796

Hey all. When you configure a Forward Incremental job with either Synthetic Fulls or Active Fulls, then the job is switched from Forward Incremental Forever to a regular Forward Incremental. (source)

For synthetic fulls that seems logical, but not so for Active Fulls imho (hence the Case ID ). I would like to combine:
- having a Forward Incremental Forever job with, for example, 14 restore points with all its benefits,
- while also having automatic Active Fulls every three months for added robustness.

Is there a specific reason why this is not permitted, or is it a product limitation you haven't yet addressed?

[foggy]

You can schedule "manual" active fulls triggered by script every 3 months, if required. This will not switch the job to forward incremental.

[thomas.biesmans]

Hm, so are you evaluating whether to change this? Your own recommendation is to always schedule Active Fulls (1-3 months), rendering Forward Incremental Forever pretty much useless. Yet I want the option not to have those extra synthetic fulls on disk and not having Reverse Incremental's performance hit.

I'd even settle for a registry key, but using PowerShell scripts to trigger Active Fulls is such an HPE-way to solve this, I expect better

[foggy]

Periodic active fulls requirement was effective prior to introducing forever forward incremental mode. Please review this thread for more information.