A server process is a task that is performed on the server. You can assign the task to perform a specific operation, such as migrating data from a storage pool to the next storage pool in the hierarchy. Issue the server processes to resolve problems that you are having with your server.
Server processes are typically initiated as an automated process on the server. The process might or might not be influenced by a server option or other setting. The server process can also be started by a command.
Many server processes can be run in the FOREGROUND or synchronously. Processes that run in the FOREGROUND can be initiated by a command using the WAIT=YES parameter. Commands that start server processes that do not allow the WAIT=YES parameter or commands specified with WAIT=NO are run in the BACKGROUND or asynchronously.
| Process or command | Description | Runs in the foreground or as a multiple process |
|---|---|---|
| AUDIT VOLUME | Audit the contents of a volume to validate that the data can still be read and that the server database definitions describing the data are correct. | |
| BACKUP DB | Back up the server database (FULL or INCREMENTAL). | The BACKUP DB can run as a synchronous process by specifying WAIT=YES. |
| BACKUP STGPOOL | Back up a primary server storage pool to a copy storage pool. The result is that you can make duplicate copies of the data and potentially take duplicate copies to an off-site location. | The BACKUP STGPOOL can run as a synchronous process by specifying WAIT=YES. BACKUP STGPOOL might be run using multiple concurrent processes, which is controlled by the MAXPROCESS parameter specified on the BACKUP STGPOOL command. |
| CHECKIN LIBVOLUME | Check a tape volume into a tape library. | |
| CHECKOUT LIBVOLUME | Check a tape volume out from a tape library. | |
| Expiration | Delete client backup and archive files from
the server, based on the policies defined to manage those files. You can run expiration automatically by specifying EXPINTERVAL=n in the server options file, where n is any number other than zero. Expiration can also be initiated by issuing the EXPIRE INVENTORY command. It is not possible to have more than one expiration process running at a time, although you can run more than one thread at a time. |
The EXPIRATION command can run as a synchronous process by specifying WAIT=YES. |
| IMPORT | Import data from sequential media volumes or
directly from another server using TCP/IP communication connections
between the servers. Import processing can be started by any of
the following commands:
|
|
| LABEL LIBVOLUME | Label one or more library volumes in a library. | |
| Migration | Migrate data from one storage pool to the next
in the storage hierarchy. Migration starts and stops, based on the HighMig and LowMig thresholds defined for the storage pool. Whenever UPDATE STGPOOL is issued, these values are reexamined and, if appropriate, MIGRATION is started. Otherwise, the server monitors the percentage utilization for non-migrated data in a storage pool. As the server needs, it starts migration processing for that storage pool when the HighMig threshold is exceeded. You can also issue the MIGRATE STGPOOL command to manually start migration processing. |
Migration might be configured to run multiple concurrent processes. The multiple processes are controlled by the MIGPROCESS attribute of the storage pool and might be updated by issuing the UPDATE STGPOOL command. |
| MOVE DATA | Move data from one volume to other volumes in the same storage pool or to a different storage pool. | The MOVE DATA command can run as a synchronous process by specifying WAIT=YES. |
| MOVE DRMEDIA | Manage the disaster recovery media by moving on-site volumes off-site, or by bringing back off-site volumes, on-site. Disaster recovery media is the database backup and storage pool backup volumes necessary to protect and recover the server. | The MOVE DRMEDIA command can run as a synchronous process by specifying WAIT=YES. |
| MOVE MEDIA | Move volumes from a tape library to the overflow location to prevent a library from becoming full. | |
| MOVE NODEDATA | Move all the data for the node or nodes specified to other volumes in the same storage pool or to a different storage pool. | The MOVE NODEDATA command can run as a synchronous process by specifying WAIT=YES. |
| PREPARE | Create a recovery plan file. | The PREPARE command can run as a synchronous process by specifying WAIT=YES. |
| Reclamation | Reclaim space from tape volumes by moving active
data to other volumes and returning the volume back to empty and private,
or else back to scratch. The server monitors the RECLAMATION THRESHOLD defined for a storage pool. It starts a reclamation process for that storage pool to reclaim any eligible volumes if it determines that one or more eligible volumes exist. |
|
| RESTORE STGPOOL | Restore all files for a given storage pool from a copy storage pool. | The RESTORE STGPOOL can run as a synchronous process by specifying WAIT=YES. RESTORE STGPOOL might be run using multiple concurrent processes, which is controlled by the MAXPROCESS parameter specified on the RESTORE STGPOOL command. |
| RESTORE VOLUME | Restore all files for a given volume from a copy storage pool. | The RESTORE VOLUME command can run as a synchronous process by specifying WAIT=YES. RESTORE VOLUME might be run using multiple concurrent processes, which is controlled by the MAXPROCESS parameter specified on the RESTORE VOLUME command. |