Mitigating the "fat-finger delete" with Queryable Backups

Facebook ShareLinkedin ShareReddit ShareTwitter Share

Database Administrators dread the call saying someone, “accidentally deleted data”. Restoring from backups is sometimes the only way to recover the data and given today’s ever-increasing database sizes it may be difficult to source the hardware needed for a restore. Even in the public cloud, restoring large data sets are time consuming and expensive. Wouldn’t it be great to just connect to your backup and query for the data that was “accidentally deleted”?

Queryable Backups, available in MongoDB OpsManager 3.6+ and MongoDB Atlas, allows administrators to make a database connection to a backup snapshot. From within the MongoDB OpsManager or MongoDB Atlas management UI, the user can choose one of two methods to connect to the snapshot:

Option 1: Download the tunnel application

The tunnel application can be downloaded from the OpsManager UI or from MongoDB Atlas. The application listens to a local port and passes through communications from a Mongo client to the MongoDB server hosting the backup snapshot. The tunnel includes all the necessary server certificates. All the user has to do on the command line is run the tunnel application:

Next, the user connects to the backup by using the Mongo Shell or other client application and connects locally to the tunnel as shown below.

Option 2: Manually download the server certificates

When the user enables queryable backups, OpsManager will generate X.509 certificates that are valid for 24 hours. The tunnel executable mentioned in Option 1 has these certificates already included on the users behalf. Alternatively, the user can download certificates manually and just use the mongo shell to connect to the backup passing the certificates as parameters.

For more information check out the following Queryable backup documentation: MongoDB OpsManager Queryable Backup and MongoDB Atlas Queryable Backup.