We’ve made several major improvements and bug fixes to the MongoDB Backup Agent used by MMS, including:
- More granular restore points for sharded clusters
- Support for the latest version of MongoDB, version 2.6
- Improved packaging with service scripts to make deployment easier
- SSL connectivity improvements, resulting in fewer connection resets and hangs
- Fixed a file descriptor resource leak
We encourage all backup users to upgrade to the latest agent version for a better overall experience with the service.
To access these improvements, please download the agent from the MongoDB Management Service by going to Settings > Backup Agent.
Don’t Let Your MongoDB Standalone Stand Alone: How to Back Up a MongoDB Single Server
Lots of people start with standalone servers when they first try MongoDB. If you are running standalone, it’s especially critical that you back it up because you don’t have the fault tolerance and redundancy of a multi-node replica set. MongoDB Management Service (MMS) requires that you run a replica set in order to back up. What is not widely known is that you can run a one node replica set, thereby producing the oplog that MMS Backup requires to work, while still running only a single mongod server. Here is how you do it. Shut down the standalone mongod instance. The safe way do this is by calling db.shutdownServer() from the mongo shell. Restart the instance. Use the –replSet option to specify the name of the new replica set. Connect to the mongod instance. Use rs.initiate() to initiate the new replica set. Here is a concrete example. If you your database is running on the standard ports and uses the standard location for the data directory (/data/db) then you might issue the following command to start the server: # mongod --replSet rs0 You can name the replica set however you like. Using “rs0” was just an example. After you do this, initiate the replica set: # mongo # rs.initiate() You now have a replica set! If you need more detailed instructions, you can visit the docs . Now that your single server is a one-node replica set, you can configure backup through MMS Backup. 1) Get Monitoring Running Using MMS Monitoring is prerequisite of using MMS Backup because the backup service relies on the configuration information gathered by the monitoring service to figure out what to backup. Monitoring is free. If you are not already monitoring your server using MMS Monitoring, go to mms.mongodb.com and signup for a free account. You will then need to download the monitoring agent and run it on a machine that can see your server. 2) Register for Backup Visit the Backup tab within MMS to register for the service. This includes setting up two-factor authentication for restores, entering your credit card for billing and accepting the terms of service. 3) Install the Agent The next step is installing the backup agent on your deployment. This step is easy - just download the appropriate agent for your operating system from the Settings section of mms.mongodb.com and unzip or untar the file in the preferred directory. In the backup-agent directory, issue the following command to start the agent (unix variant): # ./backup-agent 4) Start Your Sync Now that you’ve got replica sets going and the backup agent installed, the final step is to go the backups page on the MMS UI and enable your one-node replica set for backup. 5) Rest Easy - Your Standalone Server is No Longer Standing Alone - It’s Backed Up! An initial sync will begin, and soon your database server will be backed up to MongoDB’s datacenters. Start backing up now. Create an MMS account!
What’s New in Atlas Charts: Easy Organization-Wide Sharing
We’re excited to announce improvements to sharing dashboards in MongoDB Atlas Charts . Data visualization is a powerful tool for discovering insights, and sharing visualizations across your team helps amplify those insights to propel businesses forward. With organization-wide sharing in Atlas Charts, we’re making it even easier to share the insights you discover from your application data across your entire organization. Sharing dashboards Atlas Charts has always made it possible to share visualizations with either individual members or everyone inside your Atlas project. Assuming a user had access to a given data source in Atlas, adding a user to a Charts project was effectively a one-click process. However, many teams do not broadly share database access unless an individual specifically needs it. And, if you want to share data with many members of your team, provisioning users one by one is tedious. Once users are in a Charts project, however, sharing a dashboard with everyone inside the project becomes relatively easy — you can invite all users in your project to view your dashboard with a single action. There are probably scenarios in which some members of your organization have Atlas access and others do not. In this case, if your team has enabled Federated Authentication and uses a third-party authentication provider, such as Google or Okta, Charts now makes it simple to turn on sharing dashboards across your entire organization. Granting access This approach makes sharing company-wide information quick and easy. For example, you can keep employees aware of product or platform growth or other key business metrics. Any members of your organization can be granted access to view these dashboards with a single click, as shown in Figure 1. Figure 1: A look at a dashboard shared across an organization. Note that, with these changes to dashboard sharing, your ability to maintain the security of your data remains unchanged. New dashboard viewers still need at least viewer access to any data source behind the charts in a shared dashboard, thereby ensuring that your company's sensitive data remains private. Additionally, project owners can now manage data source access at a deployment level, which means they can give access to their clusters or federated database instances . This capability is in addition to the already available granular control of data source access at a collection level, which was introduced as part of recent improvements we made to data sources. You can read more about managing access to data sources in your organization in our documentation . We hope you find these sharing improvements valuable and start leveraging this capability to share additional insights across your organization. New to Atlas Charts? Get started today by logging into or signing up for MongoDB Atlas , deploying or selecting a cluster, and activating Charts for free.