IBM Tivoli Storage Manager, Version 7.1

Specifying how the server reacts to a write failure during simultaneous-write operations

Write failures to copy or active-data pools might occur during while data is being simultaneously written. If a write failure occurs during a client store session, you can specify whether to continue or discontinue the operation.

About this task

Use the COPYCONTINUE parameter on the DEFINE STGPOOL command to specify how the server reacts to a write failure to copy storage pools during client store sessions:

Procedure

To stop writing to failing copy storage pools for the remainder of the session, but continue storing files into the primary pool and any remaining copy pools or active-data pools, specify COPYCONTINUE=YES.
The copy storage pool list is active only for the life of the session and applies to all the primary storage pools in a particular storage pool hierarchy.
To fail the transaction and discontinue the store operation, specify COPYCONTINUE=NO.

What to do next

Restrictions:

The setting of the COPYCONTINUE parameter does not affect active-data pools. If a write failure occurs for any of active-data pools, the server stops writing to the failing active-data pool for the remainder of the session, but continues storing files into the primary pool and any remaining active-data pools and copy storage pools. The active-data pool list is active only for the life of the session and applies to all the primary storage pools in a particular storage pool hierarchy.
The setting of the COPYCONTINUE parameter does not affect the simultaneous-write function during server import. If data is being written simultaneously and a write failure occurs to the primary storage pool or any copy storage pool, the server import process fails.
The setting of the COPYCONTINUE parameter does not affect the simultaneous-write function during migration. If data is being written simultaneously and a write failure occurs to any copy storage pool or active-data pool, the failing storage pool is removed and the data migration process continues. Write failures to the primary storage pool cause the migration process to fail.

Feedback