Reactivating the original vFiler

Boot the original filer and interrupt the boot process by pressing the Del or Esc key while the memory self-test is in progress.

Note
If you don't press the Del or Esc key in time, you can press Ctrl-C when prompted later during the boot; then choose option 5 (maintenance mode); then enter halt.

At the OK prompt, set the no-vfiler-ips? variable as follows:

setenv no-vfiler-ips? true

This ensures that the filer does not try to bind IP addresses already being used by the disaster-recovery vFiler. When the filer boots, the original vFiler starts running, but it does not accept any read or write requests because its interfaces are unconfigured.

Resynchronize the mirrored volumes and qtrees.

For each volume and qtree owned by the original vFiler, enter the following command on the original filer:

snapmirror resync -S disaster_recovery_filer:/pathname 
production_filer:/pathname

Example

snapmirror resync -S drfiler:/vol/vfiler1/qtree1 prfiler:/vol/vfiler1/qtree

Troubleshooting

If the snapmirror resync command fails, telling you that there are no matching snapshots, you have probably accidentally deleted the snapshots that SnapMirror depends on. In this case you need to initialize SnapMirror using the snapmirror initialize command (see the na_snapmirror man page for details). Then continue with the next step of this procedure, but skip Step 7 when you get there.

Find out if the snapmirror.access option on the disaster-recovery filer is set to legacy. Enter the following command on the disaster-recovery filer:

options snapmirror 

If...

Then...

The options snapmirror command returns snapmirror.access legacy

Edit the file /etc/snapmirror.allow and add the host name of the original filer if it is not already there.

The options snapmirror command returns a list of host names, and the name of the original filer is not in the list

Use the options snapmirror command to add the host name of the original filer.

Example

options snapmirror.access host=fridge,toaster,prfiler

Run setup on the disaster-recovery vFiler and unconfigure its IP addresses.

Update the data on the original vFiler.

For each volume and qtree owned by the original vFiler, enter the following command on the original filer:

snapmirror update -S disaster_recovery_filer:/pathname 
production_filer:/pathname

Example

snapmirror update -S drfiler:/vol/vfiler1/qtree1 prfiler:/vol/vfiler1/qtree1

Stop SnapMirror transfers to the disaster-recovery vFiler.

For each volume and qtree owned by the original vFiler, enter the following command on the original filer:

snapmirror quiesce pathname 

Example

snapmirror quiesce /vol/vfiler1/qtree1

Note
This operation can take a long time. Use Ctrl-C to interrupt it if you need to.

Check that all the paths are quiesced:

snapmirror status

The status column in the output should show each path as Quiesced.

Break the SnapMirror relationship.

For each volume and qtree owned by the original vFiler, enter the following command on the original filer:

snapmirror break pathname 

Example

snapmirror break /vol/vfiler1/qtree1

On the original vFiler, run setup to configure the vFiler's IP addresses and configure the NIS and DNS servers.

If the storage units that have been copied contain iSCSI LUNs, check that the iSCSI configuration on the original vFiler is intact and still makes sense.

You might need to remap the LUNs and re-create initiator groups (igroups).

If the storage units that have been copied contain iSCSI LUNs, bring the LUNs back online on the original vFiler.

Destroy the disaster-recovery vFiler. On the disaster-recovery filer, enter the following command:

vfiler destroy vfilername

vfilername is the name of the disaster-recovery vFiler.

Recreate the disaster-recovery vFiler.

From the disaster-recovery filer, perform the procedure Creating the disaster-recovery vFiler.

Boot the original filer and interrupt the boot process by pressing the Del or Esc key while the memory self-test is in progress.

Note
If you don't press the Del or Esc key in time, you can press Ctrl-C when prompted later during the boot; then choose option 5 (maintenance mode); then enter halt.

At the OK prompt, set the no-vfiler-ips? variable as follows:

setenv no-vfiler-ips? true

This ensures that the filer does not try to bind IP addresses already being used by the disaster-recovery vFiler.

At the OK prompt, enter boot.

Destroy the original vFiler. Enter the following command on the original filer:

vfiler destroy vfilername

vfilername is the name of the original vFiler.

Follow the procedure for Creating a replacement vFiler on the original filer or its replacement.

Boot the replacement filer.

Follow the procedure for Creating a replacement vFiler on the original filer or its replacement.

Step

Action

Prepare the new vFiler:

Perform the preparation steps under Preparing the destination filer.

Note
Remember that you are performing these checks to inventory the resources of the original filer or its replacement.

Create the new vFiler, following directions under Creating the vFiler.

Note
Perform those steps on the original filer or its replacement.

After performing those steps, you have a production vFiler and a backup vFiler, as you did before the disaster, but their roles are reversed: the vFiler you have just created is now the backup, and what was originally the disaster-recovery vFiler is still managing the live data. This might or might not suit your needs.

• If you want to put things back the way they were before the disaster, continue with the next step.
• If you don't care about the roles of the two vFilers, you are done.

Run setup on the disaster-recovery vFiler and unconfigure its IP addresses.

Update the data on the new vFiler.

For each volume and qtree owned by the new vFiler, enter the following command on the original filer or its replacement:

snapmirror update -S disaster_recovery_filer:/pathname 
production_filer:/pathname

Example

snapmirror update -S drfiler:/vol/vfiler1/qtree1 prfiler:/vol/vfiler1/qtree1

Step

Action

Activate the new vFiler, following directions under Activating the disaster-recovery vFiler.

Note
Perform these steps on the original filer or its replacement.

Destroy the disaster-recovery vFiler by entering the following command on the disaster-recovery hosting filer:

vfiler destroy vfilername

vfilername is the name of the original vFiler

Recreate the disaster-recovery vFiler.

From the original filer or its replacement, perform the procedure Creating the disaster-recovery vFiler.