Advertisement
Quick Links
™
BeyondRAID
technology in Drobo enables users to quickly migrate the set of disks (referred to as a "disk pack") in
one Drobo to a Drobo of the same model. Also, in certain cases, disk pack migration is supported from a smaller or
older Drobo to a larger or newer model.
Disk pack migration may be required when you need to replace a system or when you want to upgrade from an older
model such as DroboElite to a newer Drobo model B800i. This document uses the example of migrating a disk pack
from DroboElite to Drobo B800i, though these steps can be used to migrate a disk pack for B1200i.
The first section is universal to disk pack migration for supported paths. A list of supported paths can be found @
http://www.drobo.com/migration. If the Drobo is an iSCSI SAN model being used for VMware primary storage, then
additional steps are required, as detailed in the other sections in this document. These steps apply to any SAN
storage where a controller is changed, though Drobo does make it easier than most storage devices to get updated
and return to normal use.
Note: In most cases migrating drives is a one-way operation for supported migrations from one Drobo model to
another. Once a disk pack is migrated, you will no longer be able to access the data it contained with the older Drobo.
Topics
What will you need
Preparing for migration and moving the disk pack
Preparing to resignature volumes
Mounting VMFS datastores after migration
Connecting VMs to their disks
What You Will Need
•
Source Drobo system and the new target system
The most recent firmware installed on both Drobo devices
•
•
The latest version Drobo Dashboard management software, minimum version 2.0 or higher
To download the latest version of firmware and Drobo Dashboard for your device, visit
http://www.drobo.com/support/updates.php.
Migrating a Disk Pack Between Drobo iSCSI SAN Systems
drobo.com | Migrating a Disk Pack between Drobo iSCSI SAN systems
Drobo How-To Guide
1
Advertisement
Related Manuals for Drobo Elite
Summary of Contents for Drobo Elite
- Page 1 Note: In most cases migrating drives is a one-way operation for supported migrations from one Drobo model to another. Once a disk pack is migrated, you will no longer be able to access the data it contained with the older Drobo.
- Page 2 Drobo. Since Drobo is slot independent, you don’t need to keep track of which drives came out of which slots when you re-insert them into the destination Drobo. drobo.com | Migrating a Disk Pack between Drobo iSCSI SAN systems...
- Page 3 The IP address and other device settings such as the name are retained within the disk pack, so the destination system will appear with the same name and IP address as it had in the source Drobo Insert the disks from source Drobo into the new Drobo in any order.
- Page 4 VMFS volume is a user-defined device name that is a symbolic link to the UUID of the VMFS volume (done to solve the problem of changing the device name). When you change the volume name you are changing only the user- defined device name and not the volume UUID. drobo.com | Migrating a Disk Pack between Drobo iSCSI SAN systems...
- Page 5 The APD state is a condition in which no working path exists to a storage device (LUN). In this case, it is a result of migrating the disk pack from DroboElite to Drobo B800i. Reboot the ESX/ESXi host, ensuring that no VM is active before rebooting.
- Page 6 Mounting VMFS Datastores after Migration As part of the disk pack migration process, LUNs from the Drobo will appear to VMware as snapshots. VMFS datastores on your existing volumes detected by VMware as snapshot LUNs can be mounted using one of the following options: •...
- Page 7 1.866.97.DROBO Copyright 2012 Drobo, Inc. Data Robotics, Drobo, DroboEllite, DroboPro, BeyondRAID, and Smart Volumes are trademarks of Drobo, Inc., which may be registered in some jurisdictions. All other trademarks used are owned by their respective owners. Ÿ Ÿ All rights reserved. Specifications subject to change without notice.