Configuring the Parallelism for Backups and Restores

Note: If you use deduplication, set the Parallelism value to 0.

If the DB2 database contains large number of tablespaces and indexes, you can perform backups and restores faster when you set a maximum number of concurrent parallelism queries to take advantage of available Input/Output bandwidth and processor power of DB2 server. DB2's query parallelism targets Input/Output intensive queries for example, tablespace scans, large index scans etc.) and CPU intensive queries (for example, joins, sorts, complex expressions etc.). If the number is not set, the optimal value is automatically chosen. When you set this parameter, it can reduce the time required to complete the backup (specially, if the backup is going to a disk).

This parameter defines the number (n) of processes that are started to read the data from the database. A specific table space is assigned to backup as part of each process. When it completes the tablespace backup, it requests another.  If you are trying to backup to different targets (for example, using multiple sessions to send the data), parallelism should not be greater than the number of targets (sessions).

Last modified: 8/10/2018 3:28:28 PM