Directories in /tmp/vbr on the Data Repository system are taking up disk space

Products

• CA Infrastructure Management
• CA Performance Management - Usage and Administration

Issue/Introduction

ISSUE:

Directories in /tmp/vbr on the Data Repository system are taking up disk space

ENVIRONMENT:

CAPM
RHEL

SYMPTOMS:

Data Repository system is running low on disk space. Much space is consumed by numerous sub-directories under /tmp/vbr.

CAUSE:

The /tmp/vbr sub-directories are temp directories created by Vertica database backups. If you look in the directories you would see the run of the backup and the output from running the re-synch between the node and backup host.


To verify the number of directories corresponds to backups, the following procedure can be used:

1. As your database admin user (dradmin by default), CD to the /vertica/bin directory and run the following:

vbr.py --task listbackup --config-file <path to .ini file>

*Typically the .ini file will be in /vertica/config (vbr.ini by default)

2. From the same directory, run ./vsql to enter a vsql session: ./vsql -U <db admin user>

Run the following 2 queries to obtain the output:

A. select * from database_snapshots;

B. select * from v_monitor.database_backups;


RESOLUTION:

The /tmp/vbr sub-directories are temp directories created by Vertica database backups. These temp directories are not cleaned up automatically - manual intervention is required. Administrators need to decide on how long / how many to retain and remove directories as needed.

ADDITIONAL INFORMATION:

Below is a link to Vertica's site regarding the backups:

https://my.vertica.com/docs/7.1.x/HTML/Content/Authoring/AdministratorsGuide/BackupRestore/ConfiguringBackupHosts.htm


*Specifically note the following: "The vbr.py log files are not removed automatically, so delete older log files manually as necessary."

Environment

Release: IMDAGG99000-2.5-Infrastructure Management-Data Aggregator
Component: