Hitachi

uCosminexus Application Server Operation, Monitoring, and Linkage Guide


17.10.5 Starting and stopping the 1-to-1 node switching system of the Management Server for maintenance

This subsection describes how to start and stop the 1-to-1 node switching system of the Management Server for maintenance in order to change the Management Server settings.

Note that this is a procedure for the case in which the Management Server is already running in the executing node host.

  1. Execute the mstrexport command in the executing node host (active node host).

    # mstrexport mstruct.zip

    The Management Server settings of the active node host are automatically collected and the collected information is saved in a ZIP file.

    In the underlined part, specify the path of the ZIP file that saves the automatically collected settings.

  2. Copy the ZIP file saved in step 1 from the executing node to the standby node.

  3. Execute the mstrimport command in the standby node host (spare node host).

    # mstrimport mstruct.zip

    In the underlined part, specify the path of the ZIP file copied in step 2.

    As a result, the Management Server settings copied in step 2. are deployed in the standby node host and the Management Server of the executing node and the standby node have the same settings.

  4. Execute the monswap command in the executing node host to switch the nodes.

    # monswap server-identification-name

    In the underlined part, specify the server identification name specified in the operand 'alias' of the servers file.

    The Management Server of the executing node host stops, and then the Management Server starts through the node that was in standby status until now. The executing node settings are applied in the system when the Management Server starts.

  5. As and when required, check the operations related to the changes in definitions in the executing node host (spare node host) after the nodes are switched.

  6. As and when required, re-execute the monswap command in the executing node host (spare node host) after the nodes are switched.

    Execute the command to return the active node host to the executing node.

  7. As and when required, check the operations related to the changes in definitions in the executing node host (active node host) after the nodes are switched.

    Therefore, the procedure for starting and stopping the system for maintenance is complete.

Reference note

For details on the servers file definition (server environment settings in the HA monitor), see 17.7.7 Server-compliant environment settings.