Skip to content

Get free database assistance or contact our experts for personalized support.

Multiple endpoints to the same storage

Version added: 2.8.0

In environments where pbm-agents run on servers that are distributed across several data centers, accessing the same remote backup storage can become challenging. This can be due to complex network configurations or strict policies that prevent direct connections to the outside world. As a result, pbm-agents can’t use the same URL to reach the storage, which is necessary for Percona Backup for MongoDB to work properly.

To address these challenges, you can configure custom endpoint URLs for specific nodes in the PBM configuration. This allows all pbm-agents to access the same storage while respecting the network settings of their data centers.

The supported storage types are:

  • AWS S3
  • MinIO and S3-compatible storage services
  • Microsoft Azure Blob storage

Here’s the example of the configuration file with the endpoint map:

storage:
    type: s3
    s3:
      endpointUrl: http://S3:9000
      endpointUrlMap:
        "node01:27017": "did.socf.s3.com"
        "node03:27017": "https://example.aws.s3.com"
      ...
storage:
    type: minio
    minio:
      endpoint: localhost:9100
      endpointMap:
        "node01:27017": "did.socf.s3.com"
        "node03:27017": "example.min.io"
      ...
storage:
    type: azure
    azure:
      endpointUrl: https://myaccount.blob.core.windows.net
      endpointUrlMap:
        "node01:27017": "did.socf.blob.core.windows.net"
        "node03:27017": "example.azure.blob.core.windows.net"
      ...

You can define specific nodes using the endpointUrlMap (for AWS S3 and Azure) or endpointMap (for MinIO and S3-compatible storage) parameters. Both parameters are maps of 'host:port' to endpoint URL, as shown in the earlier examples. Nodes not listed in the map use the endpoint defined by the endpointUrl or endpoint parameter, respectively.

For the solution to work, you should also have the mapping mechanism in place. This mechanism should be able to map the custom endpoints to the main endpoint URL of the storage, routing the requests from pbm-agents to the storage and back seamlessly.

With this ability to control the endpoints for pbm-agents to reach the same storage, you reduce the administrative overhead on PBM configuration and ensure its proper functioning.


Last update: November 4, 2025
Created: November 4, 2025