Before migrating, you need to create a destination aggregate and volume of the correct size. Since the new FlexVol volume will be the root volume, it must meet the minimum size requirements for root volumes, which are based on your storage system. Data ONTAP prevents you from designating as root a volume that does not meet the minimum size requirement. The table below is for Data ONTAP 7.3.3.

Storage Model              Minimum Root FlexVol volume size

FAS2020                       10 GB
FAS2040                       16 GB
FAS3040                       16 GB
FAS3140                       16 GB
FAS3170                       37 GB

1)     Enter the following command to determine the amount of space your traditional volume uses:

> df -Ah vol0

Aggregate            total                  used                  avail                capacity

vol0                      192GB              6278MB            186GB              3%
vol0/.snapshot   48GB               2494MB            45GB                5%

The total space used by the traditional volume is displayed as “used” for the volume name.

2)     Create an aggregate to contain the new FlexVol volume. In filerView, click Aggregates | Add | aggr name=aggr0 | RID Group Size=16 | Disk Selection=Auto | Disk Type=Any Type | Disk Size=click the down arrow and select the smallest disks you have | Number of Disks=3 | Commit.

3)     Create the destination volume in the new aggregate you just created. In FilerView, click Volumes | Add | Volume Type Selection=Flexible | Volume Name=vol00 | Containing Aggregate=aggr0 | Volume Size Type=Total Size, Volume Size=200 Gigs, Snapshot Reserve=20 | Commit.


4)     Due to a rare occurrence where the kernel is cleared from your flash rendering the system unbootable after an ndmpcopy, copy the same ONTAP version you are now running into /etc/software on the filer before you start.

  1. If the /etc/software folder is not present simply run the “software list” command on the filer to create it.
  2. For example, on a 3140, make sure you have 733P5_setup_q.exe in /etc/software on the filer before you start. If the system won’t boot after the ndmpcopy with a “kernel not found” or similar error, netboot the filer and run software update 733P5_setup_q.exe to reinstall your OS. See the System Administration Guide for your ONTAP version for steps on how to create a netboot filer.
  3. Collect the IP information on your filer in case you need to netboot.

> ifconfig -a (get the IP and interface name)

> rdfile /etc/rc (get the mask and default route)

> dns info (get the DNS server’s IP and domain)

Attention: Make sure that you use the storage system command-line interface from a serial connection to run the ndmpcopy command. If you run this command from a client like Putty, your data may not migrate successfully. For more information about the ndmpcopy command, see the Data ONTAP Data Protection Online Backup and Recovery Guide.

Migrate the Volume

1)     You will use the ndmpcopy command to migrate your data to the target volume. Ensure that NDMP is configured correctly by entering the following commands:

> options ndmpd.enable on

> options ndmpd.authtype challenge

2)     Migrate the data by entering the following command at the storage system prompt:

> ndmpcopy /vol/vol0 /vol/vol00

3)     Verify copy. Look for something similar to:

ndmpcopy: filername: Log: Dump: Dump is Done

ndmpcopy: filername: Log: RESTORE: RESTORE is Done

ndmpcopy: filername: Log: RESTORE: The destination path is /vol/vol00

ndmpcopy: filername: Log: Notify: restore successful

ndmpcopy: filername: Log: Notify: dump successful

ndmpcopy: transfer successful

ndmpcopy: done

Completing the Migration

1)     After you copy your data, you need to perform some additional tasks before the migration is complete. Make the new FlexVol volume the root volume by entering the following command:

> vol options vol00 root

> reboot

Note: if the filer won’t boot with a kernel missing error and dumps to the CFE> or LOADER> prompt, netboot the filer and reinstall the OS. The following steps are based on a FAS3140.

> ifconfig e0a -addr=<filer IP> -mask=<filer mask> -gw=<filer gateway> -dns=<filer DNS server IP>

Ping your gateway and netboot filer to make sure you are up. Some switches take 30 seconds to one minute to fully establish the link. Pause for a moment if the ping fails and verify your net mask.

> netboot http://<IP of netboot filer>/path_to_kernel/netapp_7.3.3P5-x86-64

The system will boot to the 1-5 menu. Select option 1 for a normal boot. When the filer is up, login as an administrative user.

> software list

> software update 733P5_setup_q.exe

The install will complete and the filer will reboot. You should now have a properly seated kernel. To verify enter:

> version -b

The first line should read: 1:/x86_64/kernel/primary.krn: 7.3.3P5

2)     Rename and offline the existing traditional vol0 to prevent hairballs.

> vol rename vol0 vol0trad

> vol offline vol0trad

Note: you can destroy vol0trad later when you’re confident everything is stable.

3)     Rename the new Flexvol vol00 to vol0 and reboot.

> vol rename vol00 vol0

> vol options vol0 root

> reboot

4)     Verify that the new vol0 is the root vol.

> vol status vol0

Look under Options for root:

Volume       State    Status               Options

vol0            online   raid_dp, flex      root   (and whatever other default options you have)

5)     Fix FilerView.  This is a bug. See https://kb.netapp.com/support/index?page=content&id=2010752

> secureadmin disable ssl

           > secureadmin setup ssl  (answer the questions for your environment)

> secureadmin enable ssl

Launch FilerView and you should be able to login and render each page.