Creating Phase 3 incremental backups that do not get index conflicts if they run before a previous backup from the saveset has completed
At the moment netvault does not have the ability via the GUI to schedule phase 3 backups so phase 3 backups need to be triggered. If the phase 3 backup triggers before any other previous backup from this saveset has completed, the backup will fail with an index conflict. This is because the index is locked by the previous backup.
Create separate Daily incremental jobs Mon, Tue, Wed, Thu, Fri - individual jobs using the same selection set but scheduled on days of the week to designate tape or smartdisk.
Each job has a separate trigger that it sets. For each incremental job ID the trigger sets off a datacopy job for which the first phase runs IMMEDIATELY the incremental completes thus ensuring that the first phase of the datacopy completes to the selected media
Note the datacopy job needs to use backup sets, with option "Use sets most recent job
This solution also resolves any problem seen if media for the phase 3 backups are put in on a Friday and taken off site on a Monday because all weekly incremental backups will sit waiting for media until the required media is loaded.
There are other solutions that deal with this problem but this one enables netvault to wait until the weekend before writing all the phase 3 incremental backups to tape and fulfil many company offsite criteria