脱离VMware环境后，企业必须重新审视数据中心的各个层面，而数据保护无疑是其中最为关键的环节。多数团队计划原封不动地将现有的备份方案迁移至新的虚拟化平台并重新部署。不过更明智的做法是借此契机提升系统的容错能力与恢复速度：保留原有的备份应用，同时让各技术层各司其职、发挥各自优势。
Leaving VMware forces a fresh look at every layer of the datacenter, and data protection belongs near the top of that list. Most teams plan to move the backup design across as it stands and rebuild it on the new hypervisor. The better plan uses the exit to raise resiliency and recovery speed, keeps the backup application, and gives each layer the work it does best.
大多数数据中心的备份方案均依托vSphere的各项机制：从数据块变更追踪技术、vStorage API，到备份任务执行期间的VMware快照机制，再到与vCenter资源目录的存储集成以及按集群部署的备份代理。不少企业还会引入Site Recovery Manager这类编排工具来落实故障转移计划。一旦更换虚拟化平台，上述所有设计前提都需重新评估。目前各大备份厂商已针对此场景做了大量优化，过去一年里对主流KVM类平台的适配能力也迅速成熟。
What the migration touches Backup designs in most data centers rest on vSphere mechanics, from changed block tracking through the vStorage APIs and VMware snapshot behavior during a job to storage integrationed against the vCenter inventory and proxies placed per cluster. Many shops add an orchestration product such as Site Recovery Manager to drive the failover plan. Change the hypervisor and each of those assumptions gets a second look. Backup vendors have done real work here, and support for the major KVM-based platforms has matured quickly over the past year.
不过比备份应用本身更值得深思的是底层架构设计。在传统的vSphere架构下，生产环境仅负责运行业务负载，其余所有数据保护相关工作均由独立的保护层负责。为应对硬盘故障、实现快速回滚、完成数据复制、实现站点级故障转移以及生成不可篡改的备份副本，企业往往需要部署多个独立产品，每个产品都配有专属许可证、管理控制台，还需单独进行续约。
The bigger question sits upstream of the backup application. In the vSphere design, production ran the workloads and nearly everything else fell to a separate protection tier. Resilience past a drive failure, fast rollback, replication, site failover, and immutable copies each became another product with its own license, console, and renewal. Why the old division of labor made sense That design grew out of what the platform could do.
这种分工模式之所以曾经行得通，是因为当时的平台能力决定了这样的架构设计：服务器虚拟化技术将单台物理服务器抽象化，为虚拟机提供虚拟CPU、内存与磁盘资源，而存储层面的容错能力则交由存储阵列负责，数据恢复工作则由备份产品承担。早期的第一代超融合基础设施虽然将存储功能集成到了服务器中，但依然沿用了这种分工模式，通常还会在每个节点上运行一个控制虚拟机。
Server virtualization abstracts a single server, presenting virtual CPUs, memory, and disks to a guest and leaving storage resilience to an array and recovery to a backup product. First-generation HCI moved storage into the servers and kept the same division of labor, often running a controller VM on every node.
对于这类架构而言，由独立的备份层来处理从硬盘故障到整个站点失效的各种问题确实是最合适的解决方案。只是这种架构的代价往往要在最糟糕的故障时刻才会显现出来。
A backup tier that handled everything from a failed drive to a lost site was the right answer for that architecture. The cost of that arrangement shows up on the worst day.
单点故障会波及虚拟化管理程序、存储系统、备份应用、复制工具和网络配置，而恢复路径则跨越了它们之间的每一个边界。退出时刻是多年来首次让这一假设接受审视。生产平台应承担的职责数据中心虚拟化将整个环境抽象化。计算、存储、网络和数据保护共享同一代码库和同一组元数据，因此平台掌握的是工作负载的完整图景，而非一堆数据块的集合。
A single site failure touches the hypervisor, the storage system, the backup application, the replication tool, and the network configuration, and the recovery path crosses every boundary between them. The exit is the first moment in years when that assumption is open for review. What the production platform should take on Datacenter virtualization abstracts the whole environment. Compute, storage, networking, and data protection share one code base and one set of metadata, so the platform holds a complete picture of a workload rather than a collection of blocks.
这种共享视图让生产端能够吸收旧设计下推给下游的职责。一旦生产端接管处理，到达备份层的事件将大幅减少。第二块磁盘故障仅是硬件更换任务，而非在工作日中间进行恢复；糟糕的补丁变成快速的快照回滚，应用负责人几乎察觉不到。正是这种韧性，让翻新服务器和硬盘成为生产环境的可靠选择；而闪存和内存价格在 2026 年持续上涨，使您已拥有的硬件比去年型号假设的价值更高。
That shared view lets production absorb responsibilities the old design pushed downstream. Far fewer events reach the backup tier once production handles them. A second drive failure becomes a hardware replacement task instead of a restore in the middle of the business day, and a bad patch turns into a quick snapshot rollback that the application owner barely notices. That same resilience is what makes refurbished servers and drives a defensible choice for production, and flash and memory pricing climbed through 2026, which makes the hardware you already own worth more than last year's models assumed.
备份的职责扩大，始于迁移将日常恢复下沉到平台，扩展了备份应用的角色。第一项新任务在新环境运行任何生产工作负载之前就已到来。已在保护 vSphere 环境的备份产品持有每个 VM 的当前一致性副本，而同时支持旧虚拟化管理程序和新平台的备份应用，可将该副本转化为迁移路径。Veeam Backup & Replication 即是此模式的典范，现已支持 VergeOS 平台，因此团队可将 vSphere 备份恢复到新环境，在当地测试，并按自主节奏完成割接。用于保护 VMware 的投资，反而成为将工作负载迁移离开它的载体。
Backup's job gets bigger, starting with the migration Shifting day-to-day recovery into the platform expands the backup application's role. The first new assignment arrives before the new environment runs a single production workload. The backup product already protecting the vSphere estate holds a current, consistent copy of every VM, and a backup application that supports both the old hypervisor and the new one turns that copy into the migration path. Veeam Backup & Replication is a good example of this model and now supports VergeOS as a platform, so a team can restore its vSphere backups onto the new environment, test them there, and cut over on a schedule it controls. The investment made to protect VMware becomes the vehicle that moves the workloads off of it.
迁移完成后，备份应用将继续承担其擅长的工作。长期保留、合规归档、离线及异地副本，以及面向应用所有者的颗粒级恢复，均保留在备份层。它同时也成为位于生产平台故障域之外的独立副本，这是最后一道防线的正确归属。验证平台侧能力要求生产环境承担更多职责，意味着将责任集中在单一供应商的工程能力上。
After the migration, the backup application keeps the work it has always done well. Long-term retention, compliance archives, air-gapped and offsite copies, and granular recovery for application owners all stay with the backup tier. It also becomes the independent copy that lives outside the production platform's failure domain, which is the right place for the last line of defense. Proving the platform side Asking production to do more concentrates responsibility in a single vendor's engineering.
这种权衡站得住脚，但仅凭确凿证据才能站得住脚。要求在运行中的应用上演示实时故障场景，而非仅看功能矩阵。让供应商拔掉一块硬盘，然后在工作负载仍在运行时、超出声明的保护限度再拔掉第二块。要求他们删除一台虚拟机并从中恢复单个文件，随后让主站点离线并在别处启动环境。能在通话中完成这四项测试的供应商已给出答案；只提供架构图的供应商也同样透露了关键信息。
That trade is defensible, and it is only defensible against evidence. Ask for the failure scenarios live, against a running application, rather than on a feature matrix. Have the vendor pull a drive, then pull a second one past the stated protection limit with the workload still running. Ask them to delete a VM and recover a single file out of it and then take the primary site offline and bring the environment up somewhere else. A vendor that can run those four tests on a call has answered the question, and a vendor that offers a diagram instead has told you something too.
随后，通过备份应用运行测试迁移，确认恢复的虚拟机能在新平台上正常启动并运行。抉择的关键虚拟化平台更换只是该项目的显性部分。生产环境与备份之间的保护职责如何划分，将决定未来五年的运行成本，以及在这五年中最糟糕的一天系统将如何表现。重建旧有的分工是一种选择，它理应接受与许可证电子表格同等严格的审视。
Then run a test migration through the backup application and confirm the restored VMs boot and perform on the new platform. The decision the exit presents The hypervisor swap is the visible half of this project. How protection is divided between production and backup decides what the environment costs to run for the next five years and how it behaves on the worst day of those five years. Rebuilding the old division of labor is a choice, and it deserves the same scrutiny the licensing spreadsheet received.
VergeIO 基于上述数据中心虚拟化模型构建了 VergeOS，将弹性、快照、即时恢复和站点故障转移与计算、存储、网络集成在同一代码库中，并通过 Veeam Backup & Replication 对 VergeOS 的支持，实现了迁移及后续备份层的保护。
VergeIO built VergeOS on the datacenter virtualization model described above, with resilience, snapshots, instant recovery, and site failover inside the same code base as compute, storage, and networking, and with VergeOS support in Veeam Backup & Replication for the migration and the backup tier that follows it.
在最近的一次会议上，Aaron Richman和Dave Vincent针对正在运行的应用程序运行了四个故障测试中的每一个，从单个拉出的驱动器到完整的站点恢复。该会议可按需提供。看看，看看如何将一个大的退出变成一个更大的机会。George Crump是VergeIO的首席营销官。他创立了瑞士存储公司，并担任行业分析师，涵盖存储、虚拟化和数据保护。由VergeIO提供
At a recent session, Aaron Richman and Dave Vincent ran each of the four failure tests against a running application, from a single pulled drive through a full site recovery. The session is available on demand. Take a look, and see how you can turn a big exit into a bigger opportunity. George Crump is Chief Marketing Officer at VergeIO. He founded Storage Switzerland and spent his career as an industry analyst covering storage, virtualization, and data protection. Supplied by VergeIO