Why are my backup instances out of sync when I look at then in view job
When looking at a job using the view job web page we get a list called “Recent Instance” which list the job showing the time they ran and instance of the job. On occasions it can be seen that the instances are out of sync, for example:
24/04/2017 Job x instance 4
23/04/2017 Job x instance 2
22/04/2017 Job x instance 3
22/04/2017 Job x instance 1
This is because on this occasion instance 1 ran as scheduled, the next backup was then scheduled to run 23/04/2017 on completion of instance 1. The next scheduled job was allocated the instance number of instance 2 but then the backup was run manually before instance 2 scheduled time. The manually run backup is given the instance number of instance 3. Then when the next scheduled job completes NetVault is aware of instance 3 running so allocates instance 4 to the next schedule job.
Instance numbering seen is expected and as designed. It should not affect functionality or data integrity. Instance numbers are assigned either when a job is scheduled or manually run. For any periodically scheduled job, a manually run instance will appear to have an "out of order" instance number.