Skip to content

v2.6.0

Latest
Latest
Compare
Choose a tag to compare
@sandraromanchenko sandraromanchenko released this 02 Sep 10:46
· 11 commits to dev since this release
v2.6.0
f2cf881
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

Release Highlights

  • Multiple storages for backups and restores
    You can now define multiple storages for making backups and instruct PBM on what storage to save a backup: on the main or on any additional (external) one. This ability helps you save on data transfer costs when using cloud storage, as well as enables you to follow closely with the requirements of your organization’s backup policy.

  • Adjust node priority for point-in-time recovery oplog slicing
    You can now redefine node priorities not only for making backups but also for point-in-time recovery oplog slices. For example, you can instruct PBM to save oplog slices either from a dedicated node or from nodes in the geographically closest location, thus reducing network latency.

  • Additional control over PBM command execution
    You can now configure the waiting time for a command execution by passing the --wait-time flag for the following commands:

    pbm config –force-resync –wait –wait-time='5m'
pbm backup –wait –wait-time='5m'
pbm restore –wait –wait-time='5m'
pbm oplog-replay –wait –wait-time='5m'
pbm profile add –sync –wait –wait-time='5m'
pbm profile remove –wait –wait-time='5m'
pbm profile sync –wait –wait-time='5m'
pbm delete-pitr –older-than –wait –wait-time='5m'
pbm cleanup –older-than –wait –wait-time='5m'

    This way you have more control over the PBM operation. This enhancement also improves the error logging.

  • Snapshot-based physical backups are generally available
    With snapshot-based physical backups now generally available, you can use this functionality in production environments and enjoy all the benefits of faster restores from snapshots with almost immediate access to data.

  • Dropped support of MongoDB 4.4
    Percona Backup for MongoDB drops support of MongoDB 4.4. Existing functionality in Percona Backup for MongoDB remains compatible with MongoDB 4.4 and Percona Server for MongoDB 4.4; however, further enhancements and bug fixes are no longer tested against this version.

  • Packaging Changes
    Percona Backup for MongoDB is available on Ubuntu 24.04 (Noble Numbat).
    Percona Backup for MongoDB is no longer supported for Ubuntu 18.04 (Bionic Beaver), Debian 10 and Red Hat Enterprise 7 and derivatives as these operating systems reached End-Of-Life.

For more details, please check out the full list of improvements:
https://docs.percona.com/percona-backup-mongodb/release-notes/2.6.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

Assets 2
Loading