Transferring the master role to the upgraded metadata server

This topic describes how to transfer the master role to the upgraded metadata server engine.

Context

If this metadata server is the first metadata server to be upgraded, you will need to make it the new master metadata server.
Note: Transferring the master role to the upgraded metadata server requires that you shut down the current master and then make this metadata server the new master. During this procedure, the SAN File System will be unavailable to all clients.

Steps

  1. Optionally, move the current master’s workload to one of the subordinate nodes. By moving the workload, the filesets being managed by the current master will be unavailable only while you are transferring the master role. Otherwise, the filesets will be unavailable until you have upgraded the current master.
  2. From the master metadata server, take the current master offline.
    /usr/tank/admin/bin/tanktool stopserver master_mds_name
  3. Verify that the current master is offline
    /usr/tank/admin/bin/tanktool lsserver
    The status of the current master should be listed as Not Running.
    /usr/tank/admin/bin/tanktool lsserver
    Name      State       Server Role Filesets Last Boot
    ==================================================================
    evt5-mds1 Not Running Master      -        -
    evt5-mds2 Joining     Subordinate        0 Feb 27, 2004 5:18:27 AM
  4. From the upgraded metadata server, verify the cluster status.
    /usr/tank/admin/bin/sfscli lsserver
    Because you are running the lsserver command from a subordinate, you will only see the status of the upgraded metadata server.
    evt5-mds2:/usr/tank/admin/bin/sfscli lsserver
    Name      State   Server Role Filesets Last Boot
    ==============================================================
    evt5-mds2 Joining Subordinate        0 Feb 27, 2004 5:18:27 AM
  5. Make the upgraded metadata server the new master
    /usr/tank/admin/bin/sfscli setmaster upgraded_mds_name
  6. From the new master metadata server, verify that the cluster has been reformed properly.
    /usr/tank/admin/bin/sfscli lsserver 
    The upgraded metadata server should now be listed as the master. All other metadata servers should be listed as subordinates with a status of active.
    Note: The former master metadata server will still show a status of Not Running.
    Name      State       Server Role Filesets Last Boot
    ==================================================================
    evt5-mds2 Online      Master             2 Feb 16, 2004 6:15:39 AM
    evt5-mds1 Not Running Subordinate -        -
  7. Verify the software version and committed software version of the cluster:
    /usr/tank/admin/bin/sfscli statcluster 
    The software version should be at version 2.1 (such as 2.1.0.65), but the committed software version should still be at version 1.1 (such as 1.1.2.8).
    Name                       sanfs
    ID                         21443
    State                      Online
    Target State               Online
    Last State Change          Feb 16, 2004 6:15:47 AM
    Last Target State Change   -
    Servers                    2
    Active Servers             1
    Software Version           2.1.0.65
    Committed Software Version 1.1.2.8
    Last Software Commit   Feb 13, 2004 2:46:27 PM
    Software Commit Status     Not In Progress
    Installation Date          Feb 13, 2004 2:46:27 PM

Result

The SAN File System is now back online and fully operational (with the exception of any filesets that are still being managed by the former master metadata server). At this point, the SAN File System cluster is running in version 1-compatibility mode. This means that SAN File System clients and metadata servers that have not been upgraded will still continue to operate. However, they will not take advantage of any version 2.1 functionality.
Note: On metadata servers that have been upgraded to version 2.1, you will need to use the version 2.1 syntax for all administrative commands. On metadata servers that have not been upgraded, you will need to use version 1 syntax for all administrative commands.

Parent topic: Setting the upgraded server as the new master

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