Title: Triggering one job from another results in error "Index conflict: An index needed for this job is in use by another active job"
Date: Apr 07
NV Version: All
OS Version: All
Application version: N/A
Plugin version: N/A
Description:
This FAQ describes how to set up Netvault:Backup jobs in order to have one job trigger the next one when the 2nd one will need to access the index created by the first.
Symptoms:
When using the "postscript" feature of Netvault:Backup to trigger job2 from job1, job2 is not run and the error message "Index conflict: An index needed for this job is in use by another active job" is written to the log.
To resolve this:
1. Create a very simple new job which just backs up 1 file. It doesn't matter what it is, it just needs to be a very small job. This will be the "wrapper job" for job1 and job2 and it needs to run a postscript (for example name the script START1AND2.BAT or start1and2.sh on Unix/Linux).
2. Create this script which needs to contain lines such as:
"C:\Program Files\BakBone Software\NetVault\bin\nvtrigger.exe" -server YOURNVSERVERNAME -wait trig1
"C:\Program Files\BakBone Software\NetVault\bin\nvtrigger.exe" -server YOURNVSERVERNAME trig2
or on Unix/Linux:
/usr/netvault/bin/nvtrigger -server YOURNVSERVERNAME -wait trig1
/usr/netvault/bin/nvtrigger -server YOURNVSERVERNAME trig2
3. Edit job1 and set its schedule to be triggered by "trig1" - or whatever is specified in the BATch/shell script on the first line. Remember to remove the reference to any postscript that job1 may be configured to run at the moment.
4. Edit job2 and set its schedule to be triggered by "trig2" - or whatever is specified in the BATch/shell script on the second line.
The -wait on the first line of the BATch script is very important. This tells us to wait until the first job finishes before proceeding.
This situation arises because at the point in time when Netvault:Backup runs the postscript (which is merely an nvtrigger command to run job2) the index for job1 has not been "released". Consequently when job2 tries to run it finds that it cannot read the index and the job fails. The workaround is to create a "wrapper job" that runs both real jobs one after the other. The important thing to note is that using this method job1 has completely finished when job2 starts and hence the problem does not occur.
====================================
Version française disponible ID
Deutsche Version verfügbar ID
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center