Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-9687

Oracle High Availability Dataguard

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Answered
    • None
    • None
    • standalone,confluence 2.5.7, jdk14, solaris, oracle 10.2.0.3
    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      1. Primary Datacenter Confluence uses Database A.
      2. Database A used oracle high availability dataguard to Secondary Datacenter Database B.
      3. Confluence Instance in Primary Datacenter and Confluence in Secondary Datacenter are dns'd in a failover situation
      4. If Primary Datacenter is lost - automatically seemlessly fails over to Secondary Confluence Instance.
      5. End User see's no downtime or knows they were directed to the failover environment.

      We've tested this type of setup in our development environment.

      When the Secondary Confluence Instance connects to Database B it sees the connections that are created by Oracle Dataguard - user Public as a cluster and shuts down.

      If there is a way to get the secondary confluence instance to connect to database B, we'd be buying another unlimited commercial license.

        1. confluence-OracleDataguard.PNG
          confluence-OracleDataguard.PNG
          25 kB

            [CONFSERVER-9687] Oracle High Availability Dataguard

            Matt Ryall added a comment -

            Confluence only supports a single coherent database, Jeremiah. Our clustered license is for application server redundancy using a clustered in-memory cache.

            You can cluster your database using your vendor's tools, but to Confluence it must appear as a single DBMS.

            If you need any further assistance, please raise a support ticket at https://support.atlassian.com. This JIRA instance is for tracking feature requests and reproducible bugs in Confluence.

            Matt Ryall added a comment - Confluence only supports a single coherent database, Jeremiah. Our clustered license is for application server redundancy using a clustered in-memory cache. You can cluster your database using your vendor's tools, but to Confluence it must appear as a single DBMS. If you need any further assistance, please raise a support ticket at https://support.atlassian.com . This JIRA instance is for tracking feature requests and reproducible bugs in Confluence.

            Jeremiah Selander added a comment -

            Yes, I'm having problems with this configuration.

            I would like any support I can get.

            It kinda just came to me, should these instances be clustered even though they are in different datacenters?

            Jeremiah Selander added a comment - Yes, I'm having problems with this configuration. I would like any support I can get. It kinda just came to me, should these instances be clustered even though they are in different datacenters?

            Matt Ryall added a comment -

            Jeremiah, I think I understand your set-up, but I don't understand the problem.

            Do you have problems with this configuration? Do you want us to support it?

            Matt Ryall added a comment - Jeremiah, I think I understand your set-up, but I don't understand the problem. Do you have problems with this configuration? Do you want us to support it?

            Jeremiah Selander added a comment -

            Attaching png for clarity.

            Jeremiah Selander added a comment - Attaching png for clarity.

              Unassigned Unassigned
              691674ea1a9a Jeremiah Selander
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: