Creating the disaster-recovery vFiler

Before you start

Before you begin creating the disaster-recovery vFiler, make sure the following are true:

You have performed all the preparation steps listed under Storage checks and actions and Network checks and actions.
SnapMirror is licensed and enabled on both the source and the destination filer.
The source and destination filers can communicate with each other over the network (for example, by means of DNS lookup or entries in /etc/hosts).
The source filer can communicate with the destination filer via the rsh command.
If any of the source qtrees or volumes contain LUNs (virtual disks), the destination filer is running a version of Data ONTAP that supports LUNs.
- If the source vFiler owns iSCSI LUNs, the destination vFiler must be running a version of Data ONTAP that supports iSCSI LUNs on vFilers.
The destination volumes are online.
You know the source filer's administrative ID and password.

Creating the vFiler

To create the disaster-recovery vFiler, perform the following steps.

Step	Action
1	On the destination filer, enter the command `vfiler dr configure` source_vfiler@source_filer
2	Respond to the login prompt with a valid administrative ID and password for the source filer.
3	Respond to the IP address and binding prompts, using the addresses you entered on the "new interface" lines on the worksheet.
4	Respond to the NIS and DNS server prompts, using the addresses you entered under "New NIS addr" and "New DNS addr" on the worksheet.
5	Monitor progress by means of the following command: `vfiler dr status` source_vfiler@source_filer Note The `vfiler dr configure` command might take some time to complete, especially if a source qtree has many millions of inodes. When the `vfiler dr` `status` command reports all the storage units of the source vFiler as `snapmirrored`, proceed to the next step. Note The disaster-recovery vFiler now exists, but has not been started. See What the vFiler dr configure command does for more information.
6	If you copied quota information into the destination filer's /etc/quotas (see Step 8 of Preparing the destination filer earlier in this chapter) activate the quotas on that filer. For each volume you are activating quotas on, use the following command: `quota on volume`
7	Edit the disaster-recovery vFiler's /etc/hosts.equiv file, adding the name of the trusted host for administering the disaster-recovery vFiler. (This is the host name you entered on the worksheet as "new trusted host.") Note If the trusted host is a Windows system, or if it is a UNIX system and the trusted user is not the root user, you need to add the user name as well; for example, `adminhost joe_smith`
8	Add the path to the root volume and the name of the trusted host to the disaster-recover vFiler's /etc/exports file. Example /`vol/vol0 access=adminhost, root=adminhost`
9	If the vFiler's storage units contain iSCSI LUNS, reconfigure iSCSI authentication. See the Block Access Management Guide for iSCSI for instructions.

What the vFiler dr configure command does

The vfiler dr configure command does the following:

Checks that the destination filer is capable of receiving the source data.
Configures and runs SnapMirror to copy the data from the source to the destination vFiler.
- iSCSI LUNs (including the LUN maps) are copied from the source vFiler to the destination vFiler.
- Initiator groups (igroups) and the iSCSI configuration, including node names and the iSCSI service state, are also copied to the destination vFiler.
- iSCSI authentication is not copied to the destination vFiler.
Saves the IP configuration information you supply (see Step 3 under Creating the vFiler).
Saves the NIS and DNS server information you supply (see Step 4 under Creating the vFiler).
Saves the quota information from the source vFiler's /etc/quotas file.
Creates a special type of vFiler, known as a DR backup vFiler, on the destination filer.
This vFiler is stopped and cannot be started except as described under Activating the disaster-recovery vFiler. Before activation, the vFiler will respond only to the vfiler status, vfiler dr delete, and vfiler dr configure commands. You cannot use ifconfig to configure its addresses.

Creating the disaster-recovery vFiler

Before you start

Creating the vFiler

Example

What the vFiler dr configure command does