Release Highlights
Support of Alibaba Cloud as the backup storage
With Percona Backup for MongoDB (PBM) now supporting Alibaba Cloud OSS as a remote backup destination, you can seamlessly integrate your backup workflows into the Alibaba Cloud ecosystem. This means you can store any type of backups directly in OSS without extra tools or manual steps, taking full advantage of Alibaba's scalable infrastructure and strong regional performance.
You can authenticate directly using your OSS Access Key ID and Secret, or take advantage of full support for Alibaba Cloud's Security Token Service (STS) AssumeRole, which includes automatic security token refresh. The latter authentication flow is ideal for organizations that require temporary credentials for enhanced security.
This integration empowers teams already invested in Alibaba Cloud to adopt PBM better. Whether you're operating in Asia-Pacific or building cloud-native infrastructure, this gives you a secure, scalable, and compliant way to protect your data.
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. By customizing retry behavior, you gain greater resilience and reliability in backup and sync workflows. It’s a simple way to reduce failed uploads and improve peace of mind.
Native MinIO Support in PBM
PBM now includes a native support for the MinIO storage by adding the MinIO Go client library. This integration makes it easier to use custom S3-compatible storage services for backup and restore. Not all S3-compatible storage services support Signature Version 4 (SigV4) used in AWS SDK v2, which may result in compatibility and connectivity issues. 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. However, be aware of the current known limitation for using the MinIO storage type.
Known limitation for using the MinIO storage type
While MinIo SDK supports concurrency, its implementation interferes with PBM's backup logic and affects PBM functionality. Therefore, currently PBM uploads backups using a single thread which results in slower backup performance compared to S3. We're actively investigating safe ways to improve throughput without compromising reliability.
Deprecation of HMAC keys support for Google Cloud Storage
Accessing Google Cloud Storage with HMAC keys relies on AWS Signature Version 2 (SigV2), an outdated authentication method that has been officially deprecated. Google Cloud Storage doesn't support a new Signature Version 4 (SigV4) and only supports SigV2 for HMAC authentication.
Continuing to use SigV2 can lead to serious issues: Percona Backup for MongoDB may incorrectly mark incomplete backups as successful and upload corrupted data to storage. This puts your restore process at risk and undermines backup reliability. Using the outdated Signature Version 2 (SigV2) authentication for Google Cloud Storage is not recommended because it lacks important security enhancements, is no longer maintained, and can introduce critical reliability issues. To prevent this, support for HMAC keys is now deprecated. 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.
We will end-of-life HMAC support and remove it in the PBM release after April 30, 2026.
Changelog
For more details, please check out the full list of improvements
https://docs.percona.com/percona-backup-mongodb/release-notes/2.12.0.html
Join Percona Squad
Participate in monthly SWAG raffles, get an early access to new product features and invite-only “ask me anything” sessions with database performance experts. Interested? Fill in the form at https://squad.percona.com/mongodb
Contact Us
on Forums
by Email
or Professional Support