Skip to main content
commvault.com commvault.com
Question

Child job VM Synthetic full does not trigger if VM has running incremental

J
Byte
Forum|alt.badge.img+1

Backup type is for a VMware hypervisor. 

We created a plan that requires a weekly recovery point with extended retention in which it auto generated an SF schedule for every thursday at 02:18AM. The VM group was set to trigger its daily incremental everyday at 12:30AM in the same plan.

We recently accidentally (no failures in the VM parent jobs) noticed that more than 10 out of the 30 VMs for the VM group had the last synthetic full of 12th December and then realized that even though the parent SF VM backup job was being triggered, the VMs were being automatically excluded or not triggering the corresponding child VM backup job as its incremental was still running at 02:18AM. 

We raised a case with support and we were informed that child VM jobs not being triggered due to an existing incremental running and with no errors shown in the parent VM backup job is not a bug and by design. 

I would just like to ask the forum if you guys are aware of this behaviour and if you can point us to the documentation that describes this. Would this also be a behaviour applicable to commvault enterprise?

 

2 replies

K
Vaulter
Forum|alt.badge.img+5

Hi ​@JosephB ,

Currently when synthetic full at VM level run, if there is still incremental job running, the synthetic full at VM level will be skipped and the parent job should be marked as CWE. If you have “Queue jobs if other conflicting jobs are active” option turned on, then synthetic full job will be queued and waiting for incremental job to complete then run.

 

You can check below documentation for enabling the “Queuing Job” option:

Queuing Jobs

 

Thanks,

Keshika

J
Byte
Forum|alt.badge.img+1
  • JosephB
  • Author
  • Byte
  • 1 reply
  • January 29, 2025

Hi ​@Keshika Bisht , 


Thanks for the info. I think this is same as what we were expecting, that the parent VSA backup job should have at least a “Completed with Error” status, however, it just completes as successful. Also, the issue we have is that it is in commvault cloud which makes it harder as there is not much configuration you can do with an MSP or even a tenant admin account. 

We have not found any documentation regarding the whole exclusion/skipped VM logic when triggering an SF with an incremental running. The closest we have found is the following link - https://documentation.commvault.com/2024e/expert/frequently_asked_questions_for_synthetic_full_backups.html
 

Virtual Server Agents

For virtual server agents with Indexing Version 2 enabled, you can manually run or schedule incremental backup jobs while a synthetic full backup is running.

You do not need to schedule incremental backups around when synthetic full backups are performed. However, running a synthetic full backup while an incremental backup job is running is not supported. Also, running a full or differential backup job in parallel with a synthetic full backup job is not supported.

 

The above is found only on the commvault enterprise section and not on the SaaS (Commvault cloud) part. Most customers of the Commvault cloud platform would not have an idea of VSA index v2. 

 

 

Reply


Most helpful members this week

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings