<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Rollback on CloudManaged.online</title>
    <link>https://cloudmanaged.online/tags/rollback/</link>
    <description>Recent content in Rollback on CloudManaged.online</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 20 Jan 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://cloudmanaged.online/tags/rollback/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How to Run VMware Migration Waves Without Outages</title>
      <link>https://cloudmanaged.online/blog/vmware-migration-waves-and-rollback/</link>
      <pubDate>Tue, 20 Jan 2026 00:00:00 +0000</pubDate>
      <guid>https://cloudmanaged.online/blog/vmware-migration-waves-and-rollback/</guid>
      <description>&lt;h1 id=&#34;how-to-run-vmware-migration-waves-without-outages&#34;&gt;How to Run VMware Migration Waves Without Outages&lt;/h1&gt;&#xA;&lt;p&gt;Migration failure is usually an execution problem, not a technology problem. Teams that succeed use small, repeatable waves with explicit rollback checkpoints and strict go/no-go criteria.&lt;/p&gt;&#xA;&lt;hr&gt;&#xA;&lt;h2 id=&#34;wave-design-pattern&#34;&gt;Wave Design Pattern&lt;/h2&gt;&#xA;&lt;p&gt;Each migration wave should include:&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;Workload selection (single business domain)&lt;/li&gt;&#xA;&lt;li&gt;Pre-cutover validation&lt;/li&gt;&#xA;&lt;li&gt;Controlled cutover window&lt;/li&gt;&#xA;&lt;li&gt;Hypercare and monitoring&lt;/li&gt;&#xA;&lt;li&gt;Post-wave retrospective&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;p&gt;Target wave size should be small enough to rollback in one maintenance window.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
