|
|
Multiple Vault sessions can run at the same time. Vault uses a global setting, Maximum Vault Jobs, as a threshold for queuing jobs from any vault. A Vault job runs if resources are available and the maximum number of Vault jobs has not been reached. If resources are not available to run jobs, Vault queues jobs until the resources are available.
Vault also uses locks on the duplication and eject steps of a job to enforce queueing for jobs that are contending for those resources.
Vault queues jobs as follows:
If Maximum Vault Jobs is reached, any subsequent vault job is queued and its status is shown as Queued in the Activity Monitor.
If a job needs to duplicate images and another job from the same vault is duplicating images, the job is queued and shown as Active in the Activity Monitor. More detailed information about the status of these Active jobs appears in the Detailed Status tab of the Job Details dialog box.
If a job needs to eject media and another job from any vault is ejecting media in the same robot, the job is queued and shown as Active in the Activity Monitor.
Queued jobs are scheduled or run when the resources required for them become available.
For jobs that run simultaneously, the following restrictions exist:
Vaults should not share on-site and off-site volume pools. Profiles within the same vault can use the same volume pools, but profiles from one vault cannot use the same volume pools as profiles from another vault.
Vaults should not share off-site volume groups. Profiles within the same vault can use the same off-site volume groups, but profiles from one vault cannot use the same off-site volume groups as profiles from another vault.
More Information