In our recent RecoverX 2.5 launch, we introduced a host of exciting new capabilities designed specifically for MongoDB including Data Center Aware Backup for MongoDB. Data Center Aware Backup enables backing up geo-distributed MongoDB sharded database clusters at any of the geo-distributed sites and restoring at any of the sites. RecoverX can backup an entire geo distributed cluster at each geo-location even though the shard primaries are distributed across geographies.
In today’s blog I’ll discuss two additional capabilities of RecoverX for MongoDB databases; Cluster Topology Aware Protection and Any-Point-In-Time Recovery (APIT).
Cluster Topology Aware Protection:
Few database environments are static, especially modern, distributed databases. Production MongoDB clusters often need to be re-scaled as a result of growth or changing requirements. DBAs often reconfigure the topology of MongoDB clusters to address requirements for scaling of write performance, read performance or both. Topology can also be reconfigured to increase data capacity as the size of collections grow or new ones are added. Often there are requirements to shrink or scale back MongoDB cluster configurations, removing shards or replica sets, or removing individual nodes in a shard or replica set.
Because MongoDB cluster topologies can (and will) change over time, it is essential that backup and recovery operations are resilient to these changes in topology. RecoverX supports the following topology change scenarios:
- Adding a replica set/shard to an existing MongoDB cluster
- Removing a replica set/shard from an existing MongoDB cluster
- Adding a member (node) to an existing replica set/shard
- Removing a member (node) from an existing replica set/shard
RecoverX monitors the topology of protected MongoDB source clusters at every backup interval. When it recognizes a topology change it will take appropriate action based on the detected change in topology. The automatic handling of topology changes does not impact current backup policies, which remain as configured for each protected column family or selection of column families.
Topology Aware Protection delivers peace of mind for DBAs and IT administrators, and increases their productivity, freeing them from any manual configuration requirements to handle data protection of MongoDB clusters as they grow, shrink, or are reconfigured.
Any Point-in-Time (APIT) Recovery
RecoverX creates specific Point-in-Time (PIT) backups based on configured intervals in each backup policy for each collection or group of collections. Data recovery, however, is not limited to just those specific points in time. Because RecoverX utilizes MongoDB ops logs for backups, DBAs and IT administrators can also perform Any Point-in-Time (APIT) recovery. This is easily done from the GUI by selecting selecting a specific timestamp from a range of timestamps on a slider bar, as shown below. Collections can be recovered from any specific timestamp between the range of available timestamps shown on the slider bar.
The window of available Any Point-in-Time timestamps is also configurable. For example if the Point-In-Time versioning interval is every 4 hours, entering 10 results in APIT recovery that can be performed for any time period up to 10 Point-In-Time “versions” back. With a versioning interval of 4 hours, this means APIT recovery can be performed from any timestamp for the last 40 hours (10×4).
Any Point-in-Time restore equips Backup administrators and DBAs with the flexibility to configure a window of available timestamps to meet their organization’s RPO requirements for restoring data.
With advanced backup and recovery features Datos IO RecoverX increases the productivity of developers and application owners, and delivers scalable and fully featured point-in-time backup and recovery for next-generation applications built on non-relational databases and big data filesystems. If you are deploying MongoDB for production applications with business critical data, you need Datos IO RecoverX.
To learn more about our latest RecoverX 2.5 product, check out this blog.