将本地 VMware 虚拟机或物理服务器的灾难恢复设置到辅助站点Set up disaster recovery of on-premises VMware virtual machines or physical servers to a secondary site

Azure Site Recovery 中的 InMage Scout 在本地 VMware 站点之间提供实时复制。InMage Scout in Azure Site Recovery provides real-time replication between on-premises VMware sites. InMage Scout 随附在 Azure Site Recovery 服务订阅中。InMage Scout is included in Azure Site Recovery service subscriptions.

结束支持公告End-of-support announcement

Azure Site Recovery 方案(在本地 VMware 或物理数据中心之间进行复制)即将结束支持。The Azure Site Recovery scenario for replication between on-premises VMware or physical datacenters is reaching end-of-support.

  • 从 2018 年 8 月起,无法在恢复服务保管库中配置该方案,且无法从保管库下载 InMage Scout 软件。From August 2018, the scenario can't be configured in the Recovery Services vault, and the InMage Scout software can't be downloaded from the vault. 现有部署仍受支持。Existing deployments will be supported.
  • 从 2020 年 12 月 31 日起,该方案将不受支持。From December 31 2020, the scenario won't be supported.
  • 现有合作伙伴可以将新客户加入到该方案中,直到支持结束。Existing partners can onboard new customers to the scenario until support ends.

在 2018 年和 2019 年期间,将发布两个更新:During 2018 and 2019, two updates will be released:

  • 更新 7:修复了网络配置与合规性问题,并提供 TLS 1.2 支持。Update 7: Fixes network configuration and compliance issues, and provides TLS 1.2 support.

  • 更新 8:添加了对 Linux 操作系统 CentOS 7.3/7.4/7.5 和 SUSE 12 的支持Update 8: Adds support for Linux operating systems CentOS 7.3/7.4/7.5, and for SUSE 12

更新 8 之后,不会再发布进一步更新。After Update 8, no further updates will be released. 针对更新 8 中添加的操作系统,修补程序支持有限,会尽最大努力修复错误。There will be limited hotfix support for the operating systems added in Update 8, and bug fixes based on best effort.

Azure Site Recovery 为 VMware 和 Hyper-V 客户提供一流的无缝 DRaaS 解决方案,将 Azure 作为灾难恢复站点,不断创新。Azure Site Recovery continues to innovate by providing VMware and Hyper-V customers a seamless and best-in-class DRaaS solution with Azure as a disaster recovery site. Azure 建议现有 InMage/ASR Scout 客户考虑使用 Azure Site Recovery 的 VMware to Azure 方案来满足其业务连续性需求。Azure recommends that existing InMage / ASR Scout customers consider using Azure Site Recovery's VMware to Azure scenario for their business continuity needs. Azure Site Recovery 的 VMware to Azure 方案是适用于 VMware 应用程序的企业级 DR 解决方案,可提供几分钟的 RPO 和 RTO、支持多 VM 应用程序复制和恢复、可无缝入门、全面监控,且拥有显著的 TCO 优势。Azure Site Recovery's VMware to Azure scenario is an enterprise-class DR solution for VMware applications, which offers RPO and RTO of minutes, support for multi-VM application replication and recovery, seamless onboarding, comprehensive monitoring, and significant TCO advantage.

方案迁移Scenario migration

作为替代方法,我们建议将本地 VMware VM 和物理计算机复制到 Azure 来为其设置灾难恢复。As an alternative, we recommend setting up disaster recovery for on-premises VMware VMs and physical machines by replicating them to Azure. 请按如下所示执行此操作:Do this as follows:

  1. 查看以下快速比较。Review the quick comparison below. 在复制本地计算机之前,需要检查它们是否满足复制到 Azure 的要求Before you can replicate on-premises machines, you need check that they meet requirements for replication to Azure. 如果要复制 VMware VM,建议查看容量规划指南,并运行部署规划器工具来识别容量要求,然后验证符合性。If you're replicating VMware VMs, we recommend that you review capacity planning guidelines, and run the Deployment Planner tool to identity capacity requirements, and verify compliance.
  2. 运行部署规划器后,可以设置复制:*对于 VMware VM,请按照以下教程准备 Azure准备本地 VMware 环境设置灾难恢复After running the Deployment Planner, you can set up replication: *For VMware VMs, follow these tutorials to prepare Azure, prepare your on-premises VMware environment, and set up disaster recovery. *对于物理计算机,请遵循此教程*For physical machines, follow this tutorial.
  3. 在计算机复制到 Azure 后,可以运行灾难恢复演练以确保一切正常运行。After machines are replicating to Azure, you can run a disaster recovery drill to make sure everything's working as expected.

快速比较Quick comparison

功能Feature 复制到 AzureReplication to Azure 在 VMware 数据中心之间进行复制Replication between VMware datacenters
所需的组件Required components 复制的计算机上的移动服务。Mobility service on replicated machines. 本地配置服务器、进程服务器、主目标服务器。Azure 中用于故障回复的临时进程服务器。On-premises configuration server, process server, master target server.Temporary process server in Azure for failback. 移动服务、进程服务器、配置服务器和主目标Mobility service, Process Server, Configuration Server and Master Target
配置和业务流程Configuration and orchestration Azure 门户中的恢复服务保管库Recovery Services vault in the Azure portal 使用 vContinuumUsing vContinuum
复制Replicated 磁盘(Windows 和 Linux)Disk (Windows and Linux) Volume-WindowsVolume-Windows
Disk-LinuxDisk-Linux
共享磁盘群集Shared disk cluster 不支持Not supported 支持Supported
数据变动量限制(平均)Data churn limits (average) 10 MB/秒数据/磁盘10 MB/s data per disk
25 MB/秒数据/VM25MB/s data per VM
了解详细信息Learn more
> 10 MB/秒数据/磁盘> 10 MB/s data per disk
> 25 MB/秒数据/VM> 25 MB/s data per VM
监视Monitoring 通过 Azure 门户From Azure portal 通过 CX(配置服务器)From CX (Configuration Server)
支持矩阵Support Matrix 单击此处了解详细信息Click here for details 下载 ASR Scout 兼容矩阵Download ASR Scout compatible matrix

先决条件Prerequisites

完成本教程:To complete this tutorial:

下载并安装组件更新Download and install component updates

查看并安装最新的更新Review and install the latest updates. 应按以下顺序在服务器上安装更新:Updates should be installed on servers in the following order:

  1. RX 服务器(如果适用)RX server (if applicable)
  2. 配置服务器Configuration servers
  3. 进程服务器Process servers
  4. 主目标服务器Master Target servers
  5. vContinuum 服务器vContinuum servers
  6. 源服务器(Windows 和 Linux 服务器)Source server (both Windows and Linux Servers)

按以下步骤安装更新:Install the updates as follows:

备注

所有 Scout 组件的文件更新版本可能与更新 .zip 文件中的版本不同。All Scout components' file update version may not be the same in the update .zip file. 较旧的版本表示此更新自上一次更新以来组件中没有任何更改。The older version indicate that there is no change in the component since previous update to this update.

下载更新 .zip 文件与 MySQL 和 PHP 升级配置文件。Download the update .zip file and the MySQL and PHP upgrade configuration files. 更新 .zip 文件包含以下组件的所有基础二进制文件和累积的升级二进制文件:The update .zip file contains the all the base binaries and cumulative upgrade binaries of the following components:

  • InMage_ScoutCloud_RX_8.0.1.0_RHEL6-64_GA_02Mar2015.tar.gzInMage_ScoutCloud_RX_8.0.1.0_RHEL6-64_GA_02Mar2015.tar.gz

  • RX_8.0.7.0_GA_Update_7_2965621_28Dec18.tar.gzRX_8.0.7.0_GA_Update_7_2965621_28Dec18.tar.gz

  • InMage_CX_8.0.1.0_Windows_GA_26Feb2015_release.exeInMage_CX_8.0.1.0_Windows_GA_26Feb2015_release.exe

  • InMage_CX_TP_8.0.1.0_Windows_GA_26Feb2015_release.exeInMage_CX_TP_8.0.1.0_Windows_GA_26Feb2015_release.exe

  • CX_Windows_8.0.7.0_GA_Update_7_2965621_28Dec18.exeCX_Windows_8.0.7.0_GA_Update_7_2965621_28Dec18.exe

  • InMage_PI_8.0.1.0_Windows_GA_26Feb2015_release.exeInMage_PI_8.0.1.0_Windows_GA_26Feb2015_release.exe

  • InMage_Scout_vContinuum_MT_8.0.7.0_Windows_GA_27Dec2018_release.exeInMage_Scout_vContinuum_MT_8.0.7.0_Windows_GA_27Dec2018_release.exe

  • InMage_UA_8.0.7.0_Windows_GA_27Dec2018_release.exeInMage_UA_8.0.7.0_Windows_GA_27Dec2018_release.exe

  • InMage_UA_8.0.7.0_OL5-32_GA_03Dec2018_release.tar.gzInMage_UA_8.0.7.0_OL5-32_GA_03Dec2018_release.tar.gz

  • InMage_UA_8.0.7.0_OL5-64_GA_03Dec2018_release.tar.gzInMage_UA_8.0.7.0_OL5-64_GA_03Dec2018_release.tar.gz

  • InMage_UA_8.0.7.0_OL6-32_GA_03Dec2018_release.tar.gzInMage_UA_8.0.7.0_OL6-32_GA_03Dec2018_release.tar.gz

  • InMage_UA_8.0.7.0_OL6-64_GA_03Dec2018_release.tar.gzInMage_UA_8.0.7.0_OL6-64_GA_03Dec2018_release.tar.gz

  • InMage_UA_8.0.7.0_RHEL5-32_GA_03Dec2018_release.tar.gzInMage_UA_8.0.7.0_RHEL5-32_GA_03Dec2018_release.tar.gz

  • InMage_UA_8.0.7.0_RHEL5-64_GA_03Dec2018_release.tar.gzInMage_UA_8.0.7.0_RHEL5-64_GA_03Dec2018_release.tar.gz

  • InMage_UA_8.0.7.0_RHEL6-32_GA_03Dec2018_release.tar.gzInMage_UA_8.0.7.0_RHEL6-32_GA_03Dec2018_release.tar.gz

  • InMage_UA_8.0.7.0_RHEL6-64_GA_03Dec2018_release.tar.gzInMage_UA_8.0.7.0_RHEL6-64_GA_03Dec2018_release.tar.gz

  • InMage_UA_8.0.7.0_RHEL7-64_GA_03Dec2018_release.tar.gzInMage_UA_8.0.7.0_RHEL7-64_GA_03Dec2018_release.tar.gz

  • InMage_UA_8.0.7.0_SLES10-32_GA_03Dec2018_release.tar.gzInMage_UA_8.0.7.0_SLES10-32_GA_03Dec2018_release.tar.gz

  • InMage_UA_8.0.7.0_SLES10-64_GA_03Dec2018_release.tar.gzInMage_UA_8.0.7.0_SLES10-64_GA_03Dec2018_release.tar.gz

  • InMage_UA_8.0.7.0_SLES10-SP1-32_GA_03Dec2018_release.tar.gzInMage_UA_8.0.7.0_SLES10-SP1-32_GA_03Dec2018_release.tar.gz

  • InMage_UA_8.0.7.0_SLES10-SP1-64_GA_03Dec2018_release.tar.gzInMage_UA_8.0.7.0_SLES10-SP1-64_GA_03Dec2018_release.tar.gz

  • InMage_UA_8.0.7.0_SLES10-SP2-32_GA_03Dec2018_release.tar.gzInMage_UA_8.0.7.0_SLES10-SP2-32_GA_03Dec2018_release.tar.gz

  • InMage_UA_8.0.7.0_SLES10-SP2-64_GA_03Dec2018_release.tar.gzInMage_UA_8.0.7.0_SLES10-SP2-64_GA_03Dec2018_release.tar.gz

  • InMage_UA_8.0.7.0_SLES10-SP3-32_GA_03Dec2018_release.tar.gzInMage_UA_8.0.7.0_SLES10-SP3-32_GA_03Dec2018_release.tar.gz

  • InMage_UA_8.0.7.0_SLES10-SP3-64_GA_03Dec2018_release.tar.gzInMage_UA_8.0.7.0_SLES10-SP3-64_GA_03Dec2018_release.tar.gz

  • InMage_UA_8.0.7.0_SLES10-SP4-32_GA_03Dec2018_release.tar.gzInMage_UA_8.0.7.0_SLES10-SP4-32_GA_03Dec2018_release.tar.gz

  • InMage_UA_8.0.7.0_SLES10-SP4-64_GA_03Dec2018_release.tar.gzInMage_UA_8.0.7.0_SLES10-SP4-64_GA_03Dec2018_release.tar.gz

  • InMage_UA_8.0.7.0_SLES11-32_GA_03Dec2018_release.tar.gzInMage_UA_8.0.7.0_SLES11-32_GA_03Dec2018_release.tar.gz

  • InMage_UA_8.0.7.0_SLES11-64_GA_04Dec2018_release.tar.gzInMage_UA_8.0.7.0_SLES11-64_GA_04Dec2018_release.tar.gz

  • InMage_UA_8.0.7.0_SLES11-SP1-32_GA_03Dec2018_release.tar.gzInMage_UA_8.0.7.0_SLES11-SP1-32_GA_03Dec2018_release.tar.gz

  • InMage_UA_8.0.7.0_SLES11-SP1-64_GA_04Dec2018_release.tar.gzInMage_UA_8.0.7.0_SLES11-SP1-64_GA_04Dec2018_release.tar.gz

  • InMage_UA_8.0.7.0_SLES11-SP2-32_GA_03Dec2018_release.tar.gzInMage_UA_8.0.7.0_SLES11-SP2-32_GA_03Dec2018_release.tar.gz

  • InMage_UA_8.0.7.0_SLES11-SP2-64_GA_03Dec2018_release.tar.gzInMage_UA_8.0.7.0_SLES11-SP2-64_GA_03Dec2018_release.tar.gz

  • InMage_UA_8.0.7.0_SLES11-SP3-32_GA_03Dec2018_release.tar.gzInMage_UA_8.0.7.0_SLES11-SP3-32_GA_03Dec2018_release.tar.gz

  • InMage_UA_8.0.7.0_SLES11-SP3-64_GA_03Dec2018_release.tar.gzInMage_UA_8.0.7.0_SLES11-SP3-64_GA_03Dec2018_release.tar.gz

  • InMage_UA_8.0.7.0_SLES11-SP4-64_GA_03Dec2018_release.tar.gzInMage_UA_8.0.7.0_SLES11-SP4-64_GA_03Dec2018_release.tar.gz

    1. 解压缩 .zip 文件。Extract the .zip files.
    2. RX 服务器 :将 RX_8.0.7.0_GA_Update_7_2965621_28Dec18.tar.gz 复制到 RX 服务器,并将其解压缩。RX server : Copy RX_8.0.7.0_GA_Update_7_2965621_28Dec18.tar.gz to the RX server, and extract it. 在解压缩的文件夹中运行 /InstallIn the extracted folder, run /Install .
    3. 配置服务器和进程服务器 :将 CX_Windows_8.0.7.0_GA_Update_7_2965621_28Dec18.exe 复制到配置服务器和进程服务器。Configuration server and process server : Copy CX_Windows_8.0.7.0_GA_Update_7_2965621_28Dec18.exe to the configuration server and process server. 双击以运行该文件。Double-click to run it.
    4. Windows 主目标服务器 :若要更新统一代理,请将 InMage_UA_8.0.7.0_Windows_GA_27Dec2018_release.exe 复制到服务器。Windows Master Target server : To update the unified agent, copy InMage_UA_8.0.7.0_Windows_GA_27Dec2018_release.exe to the server. 双击以运行该文件。Double-click it to run it. 同一文件还可用于全新安装。The same file can also be used for fresh installation. 相同的统一代理更新也适用于源服务器。The same unified agent update is also applicable for the source server. 由于 InMage_Scout_vContinuum_MT_8.0.7.0_Windows_GA_27Dec2018_release.exe 是拥有所有最新更改的新 GA 安装程序,因此,在通过该安装程序执行了准备工作的主目标服务器上不需要应用更新。The update does not need to apply on the Master target prepared with InMage_Scout_vContinuum_MT_8.0.7.0_Windows_GA_27Dec2018_release.exe as this is new GA installer with all the latest changes.
    5. vContinuum 服务器 :将 InMage_Scout_vContinuum_MT_8.0.7.0_Windows_GA_27Dec2018_release.exe 复制到服务器。vContinuum server : Copy InMage_Scout_vContinuum_MT_8.0.7.0_Windows_GA_27Dec2018_release.exe to the server. 确保已关闭 vContinuum 向导。Make sure that you've closed the vContinuum wizard. 双击以运行该文件。Double-click on the file to run it.
    6. Linux 主目标服务器 :若要更新统一代理,请将 InMage_UA_8.0.7.0_RHEL6-64_GA_03Dec2018_release.tar.gz 复制到 Linux 主目标服务器并将其解压缩。Linux master target server : To update the unified agent, copy InMage_UA_8.0.7.0_RHEL6-64_GA_03Dec2018_release.tar.gz to the Linux Master Target server and extract it. 在解压缩的文件夹中运行 /InstallIn the extracted folder, run /Install .
    7. Windows 源服务器 :若要更新统一代理,请将 InMage_UA_8.0.7.0_Windows_GA_27Dec2018_release.exe 复制到源服务器。Windows source server : To update the unified agent, copy InMage_UA_8.0.7.0_Windows_GA_27Dec2018_release.exe to the source server. 双击以运行该文件。Double-click on the file to run it.
    8. Linux 源服务器 :若要更新统一代理,请将相应版本的统一代理文件复制到 Linux 服务器并将其解压缩。Linux source server : To update the unified agent, copy the corresponding version of the unified agent file to the Linux server, and extract it. 在解压缩的文件夹中运行 /InstallIn the extracted folder, run /Install . 示例:对于 RHEL 6.7 64 位服务器,将 InMage_UA_8.0.7.0_RHEL6-64_GA_03Dec2018_release.tar.gz 复制到服务器并将其解压缩。Example: For RHEL 6.7 64-bit server, copy InMage_UA_8.0.7.0_RHEL6-64_GA_03Dec2018_release.tar.gz to the server, and extract it. 在解压缩的文件夹中运行 /InstallIn the extracted folder, run /Install .
    9. 在使用上述安装程序升级配置服务器、进程服务器和 RX 服务器后,需要通过快速安装指南的第 7.4 部分中提到的步骤手动升级 PHP 和 MySQL 二进制文件。After upgrading Configuration Server, Process Server and RX server with the above mentioned installers, the PHP and MySQL libraries needs to be upgraded manually with steps mentioned in section 7.4 of the quick installation guide.

启用复制Enable replication

  1. 设置源与目标 VMware 站点之间的复制。Set up replication between the source and target VMware sites.

  2. 请参阅以下文档,了解有关安装、保护和恢复的详细信息:Refer to following documents to learn more about installation, protection, and recovery:

更新Updates

Site Recovery Scout 8.0.1 Update 7Site Recovery Scout 8.0.1 Update 7

更新时间:2018 年 12 月 31 日,下载 Scout update 7Updated: December 31, 2018 Download Scout update 7. Scout Update 7 是一个完整的安装程序,可用于全新安装以及升级采用早期更新(从 Update 1 到 Update 6)的现有代理/MT。Scout Update 7 is a full installer which can be used for fresh installation as well as to upgrade existing agents/MT which are on previous updates (from Update 1 to Update 6). 它包含从 Update 1 到 Update 6 的所有修补程序,以及下面所述的新修补程序和增强功能。It contains all fixes from Update 1 to Update 6 plus the new fixes and enhancements described below.

新增功能New features

  • PCI 符合性PCI compliance
  • TLS v1.2 支持TLS v1.2 Support

Bug 和安全修补程序Bug and Security Fixes

  • 已修复:Windows 群集/独立计算机在进行恢复/灾难恢复演练时具有不正确的 IP 配置。Fixed: Windows Cluster/Standalone Machines have incorrect IP configuration upon recovery/DR-Drill.
  • 已修复:对于 V2V 群集,添加磁盘操作有时候会失败。Fixed: Sometimes Add disk operation fails for V2V cluster.
  • 已修复:如果主目标服务器是 Windows Server 2016,vContinuum 向导在恢复阶段中会停滞。Fixed: vContinuum Wizard gets stuck during recovery phase if the Master Target is Windows Server 2016
  • 已修复:通过将 MySQL 升级到版本 5.7.23 缓解了 MySQL 安全问题。Fixed: MySQL security issues are mitigated by upgrading MySQL to version 5.7.23

在 CS、PS 和 RX 上针对 PHP 和 MySQL 进行手动升级Manual Upgrade for PHP and MySQL on CS,PS, and RX

在配置服务器、进程服务器和 RX 服务器上,PHP 脚本平台应当升级到版本 7.2.10。The PHP scripting platform should be upgraded to version 7.2.10 on Configuration Server, Process Server and RX Server. 在配置服务器、进程服务器和 RX 服务器上,MySQL 数据库管理系统应当升级到版本 5.7.23。The MySQL database management system should be upgraded to version 5.7.23 on Configuration Server, Process Server and RX Server. 请按照快速安装指南中提供的手动步骤来升级 PHP 和 MySQL 版本。Please follow the manual steps given in the Quick installation guide to upgrade PHP and MySQL versions.

Site Recovery Scout 8.0.1 Update 6Site Recovery Scout 8.0.1 Update 6

更新时间:2017 年 10 月 12 日Updated: October 12, 2017

下载 Scout Update 6Download Scout update 6.

Scout Update 6 是累积更新。Scout Update 6 is a cumulative update. 其中包含从 Update 1 到 Update 5 的所有修补程序,以及下面所述的新修补程序和增强功能。It contains all fixes from Update 1 to Update 5 plus the new fixes and enhancements described below.

新的平台支持New platform support

  • 已添加对 Source Windows Server 2016 的支持Support has been added for Source Windows Server 2016

  • 已添加对以下 Linux 操作系统的支持:Support has been added for following Linux operating systems:

    • CentOS 6.9CentOS 6.9
  • 已添加对 VMware Center 6.5 的支持Support has been added for VMware Center 6.5

按以下步骤安装更新:Install the updates as follows:

备注

所有 Scout 组件的文件更新版本可能与更新 .zip 文件中的版本不同。All Scout components' file update version may not be the same in the update .zip file. 较旧的版本表示此更新自上一次更新以来组件中没有任何更改。The older version indicate that there is no change in the component since previous update to this update.

下载更新 .zip 文件。Download the update .zip file. 文件包含以下组件:The file contains the following components:

  • RX_8.0.4.0_GA_Update_4_8725872_16Sep16.tar.gzRX_8.0.4.0_GA_Update_4_8725872_16Sep16.tar.gz

  • CX_Windows_8.0.6.0_GA_Update_6_13746667_18Sep17.exeCX_Windows_8.0.6.0_GA_Update_6_13746667_18Sep17.exe

  • UA_Windows_8.0.5.0_GA_Update_5_11525802_20Apr17.exeUA_Windows_8.0.5.0_GA_Update_5_11525802_20Apr17.exe

  • UA_RHEL6-64_8.0.4.0_GA_Update_4_9035261_26Sep16.tar.gzUA_RHEL6-64_8.0.4.0_GA_Update_4_9035261_26Sep16.tar.gz

  • vCon_Windows_8.0.6.0_GA_Update_6_11525767_21Sep17.exevCon_Windows_8.0.6.0_GA_Update_6_11525767_21Sep17.exe

  • 对于 RHEL5、OL5、OL6、SUSE 10、SUSE 11 的 UA update4 位:UA_<Linux OS>8.0.4.0_GA_Update_4_9035261_26Sep16.tar.gzUA update4 bits for RHEL5, OL5, OL6, SUSE 10, SUSE 11: UA<Linux OS>_8.0.4.0_GA_Update_4_9035261_26Sep16.tar.gz

    1. 解压缩 .zip 文件。Extract the .zip files.
    2. RX 服务器 :将 RX_8.0.4.0_GA_Update_4_8725872_16Sep16.tar.gz 复制到 RX 服务器并将其解压缩。RX server : Copy RX_8.0.4.0_GA_Update_4_8725872_16Sep16.tar.gz to the RX server, and extract it. 在解压缩的文件夹中运行 /InstallIn the extracted folder, run /Install .
    3. 配置服务器和进程服务器 :将 CX_Windows_8.0.6.0_GA_Update_6_13746667_18Sep17.exe 复制到配置服务器和进程服务器。Configuration server and process server : Copy CX_Windows_8.0.6.0_GA_Update_6_13746667_18Sep17.exe to the configuration server and process server. 双击以运行该文件。Double-click to run it.
    4. Windows 主目标服务器 :若要更新统一代理,请将 UA_Windows_8.0.5.0_GA_Update_5_11525802_20Apr17.exe 复制到服务器。Windows Master Target server : To update the unified agent, copy UA_Windows_8.0.5.0_GA_Update_5_11525802_20Apr17.exe to the server. 双击以运行该文件。Double-click it to run it. 相同的统一代理更新也适用于源服务器。The same unified agent update is also applicable for the source server. 如果源尚未更新到 Update 4,则应更新统一代理。If source hasn't been updated to Update 4, you should update the unified agent. 更新不需要应用于备有 InMage_Scout_vContinuum_MT_8.0.1.0_Windows_GA_10Oct2017_release.exe 的主目标服务器,因为这是拥有所有最新更改的新 GA 安装程序。The update does not need to apply on the Master target prepared with InMage_Scout_vContinuum_MT_8.0.1.0_Windows_GA_10Oct2017_release.exe as this is new GA installer with all the latest changes.
    5. vContinuum 服务器 :将 vCon_Windows_8.0.6.0_GA_Update_6_11525767_21Sep17.exe 复制到服务器。vContinuum server : Copy vCon_Windows_8.0.6.0_GA_Update_6_11525767_21Sep17.exe to the server. 确保已关闭 vContinuum 向导。Make sure that you've closed the vContinuum wizard. 双击以运行该文件。Double-click on the file to run it. 更新不需要应用于备有 InMage_Scout_vContinuum_MT_8.0.1.0_Windows_GA_10Oct2017_release.exe 的主目标服务器,因为这是拥有所有最新更改的新 GA 安装程序。The update does not need to apply on the Master Target prepared with InMage_Scout_vContinuum_MT_8.0.1.0_Windows_GA_10Oct2017_release.exe as this is new GA installer with all the latest changes.
    6. Linux 主目标服务器 :若要更新统一代理,请将 UA_RHEL6-64_8.0.4.0_GA_Update_4_9035261_26Sep16.tar.gz 复制到主目标服务器并将其解压缩。Linux master target server : To update the unified agent, copy UA_RHEL6-64_8.0.4.0_GA_Update_4_9035261_26Sep16.tar.gz to the master target server and extract it. 在解压缩的文件夹中运行 /InstallIn the extracted folder, run /Install .
    7. Windows 源服务器 :要更新统一代理,请将 UA_Windows_8.0.5.0_GA_Update_5_11525802_20Apr17.exe 复制到源服务器。Windows source server : To update the unified agent, copy UA_Windows_8.0.5.0_GA_Update_5_11525802_20Apr17.exe to the source server. 双击以运行该文件。Double-click on the file to run it. 如果源服务器已更新到 Update 4 或源代理已安装有最新的基本安装程序 InMage_UA_8.0.1.0_Windows_GA_28Sep2017_release.exe ,则不需要在源服务器上安装 Update 5 代理。You don't need to install the Update 5 agent on the source server if it has already been updated to Update 4 or source agent is installed with latest base installer InMage_UA_8.0.1.0_Windows_GA_28Sep2017_release.exe .
    8. Linux 源服务器 :若要更新统一代理,请将相应版本的统一代理文件复制到 Linux 服务器并将其解压缩。Linux source server : To update the unified agent, copy the corresponding version of the unified agent file to the Linux server, and extract it. 在解压缩的文件夹中运行 /InstallIn the extracted folder, run /Install .

备注

  • 已刷新面向 Windows 的基本统一代理 (UA) 安装程序,以支持 Windows Server 2016。Base Unified Agent(UA) installer for Windows has been refreshed to support Windows Server 2016. 新的安装程序 InMage_UA_8.0.1.0_Windows_GA_28Sep2017_release.exe 与基本 Scout GA 程序包一起打包 (InMage_Scout_Standard_8.0.1 GA-Oct17.zip )。The new installer InMage_UA_8.0.1.0_Windows_GA_28Sep2017_release.exe is packaged with the base Scout GA package ( InMage_Scout_Standard_8.0.1 GA-Oct17.zip ). 相同的安装程序将用于所有受支持的 Windows 版本。The same installer will be used for all supported Windows version.
  • 已刷新基本 Windows vContinuum 和主目标安装程序来支持 Windows Server 2016。Base Windows vContinuum & Master Target installer has been refreshed to support Windows Server 2016. 新的安装程序 InMage_Scout_vContinuum_MT_8.0.1.0_Windows_GA_10Oct2017_release.exe 与基本 Scout GA 程序包一起打包 (InMage_Scout_Standard_8.0.1 GA-Oct17.zip )。The new installer InMage_Scout_vContinuum_MT_8.0.1.0_Windows_GA_10Oct2017_release.exe is packaged with the base Scout GA package ( InMage_Scout_Standard_8.0.1 GA-Oct17.zip ). 相同的安装程序将用于部署 Windows 2016 主目标和 Windows 2012R2 主目标。The same installer will be used to deploy Windows 2016 Master Target and Windows 2012R2 Master Target.
  • ASR Scout 不支持物理服务器上的 Windows Server 2016。Windows server 2016 on physical server is not supported by ASR Scout. 它仅支持 Windows Server 2016 VMware VM。It supports only Windows Server 2016 VMware VM.

Bug 修复和增强功能Bug fixes and enhancements

  • Linux VM 的故障回复保护失败,而且在配置结束时,要复制的磁盘列表为空。Failback protection fails for Linux VM with list of disks to be replicated is empty at the end of config.

Site Recovery Scout 8.0.1 Update 5Site Recovery Scout 8.0.1 Update 5

Scout Update 5 是累积更新。Scout Update 5 is a cumulative update. 其中包含从 Update 1 到 Update 4 的所有修补程序,以及下面所述的新修补程序。It contains all fixes from Update 1 to Update 4, and the new fixes described below.

  • Site Recovery Scout Update 4 至 Update 5 中的修补程序专门用于主目标组件和 vContinuum 组件。Fixes from Site Recovery Scout Update 4 to Update 5 are specifically for the master target and vContinuum components.
  • 如果源服务器、主目标、配置、进程和 RX 服务器已在运行 Update 4,则仅将其应用在主目标服务器上。If source servers, the master target, configuration, process, and RX servers are already running Update 4, then apply it only on the master target server.

新的平台支持New platform support

  • SUSE Linux Enterprise Server 11 Service Pack 4(SP4)SUSE Linux Enterprise Server 11 Service Pack 4(SP4)
  • SLES 11 SP4 64 位 InMage_UA_8.0.1.0_SLES11-SP4-64_GA_13Apr2017_release.tar.gz 与基础 Scout GA 包 ( InMage_Scout_Standard_8.0.1 GA.zip ) 打包在一起。SLES 11 SP4 64 bit InMage_UA_8.0.1.0_SLES11-SP4-64_GA_13Apr2017_release.tar.gz is packaged with the base Scout GA package ( InMage_Scout_Standard_8.0.1 GA.zip ). 从门户中下载 GA 包,如“创建保管库”中所述。Download the GA package from the portal, as described in create a vault.

Bug 修复和增强功能Bug fixes and enhancements

  • 用于提高 Windows 群集支持可靠性的修补程序:Fixes for increased Windows cluster support reliability:

    • 已修复 - 某些 P2V MSCS 群集磁盘在恢复后成为 RAW。Fixed- Some of the P2V MSCS cluster disks become RAW after recovery.
    • 已修复 - P2V MSCS 群集恢复由于磁盘顺序不匹配而失败。Fixed- P2V MSCS cluster recovery fails due to a disk order mismatch.
    • 已修复 - 添加磁盘的 MSCS 群集操作失败并出现磁盘大小不匹配错误。Fixed- The MSCS cluster operation to add disks fails with a disk size mismatch error.
    • 已修复 - 包含 RDM LUN 的源 MSCS 群集的映射就绪状态检查在验证大小时失败。Fixed- The readiness check for the source MSCS cluster with RDM LUNs mapping fails in size verification.
    • 已修复 - 单节点群集保护由于 SCSI 不匹配问题而失败。Fixed- Single node cluster protection fails because of a SCSI mismatch issue.
    • 已修复 - 当存在目标群集磁盘时,P2V Windows 群集服务器的重新保护失败。Fixed- Re-protection of the P2V Windows cluster server fails if target cluster disks are present.
  • 已修复:在故障回复保护期间,如果所选主目标服务器与受保护源计算机(在正向保护期间)不在同一 ESXi 服务器上,则 vContinuum 在故障回复恢复期间会选取错误的主目标服务器,并且恢复操作会失败。Fixed: During failback protection, if the selected master target server isn't on the same ESXi server as the protected source machine (during forward protection), then vContinuum picks up the wrong master target server during failback recovery, and the recovery operation fails.

备注

  • P2V 群集修补程序仅适用于使用 Site Recovery Scout Update 5 全新保护的物理 MSCS 群集。The P2V cluster fixes are applicable only to physical MSCS clusters that are newly protected with Site Recovery Scout Update 5. 若要在使用较旧更新程序保护的 P2V MSCS 群集上安装群集修补程序,请按照 Site Recovery Scout 发行说明第 12 节中所述的升级步骤进行操作。To install the cluster fixes on protected P2V MSCS clusters with older updates, follow the upgrade steps mentioned in section 12 of the Site Recovery Scout Release Notes.
  • 如果在重新保护时,同一组磁盘在最初受保护的每个群集节点上都处于活动状态,则物理 MSCS 群集的重新保护只能重新使用现有的目标磁盘。if at the time of re-protection, the same set of disks are active on each of the cluster nodes as they were when initially protected, then re-protection of a physical MSCS cluster can only reuse existing target disks. 如果不是,则需执行 Site Recovery Scout 发行说明第 12 节中提到的手动步骤,将目标端磁盘移动到正确的数据存储路径,以便在重新保护期间重新使用它们。If not, then use the manual steps in section 12 of Site Recovery Scout Release Notes, to move the target side disks to the correct datastore path, for reuse during re-protection. 如果在不执行以下升级步骤的情况下重新保护处于 P2V 模式的 MSCS 群集,则它会在目标 ESXi 服务器上创建新磁盘。If you reprotect the MSCS cluster in P2V mode without following the upgrade steps, it creates a new disk on the target ESXi server. 你将需要手动从数据存储中删除旧磁盘。You will need to manually delete the old disks from the datastore.
  • 当源 SLES11 或 SLES11(具有任何 Service Pack)服务器正常重新启动时,手动标记根 磁盘复制对,以便重新同步。When a source SLES11 or SLES11 (with any service pack) server is rebooted gracefully, then manually mark the root disk replication pairs for re-synchronization. CX 界面中不显示任何通知。There's no notification in the CX interface. 如果不标记用于重新同步的根磁盘,则可能会发现数据完整性问题。 If you don't mark the root disk for resynchronization, you might notice data integrity issues.

Azure Site Recovery Scout 8.0.1 Update 4Azure Site Recovery Scout 8.0.1 Update 4

Scout Update 4 是累积更新。Scout Update 4 is a cumulative update. 其中包含从 Update 1 到 Update 3 的所有修补程序,以及下面所述的新修补程序。It includes all fixes from Update 1 to Update 3, and the new fixes described below.

新的平台支持New platform support

  • 添加了对 vCenter/vSphere 6.0、6.1 和 6.2 的支持Support has been added for vCenter/vSphere 6.0, 6.1 and 6.2

  • 已添加对以下 Linux 操作系统的支持:Support has been added for these Linux operating systems:

    • CentOS 7.0、7.1 和 7.2CentOS 7.0, 7.1 and 7.2
    • CentOS 6.8CentOS 6.8

    备注

    CentOS 7 64 位 InMage_UA_8.0.1.0_RHEL7-64_GA_06Oct2016_release.tar.gz 与基础 Scout GA 包 InMage_Scout_Standard_8.0.1 GA.zip 一起打包。CentOS 7 64 bit InMage_UA_8.0.1.0_RHEL7-64_GA_06Oct2016_release.tar.gz is packaged with the base Scout GA package InMage_Scout_Standard_8.0.1 GA.zip . 从门户中下载 Scout GA 包,如“创建保管库”中所述。Download the Scout GA package from the portal as described in create a vault.

Bug 修复和增强功能Bug fixes and enhancements

  • 改进了以下 Linux 操作系统和克隆的关闭处理方式,以防止意外的重新同步问题:Improved shutdown handling for the following Linux operating systems and clones, to prevent unwanted resynchronization issues:
    • Red Hat Enterprise Linux (RHEL) 6.xRed Hat Enterprise Linux (RHEL) 6.x
    • Oracle Linux (OL) 6.xOracle Linux (OL) 6.x
  • 对于 Linux,统一代理安装目录中的所有文件夹访问权限现在仅限为本地用户。For Linux, all folder access permissions in the unified agent installation directory are now restricted to the local user only.
  • 在 Windows 上,修复了在重负载分布式应用程序(例如 SQL Server 和 Share Point 群集)上发出通用分布式一致性书签时出现的超时问题。On Windows, a fix for a timing out issue that occurred when issuing common distributed consistency bookmarks, on heavily loaded distributed applications such as SQL Server and Share Point clusters.
  • 配置服务器基本安装程序中日志相关的修复。A log related fix in the configuration server base installer.
  • 将 VMware vCLI 6.0 的下载链接添加到了 Windows 主目标基本安装程序中。A download link to VMware vCLI 6.0 was added to the Windows master target base installer.
  • 在故障转移和灾难恢复演练期间,针对网络配置更改添加了其他检查和日志。Additional checks and logs were added, for network configuration changes during failover and disaster recovery drills.
  • 修复了导致保留信息无法报告给配置服务器的问题。A fix for an issue that caused retention information not to be reported to the configuration server.
  • 对于物理群集,修复了在 vContinuum 向导中收缩源卷时导致卷大小调整失败的问题。For physical clusters, a fix for an issue that caused volume resizing to fail in the vContinuum wizard, when shrinking the source volume.
  • 修复了当群集磁盘为 PRDM 磁盘时,群集保护失败并出现以下错误的问题:“找不到磁盘签名”。A fix for a cluster protection issue that failed with error: "Failed to find the disk signature", when the cluster disk is a PRDM disk.
  • 修复了 cxps 传输服务器由于超出范围的异常而崩溃的问题。A fix for a cxps transport server crash, caused by an out-of-range exception.
  • 在 vContinuum 向导的“推送安装” 页面中,现在可对服务器名称列和 IP 地址列的大小进行调整。Server name and IP address columns are now resizable in the Push Installation page of the vContinuum wizard.
  • RX API 的增强功能:RX API enhancements:
    • 现在提供了 5 个最新可用的通用一致性点(仅适用于“保证”标记)。The five latest available common consistency points now available (only guaranteed tags).
    • 显示有关所有受保护设备的容量及可用空间的详细信息。Capacity and free space details are displayed for all protected devices.
    • 提供源服务器上的 Scout 驱动程序状态。Scout driver state on the source server is available.

备注

  • InMage_Scout_Standard_8.0.1_GA.zip 基础包中含有:InMage_Scout_Standard_8.0.1_GA.zip base package has:
    • 更新的配置服务器基本安装程序 (InMage_CX_8.0.1.0_Windows_GA_26Feb2015_release.exe )An updated configuration server base installer ( InMage_CX_8.0.1.0_Windows_GA_26Feb2015_release.exe )
    • Windows 主目标基本安装程序 (InMage_Scout_vContinuum_MT_8.0.1.0_Windows_GA_26Feb2015_release.exe )。A Windows master target base installer ( InMage_Scout_vContinuum_MT_8.0.1.0_Windows_GA_26Feb2015_release.exe ).
    • 对于所有新安装,请使用新的配置服务器和 Windows 主目标 GA 位。For all new installations, use the new configuration server and Windows master target GA bits.
  • Update 4 可以直接应用于 8.0.1 GA。Update 4 can be applied directly on 8.0.1 GA.
  • 应用配置服务器和 RX 更新后,不能进行回退。The configuration server and RX updates can't be rolled back after they've been applied.

Azure Site Recovery Scout 8.0.1 Update 3Azure Site Recovery Scout 8.0.1 Update 3

所有 Site Recovery 更新都是累积更新。All Site Recovery updates are cumulative. Update 3 包含来自 Update 1 和 Update 2 的所有修补程序。Update 3 contains all fixes from Update 1 and Update 2. Update 3 可以直接应用于 8.0.1 GA。Update 3 can be directly applied on 8.0.1 GA. 应用配置服务器和 RX 更新后,不能进行回退。The configuration server and RX updates can't be rolled back after they've been applied.

Bug 修复和增强功能Bug fixes and enhancements

Update 3 修复了以下问题:Update 3 fixes the following issues:

  • 配置服务器和 RX 位于代理后面时不会在保管库进行注册。The configuration server and RX aren't registered in the vault when they're behind the proxy.

  • 恢复点目标 (RPO) 未达到的小时数不会在运行状况报告中更新。The number of hours in which the recovery point objective (RPO) wasn't reached is not updated in the health report.

  • 当 ESX 硬件详细信息或网络详细信息包含任何 UTF-8 字符时,配置服务器不会与 RX 同步。The configuration server isn't syncing with RX when the ESX hardware details, or network details, contain any UTF-8 characters.

  • Windows Server 2008 R2 域控制器在恢复之后不启动。Windows Server 2008 R2 domain controllers don't start after recovery.

  • 脱机同步不按预期工作。Offline synchronization isn't working as expected.

  • VM 故障转移后,复制对删除的进度在配置服务器控制台中长时间没有变化。After VM failover, replication-pair deletion doesn't progress in the configuration server console for a long time. 用户无法完成故障回复或恢复操作。Users can't complete the failback or resume operations.

  • 由一致性作业执行的整体快照操作已经过优化,可帮助减少应用程序(例如 SQL Server 客户端)断开连接的问题。Overall snapshot operations by the consistency job have been optimized, to help reduce application disconnects such as SQL Server clients.

  • 改进了一致性工具 (VACP.exe) 的性能。Consistency tool (VACP.exe) performance has been improved. 减少了在 Windows 上创建快照所需的内存使用量。Memory usage required for creating snapshots on Windows has been reduced.

  • 密码超过 16 个字符时,推送安装服务会崩溃。The push install service crashes when the password is larger than 16 characters.

  • 修改凭据后,vContinuum 不检查和提示输入新的 vCenter 凭据。vContinuum doesn't check and prompt for new vCenter credentials, when credentials are modified.

  • 在 Linux 上,主目标缓存管理器 (cachemgr) 不会从进程服务器下载文件。On Linux, the master target cache manager (cachemgr) isn't downloading files from the process server. 这会导致复制对限制。This results in replication pair throttling.

  • 当物理故障转移群集 (MSCS) 磁盘顺序在所有节点上都不相同时,不会为某些群集卷设置复制。When the physical failover cluster (MSCS) disk order isn't the same on all nodes, replication isn't set for some of the cluster volumes. 群集必须获得重新保护才能利用这一修复。The cluster must be reprotected to take advantage of this fix.

  • 在 RX 从 Scout 7.1 升级到 Scout 8.0.1 之后,SMTP 功能无法正常工作。SMTP functionality isn't working as expected, after RX is upgraded from Scout 7.1 to Scout 8.0.1.

  • 已在回滚操作日志中添加更多统计信息,以跟踪完成此操作所需的时间。More statistics have been added in the log for the rollback operation, to track the time taken to complete it.

  • 已添加对源服务器上 Linux 操作系统的支持:Support has been added for Linux operating systems on the source server:

    • CentOS 6 Update 7CentOS 6 update 7
  • 配置服务器和 RX 控制台现在显示进入位图模式的对的通知。The configuration server and RX consoles now show notifications for the pair, which goes into bitmap mode.

  • 已将以下安全修复程序添加到 RX 中:The following security fixes have been added in RX:

    • 通过参数篡改绕过授权:已将访问权限限制为不适用的用户。Authorization bypass via parameter tampering: Restricted access to non-applicable users.
    • 跨站点请求伪造:已实施页面令牌的概念,它会针对每个页面随机生成。Cross-site request forgery: The page-token concept was implemented, and it generates randomly for every page. 这意味着同一用户只有一个登录实例,并且页面刷新不起作用。This means there's only a single sign-in instance for the same user, and page refresh doesn't work. 相反,它将重定向到仪表板。Instead, it redirects to the dashboard.
    • 恶意文件上传:限制文件使用特定的扩展名:z、aiff、asf、avi、bmp、csv、doc、docx、fla、flv、gif、gz、gzip、jpeg、jpg、log、mid、mov、mp3、mp4、mpc、mpeg、mpg、ods、odt、pdf、png、ppt、pptx、pxd、qt、ram、rar、rm、rmi、rmvb、rtf、sdc、sitd、swf、sxc、sxw、tar、tgz、tif、tiff、txt、vsd、wav、wma、wmv、xls、xlsx、xml 和 zip。Malicious file upload: Files are restricted to specific extensions: z, aiff, asf, avi, bmp, csv, doc, docx, fla, flv, gif, gz, gzip, jpeg, jpg, log, mid, mov, mp3, mp4, mpc, mpeg, mpg, ods, odt, pdf, png, ppt, pptx, pxd, qt, ram, rar, rm, rmi, rmvb, rtf, sdc, sitd, swf, sxc, sxw, tar, tgz, tif, tiff, txt, vsd, wav, wma, wmv, xls, xlsx, xml, and zip.
    • 持久性跨站点脚本:添加了输入验证。Persistent cross-site scripting: Input validations were added.

Azure Site Recovery Scout 8.0.1 Update 2 (Update 03Dec15)Azure Site Recovery Scout 8.0.1 Update 2 (Update 03Dec15)

Update 2 中的修复包括:Fixes in Update 2 include:

  • 配置服务器 :在将配置服务器注册到 Azure Site Recovery 保管库时阻止 31 天免费计量功能正常使用的问题。Configuration server : Issues that prevented the 31-day free metering feature from working as expected, when the configuration server was registered to Azure Site Recovery vault.
  • 统一代理 :修复了 Update 1 中导致从版本 8.0 升级到 8.0.1 期间,更新无法安装在主目标服务器上的问题。Unified agent : Fix for an issue in Update 1 that resulted in the update not being installed on the master target server, during upgrade from version 8.0 to 8.0.1.

Azure Site Recovery Scout 8.0.1 Update 1Azure Site Recovery Scout 8.0.1 Update 1

Update 1 包含以下 bug 修复和新功能:Update 1 includes the following bug fixes and new features:

  • 每个服务器实例享有 31 天的免费保护。31 days of free protection per server instance. 这样,便可以测试功能或建立概念认证。This enables you to test functionality, or set up a proof-of-concept.

  • 服务器上的所有操作(包括故障转移和故障回复),前 31 天都可免费使用。All operations on the server, including failover and failback, are free for the first 31 days. 从第一次使用 Site Recovery Scout 保护服务器开始计时。The time starts when a server is first protected with Site Recovery Scout. 从第 32 天起,会根据标准实例费率,针对每个受保护的服务器,向客户拥有的站点收取 Site Recovery 保护费用。From the 32nd day, each protected server is charged at the standard instance rate for Site Recovery protection to a customer-owned site.

  • 在保管库中的“仪表板” 上随时会显示当前计费的受保护服务器数目。At any time, the number of protected servers currently being charged is available on the Dashboard in the vault.

  • 添加了对 vSphere 命令行接口 (vCLI) 5.5 Update 2 的支持。Support was added for vSphere Command-Line Interface (vCLI) 5.5 Update 2.

  • 添加了对源服务器上以下 Linux 操作系统的支持:Support was added for these Linux operating systems on the source server:

    • CentOS 6 Update 6CentOS 6 Update 6
    • CentOS 5 Update 11CentOS 5 Update 11
  • 用于解决以下问题的 Bug 修复:Bug fixes to address the following issues:

    • 配置服务器或 RX 服务器的保管库注册失败。Vault registration fails for the configuration server, or RX server.
    • 当群集 VM 在恢复期间被重新保护时,群集卷不会按预期显示。Cluster volumes don't appear as expected when clustered VMs are reprotected as they resume.
    • 当主目标服务器托管在与本地生产 VM 不同的 ESXi 服务器中时,故障回复失败。Failback fails when the master target server is hosted on a different ESXi server from the on-premises production VMs.
    • 升级到 8.0.1 时,配置文件权限发生更改。Configuration file permissions are changed when you upgrade to 8.0.1. 此更改会影响保护和操作。This change affects protection and operations.
    • 重新同步阈值不按预期强制执行,导致复制行为不一致。The resynchronization threshold isn't enforced as expected, causing inconsistent replication behavior.
    • RPO 设置未正常显示在配置服务器控制台中。The RPO settings don't appear correctly in the configuration server console. 未压缩的数据值错误地显示压缩值。The uncompressed data value incorrectly shows the compressed value.
    • 在 vContinuum 向导中使用“删除”操作不会按预期执行删除,因而无法从配置服务器控制台删除复制内容。The Remove operation doesn't delete as expected in the vContinuum wizard, and replication isn't deleted from the configuration server console.
    • 在 vContinuum 向导中保护 MSCS VM 期间,单击磁盘视图中的“详细信息” 会自动取消选择磁盘。In the vContinuum wizard, the disk is automatically unselected when you click Details in the disk view, during protection of MSCS VMs.
    • 在物理到虚拟 (P2V) 方案中,所需的 HP 服务(例如 CIMnotify、CqMgHost)不会在 VM 恢复中变为“手动”。In the physical-to-virtual (P2V) scenario, required HP services (such as CIMnotify and CqMgHost) aren't moved to manual in VM recovery. 此问题会导致启动时间延长。This issue results in additional boot time.
    • 当主目标服务器上的磁盘数超过 26 个时,Linux VM 保护会失败。Linux VM protection fails when there are more than 26 disks on the master target server.