Message-ID: <484cbe3c-eb15-5327-df72-3338c17c7855@pgmasters.net>
Date: Mon, 26 Jun 2023 15:08:42 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0)
 Gecko/20100101 Thunderbird/102.12.0
Subject: Re: Postgresql Database cant start after restore using pgBackRest
Content-Language: en-US
To: Deo Felix <deofelix9@gmail.com>, pgsql-admin@lists.postgresql.org
References: 
 <CALW=F4MZsscvQ-x+fGmxSY2q4xaGk1stKPsKuts-om-ewdeR5A@mail.gmail.com>
From: David Steele <david@pgmasters.net>
In-Reply-To: 
 <CALW=F4MZsscvQ-x+fGmxSY2q4xaGk1stKPsKuts-om-ewdeR5A@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: 
 <https://www.postgresql.org/message-id/484cbe3c-eb15-5327-df72-3338c17c7855%40pgmasters.net>
Precedence: bulk

On 6/25/23 18:53, Deo Felix wrote:
>   I am doing backup with pgbackrest in the database server every day at 
> night, I was testing to restore the backup in another server, the 
> restore was successfully however the database cant start
> 
> *pgbackrest --stanza=data --delta --log-level-console=detail restore*

Usually this happens when you promote a standby while the primary is 
still running. The promotion of the standby will create a new timeline 
(in this case 2) and then push WAL to the archive on this new timeline.

When you restore, PostgreSQL will try to recover to timeline 2 (by 
default) even though timeline 2 can't be reached from timeline 1 backups 
that were made after the promotion.

So, you need to instruct PostgreSQL to stay on timeline 1 rather than 
try to switch to timeline 2. You can do that by setting 
--target-timeline=current, i.e. stay on the timeline that was current 
when the backup was made.

Regards,
-David