search cancel

Error While Checking Vertica Copycluster Command On Primary Data Repository IP:123.456.789.10

book

Article ID: 134591

calendar_today

Updated On:

Products

CA Infrastructure Management CA Performance Management - Usage and Administration

Issue/Introduction

The recommended approach to copying the Vertica database to another server is via the Vertica copycluster command.

Cause

The cause was the full path to copydrdata.ini file was not specified:


Environment

CA Performance management r3.6 above. 

Resolution

The solution is specify the full path to the .INI file, in the below example the slash before home was missing:

vbr.py --task copycluster --config-file /home/dradmin/copydrdata.ini

Additional Information

Pleas note this only covers one example,  there are multiple reasons why vbr copycluster command can fail.  To get a better understanding run the vbr command with debug 3 (default is 0)

vbr.py --task copycluster --debug 3 --config-file /home/dradmin/copydrdata.ini

Afterwards check the log file in /tmp/vbr.log, if necessary open a case with Broadcom support.