<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Veeam on Aperture Zone</title>
    <link>https://aperturezone.com/tags/veeam/</link>
    <description>Recent content in Veeam on Aperture Zone</description>
    <image>
      <url>https://aperturezone.com/logo.webp</url>
      <link>https://aperturezone.com/logo.webp</link>
    </image>
    <generator>Hugo -- gohugo.io</generator>
    <language>fr-fr</language>
    <lastBuildDate>Fri, 03 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aperturezone.com/tags/veeam/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>DRP on Hyper-V with Veeam: from chaos to clean failover</title>
      <link>https://aperturezone.com/posts/drpveeam/</link>
      <pubDate>Fri, 03 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/drpveeam/</guid>
      <description>&lt;p&gt;I have a virtualized infrastructure running on &lt;strong&gt;Hyper-V&lt;/strong&gt; with a separate backup/DRP server. The entire stack runs on &lt;strong&gt;19 VMs&lt;/strong&gt;: two Active Directory domains with domain joining, Linux DNS forwarders (BIND9), RADIUS, monitoring, application services&amp;hellip; in short, not something we can afford to just reboot haphazardly.&lt;/p&gt;
&lt;p&gt;The project’s objective was simple to state, but complex to achieve:&lt;/p&gt;
&lt;p&gt;&amp;gt; &lt;strong&gt;Switchover the entire infrastructure to the DRP server with minimal effort, ensuring service continuity (at the very least, not cutting off internet access), then return to production cleanly.&lt;/strong&gt;&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
