Unable to See Failed Error Statements in gprestore Log File After Database Restore from GPBackup/GPRestore Version 1.30.5
Article ID: 397482
Updated On:
Products
Issue/Introduction
After performing a database restore using GPBackup/GPRestore version 1.30.5 from one Greenplum Database (6.X) backup dump to another Greenplum Database (6.X), users may encounter a situation where failed error statements are not visible in the gprestore log file, despite the restore operation indicating non-fatal errors. The restore status reported success with the message:
"Success but non-fatal errors occurred. See log file /apps/greenplum/gpAdminLogs/gprestore.log for details."Environment
GPDB: 6.X
GPBackup/GPRestore Version: 1.30.5
Cause
In GPBackup/GPRestore version 1.30.5, a change was introduced to reduce the volume of DEBUG and VERBOSE logs written to disk. This modification was made in response to customer feedback about the overwhelming amount of disk space consumed by logging, especially during large restore operations. However, this change unintentionally caused the details of failed SQL commands to not be written into the gprestore log file.
In the original log, the restore process mentions encountering errors during metadata restore:
[ERROR]:-Encountered 'N' errors during metadata restore; see log file /apps/greenplum/gpAdminLogs/gprestore.log for a list of failed statements.
Resolution
The issue was traced back to the changes introduced in GPBackup/GPRestore version 1.30.5, which suppressed verbose logging, including the details of failed SQL commands. This problem was addressed in GPBackup/GPRestore version 1.30.6. Users experiencing this issue are advised to upgrade to at least GPBackup/GPRestore version 1.30.6 to restore the functionality of logging failed SQL statements in the gprestore log file.
Feedback
