What is the result when the migrate process moves data from a deduplicated pool to a non-deduplicated pool?
A. The migration process fails.
B. The target pool is marked as deduplicated.
C. The data is reconstituted on the target pool.
D. The data in both storage pools is reconstituted.
* Data deduplication in Tivoli Storage Manager is a two-phase process. In the first phase, the server identifies the duplicate data in the storage pool. As volumes in the storage pool are filled, data becomes eligible for duplicate identification. A volume does not have to be full before duplicate identification starts. In the second phase, duplicate data is removed by any of the following processes:
Reclaiming volumes in the primary-storage pool, copy-storage pool, or active-data pool
Backing up a primary-storage pool to a copy-storage pool that is also set up for deduplication
Copying active data in the primary-storage pool to an active-data pool that is also set up for deduplication
Migrating data from the primary-storage pool to another primary-storage pool that is also set up for deduplication
Moving data from the primary-storage pool to a different primary-storage pool that is also set up for deduplication, moving data within the same copy-storage pool, or moving data within the same active-data pool