<?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>Azure Site Recovery on Exploring IT with Michaël</title>
    <link>https://mvdb.io/tags/azure-site-recovery/</link>
    <description>Recent content in Azure Site Recovery on Exploring IT with Michaël</description>
    <image>
      <title>Exploring IT with Michaël</title>
      <url>https://mvdb.io/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</url>
      <link>https://mvdb.io/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</link>
    </image>
    <generator>Hugo -- 0.127.0</generator>
    <language>en</language>
    <lastBuildDate>Thu, 04 Jul 2024 12:00:03 +0000</lastBuildDate>
    <atom:link href="https://mvdb.io/tags/azure-site-recovery/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Azure Site Recovery: migration to modernized VMware replication</title>
      <link>https://mvdb.io/posts/azure-site-recovery-source-agent-driver-version-is-not-supported/</link>
      <pubDate>Thu, 04 Jul 2024 12:00:03 +0000</pubDate>
      <guid>https://mvdb.io/posts/azure-site-recovery-source-agent-driver-version-is-not-supported/</guid>
      <description>I was recently busy migrating a customer from the classic ASR vault to the modernized ASR vault. However, during the process I ran into an issue. This post is to explain the issue and how you can easily resolve it yourself. In my scenario, I already deployed modern vault in Azure with a new ASR appliance.
In your classic ASR vault, navigate to replicated items and click on Upgrade to modernized VMware replication.</description>
    </item>
  </channel>
</rss>
