{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-470-verify-multidisk-backup-coordination-before-striping-an-avs-guest-filesystem/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/dse-20260909-470-verify-multidisk-backup-coordination-before-striping-an-avs-guest-filesystem/",
        "slug": "dse-20260909-470-verify-multidisk-backup-coordination-before-striping-an-avs-guest-filesystem",
        "url": "https://update.dsesecurity.com/updates/dse-20260909-470-verify-multidisk-backup-coordination-before-striping-an-avs-guest-filesystem/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/dse-20260909-470-verify-multidisk-backup-coordination-before-striping-an-avs-guest-filesystem.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-470-verify-multidisk-backup-coordination-before-striping-an-avs-guest-filesystem/"
        },
        "title": "Verify multidisk backup coordination before striping an AVS guest filesystem",
        "summary": "Treat simultaneous protection of the participating VMDKs as an eligibility check for the striped layout.",
        "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:24:06+00:00",
        "modified_at": "2026-09-10T02:08:04+00:00",
        "reviewed_on": "2026-09-09",
        "reading_minutes": 2,
        "word_count": 237,
        "potentially_affected": "Azure VMware Solution guests with filesystems striped across multiple VMDKs on Azure NetApp Files datastores.",
        "dse_recommendation": "Confirm coordinated protection of every participating virtual disk before approving the striped layout.",
        "primary_source": {
            "name": "Azure VMware Solution datastore performance considerations for Azure NetApp Files | Microsoft Learn",
            "url": "https://learn.microsoft.com/en-us/azure/azure-netapp-files/performance-azure-vmware-solution-datastore",
            "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&#8217;s Azure VMware Solution guidance warns that, when a volume is striped across disks, the backup or disaster-recovery product must support backing up multiple virtual disks simultaneously. The filesystem needs the participating disks frozen during the snapshot or backup.</p>\n<p>For a single VM, the source contrasts separate VMDK filesystems with storage-management tools that stripe across VMDKs. Its examples include LVM, MSSQL Filegroups, and Oracle ASM. <a href=\"https://learn.microsoft.com/en-us/azure/azure-netapp-files/performance-azure-vmware-solution-datastore\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn</a>.</p>\n<h2>Applicability</h2>\n<p>Map the guest filesystem or application data layout to its VMDKs and datastores. Review the exact backup product&#8217;s support for that arrangement before adopting striping. Do not treat performance examples from the source as a guarantee for the proposed workload.</p>\n<h2>DSE recommendation</h2>\n<p>DSE recommends making the protection review a prerequisite to the layout decision. Have the virtualization, storage, application, and backup owners identify the complete participating disk set and how a consistent point is captured. If that coordination cannot be established, reconsider the proposed layout instead of accepting an untested recovery dependency for a performance target.</p>\n<h2>Verification</h2>\n<p>Use an isolated representative guest to exercise the approved coordinated backup and restore procedure. Confirm every member disk belongs to the intended recovery point, then have the application owner validate the restored dataset. Preserve the disk-to-datastore map and coordination evidence; separate per-disk job successes are not the agreed test of the striped filesystem.</p>\n<h2>Official references</h2>\n<p><a href=\"https://learn.microsoft.com/en-us/azure/azure-netapp-files/performance-azure-vmware-solution-datastore\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn: Azure VMware Solution datastore performance considerations for Azure NetApp Files</a>. Source retrieved September 9, 2026.</p>",
        "content_text": "Source facts\nMicrosoft’s Azure VMware Solution guidance warns that, when a volume is striped across disks, the backup or disaster-recovery product must support backing up multiple virtual disks simultaneously. The filesystem needs the participating disks frozen during the snapshot or backup.\nFor a single VM, the source contrasts separate VMDK filesystems with storage-management tools that stripe across VMDKs. Its examples include LVM, MSSQL Filegroups, and Oracle ASM. Microsoft Learn.\nApplicability\nMap the guest filesystem or application data layout to its VMDKs and datastores. Review the exact backup product’s support for that arrangement before adopting striping. Do not treat performance examples from the source as a guarantee for the proposed workload.\nDSE recommendation\nDSE recommends making the protection review a prerequisite to the layout decision. Have the virtualization, storage, application, and backup owners identify the complete participating disk set and how a consistent point is captured. If that coordination cannot be established, reconsider the proposed layout instead of accepting an untested recovery dependency for a performance target.\nVerification\nUse an isolated representative guest to exercise the approved coordinated backup and restore procedure. Confirm every member disk belongs to the intended recovery point, then have the application owner validate the restored dataset. Preserve the disk-to-datastore map and coordination evidence; separate per-disk job successes are not the agreed test of the striped filesystem.\nOfficial references\nMicrosoft Learn: Azure VMware Solution datastore performance considerations for Azure NetApp Files. Source retrieved September 9, 2026.",
        "content_markdown": "## Source facts\n\nMicrosoft’s Azure VMware Solution guidance warns that, when a volume is striped across disks, the backup or disaster-recovery product must support backing up multiple virtual disks simultaneously. The filesystem needs the participating disks frozen during the snapshot or backup.\n\nFor a single VM, the source contrasts separate VMDK filesystems with storage-management tools that stripe across VMDKs. Its examples include LVM, MSSQL Filegroups, and Oracle ASM. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/azure-netapp-files/performance-azure-vmware-solution-datastore).\n\n## Applicability\n\nMap the guest filesystem or application data layout to its VMDKs and datastores. Review the exact backup product’s support for that arrangement before adopting striping. Do not treat performance examples from the source as a guarantee for the proposed workload.\n\n## DSE recommendation\n\nDSE recommends making the protection review a prerequisite to the layout decision. Have the virtualization, storage, application, and backup owners identify the complete participating disk set and how a consistent point is captured. If that coordination cannot be established, reconsider the proposed layout instead of accepting an untested recovery dependency for a performance target.\n\n## Verification\n\nUse an isolated representative guest to exercise the approved coordinated backup and restore procedure. Confirm every member disk belongs to the intended recovery point, then have the application owner validate the restored dataset. Preserve the disk-to-datastore map and coordination evidence; separate per-disk job successes are not the agreed test of the striped filesystem.\n\n## Official references\n\n[Microsoft Learn: Azure VMware Solution datastore performance considerations for Azure NetApp Files](https://learn.microsoft.com/en-us/azure/azure-netapp-files/performance-azure-vmware-solution-datastore). 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-470-verify-multidisk-backup-coordination-before-striping-an-avs-guest-filesystem/",
                "url": "https://update.dsesecurity.com/updates/dse-20260909-470-verify-multidisk-backup-coordination-before-striping-an-avs-guest-filesystem/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-09-09"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/dse-20260909-470-verify-multidisk-backup-coordination-before-striping-an-avs-guest-filesystem/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Verify multidisk backup coordination before striping an AVS guest filesystem",
                        "item": "https://update.dsesecurity.com/updates/dse-20260909-470-verify-multidisk-backup-coordination-before-striping-an-avs-guest-filesystem/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/dse-20260909-470-verify-multidisk-backup-coordination-before-striping-an-avs-guest-filesystem/#article",
                "identifier": "https://update.dsesecurity.com/updates/dse-20260909-470-verify-multidisk-backup-coordination-before-striping-an-avs-guest-filesystem/",
                "url": "https://update.dsesecurity.com/updates/dse-20260909-470-verify-multidisk-backup-coordination-before-striping-an-avs-guest-filesystem/",
                "headline": "Verify multidisk backup coordination before striping an AVS guest filesystem",
                "description": "Treat simultaneous protection of the participating VMDKs as an eligibility check for the striped layout.",
                "abstract": "Treat simultaneous protection of the participating VMDKs as an eligibility check for the striped layout.",
                "articleBody": "Source facts\nMicrosoft’s Azure VMware Solution guidance warns that, when a volume is striped across disks, the backup or disaster-recovery product must support backing up multiple virtual disks simultaneously. The filesystem needs the participating disks frozen during the snapshot or backup.\nFor a single VM, the source contrasts separate VMDK filesystems with storage-management tools that stripe across VMDKs. Its examples include LVM, MSSQL Filegroups, and Oracle ASM. Microsoft Learn.\nApplicability\nMap the guest filesystem or application data layout to its VMDKs and datastores. Review the exact backup product’s support for that arrangement before adopting striping. Do not treat performance examples from the source as a guarantee for the proposed workload.\nDSE recommendation\nDSE recommends making the protection review a prerequisite to the layout decision. Have the virtualization, storage, application, and backup owners identify the complete participating disk set and how a consistent point is captured. If that coordination cannot be established, reconsider the proposed layout instead of accepting an untested recovery dependency for a performance target.\nVerification\nUse an isolated representative guest to exercise the approved coordinated backup and restore procedure. Confirm every member disk belongs to the intended recovery point, then have the application owner validate the restored dataset. Preserve the disk-to-datastore map and coordination evidence; separate per-disk job successes are not the agreed test of the striped filesystem.\nOfficial references\nMicrosoft Learn: Azure VMware Solution datastore performance considerations for Azure NetApp Files. Source retrieved September 9, 2026.",
                "datePublished": "2026-09-10T00:24:06+00:00",
                "dateModified": "2026-09-10T02:08:04+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/dse-20260909-470-verify-multidisk-backup-coordination-before-striping-an-avs-guest-filesystem/"
                },
                "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-470-verify-multidisk-backup-coordination-before-striping-an-avs-guest-filesystem/#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": "Verify multidisk backup coordination before striping an AVS guest filesystem"
                },
                "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": 237,
                "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": "Azure VMware Solution datastore performance considerations for Azure NetApp Files | Microsoft Learn",
                    "url": "https://learn.microsoft.com/en-us/azure/azure-netapp-files/performance-azure-vmware-solution-datastore"
                }
            }
        ]
    }
}