Backup job fails with error message "Backup failed to run due to index conflict" or "Index conflict: An index needed for this job is in use by another active job".
The message indicates that you can't run two jobs at the same time on the same client with the same selection set, particularly not an incremental and a full or consolidated backup. For a backup sequence (Full - Incremental - Consolidate - Data Copy) only one job may run at any given time. During a backup job, the selections set is locked preventing other jobs that use the same set from running.
For example, suppose a sequence of File System jobs use a Backup Selection Set configured and named "User File System Data", which specifies "D:\Fileserver\Userdata" to be backed up.
Make sure that no jobs using the same Backup Selection Set are scheduled to run on the same client simultaneously. For a backup sequence (Full - Incremental - Consolidate - Data Copy) only one type of job may run at any given time. Schedule the backups in such a way that there is enough time for the other job to complete before running the next one (i.e. Daily incremental backup with a average run time of three hours starts at 9 PM, and Full Weekly job runs on Friday at 1 AM).
Check for previous instances of a job which could be in waiting status. Determine the cause, and resolve it. Refer to other solutions in the Support Knowledge Base for assistance resolving "Waiting for Media" issues.
Last, consider creating a separate Backup Selection set to protect the files. Perhaps splitting the job into smaller one will allow them to complete earlier and allow the next job to start as scheduled without causing a conflict.
