Step 5: After the StorNext GUI Upgrade: Server Failover (optional)

This applies to dual-server configurations (not single-server) Xcellis Workflow Director, Xcellis Foundation, aiWARE for Xcellis Embedded, and Artico (R630) systemsand Artico (R520), Pro Foundation, M660, M440, and M330 systems.

Note: This applies to dual-server (HA) systems only.

Use this procedure to perform a fail-over of server operations from a server node operating as primary to a server node operating as secondary without losing client access to metadata. This can also be used to reverse which server is primary and secondary, if the system previously failed over.

Caution: StorNext Connect is intended to run on server node 2. If you perform a fail-over on node 1, StorNext Connect will cease to operate unless you enable Connect to run concurrently with StorNext on node 2. (See the StorNext Connect Documentation Center for this procedure: www.quantum.com/sncdocs)

Caution: For systems running NAS with NFS-HA enabled, DO NOT stop cvfs on the system before first stopping NAS. Learn more about this issue before you continue with this procedure.

Access the command line of the node currently operating as primary, and initiate the graceful fail-over to the server node currently acting as secondary:

  1. Open an SSH connection to the appropriate server and use the IP address assigned to the node on the Management or LAN Client network, or use the Service Port IP address.

    • Node 1 : 10.17.21.1 (dual-server node systems)
    • Node 2 : 10.17.21.2 (dual-server node, or supported "HA-ready" single-server node StorNext appliances)

  2. Initiate an ssh session to the system using Terminal or PuTTY:
    1. Log in to the command line using the following credentials:
      • User name: stornext
      • Password: <stornext user account password>

        Note: "password" is the default password for the stornext user account. If the password has been changed, use the current password. Beginning with StorNext 7.0.2, you must change the default password for the stornext user account. As of StorNext 7.0.2, the first time you log in, you will be prompted to change the password to a different one.

    2. Enter sudo rootsh to gain root user access.
    3. Enter the password for the stornext user account again.
  1. Confirm that the server node you are connected to is operating as the primary. Enter:

    2. snhamgr -m status

  2. Verify the output is as follows (in green):

    3. LocalMode=default

    LocalStatus=primary

    RemoteMode=default

    RemoteStatus=running

    This indicates the "Local" node you are connected to is operating as primary ("LocalStatus=primary"), and that the other node is operating as secondary ("RemoteStatus=running"). If you do not see this status, close this PuTTY/terminal session and SSH in to the other server node.

  3. On the node operating as the primary, initiate an HA fail-over to the node operating as the secondary.

    4. Note: If you have NFS-HA enabled, click here for the instructions to stop NAS prior to using this command.

    For CentOS6-based systems (includes Artico (R520), Pro Foundation, M660, M440, and M330 systems), enter:

    service cvfs stop

    For CentOS7-based systems (Xcellis Workflow Director, Xcellis Foundation, aiWARE for Xcellis Embedded, and Artico (R630) systems), enter:

    systemctl stop cvfs

    Note: The systemctl stop cvfs command does not provide any command-line status feedback on the progress of stopping cvfs operations. You will need to be patient and wait until you again have access to the command line prompt.

    Wait until the secondary node becomes the primary. (Time may vary.)

  4. Verify the node has failed over. Enter:

    5. snhamgr -m status

  5. Verify the output is (bold text used for clarification):

    6. LocalMode=default

    LocalStatus=stopped

    RemoteMode=primary

    RemoteStatus=running

    This indicates the "Local" node you are connected to is operating as secondary ("LocalStatus=stopped"), and that the other node is operating as secondary ("RemoteMode=primary").

    If this is not what is shown, wait and enter the snhamgr -m status command again.

    You can leave the SSH connection to this server node running if you will access this server again soon.

To verify the node previously operating as secondary is now operating as primary:

  1. Open an SSH connection to the appropriate server and use the IP address assigned to the node on the Management or LAN Client network, or use the Service Port IP address.

    • Node 1 : 10.17.21.1 (dual-server node systems)
    • Node 2 : 10.17.21.2 (dual-server node, or supported "HA-ready" single-server node StorNext appliances)

  2. Initiate an ssh session to the system using Terminal or PuTTY:
    1. Log in to the command line using the following credentials:
      • User name: stornext
      • Password: <stornext user account password>

        Note: "password" is the default password for the stornext user account. If the password has been changed, use the current password. Beginning with StorNext 7.0.2, you must change the default password for the stornext user account. As of StorNext 7.0.2, the first time you log in, you will be prompted to change the password to a different one.

    2. Enter sudo rootsh to gain root user access.
    3. Enter the password for the stornext user account again.
  1. Confirm that the server node you are connected to is operating as the primary. Enter:

    2. snhamgr -m status

  2. Verify the output is (bold text used for clarification):

    3. :default:primary:default:stopped:

    This indicates the node you are connected to is "primary", and that the node previously operating as primary is still "stopped".

  1. Open an SSH connection to the appropriate server and use the IP address assigned to the node on the Management or LAN Client network, or use the Service Port IP address.

    • Node 1 : 10.17.21.1 (dual-server node systems)
    • Node 2 : 10.17.21.2 (dual-server node, or supported "HA-ready" single-server node StorNext appliances)

  2. Initiate an ssh session to the system using Terminal or PuTTY:
    1. Log in to the command line using the following credentials:
      • User name: stornext
      • Password: <stornext user account password>

        Note: "password" is the default password for the stornext user account. If the password has been changed, use the current password. Beginning with StorNext 7.0.2, you must change the default password for the stornext user account. As of StorNext 7.0.2, the first time you log in, you will be prompted to change the password to a different one.

    2. Enter sudo rootsh to gain root user access.
    3. Enter the password for the stornext user account again.
  1. Confirm that the server node you are connected to is operating as the primary. Enter:

    2. snhamgr -m status

  2. Verify the output is (bold text used for clarification):

    3. :default:stopped:default:primary:

    This indicates the node you are connected to is operating as secondary, that its services are "stopped", and that the other node is now operating as "primary".

  3. Restart StorNext services on the secondary node.:

    4. For CentOS6-based systems (Artico (R520), Pro Foundation, M660, M440, and M330 systems), enter:

    service cvfs start

    For CentOS7-based systems (Xcellis Workflow Director, Xcellis Foundation, aiWARE for Xcellis Embedded, and Artico (R630) systems), e Enter:

    systemctl start cvfs

    Note: The systemctl start cvfs command does not provide any command-line status feedback on the progress of starting cvfs operations. You will need to be patient and wait until you again have access to the command line prompt.

  4. Confirm that the node is operating as the secondary. Enter:

    5. snhamgr -m status

  5. Verify the output is (bold text used for clarification):

    6. :default:running:default:primary:

If desired, use this procedure to return the original server to again operate as the primary:

  1. Open an SSH connection to the appropriate server and use the IP address assigned to the node on the Management or LAN Client network, or use the Service Port IP address.

    • Node 1 : 10.17.21.1 (dual-server node systems)
    • Node 2 : 10.17.21.2 (dual-server node, or supported "HA-ready" single-server node StorNext appliances)

  2. Initiate an ssh session to the system using Terminal or PuTTY:
    1. Log in to the command line using the following credentials:
      • User name: stornext
      • Password: <stornext user account password>

        Note: "password" is the default password for the stornext user account. If the password has been changed, use the current password. Beginning with StorNext 7.0.2, you must change the default password for the stornext user account. As of StorNext 7.0.2, the first time you log in, you will be prompted to change the password to a different one.

    2. Enter sudo rootsh to gain root user access.
    3. Enter the password for the stornext user account again.
  1. Confirm that the server node you are connected to is operating as the primary. Enter:

    2. snhamgr -m status

  2. Verify the output is (bold text used for clarification):

    3. :default:primary:default:running:

    This indicates the node you are connected to is running, and is set as "primary", and that the secondary node is currently "running".

  3. On the node operating as the primary, initiate an HA failover to the node operating as the secondary.:

    4. For CentOS6-based systems (Artico (R520), Pro Foundation, M660, M440, and M330 systems), enter:

    service cvfs stop

    For CentOS7-based systems (Xcellis Workflow Director, Xcellis Foundation, aiWARE for Xcellis Embedded, and Artico (R630) systems), e Enter:

    systemctl stop cvfs

    Note: The systemctl stop cvfs command does not provide any command-line status feedback on the progress of stopping cvfs operations. You will need to be patient and wait until you again have access to the command line prompt.

    Wait until the secondary node becomes the primary. (Time may vary.)

  4. Verify the node has failed over. Enter:

    5. snhamgr -m status

  5. Verify the output is (bold text used for clarification):

    6. :default:stopped:default:primary:

    This indicates that the node you are connected to has "stopped" as primary, and that the node previously operating as secondary is now operating as "primary". If this is not what is shown, wait and rerun the snhamgr -m status command until you see the output shown above.

  6. Restart StorNext services on this node.

    7. For CentOS6-based systems (Artico (R520), Pro Foundation, M660, M440, and M330 systems), enter:

    service cvfs start

    For CentOS7-based systems (Xcellis Workflow Director, Xcellis Foundation, aiWARE for Xcellis Embedded, and Artico (R630) systems), e Enter:

    systemctl start cvfs

    Note: The systemctl start cvfs command does not provide any command-line status feedback on the progress of starting cvfs operations. You will need to be patient and wait until you again have access to the command line prompt.

  7. Verify the output is (bold text used for clarification):

    8. :default:running:default:primary:

  8. Continue to the next section, to complete the procedure.
  1. If NAS Fail-over for NFS Clusters (NFS-HA) was previously enabled, click here to re-enable NFS-HA.
  2. Verify that all clients have full access.
  3. Test access to all file systems.
The fail-over procedure is complete.