Restoring SAN File System metadata

This topic explains how to restore the metadata for the SAN File System cluster.

Steps

  1. Verify that all metadata servers in the cluster are online and that the cluster is running.
    sfscli lsserver -state online
  2. Copy the system-metadata disaster-recovery file (and the scripts) that you had previously backed up to /usr/tank/server/DR on the master metadata server.
  3. Use the TankSysCLI.auto script:
    1. Edit the script TankSysCLI.auto for information about how the script is used and any changes that might need to be made to the script.
      #########################################################################
      # CLI Commands to create Storage Pools, Filesets, Service Classes and 
      # Policy Sets.
      # These commands need NO manual intervention.
      #########################################################################
    2. Run the script TankSysCLI.auto.
      sfscli -script /usr/tank/server/DR/TankSysCLI.auto
    3. If any errors occur while running the script, ensure that you resolve those errors before continuing.
  4. Use the TankSysCLI.volume script:
    1. Edit /usr/tank/server/DR/TankSysCLI.volume and modify it to match your current SAN settings. It also contains usage information as well as information about any changes that might need to be made to the script.
      #########################################################################
      # CLI Commands to add Volumes to Storage pools.
      # These commands need manual intervention.
      # The device names were as they appeared during backup.
      # Please make sure that the device names appearing here actually
      # exist and have correct sizes and if not edit the device names to 
      # correct values.
      # The System MASTER volume has to be specified in tank install command  
      # and therefore has no corresponding CLI.
      # The other System Volumes can either be specified in tank install  
      # command, or, added using the CLI command, which appears inside comments
      # for this reason.
      #########################################################################
    2. Run the script TankSysCLI.volume.
      sfscli -script /usr/tank/server/DR/TankSysCLI.volume
    3. If any errors occur while running the script, ensure that you resolve those errors before continuing.
  5. Use the TankSysCLI.attachpoint script:
    1. Edit /usr/tank/server/DR/TankSysCLI.attachpoint to verify the settings. It also contains usage information as well as information about any changes that may need to be made to the script.
      #########################################################################
      # CLI Commands to attach filesets.
      # These commands need manual intervention.
      # All the "mkdir" and "attachfileset" commands should be run in the
      # order given.
      # The "mkdir" command should be run on a client to recreate the directory
      # path before running the following attachfileset CLI commands.
      #########################################################################
    2. If all filesets are attached only to the root directories of other filesets, run the script TankSysCLI.attachpoint.
      sfscli -script /usr/tank/server/DR/TankSysCLI.attachpoint
      Note: If you have any filesets attached to directories, you must reattach them manually.
    3. If any errors occur while running the script, ensure that you resolve those errors before continuing.
  6. Grant privileges to those clients that require root or Administrator access to SAN File System using the chclusterconfig –privclient command.

Parent topic: Managing disaster recovery

Related reference
chclusterconfig
lsserver

Library | Support | Terms of use | Feedback
(C) Copyright IBM Corporation 2003, 2004. All Rights Reserved.
IBM TotalStorage SAN File System v2.2