BACKUP STGPOOL (Back up primary storage pool to copy storage pool)

In addition to backing up primary storage pools having NATIVE or NONBLOCK data formats, this command lets you back up primary storage pools that have NDMP data formats (NETAPPDUMP, CELERRADUMP, or NDMPDUMP). The copy storage pool to which data is to be backed up must have the same data format as the primary storage pool. Tivoli® Storage Manager supports backend data movement for NDMP images.

You cannot back up data from or to storage pools defined with a CENTERA device class.

If a file already exists in the copy storage pool, the file is not backed up unless the copy of the file in the copy storage pool is marked as damaged. However, a new copy is not created if the file in the primary storage pool is also marked as damaged. In a random-access storage pool, neither cached copies of migrated files nor damaged primary files are backed up.

If migration for a storage pool starts during a storage pool backup, some files may be migrated before they are backed up. You may want to back up storage pools that are higher in the migration hierarchy before backing up storage pools that are lower. For example, when performing a storage pool backup to copy the contents of a storage pool offsite, if the process is not done according to the existing storage pool hierarchy, some files may not be copied to the copy storage pool. This could become critical for disaster recovery purposes. When performing a storage pool backup on multiple storage pools, the primary storage pool should be completed before starting the backup process on the next storage pool.

Privilege class

To issue this command, you must have system privilege, unrestricted storage privilege, or restricted storage privilege for the copy storage pool in which backup copies are to be produced.

Parameters

primary_pool (Required)

Specifies the primary storage pool.

copy_pool (Required)

Specifies the copy storage pool.

MAXPRocess

Specifies the maximum number of parallel processes to use for backing up files. This parameter is optional. Enter a value from 1 to 999. The default is 1.

Using multiple, parallel processes may improve throughput for the backup. The expectation is that the time needed to perform the storage pool backup will be decreased by using multiple processes. However, when multiple processes are running, in some cases one or more of the processes needs to wait to use a volume that is already in use by a different backup process.

When determining this value, consider the number of logical and physical drives that can be dedicated to this operation. To access a sequential access volume, Tivoli Storage Manager uses a mount point and, if the device type is not FILE, a physical drive. The number of available mount points and drives depends on other Tivoli Storage Manager and system activity and on the mount limits of the device classes for the sequential access storage pools that are involved in the backup.

Each process needs a mount point for copy storage pool volumes, and, if the device type is not FILE, each process also needs a drive. If you are backing up a sequential storage pool, each process needs an additional mount point for primary storage pool volumes and, if the device type is not FILE, an additional drive. For example, suppose you specify a maximum of 3 processes to back up a primary sequential storage pool to a copy storage pool of the same device class. Each process requires 2 mount points and 2 drives. To run all 3 processes, the device class must have a mount limit of at least 6, and at least 6 mount points and 6 drives must be available.

To preview a backup, only one process is used and no mount points or drives are needed.

Preview

Specifies if you want to preview but not perform the backup. The preview displays the number of files and bytes to be backed up and a list of the primary storage pool volumes that you must mount. This parameter is optional. The default is NO. Possible values are:

No

Specifies that the backup is done.

Yes

Specifies that you want to preview the backup but not do the backup.

VOLumesonly

Specifies that you want to preview the backup only as a list of the volumes that must be mounted. This choice requires the least processing time. The VOLUMESONLY option is valid only for storage pools associated with a sequential-access device class.

SHREDTONOshred

Specifies whether data will be backed up to a copy storage pool from a primary storage pool that enforces shredding. This parameter is optional. The default value is NO. Possible values are:

No

Specifies that the server will not allow data to be backed up to a copy storage pool from a primary storage pool that enforces shredding. If the primary storage pool enforces shredding, the operation will fail.

Yes

Specifies that the server does allow data to be backed up to a copy storage pool from a primary storage pool that enforces shredding. The data in the copy storage pool will not be shredded when it is deleted.

Wait

Specifies whether to wait for the server to complete processing this command in the foreground. This parameter is optional. The default is NO. Possible values are:

No

Specifies that the server processes this command in the background.

You can continue with other tasks while the command is being processed. Messages created from the background process are displayed either in the activity log or the server console, depending on where messages are logged.

To cancel a background process, use the CANCEL PROCESS command. If you cancel this process, some files may have already been backed up prior to the cancellation.

Yes

Specifies that the server performs this operation in the foreground. You must wait for the operation to complete before continuing with other tasks. The server displays the output messages to the administrative client when the operation completes.

Note: You cannot specify WAIT=YES from the server console.

Related commands