{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-378-match-the-mabs-database-version-before-rebuilding-its-server/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/dse-20260909-378-match-the-mabs-database-version-before-rebuilding-its-server/",
        "slug": "dse-20260909-378-match-the-mabs-database-version-before-rebuilding-its-server",
        "url": "https://update.dsesecurity.com/updates/dse-20260909-378-match-the-mabs-database-version-before-rebuilding-its-server/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/dse-20260909-378-match-the-mabs-database-version-before-rebuilding-its-server.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-378-match-the-mabs-database-version-before-rebuilding-its-server/"
        },
        "title": "Match the MABS database version before rebuilding its server",
        "summary": "Include the database's update-rollup level and post-restore synchronization in a MABS rebuild plan.",
        "format": {
            "slug": "guide",
            "name": "Guide"
        },
        "priority": {
            "slug": "info",
            "name": "Information"
        },
        "featured": false,
        "image": {
            "theme": "continuity-recovery",
            "label": "Continuity & recovery",
            "alt": "Paired infrastructure paths converging on a stable recovered service.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20",
            "width": 2400,
            "height": 1350
        },
        "topics": [
            {
                "slug": "business-continuity",
                "name": "Business Continuity",
                "url": "https://update.dsesecurity.com/topic/business-continuity/"
            },
            {
                "slug": "it",
                "name": "IT",
                "url": "https://update.dsesecurity.com/topic/it/"
            }
        ],
        "author": {
            "name": "DSE Security Editorial Team",
            "url": "https://update.dsesecurity.com/#editorial-team",
            "type": "Organization"
        },
        "publisher": {
            "name": "Detection Systems & Engineering",
            "url": "https://dsesecurity.com/"
        },
        "published_at": "2026-09-10T00:25:38+00:00",
        "modified_at": "2026-09-10T02:01:56+00:00",
        "reviewed_on": "2026-09-09",
        "reading_minutes": 2,
        "word_count": 226,
        "potentially_affected": "Microsoft Azure Backup Server recovery using a backed-up DPMDB database.",
        "dse_recommendation": "Preserve the database's exact MABS version and plan synchronization before relying on recovered backup records.",
        "primary_source": {
            "name": "Back up the MABS server - Azure Backup | Microsoft Learn",
            "url": "https://learn.microsoft.com/en-us/azure/backup/backup-the-mabs-server",
            "published_on": null,
            "authority": "Microsoft Learn"
        },
        "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
        "usage_info": "https://update.dsesecurity.com/usage/",
        "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
        "content_html": "<h2>Source facts</h2>\n<p>Microsoft Azure Backup Server stores its configuration and backup information in DPMDB. To restore that database, the MABS installation must match its version, including the applicable update rollup.</p>\n<p>Microsoft requires DpmSync -Sync after restoring the database. The source warns that some replicas can still be marked missing after synchronization. It also conditions reuse of disk-based backups after a rebuild on the storage-pool disks having survived the outage. <a href=\"https://learn.microsoft.com/en-us/azure/backup/backup-the-mabs-server\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn</a>.</p>\n<h2>Applicability</h2>\n<p>Identify the saved database, originating MABS build, installed rollup, intended recovery server, and storage-pool condition. Review the source&#8217;s method-specific recovery procedure before restoring anything. Keep the database backup and access to protected backup data as separate recovery dependencies.</p>\n<h2>DSE recommendation</h2>\n<p>DSE recommends retaining the build and rollup evidence with the database recovery record. Confirm suitable installation media and an approved rebuild location before an incident. Assign someone to reconcile synchronization results and missing replicas instead of declaring the server recovered as soon as SQL accepts the database.</p>\n<h2>Verification</h2>\n<p>In an isolated authorized exercise, verify the installation/database version match, perform the documented restoration and synchronization, and inspect the resulting replica state. Test a representative recovery through the rebuilt service. Record unresolved replicas explicitly and preserve the observed storage-pool condition; do not generalize one successful restore to backups whose underlying disks were lost.</p>\n<h2>Official references</h2>\n<p><a href=\"https://learn.microsoft.com/en-us/azure/backup/backup-the-mabs-server\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn: Back up the MABS server</a>. Source retrieved September 9, 2026.</p>",
        "content_text": "Source facts\nMicrosoft Azure Backup Server stores its configuration and backup information in DPMDB. To restore that database, the MABS installation must match its version, including the applicable update rollup.\nMicrosoft requires DpmSync -Sync after restoring the database. The source warns that some replicas can still be marked missing after synchronization. It also conditions reuse of disk-based backups after a rebuild on the storage-pool disks having survived the outage. Microsoft Learn.\nApplicability\nIdentify the saved database, originating MABS build, installed rollup, intended recovery server, and storage-pool condition. Review the source’s method-specific recovery procedure before restoring anything. Keep the database backup and access to protected backup data as separate recovery dependencies.\nDSE recommendation\nDSE recommends retaining the build and rollup evidence with the database recovery record. Confirm suitable installation media and an approved rebuild location before an incident. Assign someone to reconcile synchronization results and missing replicas instead of declaring the server recovered as soon as SQL accepts the database.\nVerification\nIn an isolated authorized exercise, verify the installation/database version match, perform the documented restoration and synchronization, and inspect the resulting replica state. Test a representative recovery through the rebuilt service. Record unresolved replicas explicitly and preserve the observed storage-pool condition; do not generalize one successful restore to backups whose underlying disks were lost.\nOfficial references\nMicrosoft Learn: Back up the MABS server. Source retrieved September 9, 2026.",
        "content_markdown": "## Source facts\n\nMicrosoft Azure Backup Server stores its configuration and backup information in DPMDB. To restore that database, the MABS installation must match its version, including the applicable update rollup.\n\nMicrosoft requires DpmSync -Sync after restoring the database. The source warns that some replicas can still be marked missing after synchronization. It also conditions reuse of disk-based backups after a rebuild on the storage-pool disks having survived the outage. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/backup/backup-the-mabs-server).\n\n## Applicability\n\nIdentify the saved database, originating MABS build, installed rollup, intended recovery server, and storage-pool condition. Review the source’s method-specific recovery procedure before restoring anything. Keep the database backup and access to protected backup data as separate recovery dependencies.\n\n## DSE recommendation\n\nDSE recommends retaining the build and rollup evidence with the database recovery record. Confirm suitable installation media and an approved rebuild location before an incident. Assign someone to reconcile synchronization results and missing replicas instead of declaring the server recovered as soon as SQL accepts the database.\n\n## Verification\n\nIn an isolated authorized exercise, verify the installation/database version match, perform the documented restoration and synchronization, and inspect the resulting replica state. Test a representative recovery through the rebuilt service. Record unresolved replicas explicitly and preserve the observed storage-pool condition; do not generalize one successful restore to backups whose underlying disks were lost.\n\n## Official references\n\n[Microsoft Learn: Back up the MABS server](https://learn.microsoft.com/en-us/azure/backup/backup-the-mabs-server). Source retrieved September 9, 2026."
    },
    "json_ld": {
        "@context": "https://schema.org",
        "@graph": [
            {
                "@type": "Organization",
                "@id": "https://dsesecurity.com/#organization",
                "name": "Detection Systems & Engineering",
                "alternateName": "DSE Security",
                "url": "https://dsesecurity.com/",
                "logo": {
                    "@type": "ImageObject",
                    "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20"
                }
            },
            {
                "@type": "Organization",
                "@id": "https://update.dsesecurity.com/#editorial-team",
                "name": "DSE Security Editorial Team",
                "url": "https://update.dsesecurity.com/",
                "parentOrganization": {
                    "@id": "https://dsesecurity.com/#organization"
                }
            },
            {
                "@type": "WebSite",
                "@id": "https://update.dsesecurity.com/#website",
                "name": "DSE Updates",
                "alternateName": "DSE Security Knowledge Hub",
                "url": "https://update.dsesecurity.com/",
                "inLanguage": "en-US",
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "potentialAction": {
                    "@type": "SearchAction",
                    "target": {
                        "@type": "EntryPoint",
                        "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}"
                    },
                    "query-input": "required name=search_term_string"
                }
            },
            {
                "@type": "WebPage",
                "@id": "https://update.dsesecurity.com/updates/dse-20260909-378-match-the-mabs-database-version-before-rebuilding-its-server/",
                "url": "https://update.dsesecurity.com/updates/dse-20260909-378-match-the-mabs-database-version-before-rebuilding-its-server/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-09-09"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/dse-20260909-378-match-the-mabs-database-version-before-rebuilding-its-server/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Match the MABS database version before rebuilding its server",
                        "item": "https://update.dsesecurity.com/updates/dse-20260909-378-match-the-mabs-database-version-before-rebuilding-its-server/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/dse-20260909-378-match-the-mabs-database-version-before-rebuilding-its-server/#article",
                "identifier": "https://update.dsesecurity.com/updates/dse-20260909-378-match-the-mabs-database-version-before-rebuilding-its-server/",
                "url": "https://update.dsesecurity.com/updates/dse-20260909-378-match-the-mabs-database-version-before-rebuilding-its-server/",
                "headline": "Match the MABS database version before rebuilding its server",
                "description": "Include the database's update-rollup level and post-restore synchronization in a MABS rebuild plan.",
                "abstract": "Include the database's update-rollup level and post-restore synchronization in a MABS rebuild plan.",
                "articleBody": "Source facts\nMicrosoft Azure Backup Server stores its configuration and backup information in DPMDB. To restore that database, the MABS installation must match its version, including the applicable update rollup.\nMicrosoft requires DpmSync -Sync after restoring the database. The source warns that some replicas can still be marked missing after synchronization. It also conditions reuse of disk-based backups after a rebuild on the storage-pool disks having survived the outage. Microsoft Learn.\nApplicability\nIdentify the saved database, originating MABS build, installed rollup, intended recovery server, and storage-pool condition. Review the source’s method-specific recovery procedure before restoring anything. Keep the database backup and access to protected backup data as separate recovery dependencies.\nDSE recommendation\nDSE recommends retaining the build and rollup evidence with the database recovery record. Confirm suitable installation media and an approved rebuild location before an incident. Assign someone to reconcile synchronization results and missing replicas instead of declaring the server recovered as soon as SQL accepts the database.\nVerification\nIn an isolated authorized exercise, verify the installation/database version match, perform the documented restoration and synchronization, and inspect the resulting replica state. Test a representative recovery through the rebuilt service. Record unresolved replicas explicitly and preserve the observed storage-pool condition; do not generalize one successful restore to backups whose underlying disks were lost.\nOfficial references\nMicrosoft Learn: Back up the MABS server. Source retrieved September 9, 2026.",
                "datePublished": "2026-09-10T00:25:38+00:00",
                "dateModified": "2026-09-10T02:01:56+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/dse-20260909-378-match-the-mabs-database-version-before-rebuilding-its-server/"
                },
                "inLanguage": "en-US",
                "isAccessibleForFree": true,
                "author": {
                    "@type": "Organization",
                    "name": "DSE Security Editorial Team",
                    "url": "https://update.dsesecurity.com/#editorial-team"
                },
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "image": {
                    "@type": "ImageObject",
                    "@id": "https://update.dsesecurity.com/updates/dse-20260909-378-match-the-mabs-database-version-before-rebuilding-its-server/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Match the MABS database version before rebuilding its server"
                },
                "articleSection": [
                    "Business Continuity",
                    "IT"
                ],
                "keywords": [
                    "Business Continuity",
                    "IT",
                    "Guide",
                    "Information priority"
                ],
                "genre": "Guide",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Business Continuity",
                        "url": "https://update.dsesecurity.com/topic/business-continuity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "IT",
                        "url": "https://update.dsesecurity.com/topic/it/"
                    }
                ],
                "wordCount": 226,
                "timeRequired": "PT2M",
                "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
                "usageInfo": "https://update.dsesecurity.com/usage/",
                "copyrightHolder": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
                "citation": {
                    "@type": "CreativeWork",
                    "name": "Back up the MABS server - Azure Backup | Microsoft Learn",
                    "url": "https://learn.microsoft.com/en-us/azure/backup/backup-the-mabs-server"
                }
            }
        ]
    }
}