4 Replies

  • There is a saying ... "NEVER restore DCs or replicate DCs (VMs)". Yuo should always have at least 2 DCs per network.

    There are a lot of Domain Objects that are time sensitive, depending on what servers are there in your Domain, you should never replicate a Domain Controller. If you need, you should be running a DC and backup solution (eg backup server, VCSA) at the DR site already.

    Pepper graySpice (1) flagReport
    1 found this helpful thumb_up thumb_down
  • spicehead-18hlj wrote:

    If under EFM Cluster contains
    • VMware 1 contrains for DC
        - ESX1
           - VMguest1
              - PostgreSQL - Priority 1st
              - EFM VIP
              - EFM
              - App_A(Active)
        - ESX2
          - VMguest2
             - PostgreSQL - Priority 2nd
             - EFM
             - App_A(Passive)
    • VMware 2 contrains for DR
        - ESX3
         - VMguest3
             - PostgreSQL - Priority 3nd
             - EFM
            - App_A(Passive)
    -Can EFM call App_A startup script for starting up after VIP relocates to VMGuest2 and PostgreSQL on VMGuest2 is the new primary?
    Thank you

    Wats EFM ? Wats ESX ? Where vCenter ?

    Use Veeam Backup & Replication 11.x to backup & then use backup data sets to replicate VMs, EXCEPT for Domain Controllers (have 3rd DC at DR site)

    Pepper graySpice (1) flagReport
    1 found this helpful thumb_up thumb_down
  • Hi, and welcome to the Community!

    As already mentioned by Adrian, there is no sense in using application-based HA/Failover options when running a virtual environment. You should do those kinds of things at the hypervisor level operating your virtual machines as complete objects https://www.vmwareblog.org/starting-vmware-6-things-beginners-know/. vSphere Replication or 3rd party options like Veeam B&R will have you covered.

    Was this post helpful? thumb_up thumb_down
  • Let’s have a look at the three-node cluster architecture of EDB Postgres Failover Manager with one master and two standbys. EDB Postgres Failover Manager with Multi-node Cluster You can see EFM agents I, II, and III have a hard line for the local database and a dashed line for remote databases. The definition of two are given below: 
     Hard lines mean continuous monitoring of the local database.
     Dashed lines mean on-demand remote database health check i.e. if an EFM agent fails to connect to the local database due to some reason it asks EFM agents on the other nodes to confirm if they can reach out to the database.
    J Wick
    Was this post helpful? thumb_up thumb_down

Read these next...