Data Domain Storage Migration - license - 1 server

Mfg.Part: L-DD-SMIG | CDW Part: 4381696 | UNSPSC: 43232907
Availability: In Stock
Request Pricing
Product Details
  • License
  • 1 server
View Full Product Details
Better Together
Data Domain Storage Migration - license - 1 server
Quick View
Total Price:

Product Overview

Main Features
  • License
  • 1 server
Storage migration supports the replacement of existing storage enclosures with new enclosures that may offer higher performance, higher capacity, and a smaller footprint. After new enclosures are installed, you can migrate the data from the older enclosures to the new enclosures while the system continues to support other processes such as data access, expansion, cleaning, and replication. The storage migration does require system resources, but you can control this with throttle settings that give the migration a relatively higher or lower priority. You can also suspend a migration to make more resources available to other processes, then resume the migration when resource demand is lower.

During the migration, the system uses data on the source and destination enclosures. New data is written to the new enclosures. Non-migrated data is updated on the source enclosures, and migrated data is updated on the destination enclosures. If the migration is interrupted, the migration can resume migrating blocks that have not been marked as migrated.

During the migration, each block of data is copied and verified, the source block is freed and marked as migrated, and the system index is updated to use the new location. New data that was destined to land in the source block will now be redirected to destination block. All new data block allocations that would have been allocated from source are allocated from the destination.

The Migration copy process is done at the shelf level, not the logical data level, so all disk sectors on the source shelf are accessed and copied over regardless of whether there is data on them. Therefore, the Storage Migration Utility cannot be used to shrink a logical data footprint.