Reassign filesets to another metadata server in the cluster

This topic describes how to reassign filesets to another metadata server in the SAN File System cluster.

Context

Any filesets managed by this metadata server engine will be unavailable to clients while the engine is being upgraded. If it is important to maintain the availability of the filesets during the upgrade process, you will need to reassign the filesets to another metadata server in the cluster.
Note: Before reassigning filesets, you should close down any client applications that use those filesets until after the reassignment is complete.

Steps

  1. From the master metadata server, list all of the filesets assigned to the metadata server to be upgraded.
    /usr/tank/admin/bin/tanktool lscontainer -server metadata_server_name
  2. Assign the filesets to different metadata server.
    /usr/tank/admin/bin/tanktool setcontainerserver -server new_metadata_server_name 
    fileset1 fileset2 fileset3

Result

There are two phases of the cluster transition when moving a fileset. The end of the first phase shows the server online, but some administrative commands will not function until the second phase completes. The second phase finishes when the new filesets are assigned and running. This normally takes less than one minute.

Parent topic: Preparing the first engine for upgrade

Terms of use | Feedback
(C) Copyright IBM Corporation 2003, 2004. All Rights Reserved.