How to recover a Vertica node from a failed start

How to recover a node from a failed start In this post we will go over the procedure you need to follow to be able to recover a Vertica database node after a failed start. 

admintools  -t  restart_node  --hosts= --database=--password= --force
During a full database restore, the node must be DOWN. If you start the restore process and the node is UP, vbr.py displays the following message: 
doc:tests/doc/tools $ vbr.py --config-file=doc.ini -t restore --nodes=v_doc_node0001

Warning: trying to restore to an UP cluster
Warning: Node state of v_doc_node0001 is UP; node must be DOWN for restore; ignoring restore on this node.
Nothing to do
restore done!
To restore the node, first bring it down, and then run the utility again.
  • Restoring from a Specific Snapshot
The snapshot has to exist before doing this., Syntax: 
vbr.py --task restore --config-file  --archive=
Example: 
vbr.py --task restore --config-file /bkp/db.ini --archive=20120906_152640
Note: the archive must corresponds with the type of backup done. You will restore a snapshot created on 2012/09/06 at 15:26:40 sec. The archive option need to receive the date_timestamp parameter that is appended to the snapshots archive. Restoring From the Most Recent Snapshot Syntax: vbr.py --task restore --config-file Example: 
vbr.py --task restore --config-file db.ini

Copying...
1871652633 out of 1871652633, 100%
All child processes terminated successfully.
restore done!

Copyright 2020. All Rights Reserved