Note: You do not need to perform the server fail-over operation at this time if continuing the installation 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, if connected to the Service Port.

Service Port IP addresses (if used):

Note: Node 2 is used for installation using the StorNext Connect Install app, for both single-node and dual-node systems only. It is the server node sold with single-node (non-HA) Workflow Director and Artico systems. This makes the server HA-ready, allowing for adding a second server node as a upgrade after initial installation.

2. Log in to the server node with the following credentials:
   • User name: stornext
   • Password: <stornext user accountpassword>

     Note: password is the default password for the stornext user account. If the password has been changed, use the current password.

3. Enter sudo rootsh to gain root user access.
4. Enter the password for the stornext user account again.

5. Confirm that the server node you are connected to is operating as the primary. Enter:

snhamgr -m status

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

: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".

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

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

For CentOS7-based systems (Xcellis Foundation, aiWARE for Xcellis Embedded (DAE), Xcellis Workflow Director, 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.)

8. Verify the node has failed over. Enter:

snhamgr -m status

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

: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 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, if connected to the Service Port.

Service Port IP addresses (if used):

Note: Node 2 is used for installation using the StorNext Connect Install app, for both single-node and dual-node systems only. It is the server node sold with single-node (non-HA) Workflow Director and Artico systems. This makes the server HA-ready, allowing for adding a second server node as a upgrade after initial installation.

2. Log in to the server node with the following credentials:
   • User name: stornext
   • Password: <stornext user accountpassword>

     Note: password is the default password for the stornext user account. If the password has been changed, use the current password.

3. Enter sudo rootsh to gain root user access.
4. Enter the password for the stornext user account again.

5. Confirm that the server node you are connected to is operating as the primary. Enter:

snhamgr -m status

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

: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, if connected to the Service Port.

Service Port IP addresses (if used):

Note: Node 2 is used for installation using the StorNext Connect Install app, for both single-node and dual-node systems only. It is the server node sold with single-node (non-HA) Workflow Director and Artico systems. This makes the server HA-ready, allowing for adding a second server node as a upgrade after initial installation.

2. Log in to the server node with the following credentials:
   • User name: stornext
   • Password: <stornext user accountpassword>

     Note: password is the default password for the stornext user account. If the password has been changed, use the current password.

3. Enter sudo rootsh to gain root user access.
4. Enter the password for the stornext user account again.

5. Confirm that the server node you are connected to is operating as the primary. Enter:

snhamgr -m status

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

: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".

7. Restart StorNext services on the secondary node.:

For CentOS7-based systems (Xcellis Foundation, aiWARE for Xcellis Embedded (DAE), Xcellis Workflow Director, and Artico (R630) systems), 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.

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

snhamgr -m status

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

: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, if connected to the Service Port.

Service Port IP addresses (if used):

Note: Node 2 is used for installation using the StorNext Connect Install app, for both single-node and dual-node systems only. It is the server node sold with single-node (non-HA) Workflow Director and Artico systems. This makes the server HA-ready, allowing for adding a second server node as a upgrade after initial installation.

2. Log in to the server node with the following credentials:
   • User name: stornext
   • Password: <stornext user accountpassword>

     Note: password is the default password for the stornext user account. If the password has been changed, use the current password.

3. Enter sudo rootsh to gain root user access.
4. Enter the password for the stornext user account again.

5. Confirm that the server node you are connected to is operating as the primary. Enter:

snhamgr -m status

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

: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".

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

For CentOS7-based systems (Xcellis Foundation, aiWARE for Xcellis Embedded (DAE), Xcellis Workflow Director, 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.)

8. Verify the node has failed over. Enter:

snhamgr -m status

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

: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.

10. Restart StorNext services on this node.

For CentOS7-based systems (Xcellis Foundation, aiWARE for Xcellis Embedded (DAE), Xcellis Workflow Director, and Artico (R630) systems), 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.

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

:default:running:default:primary:

12. 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.