The recommended approach to copying the Vertica database to another server is via the Vertica copycluster command.
CA Performance management r3.6 above.
The cause was the full path to copydrdata.ini file was not specified:
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
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