Docs Menu

Docs HomeMongoDB Cloud Manager

Backup Agent Changelog

On this page

Note

Announcement

The Backup and Monitoring Agent have been merged into the Automation Agent, which will now be known as the MongoDB Agent. Learn more about this change.

Released 2019-05-02

  • Fix: Log optimizations when applying oplogs during a point in time restore.

Released 2019-04-16

  • Convert to new MongoDB Go Driver

Released 2019-03-05

  • Work to support the upcoming MongoDB 4.2 release.

Released 2019-02-13

  • Increased timeouts when applying oplogs during a point in time restore.

  • Prevent failures during long-running index builds during a point in time restore.

Released 2019-01-23

Released 2019-01-03

  • Built on Go 1.10.

Released 2018-12-05

  • Built on Go 1.9.

Released 2018-10-04

  • Improved handling of expiration of the queryable backup tunnel utility.

Released 2018-08-01

  • Fix file extension when downloading a Backup Agent in Microsoft Edge and Firefox.

  • Ensure that the UUID of the system.views collection is preserved during a Backup initial sync.

Released 2018-07-16

  • Maintain UUID for system.views collection by copying it on initial sync.

Released 2018-06-04

  • Fix deadlock in underlying Go driver.

Released 2018-05-31

  • Make responseHeaderTimeout configurable.

  • Support for upcoming MongoDB 4.0 release.

Released 2018-05-09

  • Support for persistent HTTPS connections (default to off).

Released 2018-03-28

  • Fix corrupted build for RHEL6.

Released 2018-03-27

  • Logging enhancements.

Released 2018-03-06

  • Fix: Backup Agent should produce an error message and not crash when erroneous authentication credentials are provided for a source cluster.

Released 2018-02-13

  • During a PIT restore, suppress errors when dropping non-existent namespaces.

  • During a PIT restore, always apply oplogs with upsert=true.

Released 2018-01-23

  • Fix: Send compound index keys as ordered BSON.

  • Fix: Send less detailed data in the initial summary payload at the start of an initial sync. Collect more detailed data for each collection individually.

Released 2018-01-08

  • Fix: Relax validation when krb5ConfigLocation parameter is specified. This no longer implies that krb5Principal and krb5Keytab are required.

  • Fix: Use correct format for point in time restore oplog seed when no oplog are available.

Released 2017-11-19

Fix: Upgrades of the Backup Agent performed by the Automation Agent were missing a parameter on Windows.

Released 2017-11-14

Support for upcoming release of MongoDB 3.6.

Released 2017-10-26

  • Support for upcoming release of MongoDB 3.6.

Released 2017-10-25

  • Support for upcoming release of MongoDB 3.6.

Released 2017-09-13

  • Use BSON.d for missing docs.

Released 2017-08-25

  • Allow oplogs for a point in time restore to be applied client-side.

Released 2017-08-01

  • Support for optimized point in time restores.

Released 2017-07-11

  • During initial sync, add verification that shard name matches the expected shard name.

Released 2017-06-15

  • Use HTTP basic auth to authenticate HTTPS requests between the Backup Agent and cloud.mongodb.com.

  • Performance enhancement: Use bson.Raw for initial sync.

Released 2017-04-19

  • Reduce memory used during initial sync.

  • Ensure messages printed to STDOUT and STDERR is also included in the Backup Agent log file.

Released 2017-03-29

  • Optimization for collection of data in the initial sync phase. (Recompiled with the MGO-128 fix.)

Released 2017-01-23

  • Support for macOS Sierra.

  • Compiled with Go 1.7.4.

  • Fix: Can send logs to Cloud Manager for Backup Agents running on Windows.

Released 2016-12-13

  • Handle capped collections that are capped using a floating point size.

Released 2016-11-21

  • Support for MongoDB 3.4 Views.

  • Support for MongoDB 3.4 featureCompatiblityVersion.

Released 2016-11-07

  • Allow managed Backup Agents to be run as a service on Windows.

Released 2016-09-14

  • Update of underlying Go driver.

  • Partial support for upcoming major release of MongoDB 3.4.0.

  • Partial support for Kerberos on Windows.

Released 2016-08-24

  • Support for Power Linux.

Released 2016-07-12

  • Agent support for restarting incremental initial syncs.

Released 2016-05-16

  • Updated to use Go 1.6.

Released 2016-04-20

  • Added support for log rotation.

  • Added a sticky header to log files.

Released 2016-02-18

  • Use systemD management on RHEL7 and Ubuntu 16.04.

  • Set ulimits in the packaged builds.

Released 2016-01-07

  • Added the ability to customize the Kerberos configuration file location.

  • Added support to tune the number of concurrent initial syncs.

  • Added support to adjust the size of the oplog and sync slice channels according to the size of the documents: this can lower memory consumption.

Released 2015-11-02

  • Support for streaming initial syncs.

  • Support for MongoDB 3.2 clusters with config server replica sets.

Released 2015-10-14

  • Upgraded to Go 1.5.1.

Released 2015-09-16

  • Built with Go 1.5.0.

  • Fix: Ignore collections deleted during an initial sync.

Released 2015-08-10

  • Added fix to not trim spaces from collection names.

  • Upgraded to new version of snappy compression library.

Released 2015-07-15

  • Added minor optimization to explicitly set the Content-Type on HTTP requests.

Backup .. _bgent-5.0.286-1:

Released 2015-06-24

  • Updated documentation and setting URLs to cloud.mongodb.com.

  • Added support for backing up selected namespaces. This functionality is not yet exposed in the Cloud Manager user interface.

Released 2015-04-22

  • Added an explicit timeout for SSL connections to mongod instances.

  • Added an optimization for syncs of collections with lots of small documents.

  • The Kerberos credentials cache now uses a fixed name.

Released 2015-03-10

Logging improvements.

Released 2015-02-23

Ability to monitor and back up deployments without managing them through Automation. Specifically, you can import an existing deployment into Monitoring and then use Cloud Manager to back up the deployment.

  • Support for x.509 certificate authentication.

  • Fix: A race condition which could result in inconsistent clustershots for MongoDB 3.0+ sharded clusters using the backup role no longer occurs.

Released 2015-01-08

Logging improvements for Windows.

Released 2015-01-08

Enhancements to support backup of MongoDB 3.0.

Released 2014-12-17

Agent now encodes all collection meta-data. Avoids edge-case issues with unexpected characters in collection settings.

Released 2014-12-04

Can now explicitly pass collections options for the WiredTiger storage engine from the backed up mongod to Cloud Manager.

Released 2014-11-12

The Backup Agent will now identify itself to the Cloud Manager servers using the fully qualified domain name (FQDN) of the server on which it is running.

Released 2014-11-06

Use no-timeout cursors to work around MGO-53.

Released 2014-10-29

  • When tailing the oplog, the agent no longer pre-fetches the next batch of oplog entries before exhausting the current batch.

  • Adds support for non-default Kerberos service names.

  • Adds support for RHEL7.

Released 2014-09-30

Minor logging change, clarifying when stopping the balancer if there is no balancer settings document.

Released 2014-09-10

Added support for authentication using MongoDB 2.4 style client certificates.

Released 2014-08-19

The Backup Agent will now capture a checkpoint even if it is unable to stop the balancer. These checkpoints are not guaranteed to be consistent, because of in-progress chunk migrations. The user interface identifies these checkpoints.

Released 2014-07-29

  • Upgraded agent to use to Go 1.3.

  • Added support for version and -version.

  • Added support for connecting to hosts using LDAP authentication.

  • Agent now provides additional logging information when the Backup Agent manipulates the balancer.

  • Agent now supports configuring HTTP with the config file.

Released 2014-07-09

Fixes issue with agent on Windows using the MONGODB-CR authentication mechanism.

Released 2014-07-08

  • Fixes issues with connecting to replica set members that use auth with an updated Go client library.

  • Agent is now able to send a stack trace of its current state to Cloud Manager.

  • Fixes regression in the Agent's rollback handling.

Released 2014-06-17

Support for a new API t hat allows Cloud Manager to ingest oplog entries before the entire payload has reached the Cloud Manager servers.

Released 2014-05-28

  • Agent supports deployment architectures with multiple active (i.e. primary) Backup Agents.

  • Improved stability around oplog tokens for environments with unstable networks.

Released 2014-05-19

  • Critical update for users running the MongoDB 2.6 series that use authorization.

  • The Backup Agent now includes system.version and system.role collections from the admin database in the initial sync.

Released 2014-05-09

The agent now sends oplog slices to Cloud Manager in batches to increase throughout and stability.

  • Major stability update.

  • Prevent a file descriptor leak.

  • Correct handling of timeouts for connections hung in the TLS/SSL handshaking phase.

Support for using the Backup Agent via an HTTP proxy

  • Allow upgrading the agent using the Windows MSI installer.

  • Improved logging.

  • Fix an open files leak on bad HTTP responses.

  • Added support for Windows MSI installer.

  • For sharded clusters, less aggressive polling to determine if balancer has been stopped.

  • Fail fast on connections to mongods that are not responding.

Added support for sharded cluster checkpoints that add additional points-in-time, in between scheduled snapshots, that Cloud Manager can use to create restores. Configure checkpoints using the Edit Snapshot Schedule link and interface.

This version marks a change in the numbering scheme of Backup Agents to support improved packaging options for the Backup Agent.

  • Added support for connecting to MongoDB instances running TLS.

  • The agent will try to use additional mongos instances to take a cluster snapshot if the first mongos is unavailable.

  • Significantly reduced the amount of time needed by the agent to detect situations that require a resync.

  • Allow automatic resync operations for config servers in sharded clusters. The agent can now resync automatically from these servers.

When the agent sends the initial meta-data about the data to back up (e.g. the list of databases, collections,and indexes,) to the Cloud Manager API, the agent will not include any databases or collections in the "excluded namespace" configuration.

Adds support for managing excluded namespaces: Backup Agent no longer sends data for excluded collections or databases.

Major stability update

If the communication between the Backup Agent and the Cloud Manager API is interrupted, the Backup Agent can more reliably recover the current state. This results in fewer "resync required" errors.

←  Monitoring Agent ChangelogCloud Manager Licensing →

On this page