-
Title
Backup jobs stuck in "Waiting for previous index" -
Description
Some incremental backup jobs have been hung for days in "Waiting for previous index".
The previous incremental and full indexes are all available to restore from and there is there is ample free space on the partition hosting the netvault/tmp folder where folders are loaded.
-
Cause
Examining the NetVault logs around the time of these jobs started shows that a NetVault Database backup was in progress when these jobs started.
Specifically, the MediaDatabase was going through an integrity check of its internal tables when the request for previous backup indexes was issued to the Media Manager process, hence these requests where ignored for the integrity check to proceed.
-
Resolution
The daily NetVault Databases backups must be scheduled outside of the backup window.
The NVDB backup should ideally run when no other backup is running.The NVDB backup goes through several phases, and depending on how many jobs are running and the stage the NVDB backup is at, results may vary from success to failure of the other jobs.As part of the NVDB backup, the Logs, Reports, ScheduleDatabase, MediaDatabase, Configuration, Licenses are backed up. If a job is submitted when the Media manager process is performing its own tables integrity check, then any job request for indexes may fail or be ignored resulting in a hung job.Likewise, if the ScheduleDatabase is being checked/backed up, and a job needs to start or request backup options from the same ScheduleDatabase, then the job may not start, or will remain hung waiting for job options.