Using the Administration Tools to Replace Nodes

If you are replacing a node with a host that uses a different name and IP address, use the Administration Tools to replace the original host with the new host. Alternatively, you can use the Management Console to replace a node.

Replace the Original Host with a New Host Using the Administration Tools

To replace the original host with a new host using the Administration Tools:

  1. Back up the database. See Backing Up and Restoring the Database.
  2. From a node that is up, and is not going to be replaced, open the Administration Tools.
  3. On the Main Menu, select View Database Cluster State to verify that the database is running. If it’s not running, use the Start Database command on the Main Menu to restart it.
  4. On the Main Menu, select Advanced Menu.
  5. In the Advanced Menu, select Stop Vertica on Host.
  6. Select the host you want to replace, and then click OK to stop the node.
  7. When prompted if you want to stop the host, select Yes.
  8. In the Advanced Menu, select Cluster Management, and then click OK.
  9. In the Cluster Management menu, select Replace Host, and then click OK.
  10. Select the database that contains the host you want to replace, and then click OK.

    A list of all the hosts that are currently being used displays.

  11. Select the host you want to replace, and then click OK.
  12. Select the host you want to use as the replacement, and then click OK.
  13. When prompted, enter the password for the database, and then click OK.
  14. When prompted, click Yes to confirm that you want to replace the host.
  15. When prompted that the host was successfully replaced, click OK.
  16. In the Main Menu, select View Database Cluster State to verify that all the hosts are running. You might need to start Vertica on the host you just replaced. Use Restart Vertica on Host.

    The node enters a RECOVERING state.

Caution: If you are using a K-Safe database, keep in mind that the recovering node counts as one node down even though it might not yet contain a complete copy of the data. This means that if you have a database in which K safety=1, the current fault tolerance for your database is at a critical level. If you lose one more node, the database shuts down. Be sure that you do not stop any other nodes.