barman + postgresql not start after barman retore

Posted on

barman + postgresql not start after barman retore – Managing your servers can streamline the performance of your team by allowing them to complete complex tasks faster. Plus, it can enable them to detect problems early on before they get out of hand and compromise your business. As a result, the risk of experiencing operational setbacks is drastically lower.

But the only way to make the most of your server management is to perform it correctly. And to help you do so, this article will share nine tips on improving your server management and fix some problem about linux, backup, postgresql, backup-restoration, .

I use the barman ( http://www.pgbarman.org/ ) , for backup and restore on my linux redhat machine

after restore , we start the postgresql as the following

 systemctl start postgresql.service

but postgresql not startup

from the log:

  /var/lib/pgsql/backups/data/pg_log

we seen the following errors

 requested recovery stop point is before consistent recovery point

please advice what is the meaning of this FATAL error?

 more pg_log


 LOG:  database system was interrupted; last known up at 2017-08-06 07:30:49 UTC
 LOG:  restored log file "00000008.history" from archive
 LOG:  starting point-in-time recovery to 2017-08-06 07:30:49.813508+00
 LOG:  restored log file "0000000800000000000000C1" from archive
 LOG:  redo starts at 0/C1000080
 LOG:  recovery stopping before commit of transaction 96139, time 2017-08-06 07:30:49.855629+00
 LOG:  redo done at 0/C1001B90
 FATAL:  requested recovery stop point is before consistent recovery point
 LOG:  startup process (PID 55858) exited with exit code 1
 LOG:  terminating any other active server processes

example – when I start the postgres service:

  systemctl start postgresql.service
  Job for postgresql.service failed because the control process exited with 
  error code. See "systemctl status postgresql.service" and "journalctl -xe" 
  for details.


  ls
  backup_label.old     pg_hba.conf                   pg_hba.conf.2017-08-
  03_13:08  pg_snapshots  pg_xlog                           
  postgresql.conf.2017-08-03_13:03
  barman_xlog          pg_hba.conf.2017-08-03_12:07  pg_ident.conf                 
  pg_stat_tmp   postgresql.conf                   postgresql.conf.2017-08-
  03_13:08
  base                 pg_hba.conf.2017-08-03_12:22  pg_log                        
  pg_subtrans   postgresql.conf.2017-08-03_12:07  postgresql.conf.origin
  global               pg_hba.conf.2017-08-03_12:24  pg_multixact                  
  pg_tblspc     postgresql.conf.2017-08-03_12:22  postmaster.opts
  pg_clog              pg_hba.conf.2017-08-03_12:28  pg_notify                     
  pg_twophase   postgresql.conf.2017-08-03_12:24  recovery.done
  pg_hba_bak.conf.old  pg_hba.conf.2017-08-03_13:03  pg_serial                     
  PG_VERSION    postgresql.conf.2017-08-03_12:28

Solution :

You forgot to remove the recover.conf file after restoring.

This file is only required for PiTR and not for normal DB operation. The solution is to simply remove it.

Leave a Reply

Your email address will not be published.