Backup task for repository no longer runs and displays error message 6985
search cancel

Backup task for repository no longer runs and displays error message 6985

book

Article ID: 409172

calendar_today

Updated On:

Products

Network Observability

Issue/Introduction

1. You have a problem with the backup task for data repository cluster after replacing the hardware on the impacted server then restored everything (OS + APM software). The Task doesen't run anymore. The following error message appears:

$ /opt/vertica/bin/vbr.py --task backup --config-file /home/dradmin/BackupConfig.ini

Error: SQL command "select database_snapshot('BackupConfig',false);" failed: ERROR 6985: tar_append_tree failed:File or directory not found. Real dir:/catalog/drdata/v_drdata_node0002_catalog/Libraries/02a09f549e2c933c841599a18087460f00a00003342694a0; save dir: 02a09f549e2c933c841599a18087460f00a00003342694a0

 

2. What can be done to get the backup running again? You've already tried the following commands, but unfortunately, all without success.

/opt/vertica/bin/vbr.py --task init --config-file /home/dradmin/BackupConfig.ini

/opt/vertica/bin/vbr.py --task quick-repair --config-file /home/dradmin/BackupConfig.ini

/opt/vertica/bin/vbr.py --task remove --archive=all --config-file /home/dradmin/BackupConfig.ini

 

3. The database is running without any problems.

Environment

All supported releases of Performance Management

Cause

Directory reported in the below error does not exist in the respective node. For example, node 2 here.

$ /opt/vertica/bin/vbr.py --task backup --config-file /home/dradmin/BackupConfig.ini

Error: SQL command "select database_snapshot('BackupConfig',false);" failed: ERROR 6985: tar_append_tree failed:File or directory not found. Real dir:/catalog/drdata/v_drdata_node0002_catalog/Libraries/02a09f549e2c933c841599a18087460f00a00003342694a0; save dir: 02a09f549e2c933c841599a18087460f00a00003342694a0

Resolution

1. You can copy the /catalog/drdata/v_drdata_node0002_catalog/Libraries/02a09f549e2c933c841599a18087460f00a00003342694a0 directory from the node where it is present to the nodes (node2 here) where it is not available using scp and ensure permissions and ownership of the directory and its contents is same as the other directories under /catalog/drdata/v_drdata_node0002_catalog/Libraries/.

2. After that try to take backup process.