Preparing the destination storage system

When to use this section

Before moving (migrating) a vFiler unit or setting up a disaster-recovery vFiler unit, you must perform the checks, and the accompanying actions if necessary, listed in Storage checks and actions and Network checks and actions in this section.

Storage checks and actions

Photocopy the worksheet STORAGE CHECKLIST and fill it out as you perform the following steps.

Note
The storage checks are not necessary if you are going to use SnapMover vFiler unit migration to migrate the vFiler unit.

Step	Action
1	Check that the destination storage system has enough storage space to hold the source vFiler unit's volumes. On the source storage system, use the `vfiler status -r` command to see what volumes the vFiler unit is using. Then use the `df` command on each of those volumes to check how much space is being used. The destination volumes must have at least that much free space; run `df` on the destination storage system to check. Fill in the `df` results on the worksheet. Note If the source and destination storage systems use different-sized disks and have different block sizes, adjust the `df` numbers accordingly.
2	If...	Then...
	There is enough space on the destination volumes	Continue with Step 3.
	There is not enough space	a. If necessary, install new disk shelves. b. Use the `aggr add` command to add new disks to the destination volumes.
3	Make sure that the destination storage system has the same volume structure as the source and that the volumes to be used by the destination vFiler unit are not used by any other vFiler unit. The volumes to be used by the destination vFiler unit must have the same path names as those used by the source vFiler unit.
4	If...	Then...
	The destination storage system has volumes whose path names match those used by the source vFiler unit and the volumes to be used by the destination vFiler unit are not used by any other vFiler unit	Continue with Step 5.
	The destination storage system has a volume whose path name matches that of the source vFiler unit but the volume is used by another vFiler unit	Do one of the following: If the volume cannot be destroyed, use the `vol rename` command to rename the volume. Then, create a new volume with the old name of the volume you just renamed. If the volume can be removed, use the `vfiler remove` command to disassociate the volume from that vFiler unit. If the volume is the root volume of the vFiler unit, use the `vfiler destroy` command to destroy the vFiler unit.
	The destination storage system does not have matching volume path names	Use the `aggr create` command on the destination storage system to create volumes whose names match those being used by the source vFiler unit, or use `aggr rename` to rename a volume. For FlexVol volumes, use the `vol create` command. For more information, see the Data ONTAP Storage Management Guide.
5	Make sure there are no qtrees in the destination volumes whose names match those of qtrees in the source volumes. The migration process uses SnapMirror, which will replicate qtree names from the source to the destination volume, so these names should not already exist on the destination.
6	If...	Then...
	There are qtrees in the destination volumes whose names match those of qtrees in the source volumes	Rename the matching qtrees in the destination volumes. To rename a qtree, move it from a client as you would a directory or folder. For more information, see the Data ONTAP Storage Management Guide.
	There are no matching qtree names in the destination volumes	Continue with Step 7.
7	Check whether quotas are being enforced from the hosting storage system. Quotas enforced from the vFiler unit will be copied to the new vFiler unit, but quotas enforced from the hosting storage system will not. To see where quotas are being enforced from, use the hosting storage system to enter the following command: `quota report`
8	If...	Then...
	The output of the `quota report` command shows that quotas for qtrees used by the vFiler unit are being enforced from the hosting storage system	a. Print out a copy of the storage system's quota file: /vol/vol0/etc/quotas. b. Copy the relevant entries into the destination storage system's /vol/vol0/etc/quotas file.
	No quotas for qtrees used by the vFiler unit are being enforced from the hosting storage system	Continue with Step 9.
9	Continue with Network checks and actions.

Network checks and actions

Photocopy the worksheet NETWORK CHECKLIST and fill it out as you perform the following steps.

Step	Action
1	Check to see if the destination vFiler unit can take over the source vFiler unit's IP addresses. Use the command `ifconfig -a` on the source vFiler unit and on the destination storage system to display information about all their network interfaces. You can reuse the source IP addresses and aliases on the destination vFiler unit if the destination vFiler unit will be on the same subnet as the source vFiler unit.
2	If...	Then...
	The source and destination storage systems are on the same subnet Note This is the default case assumed by the `vfiler migrate` command.	Continue with Step 3.
	They are on different subnets	a. Obtain as many new IP addresses for the destination vFiler unit as are in use on the source vFiler unit. Note You might need to replicate subnet-separation arrangements that exist on the source vFiler unit. For example, the source vFiler unit might use one IP address for a service network and another for an administration network. b. Make a note of the new IP addresses on the worksheet. The `vfiler` `dr configure` command will prompt you for these addresses; see Creating the disaster-recovery vFiler unit. The `vfiler migrate` command will also prompt you for these addresses, but you might then need to run `setup` on the destination vFiler unit. See If you have moved the vFiler unit to a different subnet or Windows domain.
3	Check whether the source vFiler unit uses the default IPspace. Use the command `ipspace list` on the source vFiler unit to display information about IPspaces and the interfaces assigned to them. For more information about IPspaces, see Chapter 3, Using vFiler Units in Different IPspaces.
4	If...	Then...
	`ipspace list` reports `default-ipspace`	Continue with Step 5.
	`ipspace list` reports something other than `default-ipspace`	a. Use the command `ipspace create` ipspacename to create a corresponding IPspace with the same name on the destination storage system. b. Use the command `ipspace assign` ipspacename interfacename to assign physical interfaces to the IPspace. These interfaces must all be attached to the same physical network.
5	Check to see if the destination vFiler unit will have access to the same NIS servers as the source. Note You can skip this check if the source and destination vFiler units are on the same subnet. Use the command `nis info` on the source vFiler unit to see what NIS servers are available to it. (Tip: The `ypwhich` command shows which server the storage system is currently bound to.)
6	If...	Then...
	The destination vFiler unit can use the same NIS servers as the source vFiler unit Note This is the default case assumed by the `vfiler migrate` command.	Continue with Step 7.
	The destination vFiler unit cannot use same NIS servers	a. Find out which NIS servers are available to the destination storage system. b. Make a note of the IP addresses of those servers on the worksheet. The `vfiler` `dr configure` command will prompt you for these addresses; see Creating the disaster-recovery vFiler unit. The `vfiler migrate` command will not prompt you for these addresses. If you move a vFiler unit to a different subnet, you might need to run `setup` on the destination vFiler unit. See If you have moved the vFiler unit to a different subnet or Windows domain.
7	Check to see if the destination vFiler unit will have access to the same DNS servers as the source. Note You can skip this check if the source and destination vFiler units are on the same subnet. Use the command `dns info` on the source vFiler unit to see what DNS servers are available to it.
8	If...	Then...
	The destination vFiler unit can use the same DNS servers as the source vFiler unit Note This is the default case assumed by the `vfiler migrate` command.	Continue with Step 9.
	The destination vFiler unit cannot use the same DNS servers	a. Find out which DNS servers are available to the destination storage system. b. Make a note of the IP addresses of those servers on the worksheet. The `vfiler dr configure` command will prompt you for these addresses; see Creating the disaster-recovery vFiler unit. The `vfiler migrate` command will not prompt you for these addresses. If you move a vFiler unit to a different subnet, you might need to run `setup` on the destination vFiler unit. See If you have moved the vFiler unit to a different subnet or Windows domain.
9	Check to see if the destination vFiler unit will have access to the same WINS servers and the same Windows security network as the source.
10	If...	Then...
	The destination vFiler unit can use the same WINS servers and Windows security network as the source vFiler unit	Continue with Step 11.
	The destination vFiler unit cannot use the same WINS servers and Windows security network	a. Find out the name and type (Windows NT 4 or Windows 2000) of the domain the destination vFiler unit will be in. b. Make a note of this information on the worksheet. When you activate the disaster-recovery vFiler unit, you will need to configure it into the new domain. See Activating the disaster-recovery vFiler unit. If you move a vFiler unit into a different domain, you will need to configure it into the new domain. See If you have moved the vFiler unit to a different subnet or Windows domain.
11	Check to see if the destination vFiler unit can use the same trusted host for vFiler unit administration as the source vFiler unit.
12	If...	Then...
	The destination vFiler unit can use the same trusted host as the source vFiler unit	You are done.
	The destination vFiler unit cannot use the same trusted host	a. Find out the name of the new trusted host. b. Make a note of this information on the worksheet. You will need to configure the new trusted-host information after configuring the disaster-recovery vFiler unit, or after moving the vFiler unit. See Creating the disaster-recovery vFiler unit or If you have moved the vFiler unit to a different subnet or Windows domain.