Table of ContentsView in Frames

Reactivating the original vFiler unit by using SnapMirror commands

If the storage system is not physically damaged but has failed temporarily and if the storage element associated with the vFiler unit is a qtree, you can reactivate the vFiler unit by using SnapMirror commands. When you reactivate, the disaster recovery configuration is re-created.

Steps

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

    Note: If you do not press the Del or Esc key in time, you can press Ctrl-C when prompted later during the boot, select option 5 (maintenance mode), and enter the halt command.

  2. At the loader prompt, set the no-vfiler-ips? parameter as follows:
    setenv no-vfiler-ips? true

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

  3. Verify that the snapmirror.access option on the disaster recovery storage system is set to legacy by entering the following command on the disaster recovery storage system:
    options snapmirror
  4. Depending on the result of the options snapmirror command, perform the appropriate action:
    If the options snapmirror command returns... Then...
    snapmirror.access legacy
    Add the host name of the original storage system to the/etc/snapmirror.allow file.
    A list of host names that does not contain the name of the original storage system Use the options snapmirror command to add the host name of the original storage system. For example:
    options snapmirror.access host=f3070-216-45,f6070-214-72
  5. Resynchronize each volume and qtree owned by the original vFiler unit by entering the following command on the original storage system that you are trying to activate:
    snapmirror resync -S disaster_recovery_filer:/pathname original_filer:/pathname

    Example

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

    If the snapmirror resync command fails with a message that there are no matching Snapshot copies, you might have accidentally deleted the Snapshot copies that SnapMirror depends on. You must then initialize SnapMirror relationship between the original storage system and destination storage system by using the snapmirror initialize command.

    For more information about the snapmirror initialize command, see the na_snapmirror(1) man page.

  6. Stop the disaster recovery vFiler unit by entering the following command on the disaster recovery storage system:
    vfiler stop vfilername

    vfilername is the name of the disaster recovery vFiler unit.

  7. Run the setup command on the disaster recovery vFiler unit and unconfigure its IP addresses by following prompts of the wizard.
  8. Update the data on the original vFiler unit by entering the following command on the original storage system:
    snapmirror update -S disaster_recovery_filer:/pathname original_filer:/pathname

    Example

    snapmirror update -S drfiler:/vol/vfiler1/qtree1 prfiler:/vol/vfiler1/qtree1
    Note: You do not have to update the data on the original vFiler unit by using the snapmirror update command, if you have resynchronized each volume and qtree owned by the original vFiler unit.

  9. Stop SnapMirror copy transfers to the disaster recovery vFiler unit.

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

    snapmirror quiesce pathname

    Example

    snapmirror quiesce /vol/vfiler1/qtree1

    Note: This operation can take a long time. Use Ctrl-C to interrupt it, if required.

  10. Verify that all the paths are quiesced by entering the following command:
    snapmirror status

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

  11. Break the SnapMirror relationship.

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

    snapmirror break pathname

    Example

    snapmirror break /vol/vfiler1/qtree1

  12. Start the original vFiler unit by entering the following command:
    vfiler start vfilername

    vfilername is the name of the original vFiler unit.

  13. Run the setup command on the original vFiler to configure the vFiler unit’s IP addresses and the NIS and DNS servers.

    You have completed reactivating the original storage system.

  14. If the storage units that have been copied contain iSCSI LUNs, check that the iSCSI configuration on the original vFiler unit is not affected.

    You might have to remap the LUNs and re-create the initiator groups (igroups) if you have created new LUNs on the destination vFiler unit.

  15. If the storage units that are copied contain iSCSI LUNs, bring the LUNs back online on the original vFiler unit.
  16. From the disaster recovery storage system, resynchronize the original vFiler unit and the disaster recovery vFiler unit.