Hello @Roland 

The entire idea of the Command Center is to simplify and automate the schedule process. 

By having a Inc job run before the Syth full it will roll it all together and give you a complete job.

You can change this if you find the schedule in the Java console and untick the box which forces it to run the Incremental before the Syth full if you truly want to stop this behaviour. 

Kind regards

Albert Williams

Out of curiosity, is there’s a specific use-case for why you might not want to run an Incr job immediately before the Synth Full job?

To be clear, a Synth Full job does not protect any data.  The last Incr (or traditional Full) is going to be the latest restore point.

Thanks,
Scott
 

Hello @Roland 

We would like you to log a Support case for this so we can review. If you are manually triggering a synthetic full on the client \ subclient level it should not be triggering an incremental prior to the Synthetic full. There are advanced job execution options here that depending on if you are initiating the job from the Command Center UI may not be showing up, versus if you have a Java Console.

The only time an incremental should execute before a Synth full job is if you are executing the schedule from the Plan layer, as that is expected, but not on an ad-hoc operation.

Thanks!

Hello

We run thousends of vm incremental backups every night. 
The synth full backups are done during the day between monday and friday.(Without an incr. backup before) 
Sometimes a synth full backup crashes. 
I am not able to start this backup again manually (ad-hoc) because an incr. backup is always started before the synth full backup.
I have options for starting a crashed backup.
I also know what a synth full backup does and how it works.

I just wanted to know why CV builds such a setting into the CommandCenter.

Before I opened a support ticket can you send me the documentation link where “Advanced job execution options” described?

regards