• Icon: Task Task
    • Resolution: Unresolved
    • Icon: L3 - Default L3 - Default
    • None
    • None
    • documentation
    • 2
    • Not defined

      For C7 and C8 Self-Managed customers running their own Elasticsearch databases, some customers (SUPPORT-11492) want to back up a limited part of their Optimize databases. We could use the existing Elasticsearch snapshotting, targeting specific indices.

      Optimize has separate indexes for each of the following:

      • process reports
      • decision reports
      • combined reports
      • dashboards
      • collections
      • alerts
        In addition, there are indices for dashboard and report shares

      We should provide a 'menu of options' with instructions for:
      1. Full Backup: If you recover from this backup, Optimize will look just like it did when it was backed up. Any data in the engine may need to be reimported, but you don't lose archival data that exceeded the engine's TTL
      2: Config-Backup: If you recover from this backup, Optimize will look exactly how you left it, but be empty. While the obvious indices are reports, dashboards, collections, alerts, and shares, there may be additional scope once an engineer takes a closer look

        This is the controller panel for Smart Panels app

            [OPT-6082] Document how to back up Optimize data

            This ticket was migrated to github: https://github.com/camunda/camunda-optimize/issues/10267. Please use this link for any future references and continue any discussion there.

            Omran Abazeed added a comment - This ticket was migrated to github: https://github.com/camunda/camunda-optimize/issues/10267 . Please use this link for any future references and continue any discussion there.

              Unassigned Unassigned
              eric.lundberg Eric Lundberg
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: