Copycluster fails with Error: Database path does not match on source

Products

• Network Observability
• CA Performance Management

Issue/Introduction

After running

Drop db

Create db

 

Copycluster fails with this error:

2026-04-06 10:33:02 localhost vsql /opt/vertica/bin/vsql -q -t -X -ddrdata -p5433 -Udradmin -hx.x.x.x

2026-04-06 10:33:02 localhost vbr Error: Database path does not match on source (v_drdata_node0002: /catalog/drdata/v_drdata_node0002_catalog) and destination (<HOSTNAME>: /catalog/drdata/v_drdata_node0001_catalog) nodes.

  Copycluster FAILED.

Environment

 DX NetOps :: All Supported Versions

Cause

 In older versions of vertica, the create database function in admintools ordered the hosts in random order.

In newer versions it orders them by IP address, ascending

Resolution

Since it doesnt matter which node is node0001 or node0002

Edit the mapping section in the copycluster ini file to match the new node names and rerun the copycluster

Additional Information

When creating a Vertica database using admintools, the order in which hosts are selected determines the default node naming convention (e.g., v_drdata_node0001, v_drdata_node0002).

If the node names in a Disaster Recovery (DR) cluster do not perfectly match the Production cluster, copycluster jobs will fail with path or node mismatch errors.

While the initial naming order is not critical for database operation, it is mandatory for copycluster that the source and target node names align exactly, or are explicitly remapped.