Tuesday, October 7, 2014

NetApp: LUN Migration - 7-Mode to C-Mode/C-DOT

CDOT/C-Mode LUN/block FC/FCoE/iSCSI storage migration

NetApp made a huge improvement in their software moving to C-Mode, however they did not make the process to move block storage LUNs easy.  Of course, they would like you to buy their DTA2800 appliance, which is licensed per TB migrated, and/or use their professional services.

Like most of us, we more than a couple TB to move, and I don't feel I should have to pay for the migration since I bought both systems in the first place.  The good news is you don't have to....if you can deal with a little downtime.

The solution is to use the NetApp Workflow Automation tool or "WFA".  You can do offline and online block LUN replication, and with the online mode - the cutover period can be very short.

Unfortunately, the pieces needed to easily complete this task are not readily compiled and comprehensively documented.

So far, the best document is NetApp TR 4314 which is not publicly accessible - except from this scribd post.  I will not post the actual PDF - but if you have access to the NetApp field portal - you can get EVERYTHING you need to complete the migrations.

Resources:

Instructions:
  1. Install OnCommand Workflow Automater
  2. Acquire all the items listed above
  3. Follow the instructions in TR 4314 to set up WFA
  4. Build a test LUN on your 7-Mode System
  5. Wait a minute for OCUM to update, and...
Recommendations/Notes:
  • Make sure the administrative interfaces, intercluster interfaces, and replication IPs are all on 10-gigabit networks so the network is not your bottleneck in the migration process.
  • If you have a spare NetApp, use this system as a staging system between the source and destination systems.  I happened to have a spare system with a couple hundred 15k drives and multiple 10GbE interfaces which worked great as an intermediary.
  • There are a bunch of workflows, but don't be overwhelmed.  You really only need one for the initial setup, and three for most migrations.
Steps to Migrate:

Set up the igroups.  You should only need to run this once per source controller/HA pair if your igroups were set up correctly to begin with.
  1. Run the "7toC LUN Migrate igroups" workflow
  2. Select the source array
  3. Select the target cluster
  4. Select the target SVM
  5. Click Execute
  6. Wait for the workflow to execute, make sure it completes successfully
  7. Check the CDOT system
Pre-Migration - "Baseline"
  1. Run the "7toC LUN Migrate Job Baseline" workflow
  2. Select the source system (your 7-Mode controller)
  3. Select the volume, when selecting you can see how many LUNs are on that volume.
  4. Select the replication IP - this IP needs to be on the same VLAN or routeable to the staging and target systems.  Hopefully it's a 10GbE interface as well.
  5. If there is more than one LUN per volume, you can use a regex to describe the LUN(s) you wish to migrate.  If you want to do one LUN at a time (I recommend this) just put the LUN name in the "LUN Pattern" field.
  6. Select the staging system, replication IP, vfiler and NFS access IP.
  7. Select the target cluster, SVM, aggregate
  8. Enter the volume name...I like to name my block volumes LUNNAME_vol but your mileage may vary
  9. Click Execute
  10. Wait a while - if you can, keep the workflow execution status window up so you can familiarize yourself with the process
  11. Hopefully it completes successfully.  If not look at what step of the workflow failed and troubleshoot it
Migration - "Cutover"

IMPORTANT: Leave all the checkboxes at default unless you are going to read the documentation and see what they all do.
  1. Run the "7toC LUN Migrate Job Update + Cutover - Rapid" workflow
  2. Leave the offline source LUNs box checked
  3. Select the target cluster
  4. Select the target SVM
  5. Select the volume - in the dropbox, it will show you the status of the volume - it should be in the state"baselined"
  6. Leave the remap LUNs box checked
  7. Shut down the source system (if this is a boot LUN) or stop all applications using the LUN(s)
  8. Unmount the disks in the source OS
  9. Click the "Execute" button
  10. The workflow will typically take about five minutes to execute on a fast system - unless there is a substantial amount of change since the initial baseline.
  11. If the LUN migrated was a boot LUN, make sure to update the boot targets in the BIOS (or boot policy in UCS)
  12. If the LUN migrated was a data/application LUN, mount the LUN in the OS and test the application
Post-Migration - "Cleanup"

IMPORTANT: Leave all the checkboxes at default unless you are going to read the documentation and see what they all do.
  1. Run the "7toC LUN Migrate Job Cleanup" workflow
  2. Select the target cluster
  3. Select the target SVM
  4. Select the target volume - the state should be "cutover"
  5. Click Execute
Manual Post-Migration Steps

The original 7-mode LUN should be offline, and the LUN and volume will be intact.  Once you are satisfied with the migration, you may remove the source data.
  1. Delete the source LUN
  2. Offline the source LUN volume/container (make sure it's the only LUN in the volume)
  3. Delete the source LUN container
By at
Labels: , ,

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Featured Post

Remove 3D Objects and other annoying folders on Windows 10

 Microsoft just keeps adding more crap to clutter up the navigation in Windows 10.  Seriously, who needs a 3D Objects folder?  The tiny perc...