cancel
Showing results for 
Search instead for 
Did you mean: 

How to bring up the old Master as a Standby database automatically

SOLVED
Level 3 Adventurer

How to bring up the old Master as a Standby database automatically

Hi Team,

 

I'm trying a failover senario on EDB AS9.6 with EFM 3.2, steaming replication is set and all the databases are in sync. The setup is as below.

 

Master DB server IP: 192.168.216.101

Wintness server IP: 192.168.216.107

Standby DB server IP: 192.168.216.108

Standby DB server IP: 192.168.216.118

 

Due to nextwork failure the master DB was not reachable to EFM, as expected one of the Standby DBs was promoted as Master, as listed below:

 

Idle DB server IP: 192.168.216.101

Wintness server IP: 192.168.216.107

Master DB server IP: 192.168.216.108

Standby DB server IP: 192.168.216.118

 

Now I want to bring up the old Master DB 192.168.216.101 as a standby database automatically whenever the network issue gets fixed. Is this cofiguration possible? Please help.

 

 

 

 

 

2 ACCEPTED SOLUTIONS

Accepted Solutions
EDB Team Member

Re: How to bring up the old Master as a Standby database automatically

Hello Mahisha,

 

As soon as one of the slave was promoted its timeline got changed and the second slave got pointed to the new master. 

As you stated your old master is still out of network. You need to rebuild it with the help of the new master.

For that, the fastest way is as below :

1. Put New master in backup mode.

2. Rsync all data directory and its tablespace from new master to old master.

3. Stop the backup mode on the new master.

4. Create the recovery.conf file.

5. Start the old master as standby of new master.

 

Hope this helps!

Level 3 Adventurer

Re: How to bring up the old Master as a Standby database automatically

Hi Dhananjay,

 

Thank you somuch for your response, this really helps.

 

 

4 REPLIES
EDB Team Member

Re: How to bring up the old Master as a Standby database automatically

Hello Mahisha,

 

As soon as one of the slave was promoted its timeline got changed and the second slave got pointed to the new master. 

As you stated your old master is still out of network. You need to rebuild it with the help of the new master.

For that, the fastest way is as below :

1. Put New master in backup mode.

2. Rsync all data directory and its tablespace from new master to old master.

3. Stop the backup mode on the new master.

4. Create the recovery.conf file.

5. Start the old master as standby of new master.

 

Hope this helps!

Level 3 Adventurer

Re: How to bring up the old Master as a Standby database automatically

Hi Dhananjay,

 

Thank you somuch for your response, this really helps.

 

 

Level 3 Traveller

Re: How to install PostgreSQL tools ONLY for EDB 9.6 Enterprise Edition on RHEL 7.2

Hi Team,

 

I have installed EDB Postgres 9.6 Enterprise Edition.But tools are not supported with installer.So I need to install all of them separately.

I have tried installing postgresql yum repo.But tools installation is  failing due to some dependencies

Is there any solution that i can follow in this regard?

 

Tools:dbserver,connectors,pgadmin4,pgpool,pgpoolextension,edbplus,replication(All products)

 

 

EDB Team Member

Re: How to install PostgreSQL tools ONLY for EDB 9.6 Enterprise Edition on RHEL 7.2

Hi Manisha,

 

 Yes with EDB Postgres 9.6 Enterprise Edition you can't install EDB tools as a part of installer you need to install all the EDB tools from StackBuilder Plus or else from the enterprisedb website.

 

Earlier version of ppasmeta installer 9.5 version edb tools can be installed along with the installer, From EDB Postgres 9.6 Enterprise Edition version these has been changed.

 

What dependencies error your getting while installing the EDB tools.

 

Hope this helps you.