Skip to main content

Select Start Recovery to configure non-primary Admin Node

Contributors netapp-perveilerk netapp-madkat netapp-lhalbert ssantho3

After replacing a non-primary Admin Node, you must select Start Recovery in the Grid Manager to configure the new node as a replacement for the failed node.

Before you begin
  • You are signed in to the Grid Manager using a supported web browser.

  • You have the Maintenance or Root access permission.

  • You have the provisioning passphrase.

  • You have deployed and configured the replacement node.

  1. From the Grid Manager, select MAINTENANCE > Tasks > Recovery.

  2. Select the grid node you want to recover in the Pending Nodes list.

    Nodes appear in the list after they fail, but you can't select a node until it has been reinstalled and is ready for recovery.

  3. Enter the Provisioning Passphrase.

  4. Click Start Recovery.

    screenshot showing the Maintenance > Recovery page
  5. Monitor the progress of the recovery in the Recovering Grid Node table.

    Note While the recovery procedure is running, you can click Reset to start a new recovery. A dialog box appears, indicating that the node will be left in an indeterminate state if you reset the procedure.
    screenshot showing the reset recovery warning dialog box

    If you want to retry the recovery after resetting the procedure, you must restore the node to a pre-installed state, as follows:

    • VMware: Delete the deployed virtual grid node. Then, when you are ready to restart the recovery, redeploy the node.

    • Linux: Restart the node by running this command on the Linux host: storagegrid node force-recovery node-name

    • Appliance: If you want to retry the recovery after resetting the procedure, you must restore the appliance node to a pre-installed state by running sgareinstall on the node. See Prepare appliance for reinstallation (platform replacement only).

  6. If single sign-on (SSO) is enabled for your StorageGRID system and the relying party trust for the Admin Node you recovered was configured to use the default management interface certificate, update (or delete and recreate) the node's relying party trust in Active Directory Federation Services (AD FS). Use the new default server certificate that was generated during the Admin Node recovery process.

    Note To configure a relying party trust, see Configure single sign-on. To access the default server certificate, log in to the command shell of the Admin Node. Go to the /var/local/mgmt-api directory, and select the server.crt file.