# VM-centric job behavior

The Commvault can use VM-centric indexing for hypervisor protection. When VM-centric indexing is enabled, backup and restore operations are optimized, and some job behavior changes.

## How VM-centric jobs are organized

When VM-centric indexing is used, a VM group backup runs as a VM Admin job that manages one or more VM-specific child jobs.

- VM-level operations run as a VM Admin job.

- Commvault creates a child job for each VM and assigns a unique job ID to each child job.

- VM backup data is committed as each child job finishes, rather than waiting for all VMs to complete.

This job model affects what you see in job monitoring and which job types you can act on in Command Center.

## What you can manage at the VM level

VM-centric operations let you manage certain actions for individual VMs without changing the full VM group, such as:

- Start VM-level backup and restore operations.

- Enable or disable VM activity such as backups, restores, and data aging.

## Guardrails and expected behavior

Keep these behaviors in mind when you manage jobs:

- Some actions apply only to the VM Admin job, not to child jobs.

- You can change job priority only for VM Admin jobs, not for child jobs.

For the job-priority task, see changing job priority for VM backup jobs.

If you used CommCell Console

If you’re familiar with CommCell Console terminology, the Command Center uses different object names:

- A virtualization client is called a hypervisor.

- A subclient is called a VM group.

×

Loading...