Professional Documents
Culture Documents
Topic
DDOS 6.0 Storage Migration Procedures
Selections
Storage Migration: Overview and Planning
REPORT PROBLEMS
If you find any errors in this procedure or have comments regarding this application, send email to
SolVeFeedback@dell.com
THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION (“EMC”)
MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE
INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-
INFRINGEMENT AND ANY WARRANTY ARISING BY STATUTE, OPERATION OF LAW, COURSE OF
DEALING OR PERFORMANCE OR USAGE OF TRADE. IN NO EVENT SHALL EMC BE LIABLE FOR
ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL,
LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF EMC HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.
EMC believes the information in this publication is accurate as of its publication date. The information is
subject to change without notice. Use, copying, and distribution of any EMC software described in this
publication requires an applicable software license.
Dell, EMC, Dell EMC and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other
trademarks may be the property of their respective owners.
Page 1 of 6
Contents
Preliminary Activity Tasks .......................................................................................................3
Read, understand, and perform these tasks.................................................................................................3
Page 2 of 6
Preliminary Activity Tasks
This section may contain tasks that you must complete before performing this procedure.
Table 1 List of cautions, warnings, notes, and/or KB solutions related to this activity
493216: Usable capacity is smaller than the expected overall tier size
2. This is a link to the top trending service topics. These topics may or not be related to this activity.
This is merely a proactive attempt to make you aware of any KB articles that may be associated with
this product.
Note: There may not be any top trending service topics for this product at any given time.
Page 3 of 6
Storage migration overview
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.
Note: Because the data set is divided between the source and destination enclosures during migration,
you cannot halt a migration and resume use of only the source enclosures. Once started, the migration
must complete. If a failure, such as a faulty disk drive, interrupts the migration, address the issue and
resume the migration.
Depending on the amount of data to migrate and the throttle settings selected, a storage migration can
take days or weeks. When all data is migrated, the finalize process, which must be manually initiated
using the storage migration finalize command, restarts the filesystem. During the restart, the
source enclosures are removed from the system configuration and the destination enclosures become
part of the filesystem. When the finalize process is complete, the source enclosures can be removed from
the system.
Note: Storage Migration can be done one to one, one to many or many to one of enclosures or disk
packs with the following list of requirements and cautions. Proper planning for storage migration is
critical to efficiently move the data with performance considerations taken into account. If multiple
storage migration operations are required, each storage migration process will require a separate
license.
Page 4 of 6
Be supported on the DD system model.
Have the correct shelf to shelf or controller to shelf SAS cabling as appropriate.
Contain at least as much usable capacity as the enclosure(s) they are replacing.
Note: It is not possible to determine the utilization of the source shelf. The Data Domain system
performs all calculations based on the capacity of the shelf.
Storage migration cannot start when the file system is disabled or while a DD OS upgrade is in
progress, another migration is in progress, or a RAID reconstruction is in progress.
Note: If a storage migration is in progress, a new storage migration license is required to start a new
storage migration operation after the in-progress migration completes. The presence or absence of a
storage migration license is reported as part of the upgrade precheck.
All specified source enclosures must be in the same tier (active or archive).
There can be only one disk group in each source enclosure, and all disks in the disk group must be
installed in within the same enclosure.
All disks in each destination enclosure must be of the same type (for example, all SATA or all SAS).
After migration begins, the destination enclosures cannot be removed.
Source enclosures cannot be removed until migration is complete and finalized.
The storage migration duration depends on the system resources (which differ for different system
models), the availability of system resources, and the data quantity to migrate. Storage migration can
take days or weeks to complete.
Note: For storage migration, the DS60 shelf can be addressed as an entire unit when fully populated or
by each disk pack.
Be aware of the following considerations when working with the DS60 shelf:
CAUTION: Loading shelves at the top of the rack may cause the shelf to tip over.
CAUTION: Validate that the floor can support the total weight of the DS60 shelves.
CAUTION: Validate that the racks can provide enough power to the DS60 shelves.
Page 5 of 6
CAUTION: When adding more than five DS60s in the first rack, or more than six DS60s in the second
rack, stabilizer bars and a ladder are required to maintain the DS60 shelves.
1. [ ] Install the destination enclosures using the instructions in the product installation guides.
2. [ ] Select Administration > Licenses and verify that the storage migration license is installed.
3. [ ] If the storage migration license is not installed, click Add Licenses and add the license.
4. [ ] Select Hardware > Storage, then click Migrate Data.
5. [ ] In the Select a Task dialog, select Estimate, then click Next.
6. [ ] In the Select Existing Enclosures dialog, use the checkboxes to select each of the source
enclosures for the storage migration, then click Next.
7. [ ] In the Select New Enclosures dialog, use the checkboxes to select each of the destination
enclosures for the storage migration, then click Next.
The Add Licenses button allows you to add storage licenses for the new enclosures as needed,
without interrupting the current task.
8. [ ] In the Review Migration Plan dialog, review the estimated migration schedule, then click Next.
9. [ ] Review the precheck results in the Verify Migration Preconditions dialog, then click Close.
If any of the precheck tests fail, resolve the issue before you start the migration.
Note: The migration status shows the percentage of blocks transferred. In a system with many free
blocks, the free blocks are not migrated, but they are included in the progress indication. In this
situation, the progress indication will climb quickly and then slow when the data migration starts.
3. [ ] When a storage migration is in progress, you can also view the status by selecting Health >
Jobs.
Page 6 of 6