{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-241-set-the-destination-and-initial-copy-for-hyper-v-replica/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-241-set-the-destination-and-initial-copy-for-hyper-v-replica/", "slug": "dse-20260908-241-set-the-destination-and-initial-copy-for-hyper-v-replica", "url": "https://update.dsesecurity.com/updates/dse-20260908-241-set-the-destination-and-initial-copy-for-hyper-v-replica/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-241-set-the-destination-and-initial-copy-for-hyper-v-replica.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-241-set-the-destination-and-initial-copy-for-hyper-v-replica/" }, "title": "Set the destination and initial copy for Hyper-V Replica", "summary": "What must be established before a virtual machine begins replication?", "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-08T18:13:10+00:00", "modified_at": "2026-09-08T18:29:34+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 1, "word_count": 212, "potentially_affected": "Operators enabling replication for a VM after the receiving Hyper-V host or cluster is configured.", "dse_recommendation": "Record the destination broker or host, authentication choice, selected disks, and initial-copy method.", "primary_source": { "name": "Replicate a virtual machine with Hyper-V Replica", "url": "https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/replication-virtual-machines", "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 describes VM replication setup after the receiving host or cluster has already been enabled for Hyper-V Replica. In Hyper-V Manager, a clustered destination is entered using the Hyper-V Replica Broker name; the connection retrieves the destination authentication and port settings. The initial copy can be transferred over the network or through external media. Microsoft Learn.

\n

Applicability

\n

Confirm the receiving configuration before opening the VM replication wizard. Use the documented tool-specific procedure for the actual topology. This review establishes the replication relationship and initial transfer; it does not replace a later failover rehearsal.

\n

DSE recommendation

\n

Record the destination broker or host, authentication choice, selected disks, and initial-copy method. Have the network and storage owners review the transfer against available capacity and the workload’s recovery objective. If external media is selected, assign custody and import ownership before exporting. Avoid treating completion of the setup wizard as completion of the initial replication.

\n

Verification

\n

Confirm that the relationship points to the intended receiver and includes the approved disks. Observe the initial-copy progress and subsequent replication health. Investigate a warning or stalled transfer before accepting the relationship into service. Retain the configuration and health evidence for the separate recovery-test plan.

\n

Official references

\n

Microsoft Learn: Replicate a virtual machine with Hyper-V Replica. Source reviewed September 8, 2026.

", "content_text": "Source facts\nMicrosoft describes VM replication setup after the receiving host or cluster has already been enabled for Hyper-V Replica. In Hyper-V Manager, a clustered destination is entered using the Hyper-V Replica Broker name; the connection retrieves the destination authentication and port settings. The initial copy can be transferred over the network or through external media. Microsoft Learn.\nApplicability\nConfirm the receiving configuration before opening the VM replication wizard. Use the documented tool-specific procedure for the actual topology. This review establishes the replication relationship and initial transfer; it does not replace a later failover rehearsal.\nDSE recommendation\nRecord the destination broker or host, authentication choice, selected disks, and initial-copy method. Have the network and storage owners review the transfer against available capacity and the workload’s recovery objective. If external media is selected, assign custody and import ownership before exporting. Avoid treating completion of the setup wizard as completion of the initial replication.\nVerification\nConfirm that the relationship points to the intended receiver and includes the approved disks. Observe the initial-copy progress and subsequent replication health. Investigate a warning or stalled transfer before accepting the relationship into service. Retain the configuration and health evidence for the separate recovery-test plan.\nOfficial references\nMicrosoft Learn: Replicate a virtual machine with Hyper-V Replica. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nMicrosoft describes VM replication setup after the receiving host or cluster has already been enabled for Hyper-V Replica. In Hyper-V Manager, a clustered destination is entered using the Hyper-V Replica Broker name; the connection retrieves the destination authentication and port settings. The initial copy can be transferred over the network or through external media. [Microsoft Learn](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/replication-virtual-machines).\n\n## Applicability\n\nConfirm the receiving configuration before opening the VM replication wizard. Use the documented tool-specific procedure for the actual topology. This review establishes the replication relationship and initial transfer; it does not replace a later failover rehearsal.\n\n## DSE recommendation\n\nRecord the destination broker or host, authentication choice, selected disks, and initial-copy method. Have the network and storage owners review the transfer against available capacity and the workload’s recovery objective. If external media is selected, assign custody and import ownership before exporting. Avoid treating completion of the setup wizard as completion of the initial replication.\n\n## Verification\n\nConfirm that the relationship points to the intended receiver and includes the approved disks. Observe the initial-copy progress and subsequent replication health. Investigate a warning or stalled transfer before accepting the relationship into service. Retain the configuration and health evidence for the separate recovery-test plan.\n\n## Official references\n\n[Microsoft Learn: Replicate a virtual machine with Hyper-V Replica](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/replication-virtual-machines). 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-241-set-the-destination-and-initial-copy-for-hyper-v-replica/", "url": "https://update.dsesecurity.com/updates/dse-20260908-241-set-the-destination-and-initial-copy-for-hyper-v-replica/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-241-set-the-destination-and-initial-copy-for-hyper-v-replica/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Set the destination and initial copy for Hyper-V Replica", "item": "https://update.dsesecurity.com/updates/dse-20260908-241-set-the-destination-and-initial-copy-for-hyper-v-replica/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-241-set-the-destination-and-initial-copy-for-hyper-v-replica/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-241-set-the-destination-and-initial-copy-for-hyper-v-replica/", "url": "https://update.dsesecurity.com/updates/dse-20260908-241-set-the-destination-and-initial-copy-for-hyper-v-replica/", "headline": "Set the destination and initial copy for Hyper-V Replica", "description": "What must be established before a virtual machine begins replication?", "abstract": "What must be established before a virtual machine begins replication?", "articleBody": "Source facts\nMicrosoft describes VM replication setup after the receiving host or cluster has already been enabled for Hyper-V Replica. In Hyper-V Manager, a clustered destination is entered using the Hyper-V Replica Broker name; the connection retrieves the destination authentication and port settings. The initial copy can be transferred over the network or through external media. Microsoft Learn.\nApplicability\nConfirm the receiving configuration before opening the VM replication wizard. Use the documented tool-specific procedure for the actual topology. This review establishes the replication relationship and initial transfer; it does not replace a later failover rehearsal.\nDSE recommendation\nRecord the destination broker or host, authentication choice, selected disks, and initial-copy method. Have the network and storage owners review the transfer against available capacity and the workload’s recovery objective. If external media is selected, assign custody and import ownership before exporting. Avoid treating completion of the setup wizard as completion of the initial replication.\nVerification\nConfirm that the relationship points to the intended receiver and includes the approved disks. Observe the initial-copy progress and subsequent replication health. Investigate a warning or stalled transfer before accepting the relationship into service. Retain the configuration and health evidence for the separate recovery-test plan.\nOfficial references\nMicrosoft Learn: Replicate a virtual machine with Hyper-V Replica. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:13:10+00:00", "dateModified": "2026-09-08T18:29:34+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-241-set-the-destination-and-initial-copy-for-hyper-v-replica/" }, "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-241-set-the-destination-and-initial-copy-for-hyper-v-replica/#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": "Set the destination and initial copy for Hyper-V Replica" }, "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": 212, "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": "Replicate a virtual machine with Hyper-V Replica", "url": "https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/replication-virtual-machines" } } ] } }