LI82844: WAL ARCHIVING STOPS AFTER SFTP RESTORE WHICH CAUSES WAL ACCUMULATION, BACKUP & SCHEDULED BACKUP FAILURES

APAR status

• Closed as program error.

Error description

• In the postgres pod the wal files were accumulating - the error
  in the pglogs were:
  backrest-set-env.sh && pgbackrest archive-push
  "pg_wal/00000034000001970000001F"
  ERROR: [045]: WAL file '00000034000001970000001F' already exists
  in the repo1 archive with a different checksum.
  

Local fix

• Followed the workaround, by removing the offending files (4) to
  /tmp.After this, the wal file count started dropping. A manual
  backup successfully completed using apicup.
  

Problem summary

• This issue only impacts customers who have SFTP backups set up
  and who have performed at least one SFTP restore.
  
  WAL archiving stops after SFTP restoration which causes the
  following issues <ul><li>WAL files will start accumulating which
  in turn leads to disk fill up and the disk monitoring feature
  kicks in and might shut down the system at 80% disk
  utilization</li><li>Scheduled backups won't work</li><li>Backups
  won't work </li></ul>
  Fix was to identify the root cause of the problem and change the
  restore process which now does not causes any wal archiving
  issues after sftp restore
  

Problem conclusion

• Fixed in v10.0.1.11 and v10.0.5.3
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  API CONNECT ENT

• Fixed component ID

  5725Z2201

Applicable component levels