DR replication Stoped after failover

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • seyiisq
    New Member
    • Jul 2018
    • 2

    DR replication Stoped after failover

    Dear Team,

    Recently, our staging database environment was not available so we had to promote the DR database using the script below.

    Code:
    [root@DRPOSDB tmp]# su postgres
    bash-4.2$
    bash-4.2$
    bash-4.2$
    bash-4.2$
    bash-4.2$ /usr/pgsql-9.2/bin/pg_ctl -D /target_directory promote
    pg_ctl: PID file "/target_directory/postmaster.pid" does not exist
    Is server running?
    bash-4.2$
    bash-4.2$
    bash-4.2$ locate postmaster.pid
    /var/lib/pgsql/9.2/data/postmaster.pid
    bash-4.2$
    bash-4.2$
    bash-4.2$ /usr/pgsql-9.2/bin/pg_ctl -D /var/lib/pgsql/9.2/data promote
    server promoting
    bash-4.2$
    bash-4.2$
    bash-4.2$
    bash-4.2$
    No changes was made to the database while in DR because the live came up alomost immediately.

    Now replication as stopped because DR was promoted from slave to master. Also, data has started coming to LIVE database.

    How do we make replication to start again, i have not been able to see any documentation to do this.
  • zmbd
    Recognized Expert Moderator Expert
    • Mar 2012
    • 5501

    #2
    Never worked with PostGreSql; however, looking through some documentation about this database I found this:

    It mentions that this feature was added to PostgreSQL 9.0 - so I think this might be available; however, you don't mention which version you're using.

    Towards the bottom of this page it mentions repeating from Step 6 - Might be a starting point.
    Last edited by zmbd; Jul 29 '18, 04:55 PM.

    Comment

    • seyiisq
      New Member
      • Jul 2018
      • 2

      #3
      Thanks zmbd,

      This is like revisiting the setup again. I will GI through it and get back.

      I am currently on postgres9.2

      Comment

      • zmbd
        Recognized Expert Moderator Expert
        • Mar 2012
        • 5501

        #4
        Best of Luck - hopefully one of the other experts has more experience with this DB

        Comment

        Working...