{"id":8815,"date":"2016-09-08T10:53:51","date_gmt":"2016-09-08T08:53:51","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-2-1-upgrading\/"},"modified":"2016-09-08T10:53:51","modified_gmt":"2016-09-08T08:53:51","slug":"edb-failover-manager-2-1-upgrading","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-2-1-upgrading\/","title":{"rendered":"EDB Failover Manager 2.1, upgrading"},"content":{"rendered":"

Some days ago EnterpriseDB<\/a> released a new version of its EDB Failover Manager<\/a> which brings one feature that really sounds great: “Controlled switchover and switchback for easier maintenance and disaster recovery tests”. This is exactly what you want when you are used to operate Oracle DataGuard. Switching back and forward as you like without caring much about the old master. The old master shall just be converted to a standby which follows the new master automatically. This post is about upgrading EFM from version 2.0 to 2.1.<\/p>\n

<\/p>\n

As I still have the environment available which was used for describing the maintenance scenarios with EDB Failover Manager (Maintenance scenarios with EDB Failover Manager (1) \u2013 Standby node<\/a>, Maintenance scenarios with EDB Failover Manager (2) \u2013 Primary node<\/a> and Maintenance scenarios with EDB Failover Manager (3) \u2013 Witness node<\/a>) I will use the same environment to upgrade to the new release. Lets start …<\/p>\n

This is the current status of my failover cluster:<\/p>\n

\n[root@edbbart ~]$ \/usr\/edb-efm\/bin\/efm cluster-status efm \nCluster Status: efm\nAutomatic failover is disabled.\n\n\tAgent Type  Address              Agent  DB       Info\n\t--------------------------------------------------------------\n\tMaster      192.168.22.245       UP     UP        \n\tWitness     192.168.22.244       UP     N\/A       \n\tStandby     192.168.22.243       UP     UP        \n\nAllowed node host list:\n\t192.168.22.244 192.168.22.245 192.168.22.243\n\nStandby priority host list:\n\t192.168.22.243\n\nPromote Status:\n\n\tDB Type     Address              XLog Loc         Info\n\t--------------------------------------------------------------\n\tMaster      192.168.22.245       0\/3B01C5E0       \n\tStandby     192.168.22.243       0\/3B01C5E0       \n\n\tStandby database(s) in sync with master. It is safe to promote.\n[root@edbbart ~]$ \n<\/pre>\n
Obviously you have to download the new version<\/a> to begin the upgrade. Once the rpm is available on all nodes simply install it on all the nodes:<\/p>\n
\n[root@edbppas tmp]$ yum localinstall efm21-2.1.0-1.rhel7.x86_64.rpm\n<\/pre>\n
EFM 2.1 comes with an utility command that helps in upgrading a cluster. You should invoke it on each node:<\/p>\n
\n[root@edbbart tmp]$ \/usr\/efm-2.1\/bin\/efm upgrade-conf efm\nProcessing efm.properties file.\nSetting new property node.timeout to 40 (sec) based on existing timeout 5000 (ms) and max tries 8.\n\nProcessing efm.nodes file.\n\nUpgrade of files is finished. Please ensure that the new file permissions match those of the template files before starting EFM.\nThe db.service.name property should be set before starting a non-witness agent.\n<\/pre>\n
This created a new configuration file in the new directory under \/etc which was created when the new version was installed:<\/p>\n
\n[root@edbbart tmp]$ ls \/etc\/efm-2.1\nefm.nodes  efm.nodes.in  efm.properties  efm.properties.in\n<\/pre>\n
All the values from the old EFM cluster should be there in the new configuration files:<\/p>\n
\n[root@edbbart efm-2.1]$ pwd\n\/etc\/efm-2.1\n[root@edbbart efm-2.1]$ cat efm.properties | grep daniel\nuser.email=daniel.westermann...\n<\/pre>\n
Before going further check the new configuration parameters for EFM 2.1, which are:<\/p>\n
\nauto.allow.hosts\nauto.resume.period\ndb.service.name\njvm.options\nminimum.standbys\nnode.timeout\npromotable\nrecovery.check.period\nscript.notification\nscript.resumed\n<\/pre>\n
I’ll leave everything as it was before for now. Notice that a new service got created:<\/p>\n
\n[root@edbppas efm-2.1]$ systemctl list-unit-files | grep efm\nefm-2.0.service                             enabled \nefm-2.1.service                             disabled\n<\/pre>\n
Lets try to shutdown the old service on all nodes and then start the new one. Step 1 (on all nodes):<\/p>\n
\n[root@edbppas efm-2.1]$ systemctl stop efm-2.0.service\n[root@edbppas efm-2.1]$ systemctl disable efm-2.0.service\nrm '\/etc\/systemd\/system\/multi-user.target.wants\/efm-2.0.service'\n<\/pre>\n
Then enable the new service:<\/p>\n
\n[root@edbppas efm-2.1]$ systemctl enable efm-2.1.service\nln -s '\/usr\/lib\/systemd\/system\/efm-2.1.service' '\/etc\/systemd\/system\/multi-user.target.wants\/efm-2.1.service'\n[root@edbppas efm-2.1]$ systemctl list-unit-files | grep efm\nefm-2.0.service                             disabled\nefm-2.1.service                             enabled \n<\/pre>\n
Make sure your efm.nodes file contains all the nodes which make up the cluster, in my case:<\/p>\n
\n[root@edbppas efm-2.1]$ cat efm.nodes\n# List of node address:port combinations separated by whitespace.\n# The list should include at least the membership coordinator's address.\n192.168.22.243:9998 192.168.22.244:9998 192.168.22.245:9998\n<\/pre>\n
Lets try to start the new service on the witness node first:<\/p>\n
\n[root@edbbart efm-2.1]$ systemctl start efm-2.1.service\n[root@edbbart efm-2.1]$ \/usr\/edb-efm\/bin\/efm cluster-status efm \nCluster Status: efm\nVIP: 192.168.22.250\nAutomatic failover is disabled.\n\n\tAgent Type  Address              Agent  DB       Info\n\t--------------------------------------------------------------\n\tWitness     192.168.22.244       UP     N\/A       \n\nAllowed node host list:\n\t192.168.22.244\n\nMembership coordinator: 192.168.22.244\n\nStandby priority host list:\n\t(List is empty.)\n\nPromote Status:\n\nDid not find XLog location for any nodes.\n<\/pre>\n
Looks good. Are we really running the new version?<\/p>\n
\n[root@edbbart efm-2.1]$ \/usr\/edb-efm\/bin\/efm -v\nFailover Manager, version 2.1.0\n<\/pre>\n
Looks fine as well. Time to add the other nodes:<\/p>\n
\n[root@edbbart efm-2.1]$ \/usr\/edb-efm\/bin\/efm add-node efm 192.168.22.243\nadd-node signal sent to local agent.\n[root@edbbart efm-2.1]$ \/usr\/edb-efm\/bin\/efm add-node efm 192.168.22.245\nadd-node signal sent to local agent.\n[root@edbbart efm-2.1]$ \/usr\/edb-efm\/bin\/efm cluster-status efm \nCluster Status: efm\nVIP: 192.168.22.250\nAutomatic failover is disabled.\n\n\tAgent Type  Address              Agent  DB       Info\n\t--------------------------------------------------------------\n\tWitness     192.168.22.244       UP     N\/A       \n\nAllowed node host list:\n\t192.168.22.244 192.168.22.243\n\nMembership coordinator: 192.168.22.244\n\nStandby priority host list:\n\t(List is empty.)\n\nPromote Status:\n\nDid not find XLog location for any nodes.\n<\/pre>\n
Proceed on the master:<\/p>\n
\n[root@ppasstandby efm-2.1]$ systemctl start efm-2.1.service\n[root@ppasstandby efm-2.1]$ systemctl status efm-2.1.service\nefm-2.1.service - EnterpriseDB Failover Manager 2.1\n   Loaded: loaded (\/usr\/lib\/systemd\/system\/efm-2.1.service; enabled)\n   Active: active (running) since Thu 2016-09-08 12:04:11 CEST; 25s ago\n  Process: 4020 ExecStart=\/bin\/bash -c \/usr\/efm-2.1\/bin\/runefm.sh start ${CLUSTER} (code=exited, status=0\/SUCCESS)\n Main PID: 4075 (java)\n   CGroup: \/system.slice\/efm-2.1.service\n           \u2514\u25004075 \/usr\/lib\/jvm\/java-1.8.0-openjdk-1.8.0.77-0.b03.el7_2.x86_64\/jre\/bin\/java -cp \/usr\/e...\n\nSep 08 12:04:07 ppasstandby systemd[1]: Starting EnterpriseDB Failover Manager 2.1...\nSep 08 12:04:08 ppasstandby sudo[4087]: efm : TTY=unknown ; PWD=\/ ; USER=root ; COMMAND=\/usr\/efm-... efm\nSep 08 12:04:08 ppasstandby sudo[4098]: efm : TTY=unknown ; PWD=\/ ; USER=root ; COMMAND=\/usr\/efm-... efm\nSep 08 12:04:08 ppasstandby sudo[4114]: efm : TTY=unknown ; PWD=\/ ; USER=postgres ; COMMAND=\/usr\/... efm\nSep 08 12:04:08 ppasstandby sudo[4125]: efm : TTY=unknown ; PWD=\/ ; USER=postgres ; COMMAND=\/usr\/... efm\nSep 08 12:04:10 ppasstandby sudo[4165]: efm : TTY=unknown ; PWD=\/ ; USER=root ; COMMAND=\/usr\/efm-...9998\nSep 08 12:04:10 ppasstandby sudo[4176]: efm : TTY=unknown ; PWD=\/ ; USER=root ; COMMAND=\/usr\/efm-...4075\nSep 08 12:04:11 ppasstandby systemd[1]: Started EnterpriseDB Failover Manager 2.1.\nHint: Some lines were ellipsized, use -l to show in full.\n<\/pre>\n
And then continue on the standby:<\/p>\n
\n[root@edbppas efm-2.1]$ systemctl start efm-2.1.service\n[root@edbppas efm-2.1]$ systemctl status efm-2.1.service\nefm-2.1.service - EnterpriseDB Failover Manager 2.1\n   Loaded: loaded (\/usr\/lib\/systemd\/system\/efm-2.1.service; enabled)\n   Active: active (running) since Thu 2016-09-08 12:05:28 CEST; 3s ago\n  Process: 3820 ExecStart=\/bin\/bash -c \/usr\/efm-2.1\/bin\/runefm.sh start ${CLUSTER} (code=exited, status=0\/SUCCESS)\n Main PID: 3875 (java)\n   CGroup: \/system.slice\/efm-2.1.service\n           \u2514\u25003875 \/usr\/lib\/jvm\/java-1.8.0-openjdk-1.8.0.77-0.b03.el7_2.x86_64\/jre\/bin\/jav...\n\nSep 08 12:05:24 edbppas systemd[1]: Starting EnterpriseDB Failover Manager 2.1...\nSep 08 12:05:25 edbppas sudo[3887]: efm : TTY=unknown ; PWD=\/ ; USER=root ; COMMAND=\/u...efm\nSep 08 12:05:25 edbppas sudo[3898]: efm : TTY=unknown ; PWD=\/ ; USER=root ; COMMAND=\/u...efm\nSep 08 12:05:25 edbppas sudo[3914]: efm : TTY=unknown ; PWD=\/ ; USER=postgres ; COMMAN...efm\nSep 08 12:05:25 edbppas sudo[3925]: efm : TTY=unknown ; PWD=\/ ; USER=postgres ; COMMAN...efm\nSep 08 12:05:25 edbppas sudo[3945]: efm : TTY=unknown ; PWD=\/ ; USER=postgres ; COMMAN...efm\nSep 08 12:05:28 edbppas sudo[3981]: efm : TTY=unknown ; PWD=\/ ; USER=root ; COMMAND=\/u...998\nSep 08 12:05:28 edbppas sudo[3994]: efm : TTY=unknown ; PWD=\/ ; USER=root ; COMMAND=\/u...875\nSep 08 12:05:28 edbppas systemd[1]: Started EnterpriseDB Failover Manager 2.1.\nHint: Some lines were ellipsized, use -l to show in full.\n<\/pre>\n
What is the cluster status now?:<\/p>\n
\n[root@edbbart efm-2.1]$ \/usr\/edb-efm\/bin\/efm cluster-status efm \nCluster Status: efm\nVIP: 192.168.22.250\nAutomatic failover is disabled.\n\n\tAgent Type  Address              Agent  DB       Info\n\t--------------------------------------------------------------\n\tMaster      192.168.22.245       UP     UP        \n\tWitness     192.168.22.244       UP     N\/A       \n\tStandby     192.168.22.243       UP     UP        \n\nAllowed node host list:\n\t192.168.22.244 192.168.22.243 192.168.22.245\n\nMembership coordinator: 192.168.22.244\n\nStandby priority host list:\n\t192.168.22.243\n\nPromote Status:\n\n\tDB Type     Address              XLog Loc         Info\n\t--------------------------------------------------------------\n\tMaster      192.168.22.245       0\/3B01C7A0       \n\tStandby     192.168.22.243       0\/3B01C7A0       \n\n\tStandby database(s) in sync with master. It is safe to promote.\n<\/pre>\n
Cool. Back in operation on the new release. Quite easy.<\/p>\n
PS: Remember to re-point your symlinks in \/etc and \/usr if you created symlinks for easy of use.<\/p>\n","protected":false},"excerpt":{"rendered":"
Some days ago EnterpriseDB released a new version of its EDB Failover Manager which brings one feature that really sounds great: “Controlled switchover and switchback for easier maintenance and disaster recovery tests”. This is exactly what you want when you are used to operate Oracle DataGuard. Switching back and forward as you like without caring […]<\/p>\n","protected":false},"author":29,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[229],"tags":[713,464,77],"type_dbi":[],"class_list":["post-8815","post","type-post","status-publish","format-standard","hentry","category-database-administration-monitoring","tag-enterprisedb","tag-failover-cluster","tag-postgresql"],"acf":[],"yoast_head":"\nEDB Failover Manager 2.1, upgrading - dbi Blog<\/title>\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-2-1-upgrading\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"EDB Failover Manager 2.1, upgrading\" \/>\n<meta property=\"og:description\" content=\"Some days ago EnterpriseDB released a new version of its EDB Failover Manager which brings one feature that really sounds great: “Controlled switchover and switchback for easier maintenance and disaster recovery tests”. This is exactly what you want when you are used to operate Oracle DataGuard. Switching back and forward as you like without caring […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-2-1-upgrading\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2016-09-08T08:53:51+00:00\" \/>\n<meta name=\"author\" content=\"Daniel Westermann\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@westermanndanie\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Daniel Westermann\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 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-2-1-upgrading\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-2-1-upgrading\/\"},\"author\":{\"name\":\"Daniel Westermann\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66\"},\"headline\":\"EDB Failover Manager 2.1, upgrading\",\"datePublished\":\"2016-09-08T08:53:51+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-2-1-upgrading\/\"},\"wordCount\":386,\"commentCount\":0,\"keywords\":[\"enterprisedb\",\"Failover cluster\",\"PostgreSQL\"],\"articleSection\":[\"Database Administration & Monitoring\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-2-1-upgrading\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-2-1-upgrading\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-2-1-upgrading\/\",\"name\":\"EDB Failover Manager 2.1, upgrading - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2016-09-08T08:53:51+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-2-1-upgrading\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-2-1-upgrading\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-2-1-upgrading\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"EDB Failover Manager 2.1, upgrading\"}]},{\"@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\/8d08e9bd996a89bd75c0286cbabf3c66\",\"name\":\"Daniel Westermann\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g\",\"caption\":\"Daniel Westermann\"},\"description\":\"Daniel Westermann is Principal Consultant and Technology Leader Open Infrastructure at dbi services. He has more than 15 years of experience in management, engineering and optimization of databases and infrastructures, especially on Oracle and PostgreSQL. Since the beginning of his career, he has specialized in Oracle Technologies and is Oracle Certified Professional 12c and Oracle Certified Expert RAC\/GridInfra. Over time, Daniel has become increasingly interested in open source technologies, becoming \u201cTechnology Leader Open Infrastructure\u201d and PostgreSQL expert. \u00a0Based on community or EnterpriseDB tools, he develops and installs complex high available solutions with PostgreSQL. He is also a certified PostgreSQL Plus 9.0 Professional and a Postgres Advanced Server 9.4 Professional. He is a regular speaker at PostgreSQL conferences in Switzerland and Europe. Today Daniel is also supporting our customers on AWS services such as AWS RDS, database migrations into the cloud, EC2 and automated infrastructure management with AWS SSM (System Manager). He is a certified AWS Solutions Architect Professional. Prior to dbi services, Daniel was Management System Engineer at LC SYSTEMS-Engineering AG in Basel. Before that, he worked as Oracle Developper &\u00a0Project Manager at Delta Energy Solutions AG in Basel (today Powel AG). Daniel holds a diploma in Business Informatics (DHBW, Germany). His branch-related experience mainly covers the pharma industry, the financial sector, energy, lottery and telecommunications.\",\"sameAs\":[\"https:\/\/x.com\/westermanndanie\"],\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/daniel-westermann\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"EDB Failover Manager 2.1, upgrading - dbi Blog","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-2-1-upgrading\/","og_locale":"en_US","og_type":"article","og_title":"EDB Failover Manager 2.1, upgrading","og_description":"Some days ago EnterpriseDB released a new version of its EDB Failover Manager which brings one feature that really sounds great: “Controlled switchover and switchback for easier maintenance and disaster recovery tests”. This is exactly what you want when you are used to operate Oracle DataGuard. Switching back and forward as you like without caring […]","og_url":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-2-1-upgrading\/","og_site_name":"dbi Blog","article_published_time":"2016-09-08T08:53:51+00:00","author":"Daniel Westermann","twitter_card":"summary_large_image","twitter_creator":"@westermanndanie","twitter_misc":{"Written by":"Daniel Westermann","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-2-1-upgrading\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-2-1-upgrading\/"},"author":{"name":"Daniel Westermann","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66"},"headline":"EDB Failover Manager 2.1, upgrading","datePublished":"2016-09-08T08:53:51+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-2-1-upgrading\/"},"wordCount":386,"commentCount":0,"keywords":["enterprisedb","Failover cluster","PostgreSQL"],"articleSection":["Database Administration & Monitoring"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-2-1-upgrading\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-2-1-upgrading\/","url":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-2-1-upgrading\/","name":"EDB Failover Manager 2.1, upgrading - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2016-09-08T08:53:51+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-2-1-upgrading\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-2-1-upgrading\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-2-1-upgrading\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"EDB Failover Manager 2.1, upgrading"}]},{"@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\/8d08e9bd996a89bd75c0286cbabf3c66","name":"Daniel Westermann","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g","caption":"Daniel Westermann"},"description":"Daniel Westermann is Principal Consultant and Technology Leader Open Infrastructure at dbi services. He has more than 15 years of experience in management, engineering and optimization of databases and infrastructures, especially on Oracle and PostgreSQL. Since the beginning of his career, he has specialized in Oracle Technologies and is Oracle Certified Professional 12c and Oracle Certified Expert RAC\/GridInfra. Over time, Daniel has become increasingly interested in open source technologies, becoming \u201cTechnology Leader Open Infrastructure\u201d and PostgreSQL expert. \u00a0Based on community or EnterpriseDB tools, he develops and installs complex high available solutions with PostgreSQL. He is also a certified PostgreSQL Plus 9.0 Professional and a Postgres Advanced Server 9.4 Professional. He is a regular speaker at PostgreSQL conferences in Switzerland and Europe. Today Daniel is also supporting our customers on AWS services such as AWS RDS, database migrations into the cloud, EC2 and automated infrastructure management with AWS SSM (System Manager). He is a certified AWS Solutions Architect Professional. Prior to dbi services, Daniel was Management System Engineer at LC SYSTEMS-Engineering AG in Basel. Before that, he worked as Oracle Developper &\u00a0Project Manager at Delta Energy Solutions AG in Basel (today Powel AG). Daniel holds a diploma in Business Informatics (DHBW, Germany). His branch-related experience mainly covers the pharma industry, the financial sector, energy, lottery and telecommunications.","sameAs":["https:\/\/x.com\/westermanndanie"],"url":"https:\/\/www.dbi-services.com\/blog\/author\/daniel-westermann\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/8815","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\/29"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=8815"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/8815\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=8815"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=8815"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=8815"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=8815"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}