IBM Tivoli Storage Manager, Version 7.1

Specifying when the simultaneous-write operations occur

You can specify simultaneous-write operations for any primary storage pool that is the target of client store sessions, server import processes, or server data-migration processes. You can also disable the simultaneous-write function.

About this task

To control the simultaneous-write function, use the AUTOCOPY parameter on the DEFINE STGPOOL or UPDATE STGPOOL commands for primary storage pools.

Remember:

Specify a value for the AUTOCOPY parameter on the primary storage pool that is the target of data movement. (The default is to write data simultaneously during client store sessions and server import processes.) For example, if you want to write data simultaneously only during server data-migration processes, specify AUTOCOPY=MIGRATION in the definition of the next storage pool in the storage pool hierarchy.
The AUTOCOPY parameter is not available for copy storage pools or active-data pools.

IBM® Tivoli® Storage Manager provides the following options for controlling when simultaneous-write operations occur:

Procedure

To disable the simultaneous-write function, specify AUTOCOPY=NONE.
This option is useful, if, for example, you have copy storage pools or active-data pools defined, and you want to temporarily disable the simultaneous-write function without having to delete and then redefine the pools.
To specify simultaneous-write operations only during client store sessions and server import processes, specify AUTOCOPY=CLIENT.
During server import processes, data is simultaneously written only to copy storage pools. Data is not written to active-data pools during import processes.
To specify that simultaneous-write operations take place only during server data-migration processes, specify AUTOCOPY=MIGRATION.
During server data migration, data is simultaneously written to copy storage pools and active-data pools only if the data does not exist in those pools.
To specify that simultaneous-write operations take place during client store sessions, server data-migration processes, and server import processes, specify AUTOCOPY=ALL.
A primary storage pool can be the target for more than one type of data movement. For example, the next storage pool in a storage pool hierarchy can be the target for data migration from the primary storage pool at the top of the hierarchy. The next storage pool can also be the target for direct backup of certain types of client files (for example, image files). The AUTOCOPY=ALL setting on a primary storage pool ensures that data is written simultaneously during both server data-migration processes and client store sessions.

Example

The following table provides examples of AUTOCOPY settings for some common scenarios in which the simultaneous-write function is used.

Table 1. AUTOCOPY settings
If your goal is...	Set the AUTOCOPY parameter for the primary storage pool at the top of the storage hierarchy to...	Set the AUTOCOPY parameter for the next primary storage pool to...
To disable the simultaneous-write function	NONE	NONE
To enable simultaneous-write operations only during client store sessions and server import processes	CLIENT	NONE
To enable simultaneous-write operations only during server data-migration processes	NONE	MIGRATION
To simultaneously write client files to copy storage pools during migration. You also want simultaneous-write operations to occur for files that are directly backed up to the next storage pool.	NONE	ALL
To enable simultaneous-write operations during any of the following operations: client store sessions, server import processes, and server data-migration processes.	ALL	ALL

Feedback