Search <book_title>...

InfoScale™ 9.0 Storage Foundation and High Availability Configuration and Upgrade Guide - Linux

Last Published: 2025-04-21

Product(s): InfoScale & Storage Foundation (9.0)

Platform: Linux

Section I. Introduction to SFHA
1. Introducing Storage Foundation and High Availability
Section II. Configuration of SFHA
Section III. Upgrade of SFHA
Section IV. Post-installation tasks
1. Performing post-installation tasks
  1. Switching on Quotas
  2. About configuring authentication for SFDB tools
    1. Configuring vxdbd for SFDB tools authentication
Section V. Adding and removing nodes
1. Adding a node to SFHA clusters
2. Removing a node from SFHA clusters
  1. Removing a node from a SFHA cluster
Section VI. Configuration and upgrade reference

Deleting the departing node from SFHA configuration

Before you remove a node from the cluster you need to identify the service groups that run on the node.

You then need to perform the following actions:

Remove the service groups that other service groups depend on, or
Switch the service groups to another node that other service groups depend on.

To remove or switch service groups from the departing node

Switch failover service groups from the departing node. You can switch grp3 from node sys5 to node sys2.
```
# hagrp -switch grp3 -to sys2
```
Check for any dependencies involving any service groups that run on the departing node; for example, grp4 runs only on the departing node.
```
# hagrp -dep
```
If the service group on the departing node requires other service groups - if it is a parent to service groups on other nodes - unlink the service groups.
```
# haconf -makerw
# hagrp -unlink grp4 grp1
```
These commands enable you to edit the configuration and to remove the requirement grp4 has for grp1.
Stop SFHA on the departing node:
```
# hastop -sys sys5
```

Check the status again. The state of the departing node should be EXITED. Make sure that any service group that you want to fail over is online on other nodes.

# hastatus -summary
  
    -- SYSTEM STATE
    -- System      State          Frozen
    A  sys1    RUNNING        0
    A  sys2      RUNNING        0
    A  sys5      EXITED         0

    -- GROUP STATE
    -- Group    System      Probed   AutoDisabled   State
    B  grp1     sys1      Y        N              ONLINE
    B  grp1     sys2      Y        N              OFFLINE
    B  grp2     sys1      Y        N              ONLINE
    B  grp3     sys2      Y        N              ONLINE
    B  grp3     sys5    Y        Y              OFFLINE
    B  grp4     sys5    Y        N              OFFLINE

Delete the departing node from the SystemList of service groups grp3 and grp4.
```
# haconf -makerw
# hagrp -modify grp3 SystemList -delete sys5
# hagrp -modify grp4 SystemList -delete sys5
```
Note:
If sys5 was in the autostart list, then you need to manually add another system in the autostart list so that after reboot, the group comes online automatically.

For the service groups that run only on the departing node, delete the resources from the group before you delete the group.

# hagrp -resources grp4
    processx_grp4
    processy_grp4
# hares -delete processx_grp4
# hares -delete processy_grp4

Delete the service group that is configured to run on the departing node.
```
# hagrp -delete grp4
```

Check the status.

# hastatus -summary
    -- SYSTEM STATE
    -- System      State          Frozen
    A  sys1      RUNNING        0
    A  sys2      RUNNING        0
    A  sys5    EXITED         0

    -- GROUP STATE
    -- Group    System      Probed   AutoDisabled   State
    B  grp1     sys1      Y        N              ONLINE
    B  grp1     sys2      Y        N              OFFLINE
    B  grp2     sys1      Y        N              ONLINE
    B  grp3     sys2      Y        N              ONLINE

Delete the node from the cluster.
```
# hasys -delete sys5
```
Save the configuration, making it read only.
```
# haconf -dump -makero
```