{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-154-back-up-the-network-controller-database-before-sdn-maintenance/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-154-back-up-the-network-controller-database-before-sdn-maintenance/", "slug": "dse-20260908-154-back-up-the-network-controller-database-before-sdn-maintenance", "url": "https://update.dsesecurity.com/updates/dse-20260908-154-back-up-the-network-controller-database-before-sdn-maintenance/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-154-back-up-the-network-controller-database-before-sdn-maintenance.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-154-back-up-the-network-controller-database-before-sdn-maintenance/" }, "title": "Back up the Network Controller database before SDN maintenance", "summary": "Which Network Controller state must an SDN maintenance recovery plan preserve?", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "network-infrastructure", "label": "Networks & infrastructure", "alt": "Resilient network core with engineered blue and gold data paths.", "card_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "slug": "networks-infrastructure", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "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-08T18:14:37+00:00", "modified_at": "2026-09-08T18:26:31+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 1, "word_count": 203, "potentially_affected": "Administrators maintaining the multi-node SDN infrastructure described in Microsoft’s upgrade and recovery guidance.", "dse_recommendation": "Have the SDN owner identify the database backup artifact, protected destination, retention owner, and approved restore instructions.", "primary_source": { "name": "Upgrade, backup, and restore SDN infrastructure", "url": "https://learn.microsoft.com/en-us/windows-server/networking/sdn/manage/Update-Backup-Restore", "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": "

Source facts

\n

Microsoft’s SDN maintenance guidance distinguishes a Network Controller database backup from backups of the controller VMs. It states that VM backups alone do not ensure session continuity across multiple controller nodes. After upgrading a controller node, the procedure checks its status with Get-NetworkControllerNode and waits for Up before upgrading another node. Microsoft documentation.

\n

Applicability

\n

Identify the actual SDN architecture and releases and compare them with the documented procedure. Review the supported backup and restore process for that design before applying guidance from a different controller hosting model.

\n

DSE recommendation

\n

Have the SDN owner identify the database backup artifact, protected destination, retention owner, and approved restore instructions. Record controller node status before maintenance. Establish a pause condition if a node does not return to the expected state, and keep the backup decision separate from ordinary VM snapshot activity.

\n

Verification

\n

Verify that the intended backup operation completed and that its artifact can be located and checked. In an approved recovery exercise, validate the documented restoration path and representative network policy state. During maintenance, record each node’s return to service before proceeding and retain unexplained controller errors for investigation.

\n

Official references

\n

Microsoft Learn: Upgrade, backup, and restore SDN infrastructure. Source reviewed September 8, 2026.

", "content_text": "Source facts\nMicrosoft’s SDN maintenance guidance distinguishes a Network Controller database backup from backups of the controller VMs. It states that VM backups alone do not ensure session continuity across multiple controller nodes. After upgrading a controller node, the procedure checks its status with Get-NetworkControllerNode and waits for Up before upgrading another node. Microsoft documentation.\nApplicability\nIdentify the actual SDN architecture and releases and compare them with the documented procedure. Review the supported backup and restore process for that design before applying guidance from a different controller hosting model.\nDSE recommendation\nHave the SDN owner identify the database backup artifact, protected destination, retention owner, and approved restore instructions. Record controller node status before maintenance. Establish a pause condition if a node does not return to the expected state, and keep the backup decision separate from ordinary VM snapshot activity.\nVerification\nVerify that the intended backup operation completed and that its artifact can be located and checked. In an approved recovery exercise, validate the documented restoration path and representative network policy state. During maintenance, record each node’s return to service before proceeding and retain unexplained controller errors for investigation.\nOfficial references\nMicrosoft Learn: Upgrade, backup, and restore SDN infrastructure. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nMicrosoft’s SDN maintenance guidance distinguishes a Network Controller database backup from backups of the controller VMs. It states that VM backups alone do not ensure session continuity across multiple controller nodes. After upgrading a controller node, the procedure checks its status with Get-NetworkControllerNode and waits for Up before upgrading another node. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/networking/sdn/manage/Update-Backup-Restore).\n\n## Applicability\n\nIdentify the actual SDN architecture and releases and compare them with the documented procedure. Review the supported backup and restore process for that design before applying guidance from a different controller hosting model.\n\n## DSE recommendation\n\nHave the SDN owner identify the database backup artifact, protected destination, retention owner, and approved restore instructions. Record controller node status before maintenance. Establish a pause condition if a node does not return to the expected state, and keep the backup decision separate from ordinary VM snapshot activity.\n\n## Verification\n\nVerify that the intended backup operation completed and that its artifact can be located and checked. In an approved recovery exercise, validate the documented restoration path and representative network policy state. During maintenance, record each node’s return to service before proceeding and retain unexplained controller errors for investigation.\n\n## Official references\n\n[Microsoft Learn: Upgrade, backup, and restore SDN infrastructure](https://learn.microsoft.com/en-us/windows-server/networking/sdn/manage/Update-Backup-Restore). Source reviewed September 8, 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-20260908-154-back-up-the-network-controller-database-before-sdn-maintenance/", "url": "https://update.dsesecurity.com/updates/dse-20260908-154-back-up-the-network-controller-database-before-sdn-maintenance/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-154-back-up-the-network-controller-database-before-sdn-maintenance/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Back up the Network Controller database before SDN maintenance", "item": "https://update.dsesecurity.com/updates/dse-20260908-154-back-up-the-network-controller-database-before-sdn-maintenance/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-154-back-up-the-network-controller-database-before-sdn-maintenance/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-154-back-up-the-network-controller-database-before-sdn-maintenance/", "url": "https://update.dsesecurity.com/updates/dse-20260908-154-back-up-the-network-controller-database-before-sdn-maintenance/", "headline": "Back up the Network Controller database before SDN maintenance", "description": "Which Network Controller state must an SDN maintenance recovery plan preserve?", "abstract": "Which Network Controller state must an SDN maintenance recovery plan preserve?", "articleBody": "Source facts\nMicrosoft’s SDN maintenance guidance distinguishes a Network Controller database backup from backups of the controller VMs. It states that VM backups alone do not ensure session continuity across multiple controller nodes. After upgrading a controller node, the procedure checks its status with Get-NetworkControllerNode and waits for Up before upgrading another node. Microsoft documentation.\nApplicability\nIdentify the actual SDN architecture and releases and compare them with the documented procedure. Review the supported backup and restore process for that design before applying guidance from a different controller hosting model.\nDSE recommendation\nHave the SDN owner identify the database backup artifact, protected destination, retention owner, and approved restore instructions. Record controller node status before maintenance. Establish a pause condition if a node does not return to the expected state, and keep the backup decision separate from ordinary VM snapshot activity.\nVerification\nVerify that the intended backup operation completed and that its artifact can be located and checked. In an approved recovery exercise, validate the documented restoration path and representative network policy state. During maintenance, record each node’s return to service before proceeding and retain unexplained controller errors for investigation.\nOfficial references\nMicrosoft Learn: Upgrade, backup, and restore SDN infrastructure. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:14:37+00:00", "dateModified": "2026-09-08T18:26:31+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-154-back-up-the-network-controller-database-before-sdn-maintenance/" }, "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-20260908-154-back-up-the-network-controller-database-before-sdn-maintenance/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Back up the Network Controller database before SDN maintenance" }, "articleSection": [ "IT", "Networks & Infrastructure" ], "keywords": [ "IT", "Networks & Infrastructure", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "@type": "Thing", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "wordCount": 203, "timeRequired": "PT1M", "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": "Upgrade, backup, and restore SDN infrastructure", "url": "https://learn.microsoft.com/en-us/windows-server/networking/sdn/manage/Update-Backup-Restore" } } ] } }