setting priority of disk stgpool migration process

[raylin]

Is it possible to set the priority of a disk stgpool migration process ?

A restore of a client for example gets automatically a higher priority and preempts the tape device.

 

[mbourne2006]

Hi

One way would be to "DISABLE SESSION" or "LOCK NODE" during migration processing, thereby preventing the nodes from requesting access to server storage.

I don't believe that you can do anything about the way in which different processes preempt one another. A TSM DB BACKUP will always jump the queue ahead of anything else.

HTH

Matthew

 

[denisl]

Preemption can only be turned off or on. Preemption is described in the admin guide:

Preemption of Client or Server Operations
The server can preempt server or client operations for a higher priority operation when a mount point is in use and no others are available, or access to a specific volume is required. You can use the QUERY MOUNT command to see the status of the volume for the mount point.

Mount Point Preemption
The following high priority operations can preempt operations for a mount point:


Backup database 
Restore 
Retrieve 
HSM recall 
Export 
Import
The following operations cannot preempt other operations nor can they be preempted:

Audit Volume 
Restore from a copy storage pool 
Prepare a recovery plan 
Store data using a remote data mover
The following operations can be preempted and are listed in order of priority. The server selects the lowest priority operation to preempt, for example reclamation.

Move data 
Migration from disk to sequential media 
Backup, archive, or HSM migration 
Migration from sequential media to sequential media 
Reclamation
You can disable preemption by specifying NOPREEMPT in the server options file. When this option is specified, the BACKUP DB command is the only operation that can preempt other operations.

Volume Access Preemption
A high priority operation that requires access to a specific volume currently in use by a low priority operation can automatically preempt the operation. For example, if a restore request requires access to a volume in use by a reclamation process and a drive is available, the reclamation process is canceled and message ANR0494I or ANR1441I is issued.

The following high priority operations can preempt operations for access to a specific volume:

Restore 
Retrieve 
HSM recall
The following operations cannot preempt other operations nor can they be preempted:

Audit Volume 
Restore from a copy storage pool 
Prepare a recovery plan 
Store data using a remote data mover
The following operations can be preempted, and are listed in order of priority. The server preempts the lowest priority operation, for example reclamation.

Move data 
Migration from disk to sequential media 
Backup, archive, or HSM migration 
Migration from sequential media 
Reclamation
You can disable preemption by specifying NOPREEMPT in the server options file. When this option is specified, no operation can preempt another operation for access to a volume.