Page 1 of 1

Node name mismatch with copycluster

Posted: Sat Dec 07, 2013 5:41 pm
by rcrcr
In copying an existing cluster to a fresh new cluster,

The source target has 3 nodes:


The target cluster has been initialized with 3 nodes:


Unfortunately, because the node names don't match, copycluster reports the following:

Source cluster has node v_mydatabase_node0004, but target cluster does not; cannot copy cluster.

What's the best approach for dealing with this?

Re: Node name mismatch with copycluster

Posted: Tue Apr 26, 2016 9:31 am
by alexey
You should fix the destination cluster naming, since you are replacing the cluster it shouldn't be a problem of dropping and creating it again with proper names.
Some time if there were previous cluster on the nodes the naming doesn't start from v_db_outbrain_node0001 as in your case.
To fix this move content of /opt/vertica/config to backup directory and run install_vertica again, then the DB will be created with proper naming.
In your case the naming issue is in source cluster, so on destination create single node db then drop it , then the db should start from v_db_outbrain_node0002