Skip to content
Percona Documentation
Rate this page
☆ ☆ ☆ ☆ ☆
Thanks for your feedback
Thank you! The feedback has been submitted.

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

Get help from Percona

Percona Backup for MongoDB 2.12.0 has been released

Percona Backup for MongoDB 2.12.0 has been released on November 4, 2025.

Try it out using the Quickstart guide

This release focuses on improvements to backup storages. It includes new storage types, enhances Azure Blob storage implementation, and fixes issues with S3-compatible storage services.

Details below:

  • Integrate your backup workflows into the Alibaba Cloud ecosystem seamlessly using Alibaba Cloud Object Storage Service (OSS) as the remote backup storage. Authenticate to Alibaba Cloud OSS directly using your AccessKey pair, or ensure compliance with your org's security policies with a full support for Alibaba Cloud's Security Token Service (STS) AssumeRole, which includes automatic security token refresh. This integration empowers teams operating in Asia-Pacific or invested in Alibaba Cloud to adopt PBM better. Read more about Alibaba Cloud OSS support in our documentation

  • Ensure data upload to Azure Blob storage even during unstable network. You can now control the number of upload retries to Azure in PBM configuration. This enhancement ensures your data reaches its destination—even when the network is unstable or intermittent. Check PBM configuration file reference for available options.

  • Improved usage of custom S3-compatible storage service implementations with a native support for MinIO client library in PBM. To prevent potential compatibility and connectivity issues if anS3-compatible storage service doesn't support Signature Version 4 (SigV4) used in AWS SDK v2, PBM now uses the MinIo Go client and supports a new minio storage type in its configuration. If your custom S3-compatible storage is not compatible with AWS SDK v2, consider re-configuring PBM to use the minio storage type after the upgrade. Check the documentation for steps. Also, be aware of the current known limitation that currently PBM uploads backups in a single thread which may result in slower performance.

  • Deprecation of HMAC keys support for Google Cloud Storage. Google Cloud Storage doesn't support a new Signature Version 4 (SigV4) and only supports SigV2 for HMAC authentication. Signature Version 2 (SigV2) authentication is not recommended because it lacks important security enhancements, is no longer maintained, and can introduce critical reliability issues. To prevent these, HMAC support in PBM is deprecated and will be removed in the release following after April 30, 2026. We strongly recommend migrating to a native GCS connection type with JSON keys. Refer to the documentation for guidance on adjusting PBM configuration to use JSON keys.