Mount point preemption
If a high-priority operation requires a mount point that is in a specific device class and all the mount points in the device class are in use, the high-priority operation can preempt a mount point from a lower-priority operation.
Mount points can be preempted only when the device class of the operation preempting and the operation that is being preempted is the same.
The following high-priority operations can preempt other operations for a mount point.
- 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 server operations cannot preempt other operations or be preempted:
- Audit a volume
- Restore data from a copy or active-data pool
- Prepare a recovery plan file
- 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 operations that are initiated by clients
- Reclaim volumes in a sequential-access storage pool
- Identify duplicates