gpbackup manager does not remove the segment backups when using default location.
Article ID: 399645
Updated On:
Products
VMware Tanzu Data Suite
VMware Tanzu Greenplum
VMware Tanzu Greenplum / Gemfire
Issue/Introduction
+ You choose to use local backup (not recommended) of greenplum databases(s).
+ Choose a default backup directory and successfully able to generate the backup.
+ Able to view/list the collected backup using gpbackup_manager command line utility.
+ `gpbackup_manager delete-backup` command not able to delete backup files/directories from the segment hosts but only on the master host.
Example -
gpbackup --dbname gpperfmon
[gpadmin@masterhost ~]$ gpbackup --dbname gpperfmon
20250429:13:23:43 gpbackup:gpadmin:masterhost:4149638-[INFO]:-gpbackup version = 1.31.0
20250429:13:23:43 gpbackup:gpadmin:masterhost:4149638-[INFO]:-Greenplum Database Version = 6.27.3 build commit:fbdb2d07da47b0f13cb166baba1d8c47d92059f2
20250429:13:23:43 gpbackup:gpadmin:masterhost:4149638-[INFO]:-Starting backup of database gpperfmon
20250429:13:23:43 gpbackup:gpadmin:masterhost:4149638-[INFO]:-Backup Timestamp = 20250429132343
20250429:13:23:43 gpbackup:gpadmin:masterhost:4149638-[INFO]:-Backup Database = gpperfmon
20250429:13:23:43 gpbackup:gpadmin:masterhost:4149638-[INFO]:-Gathering table state information
20250429:13:23:43 gpbackup:gpadmin:masterhost:4149638-[INFO]:-Acquiring ACCESS SHARE locks on tables
Locks acquired: 45 / 45 [==============================================================] 100.00% 0s
20250429:13:23:43 gpbackup:gpadmin:masterhost:4149638-[INFO]:-Gathering additional table metadata
20250429:13:23:43 gpbackup:gpadmin:masterhost:4149638-[INFO]:-Getting partition definitions
20250429:13:23:44 gpbackup:gpadmin:masterhost:4149638-[INFO]:-Getting storage information
20250429:13:23:44 gpbackup:gpadmin:masterhost:4149638-[INFO]:-Getting child partitions with altered schema
20250429:13:23:44 gpbackup:gpadmin:masterhost:4149638-[INFO]:-Metadata will be written to /data/vol1/gpdb_master/gp4s-1/backups/20250429/20250429132343/gpbackup_20250429132343_metaql
20250429:13:23:44 gpbackup:gpadmin:masterhost:4149638-[INFO]:-Writing global database metadata
20250429:13:23:44 gpbackup:gpadmin:masterhost:4149638-[INFO]:-Global database metadata backup complete
20250429:13:23:44 gpbackup:gpadmin:masterhost:4149638-[INFO]:-Writing pre-data metadata
20250429:13:23:45 gpbackup:gpadmin:masterhost:4149638-[INFO]:-Pre-data metadata backup complete
20250429:13:23:45 gpbackup:gpadmin:masterhost:4149638-[INFO]:-Writing post-data metadata
20250429:13:23:45 gpbackup:gpadmin:masterhost:4149638-[INFO]:-Post-data metadata backup complete
20250429:13:23:45 gpbackup:gpadmin:masterhost:4149638-[INFO]:-Writing data to file
Tables backed up: 26 / 26 [==========================================================] 100.00% 1m5s
20250429:13:24:50 gpbackup:gpadmin:masterhost:4149638-[INFO]:-Data backup complete
20250429:13:24:50 gpbackup:gpadmin:masterhost:4149638-[INFO]:-Skipped data backup of 19 external/foreign table(s).
20250429:13:24:50 gpbackup:gpadmin:masterhost:4149638-[INFO]:-See /home/gpadmin/gpAdminLogs/gpbackup_20250429.log for a complete list of skipped tables.
20250429:13:24:52 gpbackup:gpadmin:masterhost:4149638-[INFO]:-Found neither /usr/local/greenplum-db-6.27.3/bin/gp_email_contacts.yaml nor /home/gpadmin/gp_email_contacts.yaml
20250429:13:24:52 gpbackup:gpadmin:masterhost:4149638-[INFO]:-Email containing gpbackup report /data/vol1/gpdb_master/gp4s-1/backups/20250429/20250429132343/gpbackup_20250429132343t will not be sent
20250429:13:24:52 gpbackup:gpadmin:masterhost:4149638-[INFO]:-Beginning cleanup
20250429:13:24:52 gpbackup:gpadmin:masterhost:4149638-[INFO]:-Cleanup complete
20250429:13:24:52 gpbackup:gpadmin:masterhost:4149638-[INFO]:-Backup completed successfully
[gpadmin@vlslcgpc07 ~]$ gpbackup_manager list-backups
timestamp date status database type object filtering plugin duration
20250429132343 Tue Apr 29 2025 13:23:43 Success gpperfmon full 00:01:08
20250429130559 Tue Apr 29 2025 13:05:59 Success gpperfmon full 00:01:13
[gpadmin@masterhost ~]$ ls /data/vol*/gpdb*/gp4s*/backups/20250429
/data/vol1/gpdb_master/gp4s-1/backups/20250429:
20250429132343
/data/vol1/gpdb_p1/gp4s0/backups/20250429:
20250429132343
/data/vol1/gpdb_p3/gp4s2/backups/20250429:
20250429132343
/data/vol2/gpdb_p2/gp4s1/backups/20250429:
20250429132343
/data/vol2/gpdb_p4/gp4s3/backups/20250429:
20250429132343
[gpadmin@masterhost ~]$ gpbackup_manager delete-backup 20250429132343
Are you sure you want to delete-backup 20250429132343? (y/N): y
20250429:13:35:06 gpbackup_manager:gpadmin:masterhost:4153853-[INFO]:-Deletion of 20250429132343 in progress.
Deletion of 20250429132343 done.
[gpadmin@masterhost ~]$ ls /data/vol*/gpdb*/gp4s*/backups/20250429
/data/vol1/gpdb_master/gp4s-1/backups/20250429:
/data/vol1/gpdb_p1/gp4s0/backups/20250429:
20250429132343
/data/vol1/gpdb_p3/gp4s2/backups/20250429:
20250429132343
/data/vol2/gpdb_p2/gp4s1/backups/20250429:
20250429132343
/data/vol2/gpdb_p4/gp4s3/backups/20250429:
20250429132343
[gpadmin@masterhost ~]$ du -sh /data/vol*/gpdb*/gp4s*/backups/20250429
0 /data/vol1/gpdb_master/gp4s-1/backups/20250429
141M /data/vol1/gpdb_p1/gp4s0/backups/20250429
144M /data/vol1/gpdb_p3/gp4s2/backups/20250429
143M /data/vol2/gpdb_p2/gp4s1/backups/20250429
144M /data/vol2/gpdb_p4/gp4s3/backups/20250429Environment
All Greenplum Versions 5.x, 6.x & 7.x
All gpbackup versions.
Cause
It appears to be a code bug as of now and engineering planned the investigation/fix in future release of gpbackup utility.
Resolution
Permanent Solution -
RCA investigation & Fix planned for future releases of gpbackup utility.
Workaround -
using Linux `rm` command to remove the leftover relevant backup files/directories after execution of `gpbackup_manager delete-backup` command.
Feedback
Yes
No
Powered by
