Uploaded image for project: 'Solution Center'
  1. Solution Center
  2. SOL-237

Synchronising backups between clusters

    Details

    • Type: How To
    • Status: Obsolete
    • Affects Version/s: EXASOL 6.0.0
    • Fix Version/s: None
    • Component/s: EXAoperation
    • Labels:
      None
    • Solution:
      Hide

      Note: This solution is no longer maintained. For the latest information, please visit our Knowledge Base:

      https://community.exasol.com/t5/environment-management/synchronising-backups-between-clusters/ta-p/1423

      In case of using two or more database clusters, backups can be stored "cross-over" for failsafety reasons. The scenario might look like this:

               CLUSTER 1                             CLUSTER 2
         +-------------------+                +---------------------+
         |      DB(1)---------------+         |         DB(2)       |
         |                   |      |         |           |         |
         |                   |      |         |           |         |
         |  Archive Volume <------------------------------+         |
         |                   |      |         |                     |
         |                   |      |------------> Archive Volume   |
         +-------------------+                +---------------------+
      

      To achieve this, two remote volumes must be defined:

      1. The first one in cluster 1, referencing an archive volume in cluster 2. In this example, we reference a volume v0002:
        ftp://{IP address or comma-separated IP addresses in cluster 2}:2021/v0002
        

        For user and password, enter a valid EXAoperation account of cluster 2.

      1. The second one in cluster 2 referencing an archive volume in cluster 1.

      Please note: In case, backups should also be usable by the respective remote database (e.g. database 2 should be able to restore a backup from within its local archive volume written by remote database 1), the remote archive volume option

      nocompression
      

      must be used.

      Prior to version 6.0, it was not possible to use this approach for creating backups cross-wise. However, it was possible to use it in one direction.

      Show
      Note: This solution is no longer maintained. For the latest information, please visit our Knowledge Base: https://community.exasol.com/t5/environment-management/synchronising-backups-between-clusters/ta-p/1423 In case of using two or more database clusters, backups can be stored "cross-over" for failsafety reasons. The scenario might look like this: CLUSTER 1 CLUSTER 2 +-------------------+ +---------------------+ | DB(1)---------------+ | DB(2) | | | | | | | | | | | | | | Archive Volume <------------------------------+ | | | | | | | | |------------> Archive Volume | +-------------------+ +---------------------+ To achieve this, two remote volumes must be defined: The first one in cluster 1, referencing an archive volume in cluster 2. In this example, we reference a volume v0002: ftp://{IP address or comma-separated IP addresses in cluster 2}:2021/v0002 For user and password, enter a valid EXAoperation account of cluster 2. The second one in cluster 2 referencing an archive volume in cluster 1. Please note: In case, backups should also be usable by the respective remote database (e.g. database 2 should be able to restore a backup from within its local archive volume written by remote database 1), the remote archive volume option nocompression must be used. Prior to version 6.0, it was not possible to use this approach for creating backups cross-wise. However, it was possible to use it in one direction.
    • Category 1:
      Cluster Administration - Backup
    • Category 2:
      Cluster Administration - DB Instance Management

      Attachments

        Issue Links

          Activity

            People

            • Assignee:
              CaptainEXA Captain EXASOL
              Reporter:
              CaptainEXA Captain EXASOL
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: