backup k-safe

book

Article ID: 195721

calendar_today

Updated On:

Products

CA Infrastructure Management CA Performance Management - Usage and Administration DX NetOps

Issue/Introduction

I am getting this warning on my backup and need help to fix it before it becomes a problem for me.  I am seeing this behavior after adding 2 nodes to my existing 1 node environment


$ /opt/vertica/bin/vbr.py --task backup  --config-file /opt/vertica/config/vertica_backup.ini
WARNING 6046:  The database is currently 0-safe, which could result in catastrophic data loss in the event of a failure.  Do not use k=0 in a production environment. For test, dev or other non-production environments, K=0 may be acceptable however Vertica still recommends a minimum value of K=1
Starting backup of database drdata.
Participating nodes: v_drdata_node0001, v_drdata_node0002, v_drdata_node0003.
WARNING 6046:  The database is currently 0-safe, which could result in catastrophic data loss in the event of a failure.  Do not use k=0 in a production environment. For test, dev or other non-production environments, K=0 may be acceptable however Vertica still recommends a minimum value of K=1
Snapshotting database.
Snapshot complete.
Approximate bytes to copy: 13741051381 of 26148429015 total.
[==================================================] 100%
Copying backup metadata.
Finalizing backup.
Deleting old restore points.
Backup complete!
WARNING 6046:  The database is currently 0-safe, which could result in catastrophic data loss in the event of a failure.  Do not use k=0 in a production environment. For test, dev or other non-production environments, K=0 may be acceptable however Vertica still recommends a minimum value of K=1

Environment

DevOps Performance Management 3.7

Resolution

The following was done to resolve this:

  • Connect to vsql on the data repository
  • SELECT dbd_add_nodes_rebalance_data(1);
    • API will add buddy projection to projections missing buddy . 
  • SELECT MARK_DESIGN_KSAFE(1);
  • SELECT current_fault_tolerance from system;  ---> Should show a value of 1 now as opposed to 0

This should resolve the backup issue and set the environment to the appropriate ksafety level

 

Additional Information

Public vertica forum:

https://forum.vertica.com/discussion/238536/k-safety-issue