Volume access preemption
If a high-priority operation requires access to a specific volume and that volume is in use, the high-priority operation can preempt the lower-priority operation for that volume.
For example, if a restore request requires access to a volume in use by a reclamation operation and a drive is available, the reclamation operation is canceled.
The following high-priority operations can preempt operations for access to a specific volume:
- Database backup operations
- Retrieve, restore, or HSM recall operations that are initiated by clients
- Restore operations by using a remote data mover
- Export operations
- Import operations
- Operations to generate backup sets
The following operations cannot preempt other operations or be preempted:
- Audit volume
- Restore data from a copy or active-data pool
- Prepare a recovery plan
- Store data by using a remote data mover
The following operations can be preempted, and are listed in order of priority, from highest priority to lowest priority. The server selects the lowest priority operation to preempt, for example, identify duplicates.
- Replicate nodes
- Back up data to a copy storage pool
- Copy active data to an active data pool
- Move data on a storage pool volume
- Migrate data from disk to sequential media
- Migrate data from sequential media to sequential media
- Back up, archive, or HSM migrate data that is initiated by client
- Reclaim volumes in a sequential-access storage pool
- Identify duplicates