{"id":48877,"date":"2026-11-20T16:00:11","date_gmt":"2026-11-20T15:00:11","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/?p=48877"},"modified":"2026-11-20T16:00:20","modified_gmt":"2026-11-20T15:00:20","slug":"mongodb-dmk-2-7-0-point-in-time-recovery-9-0-support-and-auto-upgrade","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/mongodb-dmk-2-7-0-point-in-time-recovery-9-0-support-and-auto-upgrade\/","title":{"rendered":"MongoDB DMK 2.7.0 : point-in-time recovery, 9.0 support and auto-upgrade"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">In this blog, I will present the new features introduced with the latest release (<code class=\"nowrap\">2.7.0<\/code>) of the MongoDB DMK.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The DMK is a set of standardized tools that aims at easing the work of DBAs. It embeds the best practices of dbi in common scripts across all the database servers of an organization.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">dbi services provides the <a href=\"https:\/\/www.dbi-services.com\/fr\/produits\/dmk-management-kit\/\" target=\"_blank\" rel=\"noopener noreferrer\">DMK<\/a> (<em>Database Management Kit<\/em>) to its customers for multiple technologies: Oracle, Postgres, MongoDB, etc. This toolkit is provided <strong>free of charge<\/strong> to all clients who work with dbi services on a consulting project.<\/p>\n\n\n\n<h2 id=\"new-features-of-the-mongodb-dmk-in-270\" class=\"wp-block-heading\">New features of the MongoDB DMK in <code class=\"nowrap\">2.7.0<\/code><\/h2>\n\n\n\n<h3 id=\"point-in-time-recovery\" class=\"wp-block-heading\">Point-in-time recovery<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">PITR is the biggest addition of the release. It restores a whole instance, a database or a collection to a chosen moment, on a replica set.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code class=\"nowrap\">dmk_oplog_backup.py<\/code>, run frequently, archives the oplog in incremental slices between two full backups.<\/li>\n\n\n\n<li><code>dmk_restore.py --pitr &lt;timestamp&gt;<\/code> restores a backup and replays the archived oplog up to the target. Specify a custom starting full save with <code class=\"nowrap\">-s<\/code>, or leave it out. DMK can also select the newest full-instance backup that reaches the target. It asks the user for confirmation (<code class=\"nowrap\">--yes<\/code> accepts it).<\/li>\n\n\n\n<li><code class=\"nowrap\">--out-of-place<\/code> recovers a database or a collection through a scratch <code class=\"nowrap\">mongod<\/code>.<\/li>\n\n\n\n<li><code class=\"nowrap\">dmk_pitr_status.py<\/code> shows the windows that can be recovered right now.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">To restore a full instance to a specific point in time, just run the following command. Here, 150 orders were written, <code class=\"nowrap\">dmk_oplog_backup.py<\/code> archived the oplog, and a <code class=\"nowrap\">deleteMany<\/code> then emptied the collection. The target is just before the delete, and <code class=\"nowrap\">--yes<\/code> accepts the backup that DMK selects:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>$ dmk_restore.py -i mdbrs01 --pitr '2026-11-15T15:24:46' --yes\n2026-11-15 15:24:53 | INFO | PITR target '2026-11-15T15:24:46' is 2026-11-15T15:24:46+00:00 = 2026-11-15T15:24:46+00:00 (1795101886:0) (exclusive).\n2026-11-15 15:24:53 | INFO | No source given: selected the newest backup that reaches the target 2026-11-15T15:24:46+00:00 = 2026-11-15T15:24:46+00:00 (1795101886:0): '\/u90\/mongodb\/backup\/mdbrs01\/backup_mdbrs01_20261115_152434'. Its dump ended at 2026-11-15T15:24:33+00:00 = 2026-11-15T15:24:33+00:00 (1795101873:101), the archived oplog covers up to 2026-11-15T15:24:51+00:00 = 2026-11-15T15:24:51+00:00 (1795101891:1).\n2026-11-15 15:24:53 | INFO | --yes given: restoring from this backup without asking.\n2026-11-15 15:24:53 | INFO | Whole-instance PITR to 2026-11-15T15:24:46+00:00 = 2026-11-15T15:24:46+00:00 (1795101886:0), beyond the oplog the base backup captured: replaying the archived oplog slices in a scratch instance (the target instance is not replayed into).\n2026-11-15 15:24:54 | INFO | Restoring the base backup '\/u90\/mongodb\/backup\/mdbrs01\/backup_mdbrs01_20261115_152434' into the scratch instance (replaying its own captured oplog) ...\n2026-11-15 15:24:54 | INFO | Replaying archived oplog slice 1\/2 ('oplog_slice_20261115_152439_899500.archive.gz') ...\n2026-11-15 15:24:54 | INFO | Replaying archived oplog slice 2\/2 ('oplog_slice_20261115_152450_825511.archive.gz') ...\n2026-11-15 15:24:54 | INFO | Scratch instance is now at 2026-11-15T15:24:46+00:00 = 2026-11-15T15:24:46+00:00 (1795101886:0).\n2026-11-15 15:24:55 | INFO | Loading the recovered instance into 'mdbrs01' ...\n&#91;...]\n2026-11-15 15:24:56 | INFO | Restore summary: 150 document(s) restored, 0 failed.\n2026-11-15 15:24:56 | INFO | Restore completed successfully.\n2026-11-15 15:24:56 | INFO | Whole-instance PITR completed successfully.<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The orders are back: <code class=\"nowrap\">shop.orders<\/code> has 150 documents again. If no backup can be found, or if there is no archived slice to reach the target, the script fails without attempting the restore.<\/p>\n\n\n\n<h3 id=\"upgrade-and-downgrade-of-mongodb\" class=\"wp-block-heading\">Upgrade and downgrade of MongoDB<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><code class=\"nowrap\">dmk_upgrade.py<\/code> and <code class=\"nowrap\">dmk_downgrade.py<\/code> patch or upgrade an instance, a replica set or a sharded cluster to another MongoDB version. They stop each member, point it to the new home, start it and check the version. The previous home is put back if the new binaries do not start. <code class=\"nowrap\">--dry-run<\/code> shows the plan and changes nothing. The feature compatibility version changes only with <code class=\"nowrap\">--update-fcv<\/code>. <code class=\"nowrap\">dmk_upgrade_analyzer.py<\/code> checks beforehand what the new version changes for the data and the configuration. <code class=\"nowrap\">--copy-home<\/code> copies the home to the other servers of a deployment. A change that is interrupted, or a <code class=\"nowrap\">mongod<\/code> that does not start, leaves the member on its previous home.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code class=\"nowrap\">--status<\/code> shows every member with its role, running version, home and feature compatibility version. It also shows what is still pending, without changing anything. <code class=\"nowrap\">--host-map<\/code> gives the address of a host whose registered name does not resolve from where the command runs. A <code class=\"nowrap\">mongos<\/code> registers its host name in <code class=\"nowrap\">config.mongos<\/code>, and DMK reaches the members of the other hosts with <code class=\"nowrap\">ssh<\/code> under the names registered in the deployment. If <code class=\"nowrap\">vmdmk<\/code> is not known to the DNS or to <code class=\"nowrap\">\/etc\/hosts<\/code> of the host where you run the command, <code class=\"nowrap\">ssh<\/code> fails with <code>Could not resolve hostname<\/code>, and DMK tells you which name to map:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>dmk_upgrade.py -i mdbxms1 --sharded-cluster --status --host-map vmdmk=10.0.0.10<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The option is repeatable and applies to one command. To keep the mapping, put one <code>name address<\/code> line per host in <code class=\"nowrap\">$MONGO_BASE\/etc\/dmk_hosts.map<\/code> (the option wins over the file). Only the host is mapped, the ports come from the deployment.<\/p>\n\n\n\n<h4 id=\"dry-run-and-status-of-a-sharded-cluster\" class=\"wp-block-heading\">Dry run and status of a sharded cluster<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">The examples below run on a sharded cluster of 13 members, all on <code class=\"nowrap\">8.0.28<\/code>. It has three config servers (<code class=\"nowrap\">mdbcfg01<\/code> to <code class=\"nowrap\">mdbcfg03<\/code>), three shards of three members each (<code class=\"nowrap\">mdbrs11<\/code> to <code class=\"nowrap\">mdbrs33<\/code>) and one router (<code class=\"nowrap\">mdbmgs1<\/code>). The command takes one instance of the local server, here the router. The dry run starts with the analysis, then prints the plan and the steps for every member:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>$ dmk_upgrade.py -i mdbmgs1 --sharded-cluster --target-version 9.0.8 --dry-run\n2026-11-15 15:26:08 | INFO | Instance 'mdbmgs1': current home '\/u01\/app\/mongodb\/product\/8.0.28', target home '\/u01\/app\/mongodb\/product\/9.0.8' (9.0.8, Community).\n2026-11-15 15:26:11 | INFO | Running version: 8.0.28, FCV: n\/a, role: MONGOS.\n2026-11-15 15:26:19 | INFO | Topology: sharded, 13 member(s).\n2026-11-15 15:26:19 | INFO |   mdb-db1:27017 (config csrs, PRIMARY, 8.0.28)\n2026-11-15 15:26:19 | INFO |   mdb-db2:27017 (config csrs, SECONDARY, 8.0.28)\n2026-11-15 15:26:19 | INFO |   mdb-db3:27017 (config csrs, SECONDARY, 8.0.28)\n2026-11-15 15:26:19 | INFO |   mdb-db1:27018 (shard rs1, PRIMARY, 8.0.28)\n2026-11-15 15:26:19 | INFO |   mdb-db2:27018 (shard rs1, SECONDARY, 8.0.28)\n2026-11-15 15:26:19 | INFO |   mdb-db3:27018 (shard rs1, SECONDARY, 8.0.28)\n2026-11-15 15:26:19 | INFO |   mdb-db1:27019 (shard rs2, PRIMARY, 8.0.28)\n2026-11-15 15:26:19 | INFO |   mdb-db2:27019 (shard rs2, SECONDARY, 8.0.28)\n2026-11-15 15:26:19 | INFO |   mdb-db3:27019 (shard rs2, SECONDARY, 8.0.28)\n2026-11-15 15:26:19 | INFO |   mdb-db1:27020 (shard rs3, PRIMARY, 8.0.28)\n2026-11-15 15:26:19 | INFO |   mdb-db2:27020 (shard rs3, SECONDARY, 8.0.28)\n2026-11-15 15:26:19 | INFO |   mdb-db3:27020 (shard rs3, SECONDARY, 8.0.28)\n2026-11-15 15:26:19 | INFO |   mdb-mgs1:27017 (mongos mongos, MONGOS, 8.0.28)\n2026-11-15 15:26:22 | INFO | Analysis of the upgrade from 8.0.28 to 9.0.8: 0 error(s), 0 warning(s), 4 information(s).\n&#91;...]\n2026-11-15 15:26:22 | INFO | Plan:\n2026-11-15 15:26:22 | INFO |   1. mdb-db2:27017 (config csrs, SECONDARY, 8.0.28)\n2026-11-15 15:26:22 | INFO |   2. mdb-db3:27017 (config csrs, SECONDARY, 8.0.28)\n2026-11-15 15:26:22 | INFO |   3. mdb-db1:27017 (config csrs, PRIMARY, 8.0.28)\n2026-11-15 15:26:22 | INFO |   4. mdb-db2:27018 (shard rs1, SECONDARY, 8.0.28)\n2026-11-15 15:26:22 | INFO |   5. mdb-db3:27018 (shard rs1, SECONDARY, 8.0.28)\n2026-11-15 15:26:22 | INFO |   6. mdb-db1:27018 (shard rs1, PRIMARY, 8.0.28)\n2026-11-15 15:26:22 | INFO |   7. mdb-db2:27019 (shard rs2, SECONDARY, 8.0.28)\n2026-11-15 15:26:22 | INFO |   8. mdb-db3:27019 (shard rs2, SECONDARY, 8.0.28)\n2026-11-15 15:26:22 | INFO |   9. mdb-db1:27019 (shard rs2, PRIMARY, 8.0.28)\n2026-11-15 15:26:22 | INFO |   10. mdb-db2:27020 (shard rs3, SECONDARY, 8.0.28)\n2026-11-15 15:26:22 | INFO |   11. mdb-db3:27020 (shard rs3, SECONDARY, 8.0.28)\n2026-11-15 15:26:22 | INFO |   12. mdb-db1:27020 (shard rs3, PRIMARY, 8.0.28)\n2026-11-15 15:26:22 | INFO |   13. mdb-mgs1:27017 (mongos mongos, MONGOS, 8.0.28)\n2026-11-15 15:26:22 | INFO |   FCV: raise to 9.0 afterwards (requires --update-fcv or --force-fcv-update)\n2026-11-15 15:26:22 | INFO | &#91;DRY-RUN] stop the balancer\n2026-11-15 15:26:22 | INFO | --- mdb-db2:27017 (config csrs, SECONDARY, 8.0.28) ---\n    | 2026-11-15 15:26:24 | INFO | &#91;DRY-RUN] 1. stop 'mdbcfg02'\n    | 2026-11-15 15:26:24 | INFO | &#91;DRY-RUN] 2. point 'mdbcfg02' to '\/u01\/app\/mongodb\/product\/9.0.8' (mongodb.lst, systemd unit)\n    | 2026-11-15 15:26:24 | INFO | &#91;DRY-RUN] 3. start 'mdbcfg02' and check it runs 9.0.8\n    | 2026-11-15 15:26:24 | INFO | &#91;DRY-RUN] 4. wait for the member to be SECONDARY and caught up\n&#91;...]\n2026-11-15 15:26:27 | INFO | --- mdb-db1:27017 (config csrs, PRIMARY, 8.0.28) ---\n    | 2026-11-15 15:26:29 | INFO | &#91;DRY-RUN] 1. step down the primary and wait for another member to take over\n    | 2026-11-15 15:26:29 | INFO | &#91;DRY-RUN] 2. stop 'mdbcfg01'\n&#91;...]\n2026-11-15 15:26:53 | INFO | The FCV was not changed. To change it, run on the mongos: db.adminCommand({\"setFeatureCompatibilityVersion\": \"9.0\", \"confirm\": true})\n2026-11-15 15:26:53 | INFO | &#91;DRY-RUN] start the balancer<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The order is always the same: config servers, then each shard, then the routers. Inside a replica set, the secondaries come first and the primary last. The lines prefixed with <code class=\"nowrap\">|<\/code> are the steps of one member. The analysis found no error and no warning, and the dry run changes nothing. Running the same command without <code class=\"nowrap\">--dry-run<\/code> starts the upgrade. While it runs, <code class=\"nowrap\">--status<\/code> can be run from another session. It shows where every member stands against the target. Here, the config servers and the first shard are on <code class=\"nowrap\">9.0.8<\/code>, the balancer is stopped, and one member of <code class=\"nowrap\">rs2<\/code> is being restarted, so DMK cannot read it:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>$ dmk_upgrade.py -i mdbmgs1 --sharded-cluster --status --target-version 9.0.8\nSharded cluster, 13 member(s), FCV 8.0, balancer off\nMEMBER          KIND    GROUP   ROLE       INSTANCE  RUNNING  HOME    FCV  NOTE\nmdb-db1:27017   config  csrs    PRIMARY    mdbcfg01  9.0.8    9.0.8   8.0\nmdb-db2:27017   config  csrs    SECONDARY  mdbcfg02  9.0.8    9.0.8   8.0\nmdb-db3:27017   config  csrs    SECONDARY  mdbcfg03  9.0.8    9.0.8   8.0\nmdb-db1:27018   shard   rs1     SECONDARY  mdbrs11   9.0.8    9.0.8   8.0\nmdb-db2:27018   shard   rs1     PRIMARY    mdbrs12   9.0.8    9.0.8   8.0\nmdb-db3:27018   shard   rs1     SECONDARY  mdbrs13   9.0.8    9.0.8   8.0\nmdb-db1:27019   shard   rs2     PRIMARY    mdbrs21   8.0.28   8.0.28  8.0  not on target\nmdb-db2:27019   shard   rs2     SECONDARY            8.0.28                unreadable: Command execution \/u01\/app\/mongodb\/product\/8.0.28\/bin\/mongos, not on target\nmdb-db3:27019   shard   rs2     SECONDARY  mdbrs23   8.0.28   8.0.28  8.0  not on target\nmdb-db1:27020   shard   rs3     PRIMARY    mdbrs31   8.0.28   8.0.28  8.0  not on target\nmdb-db2:27020   shard   rs3     SECONDARY  mdbrs32   8.0.28   8.0.28  8.0  not on target\nmdb-db3:27020   shard   rs3     SECONDARY  mdbrs33   8.0.28   8.0.28  8.0  not on target\nmdb-mgs1:27017  mongos  mongos  MONGOS     mdbmgs1   8.0.28   8.0.28       not on target\nTarget 9.0.8: 6 of 13 member(s) run it, FCV 8.0 -&gt; 9.0 still to change.<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">When the upgrade ends, DMK starts the balancer again and leaves the feature compatibility version on <code class=\"nowrap\">8.0<\/code> (because <code class=\"nowrap\">--update-fcv<\/code> was not given).<\/p>\n\n\n\n<h3 id=\"backup-and-restore\" class=\"wp-block-heading\">Backup and restore<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Sharded clusters.<\/strong> <code class=\"nowrap\">dmk_backup.py<\/code> and <code class=\"nowrap\">dmk_restore.py<\/code> accept a <code class=\"nowrap\">mongos<\/code>, with the balancer stopped and the shard keys restored.<\/li>\n\n\n\n<li><strong>Single database or collection.<\/strong> Both scripts accept <code class=\"nowrap\">-d<\/code> (<code class=\"nowrap\">--database<\/code>), which limits the operation to one database. They also accept <code class=\"nowrap\">-c<\/code> (<code class=\"nowrap\">--collection<\/code>), which limits it to one collection and requires <code class=\"nowrap\">-d<\/code>. <code class=\"nowrap\">dmk_backup.py<\/code> was renamed from <code class=\"nowrap\">dmk_dbbackup.py<\/code>, and the old name is kept as an alias.<\/li>\n\n\n\n<li><strong>Retention.<\/strong> <code class=\"nowrap\">dmk_backup_purge.py<\/code> deletes the backups older than <code class=\"nowrap\">BACKUP_RETENTION_DAYS<\/code> (default <code class=\"nowrap\">14<\/code>) and outside the <code class=\"nowrap\">BACKUP_RETENTION_COUNT<\/code> (default <code class=\"nowrap\">5<\/code>) most recent. <code class=\"nowrap\">dmk_backup.py<\/code> runs it after every successful backup unless <code class=\"nowrap\">--no-purge<\/code> is passed.<\/li>\n\n\n\n<li><strong>Safer backups.<\/strong> A backup is written under a temporary name and renamed at the end, so a killed backup never looks valid. A lock prevents two operations on one instance from overlapping, and credentials are masked in the logs.<\/li>\n<\/ul>\n\n\n\n<h3 id=\"other-changes\" class=\"wp-block-heading\">Other changes<\/h3>\n\n\n\n<ul class=\"nv-cv-m wp-block-list\">\n<li><code class=\"nowrap\">dmk_create.py<\/code> and <code class=\"nowrap\">dmk_ctl.py<\/code> replace <code class=\"nowrap\">dmk_dbcreate.py<\/code> and <code class=\"nowrap\">dmk_db_ctl.py<\/code>, which stay as aliases. The aliases <code class=\"nowrap\">mgstart<\/code>, <code class=\"nowrap\">mgstop<\/code> and <code class=\"nowrap\">mgrestart<\/code> call <code class=\"nowrap\">dmk_ctl.py<\/code>, and <code class=\"nowrap\">--startup-report<\/code> prints the warnings found at the start of the instance.<\/li>\n\n\n\n<li>MongoDB 9.0 is supported, Community and Enterprise, on RHEL 8 and 9 and on Ubuntu 22.04.<\/li>\n\n\n\n<li>The DMK administrator user can authenticate with an X.509 client certificate instead of a password.<\/li>\n\n\n\n<li><code class=\"nowrap\">dmk_create.py<\/code> refuses invalid instance names, ports and templates before it creates anything.<\/li>\n\n\n\n<li><code class=\"nowrap\">dmk_status.py<\/code> reports the live version and edition with <code class=\"nowrap\">buildInfo<\/code>. It exits non-zero when an instance cannot be assessed.<\/li>\n\n\n\n<li>Housekeeping <code class=\"nowrap\">TRUNC<\/code> no longer deletes the newest lines of a file that is not valid UTF-8.<\/li>\n<\/ul>\n\n\n\n<h2 id=\"upgrading-from-an-earlier-version-of-dmk\" class=\"wp-block-heading\">Upgrading from an earlier version of DMK<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If you are upgrading from DMK 2.6.0, replace the DMK folder with the new one:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>cd \/u01\/app\/mongodb\/local\nmv dmk .dmk_old\nunzip \/path\/to\/dmk_mongodb-2.7.0.zip\ndmk<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Crontab entries or scripts that call <code class=\"nowrap\">dmk_dbbackup.py<\/code> directly keep working: the old name is kept as an alias for <code class=\"nowrap\">dmk_backup.py<\/code>. Anyone relying on point-in-time recovery should set up <code class=\"nowrap\">dmk_oplog_backup.py<\/code> in cron before needing it. PITR beyond the oplog window of a single backup depends on it having already been archiving.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you are upgrading from DMK 2.5.0 or earlier, read the <a href=\"https:\/\/www.dbi-services.com\/blog\/mongodb-dmk-2-6-0-pymongo-integration-and-new-features\/\">release notes of DMK 2.6.0<\/a> first.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In this blog, I will present the new features introduced with the latest release (2.7.0) of the MongoDB DMK. The DMK is a set of standardized tools that aims at easing the work of DBAs. It embeds the best practices of dbi in common scripts across all the database servers of an organization. dbi services&hellip;&nbsp;<\/p>\n","protected":false},"author":152,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"neve_meta_sidebar":"","neve_meta_container":"","neve_meta_enable_content_width":"","neve_meta_content_width":0,"neve_meta_title_alignment":"","neve_meta_author_avatar":"","neve_post_elements_order":"","neve_meta_disable_header":"","neve_meta_disable_footer":"","neve_meta_disable_title":"","neve_meta_reading_time":"","_themeisle_gutenberg_block_has_review":false,"footnotes":""},"categories":[4133,3787,59],"tags":[22691,22693,202,559,1142,3571,22690,22692,1702,854,917,219,22694],"class_list":["post-48877","post","type-post","status-publish","format-standard","category-database","category-goldengate","category-oracle","tag-2-7-0","tag-9-0","tag-backup","tag-dmk","tag-management","tag-mongo","tag-mongodb","tag-oplog","tag-pitr","tag-restore","tag-sharding","tag-upgrade","tag-x509"],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v28.8 (Yoast SEO v28.9) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>MongoDB DMK 2.7.0 : point-in-time recovery, 9.0 support and auto-upgrade - dbi services Blog<\/title>\n<meta name=\"description\" content=\"MongoDB DMK 2.7.0 adds point-in-time recovery, upgrade and downgrade scripts for MongoDB 9.0, and sharded cluster backup and restore.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/mongodb-dmk-2-7-0-point-in-time-recovery-9-0-support-and-auto-upgrade\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"MongoDB DMK 2.7.0 : point-in-time recovery, 9.0 support and auto-upgrade\" \/>\n<meta property=\"og:description\" content=\"MongoDB DMK 2.7.0 adds point-in-time recovery, upgrade and downgrade scripts for MongoDB 9.0, and sharded cluster backup and restore.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/mongodb-dmk-2-7-0-point-in-time-recovery-9-0-support-and-auto-upgrade\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi services Blog\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/dbiservices\/\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-20T15:00:11+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-11-20T15:00:20+00:00\" \/>\n<meta name=\"author\" content=\"Julien Delattre\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@dbiservices\" \/>\n<meta name=\"twitter:site\" content=\"@dbiservices\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Julien Delattre\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/mongodb-dmk-2-7-0-point-in-time-recovery-9-0-support-and-auto-upgrade\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/mongodb-dmk-2-7-0-point-in-time-recovery-9-0-support-and-auto-upgrade\\\/\"},\"author\":{\"name\":\"Julien Delattre\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/0e990b04385bd7ff84b414bb8d92c544\"},\"headline\":\"MongoDB DMK 2.7.0 : point-in-time recovery, 9.0 support and auto-upgrade\",\"datePublished\":\"2026-11-20T15:00:11+00:00\",\"dateModified\":\"2026-11-20T15:00:20+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/mongodb-dmk-2-7-0-point-in-time-recovery-9-0-support-and-auto-upgrade\\\/\"},\"wordCount\":987,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/#organization\"},\"keywords\":[\"2.7.0\",\"9.0\",\"Backup\",\"DMK\",\"Management\",\"Mongo\",\"mongodb\",\"oplog\",\"PITR\",\"Restore\",\"Sharding\",\"Upgrade\",\"x509\"],\"articleSection\":[\"Database\",\"GoldenGate\",\"Oracle\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/mongodb-dmk-2-7-0-point-in-time-recovery-9-0-support-and-auto-upgrade\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/mongodb-dmk-2-7-0-point-in-time-recovery-9-0-support-and-auto-upgrade\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/mongodb-dmk-2-7-0-point-in-time-recovery-9-0-support-and-auto-upgrade\\\/\",\"name\":\"MongoDB DMK 2.7.0 : point-in-time recovery, 9.0 support and auto-upgrade - dbi services Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\"},\"datePublished\":\"2026-11-20T15:00:11+00:00\",\"dateModified\":\"2026-11-20T15:00:20+00:00\",\"description\":\"MongoDB DMK 2.7.0 adds point-in-time recovery, upgrade and downgrade scripts for MongoDB 9.0, and sharded cluster backup and restore.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/mongodb-dmk-2-7-0-point-in-time-recovery-9-0-support-and-auto-upgrade\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/mongodb-dmk-2-7-0-point-in-time-recovery-9-0-support-and-auto-upgrade\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/mongodb-dmk-2-7-0-point-in-time-recovery-9-0-support-and-auto-upgrade\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"MongoDB DMK 2.7.0 : point-in-time recovery, 9.0 support and auto-upgrade\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\",\"name\":\"dbi services Blog\",\"description\":\"#BeSharing\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/#organization\",\"name\":\"dbi services\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/dbi-services-logo.png\",\"contentUrl\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/dbi-services-logo.png\",\"width\":512,\"height\":512,\"caption\":\"dbi services\"},\"image\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/dbiservices\\\/\",\"https:\\\/\\\/x.com\\\/dbiservices\",\"https:\\\/\\\/www.linkedin.com\\\/company\\\/dbi-services\\\/\",\"https:\\\/\\\/www.youtube.com\\\/user\\\/dbiservices\"],\"description\":\"Swiss IT consulting and services company specialized in efficient data infrastructures and platforms: databases, application servers, cloud, DevOps, digitalization, analytics, data quality and monitoring. Headquartered in Del\u00e9mont with offices in Nyon, Basel, Bern and Zurich.\",\"email\":\"info@dbi-services.com\",\"telephone\":\"+41 32 422 96 00\",\"legalName\":\"dbi services SA\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/0e990b04385bd7ff84b414bb8d92c544\",\"name\":\"Julien Delattre\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/05\\\/JDE_Web-1-scaled.jpg\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/05\\\/JDE_Web-1-scaled.jpg\",\"contentUrl\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/05\\\/JDE_Web-1-scaled.jpg\",\"caption\":\"Julien Delattre\"},\"description\":\"Julien Delattre, member of the Oracle Team Zurich, has more than five years of experience specializing in Oracle databases, plus expertise in MariaDB and MongoDB. Prior to dbi services, he was a Database Administrator at Atos in Angers, France, and a Data Scientist at Air France in Paris and Apurata in Lima. Julien holds a Master's degree in Computer Science, Data Science, and Statistics from Centrale Paris \\\/ Universit\u00e9 Paris-Saclay.\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/author\\\/julien-delattre\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"MongoDB DMK 2.7.0 : point-in-time recovery, 9.0 support and auto-upgrade - dbi services Blog","description":"MongoDB DMK 2.7.0 adds point-in-time recovery, upgrade and downgrade scripts for MongoDB 9.0, and sharded cluster backup and restore.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/mongodb-dmk-2-7-0-point-in-time-recovery-9-0-support-and-auto-upgrade\/","og_locale":"en_US","og_type":"article","og_title":"MongoDB DMK 2.7.0 : point-in-time recovery, 9.0 support and auto-upgrade","og_description":"MongoDB DMK 2.7.0 adds point-in-time recovery, upgrade and downgrade scripts for MongoDB 9.0, and sharded cluster backup and restore.","og_url":"https:\/\/www.dbi-services.com\/blog\/mongodb-dmk-2-7-0-point-in-time-recovery-9-0-support-and-auto-upgrade\/","og_site_name":"dbi services Blog","article_publisher":"https:\/\/www.facebook.com\/dbiservices\/","article_published_time":"2026-11-20T15:00:11+00:00","article_modified_time":"2026-11-20T15:00:20+00:00","author":"Julien Delattre","twitter_card":"summary_large_image","twitter_creator":"@dbiservices","twitter_site":"@dbiservices","twitter_misc":{"Written by":"Julien Delattre","Est. reading time":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/mongodb-dmk-2-7-0-point-in-time-recovery-9-0-support-and-auto-upgrade\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/mongodb-dmk-2-7-0-point-in-time-recovery-9-0-support-and-auto-upgrade\/"},"author":{"name":"Julien Delattre","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0e990b04385bd7ff84b414bb8d92c544"},"headline":"MongoDB DMK 2.7.0 : point-in-time recovery, 9.0 support and auto-upgrade","datePublished":"2026-11-20T15:00:11+00:00","dateModified":"2026-11-20T15:00:20+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/mongodb-dmk-2-7-0-point-in-time-recovery-9-0-support-and-auto-upgrade\/"},"wordCount":987,"commentCount":0,"publisher":{"@id":"https:\/\/www.dbi-services.com\/#organization"},"keywords":["2.7.0","9.0","Backup","DMK","Management","Mongo","mongodb","oplog","PITR","Restore","Sharding","Upgrade","x509"],"articleSection":["Database","GoldenGate","Oracle"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/mongodb-dmk-2-7-0-point-in-time-recovery-9-0-support-and-auto-upgrade\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/mongodb-dmk-2-7-0-point-in-time-recovery-9-0-support-and-auto-upgrade\/","url":"https:\/\/www.dbi-services.com\/blog\/mongodb-dmk-2-7-0-point-in-time-recovery-9-0-support-and-auto-upgrade\/","name":"MongoDB DMK 2.7.0 : point-in-time recovery, 9.0 support and auto-upgrade - dbi services Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2026-11-20T15:00:11+00:00","dateModified":"2026-11-20T15:00:20+00:00","description":"MongoDB DMK 2.7.0 adds point-in-time recovery, upgrade and downgrade scripts for MongoDB 9.0, and sharded cluster backup and restore.","breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/mongodb-dmk-2-7-0-point-in-time-recovery-9-0-support-and-auto-upgrade\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/mongodb-dmk-2-7-0-point-in-time-recovery-9-0-support-and-auto-upgrade\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/mongodb-dmk-2-7-0-point-in-time-recovery-9-0-support-and-auto-upgrade\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"MongoDB DMK 2.7.0 : point-in-time recovery, 9.0 support and auto-upgrade"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi services Blog","description":"#BeSharing","publisher":{"@id":"https:\/\/www.dbi-services.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.dbi-services.com\/#organization","name":"dbi services","url":"https:\/\/www.dbi-services.com\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2026\/09\/dbi-services-logo.png","contentUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2026\/09\/dbi-services-logo.png","width":512,"height":512,"caption":"dbi services"},"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/dbiservices\/","https:\/\/x.com\/dbiservices","https:\/\/www.linkedin.com\/company\/dbi-services\/","https:\/\/www.youtube.com\/user\/dbiservices"],"description":"Swiss IT consulting and services company specialized in efficient data infrastructures and platforms: databases, application servers, cloud, DevOps, digitalization, analytics, data quality and monitoring. Headquartered in Del\u00e9mont with offices in Nyon, Basel, Bern and Zurich.","email":"info@dbi-services.com","telephone":"+41 32 422 96 00","legalName":"dbi services SA"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0e990b04385bd7ff84b414bb8d92c544","name":"Julien Delattre","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2025\/05\/JDE_Web-1-scaled.jpg","url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2025\/05\/JDE_Web-1-scaled.jpg","contentUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2025\/05\/JDE_Web-1-scaled.jpg","caption":"Julien Delattre"},"description":"Julien Delattre, member of the Oracle Team Zurich, has more than five years of experience specializing in Oracle databases, plus expertise in MariaDB and MongoDB. Prior to dbi services, he was a Database Administrator at Atos in Angers, France, and a Data Scientist at Air France in Paris and Apurata in Lima. Julien holds a Master's degree in Computer Science, Data Science, and Statistics from Centrale Paris \/ Universit\u00e9 Paris-Saclay.","url":"https:\/\/www.dbi-services.com\/blog\/author\/julien-delattre\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/48877","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/152"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=48877"}],"version-history":[{"count":2,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/48877\/revisions"}],"predecessor-version":[{"id":48882,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/48877\/revisions\/48882"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=48877"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=48877"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=48877"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}