{"id":12177,"date":"2018-12-24T10:47:07","date_gmt":"2018-12-24T09:47:07","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-3-3-with-virtual-ip-address\/"},"modified":"2023-06-15T16:33:55","modified_gmt":"2023-06-15T14:33:55","slug":"edb-failover-manager-3-3-with-virtual-ip-address","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-3-3-with-virtual-ip-address\/","title":{"rendered":"EDB Failover Manager 3.3 With Virtual Ip Address"},"content":{"rendered":"

By Mouhamadou Diaw<\/strong><\/p>\n

In a previous blog <\/a>, I talked about installing and configuring Edb Failover Manager with PostgreSQL. The configuration of a Virtual Ip Address was not discussed in this previous article.In this blog I am going to show how we can implement a virtual IP with EFM.
\nWe suppose that
\n-The standby is already built
\n-EFM is configured and running (see here <\/a> for the configuration)
\nBelow our configuration ( Iam using PostgreSQL 11.1 with Centos 7)<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n
15<\/div>\n
16<\/div>\n
17<\/div>\n
18<\/div>\n
19<\/div>\n
20<\/div>\n
21<\/div>\n
22<\/div>\n
23<\/div>\n
24<\/div>\n
25<\/div>\n
26<\/div>\n<\/td>\n
\n
\n
[root@dbi-pg-tools efm-3.3]<\/code># \/usr\/edb\/efm-3.3\/bin\/efm cluster-status efm<\/code><\/div>\n
Cluster Status: efm<\/code><\/div>\n
<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Agent Type\u00a0 Address\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Agent\u00a0 DB\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 VIP<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>-----------------------------------------------------------------------<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Witness\u00a0\u00a0\u00a0\u00a0 192.168.22.100\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 UP\u00a0\u00a0\u00a0\u00a0 N<\/code>\/A<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Master\u00a0\u00a0\u00a0\u00a0\u00a0 192.168.22.101\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 UP\u00a0\u00a0\u00a0\u00a0 UP<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Standby\u00a0\u00a0\u00a0\u00a0 192.168.22.102\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 UP\u00a0\u00a0\u00a0\u00a0 UP<\/code><\/div>\n
<\/div>\n
Allowed node host list:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>192.168.22.101 192.168.22.102 192.168.22.100<\/code><\/div>\n
<\/div>\n
Membership coordinator: 192.168.22.101<\/code><\/div>\n
<\/div>\n
Standby priority host list:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>192.168.22.102<\/code><\/div>\n
<\/div>\n
Promote Status:<\/code><\/div>\n
<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>DB Type\u00a0\u00a0\u00a0\u00a0 Address\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 XLog Loc\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Info<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>--------------------------------------------------------------<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Master\u00a0\u00a0\u00a0\u00a0\u00a0 192.168.22.101\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0<\/code>\/301BE38<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Standby\u00a0\u00a0\u00a0\u00a0 192.168.22.102\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0<\/code>\/301BE38<\/code><\/div>\n
<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Standby database(s) <\/code>in<\/code> sync<\/code> with master. It is safe to promote.<\/code><\/div>\n
[root@dbi-pg-tools efm-3.3]<\/code>#<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

To resume we have three servers
\n-dbi-pg-tools : the witness with IP 192.168.22.100
\n-dbi-pg-essentials : the master with IP 192.168.22.101
\n-dbi-pg-essentials_2 : the standby with IP 192.168.22.102
\nLet\u2019s say that we want to configure a virtual IP 192.168.22.105.
\nThe first step is to update the efm.properties on both nodes with following lines<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n<\/td>\n
\n
\n
virtualIp=192.168.22.105<\/code><\/div>\n
virtualIp.interface=enp0s9\u00a0\u00a0 -- name of my interface<\/code><\/div>\n
virtualIp.prefix=24<\/code><\/div>\n
virtualIp.single=<\/code>true<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

Then restart efm on both nodes.<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n<\/td>\n
\n
\n
[root@dbi-pg-essentials network-scripts]<\/code>#\u00a0 service efm-3.3 start<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

Running again the status command should show the VIP address. Restarting efm should be enough but if ever the virtual IP is not shown we can use following command to add the virtual IP.<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n<\/td>\n
\n
\n
[root@dbi-pg-essentials network-scripts]<\/code># \/usr\/edb\/efm-3.3\/bin\/efm_address add4 enp0s9 192.168.22.105\/24<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

Then the status should be<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n
15<\/div>\n
16<\/div>\n
17<\/div>\n
18<\/div>\n
19<\/div>\n
20<\/div>\n
21<\/div>\n
22<\/div>\n
23<\/div>\n
24<\/div>\n
25<\/div>\n
26<\/div>\n<\/td>\n
\n
\n
[root@dbi-pg-tools ~]<\/code># \/usr\/edb\/efm-3.3\/bin\/efm cluster-status efm<\/code><\/div>\n
Cluster Status: efm<\/code><\/div>\n
<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Agent Type\u00a0 Address\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Agent\u00a0 DB\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 VIP<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>-----------------------------------------------------------------------<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Witness\u00a0\u00a0\u00a0\u00a0 192.168.22.100\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 UP\u00a0\u00a0\u00a0\u00a0 N<\/code>\/A<\/code>\u00a0\u00a0\u00a0\u00a0\u00a0 192.168.22.105<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Master\u00a0\u00a0\u00a0\u00a0\u00a0 192.168.22.101\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 UP\u00a0\u00a0\u00a0\u00a0 UP\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 192.168.22.105*<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Standby\u00a0\u00a0\u00a0\u00a0 192.168.22.102\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 UP\u00a0\u00a0\u00a0\u00a0 UP\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 192.168.22.105<\/code><\/div>\n
<\/div>\n
Allowed node host list:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>192.168.22.101 192.168.22.102 192.168.22.100<\/code><\/div>\n
<\/div>\n
Membership coordinator: 192.168.22.101<\/code><\/div>\n
<\/div>\n
Standby priority host list:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>192.168.22.102<\/code><\/div>\n
<\/div>\n
Promote Status:<\/code><\/div>\n
<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>DB Type\u00a0\u00a0\u00a0\u00a0 Address\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 XLog Loc\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Info<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>--------------------------------------------------------------<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Master\u00a0\u00a0\u00a0\u00a0\u00a0 192.168.22.101\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0<\/code>\/301BEE0<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Standby\u00a0\u00a0\u00a0\u00a0 192.168.22.102\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0<\/code>\/301BEE0<\/code><\/div>\n
<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Standby database(s) <\/code>in<\/code> sync<\/code> with master. It is safe to promote.<\/code><\/div>\n
[root@dbi-pg-tools ~]<\/code>#<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

We can manually ping the virtual IP from both servers. There should not exist any loss packets<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n<\/td>\n
\n
\n
[root@dbi-pg-tools ~]<\/code># ping -q -c3 -w5 192.168.22.105<\/code><\/div>\n
PING 192.168.22.105 (192.168.22.105) 56(84) bytes of data.<\/code><\/div>\n
<\/div>\n
--- 192.168.22.105 <\/code>ping<\/code> statistics ---<\/code><\/div>\n
3 packets transmitted, 3 received, 0% packet loss, <\/code>time<\/code> 2001ms<\/code><\/div>\n
rtt min<\/code>\/avg\/max\/mdev<\/code> = 0.278<\/code>\/0<\/code>.366<\/code>\/0<\/code>.528<\/code>\/0<\/code>.116 ms<\/code><\/div>\n
[root@dbi-pg-tools ~]<\/code>#<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

And from the master we can see that the VIP address is assigned to enp0s9<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n<\/td>\n
\n
\n
[root@dbi-pg-essentials network-scripts]<\/code># ifconfig enp0s9\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/code><\/div>\n
enp0s9: flags=4163\u00a0 mtu 1500<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>inet 192.168.22.105\u00a0 netmask 255.255.255.0\u00a0 broadcast 0.0.0.0<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>ether 08:00:27:53:1c:ed\u00a0 txqueuelen 1000\u00a0 (Ethernet)<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>RX packets 3394\u00a0 bytes 397433 (388.1 KiB)<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>RX errors 0\u00a0 dropped 0\u00a0 overruns 0\u00a0 frame 0<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>TX packets 3096\u00a0 bytes 571448 (558.0 KiB)<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>TX errors 0\u00a0 dropped 0 overruns 0\u00a0 carrier 0\u00a0 collisions 0<\/code><\/div>\n
<\/div>\n
[root@dbi-pg-essentials network-scripts]<\/code>#<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

So we can use the virtual address to connect to the primary database<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n<\/td>\n
\n
\n
[postgres@dbi-pg-tools ~]$ psql -h 192.168.22.105<\/code><\/div>\n
Password <\/code>for<\/code> user postgres:<\/code><\/div>\n
psql (11.1)<\/code><\/div>\n
Type <\/code>\"help\"<\/code> for<\/code> help.<\/code><\/div>\n
<\/div>\n
postgres=<\/code># c sample<\/code><\/div>\n
You are now connected to database <\/code>\"sample\"<\/code> as user <\/code>\"postgres\"<\/code>.<\/code><\/div>\n
sample=<\/code># insert into mytab values(1);<\/code><\/div>\n
INSERT 0 1<\/code><\/div>\n
sample=<\/code>#<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

And now let\u2019s do a switchover<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n<\/td>\n
\n
\n
[root@dbi-pg-tools ~]<\/code># \/usr\/edb\/efm-3.3\/bin\/efm promote efm -switchover<\/code><\/div>\n
Promote<\/code>\/switchover<\/code> command<\/code> accepted by <\/code>local<\/code> agent. Proceeding with promotion and will reconfigure original master. Run the <\/code>'cluster-status'<\/code> command<\/code> for<\/code> information about the new cluster state.<\/code><\/div>\n
[root@dbi-pg-tools ~]<\/code>#<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

A few moment after the switchover, we can see that the vip is now assigned to the new master<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n<\/td>\n
\n
\n
[root@dbi-pg-essentials_2 efm-3.3]<\/code># ifconfig enp0s9<\/code><\/div>\n
enp0s9: flags=4163\u00a0 mtu 1500<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>inet 192.168.22.105\u00a0 netmask 255.255.255.0\u00a0 broadcast 0.0.0.0<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>ether 08:00:27:4d:4d:4d\u00a0 txqueuelen 1000\u00a0 (Ethernet)<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>RX packets 1235\u00a0 bytes 149947 (146.4 KiB)<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>RX errors 0\u00a0 dropped 0\u00a0 overruns 0\u00a0 frame 0<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>TX packets 837\u00a0 bytes 525953 (513.6 KiB)<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>TX errors 0\u00a0 dropped 0 overruns 0\u00a0 carrier 0\u00a0 collisions 0<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

That we can verify by running the status command<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n
15<\/div>\n
16<\/div>\n
17<\/div>\n
18<\/div>\n
19<\/div>\n
20<\/div>\n
21<\/div>\n
22<\/div>\n
23<\/div>\n
24<\/div>\n
25<\/div>\n
26<\/div>\n<\/td>\n
\n
\n
[root@dbi-pg-tools ~]<\/code># \/usr\/edb\/efm-3.3\/bin\/efm cluster-status efm<\/code><\/div>\n
Cluster Status: efm<\/code><\/div>\n
<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Agent Type\u00a0 Address\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Agent\u00a0 DB\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 VIP<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>-----------------------------------------------------------------------<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Witness\u00a0\u00a0\u00a0\u00a0 192.168.22.100\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 UP\u00a0\u00a0\u00a0\u00a0 N<\/code>\/A<\/code>\u00a0\u00a0\u00a0\u00a0\u00a0 192.168.22.105<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Standby\u00a0\u00a0\u00a0\u00a0 192.168.22.101\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 UP\u00a0\u00a0\u00a0\u00a0 UP\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 192.168.22.105<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Master\u00a0\u00a0\u00a0\u00a0\u00a0 192.168.22.102\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 UP\u00a0\u00a0\u00a0\u00a0 UP\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 192.168.22.105*<\/code><\/div>\n
<\/div>\n
Allowed node host list:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>192.168.22.101 192.168.22.102 192.168.22.100<\/code><\/div>\n
<\/div>\n
Membership coordinator: 192.168.22.102<\/code><\/div>\n
<\/div>\n
Standby priority host list:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>192.168.22.101<\/code><\/div>\n
<\/div>\n
Promote Status:<\/code><\/div>\n
<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>DB Type\u00a0\u00a0\u00a0\u00a0 Address\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 XLog Loc\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Info<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>--------------------------------------------------------------<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Master\u00a0\u00a0\u00a0\u00a0\u00a0 192.168.22.102\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0<\/code>\/301E260<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Standby\u00a0\u00a0\u00a0\u00a0 192.168.22.101\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0<\/code>\/301E260<\/code><\/div>\n
<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Standby database(s) <\/code>in<\/code> sync<\/code> with master. It is safe to promote.<\/code><\/div>\n
[root@dbi-pg-tools ~]<\/code>#<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

Conclusion :<\/h3>\n

In this blog we have seen how we can configure a virtual IP with EFM. Hope that will help<\/p>\n","protected":false},"excerpt":{"rendered":"

By Mouhamadou Diaw In a previous blog , I talked about installing and configuring Edb Failover Manager with PostgreSQL. The configuration of a Virtual Ip Address was not discussed in this previous article.In this blog I am going to show how we can implement a virtual IP with EFM. We suppose that -The standby is […]<\/p>\n","protected":false},"author":27,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[229,83],"tags":[1537,1538,1539,77,1323],"type_dbi":[],"class_list":["post-12177","post","type-post","status-publish","format-standard","hentry","category-database-administration-monitoring","category-postgresql","tag-edb-efm","tag-edb-failover-manager","tag-high-ava","tag-postgresql","tag-postgresql-11"],"acf":[],"yoast_head":"\nEDB Failover Manager 3.3 With Virtual Ip Address - dbi Blog<\/title>\n<meta name=\"description\" content=\"PostGreSQL, PostgreSQL 11, edb efm, edb failover manager, High Ava\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-3-3-with-virtual-ip-address\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"EDB Failover Manager 3.3 With Virtual Ip Address\" \/>\n<meta property=\"og:description\" content=\"PostGreSQL, PostgreSQL 11, edb efm, edb failover manager, High Ava\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-3-3-with-virtual-ip-address\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2018-12-24T09:47:07+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2023-06-15T14:33:55+00:00\" \/>\n<meta name=\"author\" content=\"Oracle Team\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Oracle Team\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-3-3-with-virtual-ip-address\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-3-3-with-virtual-ip-address\/\"},\"author\":{\"name\":\"Oracle Team\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee\"},\"headline\":\"EDB Failover Manager 3.3 With Virtual Ip Address\",\"datePublished\":\"2018-12-24T09:47:07+00:00\",\"dateModified\":\"2023-06-15T14:33:55+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-3-3-with-virtual-ip-address\/\"},\"wordCount\":275,\"commentCount\":2,\"keywords\":[\"edb efm\",\"edb failover manager\",\"High Ava\",\"PostgreSQL\",\"PostgreSQL 11\"],\"articleSection\":[\"Database Administration & Monitoring\",\"PostgreSQL\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-3-3-with-virtual-ip-address\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-3-3-with-virtual-ip-address\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-3-3-with-virtual-ip-address\/\",\"name\":\"EDB Failover Manager 3.3 With Virtual Ip Address - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2018-12-24T09:47:07+00:00\",\"dateModified\":\"2023-06-15T14:33:55+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee\"},\"description\":\"PostGreSQL, PostgreSQL 11, edb efm, edb failover manager, High Ava\",\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-3-3-with-virtual-ip-address\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-3-3-with-virtual-ip-address\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-3-3-with-virtual-ip-address\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"EDB Failover Manager 3.3 With Virtual Ip Address\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee\",\"name\":\"Oracle Team\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g\",\"caption\":\"Oracle Team\"},\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/oracle-team\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"EDB Failover Manager 3.3 With Virtual Ip Address - dbi Blog","description":"PostGreSQL, PostgreSQL 11, edb efm, edb failover manager, High Ava","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-3-3-with-virtual-ip-address\/","og_locale":"en_US","og_type":"article","og_title":"EDB Failover Manager 3.3 With Virtual Ip Address","og_description":"PostGreSQL, PostgreSQL 11, edb efm, edb failover manager, High Ava","og_url":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-3-3-with-virtual-ip-address\/","og_site_name":"dbi Blog","article_published_time":"2018-12-24T09:47:07+00:00","article_modified_time":"2023-06-15T14:33:55+00:00","author":"Oracle Team","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Oracle Team","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-3-3-with-virtual-ip-address\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-3-3-with-virtual-ip-address\/"},"author":{"name":"Oracle Team","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee"},"headline":"EDB Failover Manager 3.3 With Virtual Ip Address","datePublished":"2018-12-24T09:47:07+00:00","dateModified":"2023-06-15T14:33:55+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-3-3-with-virtual-ip-address\/"},"wordCount":275,"commentCount":2,"keywords":["edb efm","edb failover manager","High Ava","PostgreSQL","PostgreSQL 11"],"articleSection":["Database Administration & Monitoring","PostgreSQL"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-3-3-with-virtual-ip-address\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-3-3-with-virtual-ip-address\/","url":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-3-3-with-virtual-ip-address\/","name":"EDB Failover Manager 3.3 With Virtual Ip Address - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2018-12-24T09:47:07+00:00","dateModified":"2023-06-15T14:33:55+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee"},"description":"PostGreSQL, PostgreSQL 11, edb efm, edb failover manager, High Ava","breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-3-3-with-virtual-ip-address\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-3-3-with-virtual-ip-address\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-3-3-with-virtual-ip-address\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"EDB Failover Manager 3.3 With Virtual Ip Address"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee","name":"Oracle Team","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g","caption":"Oracle Team"},"url":"https:\/\/www.dbi-services.com\/blog\/author\/oracle-team\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/12177","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/27"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=12177"}],"version-history":[{"count":1,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/12177\/revisions"}],"predecessor-version":[{"id":25939,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/12177\/revisions\/25939"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=12177"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=12177"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=12177"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=12177"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}