We recently covered the use case of Percona Backup for MongoDB and Disk Snapshots in Google Cloud Platform; now it’s time to do the same for Amazon AWS. For this demo, I have created a 2-shard MongoDB cluster (where each shard is a 3-node PSA Replica Set) deployed on EC2 instances. Each instance has an extra […]

Percona Backup for MongoDB (PBM) supports snapshot-based physical backups. This is made possible by the backup cursor functionality present in Percona Server for MongoDB.  In a previous post, we discussed Percona Backup for MongoDB and Disk Snapshots in Google Cloud Platform (part 1) and showed how to implement snapshot-based backups. Now, let’s see...

There are various ways to backup and restore Percona Server for MongoDB clusters when you run them on Kubernetes. Percona Operator for MongoDB utilizes Percona Backup for MongoDB (PBM) to take physical and logical backups, continuously upload oplogs to object storage, and maintain the backup lifecycle.  Cloud providers and various storage solutions...

Percona Backup for MongoDB (PBM) supports snapshot-based physical backups. This is made possible by the backup cursor functionality present in Percona Server for MongoDB.  The flow of snapshot-based physical backup consists of these stages: Preparing the database – done by PBM Taking the snapshots – done by the user/client app Completing the backup...

MongoDB provides scalability and high availability at ease. If you already have a sharded cluster, you know for sure what the Balancer does. If you are not an experienced MongoDB user, the Balancer is one of the key components of a sharded cluster, and the main goal is to maintain the cluster balanced, moving chunks […]

Recently, one of our customers reported a problem after upgrading a sharded cluster from MongoDB 5.0 to 6.0. The upgrade of data-bearing nodes was fine, but in the final part of the process, where mongos routers needed to be restarted, the new version did not go well. This caused problems for the applications, where suddenly […]