# Percona Backup for MongoDB 1.5.0

| Release date | May 10, 2021   |
|------------- | ---------------|
| Installation | [Installing Percona Backup for MongoDB](../installation.md) |


Percona Backup for MongoDB is a distributed, low-impact solution for consistent backups of MongoDB
sharded clusters and replica sets. This is a tool for creating consistent backups
across a MongoDB sharded cluster (or a single replica set), and for restoring
those backups to a specific point in time.

## New Features

* [PBM-596](https://jira.percona.com/browse/PBM-596): Azure Blob Storage support

* [PBM-488](https://jira.percona.com/browse/PBM-488): Create weight or tag method to influence with `pbm-agent` node will do backups

## Improvements

* [PBM-662](https://jira.percona.com/browse/PBM-662): Show PITR Status based on `admin.pbmLock` instead of config settings

* [PBM-494](https://jira.percona.com/browse/PBM-494): Prefer a (healthy) hidden secondary to any other node in automatic selection

## Bugs Fixed

* [PBM-642](https://jira.percona.com/browse/PBM-642): Display `priority=0` members on agent list in `pbm status` output

* [PBM-636](https://jira.percona.com/browse/PBM-636): Different collection UUID after restore (Thanks to Nikolay for reporting this issue and Dmitry Kuzmin for contributing)

* [PBM-646](https://jira.percona.com/browse/PBM-646): Stop the balancer during backup to make sure it doesn’t start running during restore

* [PBM-635](https://jira.percona.com/browse/PBM-635): Wait for the leader’s metadata before starting backups

* [PBM-490](https://jira.percona.com/browse/PBM-490): Use cluster time for the snapshot start time