排查移动服务推送安装问题Troubleshoot Mobility service push installation

安装移动服务是启用复制的一个关键步骤。The Mobility service installation is a key step to enable replication. 此步骤的成功取决于能否满足先决条件并使用受支持的配置。The success of this step depends on meeting prerequisites and working with supported configurations. 在安装移动服务期间可能会遇到的最常见故障是由以下原因导致的:The most common failures you might face during the Mobility service installation are due to:

启用复制时,Azure Site Recovery 会尝试在虚拟机 (VM) 上安装移动服务代理。When you enable replication, Azure Site Recovery tries to install the Mobility service agent on your virtual machine (VM). 在此过程中,配置服务器会尝试连接虚拟机并复制代理。As part of this process, the configuration server tries to connect with the virtual machine and copy the agent. 要想成功安装,请按照分步故障排除指导进行操作。To enable successful installation, follow the step-by-step troubleshooting guidance.

凭据检查(ErrorID:95107 和 95108)Credentials check (ErrorID: 95107 & 95108)

验证在启用复制期间选择的用户帐户是否有效且准确。Verify if the user account chosen during enable replication is valid and accurate. Azure Site Recovery 需要具有管理员特权root 帐户或用户帐户来执行推送安装。Azure Site Recovery requires the root account or user account with administrator privileges to perform a push installation. 否则,系统会在源计算机上阻止推送安装。Otherwise, the push installation will be blocked on the source machine.

对于 Windows(错误 95107),请验证用户是否能够使用本地帐户或域帐户在源计算机上进行管理访问。For Windows (error 95107), verify that the user account has administrative access on the source computer, with either a local account or domain account. 如果使用的不是域帐户,则需在本地计算机上禁用远程用户访问控制。If you aren't using a domain account, you need to disable Remote User Access control on the local computer.

  • 若要手动添加注册表项来禁用远程用户访问控制,请执行以下操作:To manually add a registry key that disables Remote User Access control:

    • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
    • 添加一个新的 DWORDLocalAccountTokenFilterPolicyAdd a new DWORD: LocalAccountTokenFilterPolicy
    • 将值设置为 1Set the value to 1
  • 若要添加注册表项,请在命令提示符下运行以下命令:To add the registry key, from a command prompt, run the following command:

    REG ADD HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v LocalAccountTokenFilterPolicy /t REG_DWORD /d 1

对于 Linux(错误 95108),必须选择 root 帐户才能成功安装移动服务代理。For Linux (error 95108), you must choose the root account for successful installation of Mobility service agent. 此外,SSH 文件传输协议 (SFTP) 服务应当正在运行。Additionally, SSH File Transfer Protocol (SFTP) services should be running. 若要在 sshd_config 文件中启用 SFTP 子系统和密码身份验证,请执行以下操作:To enable the SFTP subsystem and password authentication in the sshd_config file:

  1. root 身份登录。Sign in as root.
  2. 转到 /etc/ssh/sshd_config 文件,找到以 PasswordAuthentication 开头的行。Go to /etc/ssh/sshd_config file, find the line that begins with PasswordAuthentication.
  3. 取消注释该行,并将值更改为 yesUncomment the line, and change the value to yes.
  4. 找到以 Subsystem 开头的行,并取消注释该行。Find the line that begins with Subsystem, and uncomment the line.
  5. 重新启动 sshd 服务。Restart the sshd service.

如果想要修改所选用户帐户的凭据,请按照这些说明进行操作。If you wish to modify the credentials of the chosen user account, follow these instructions.

权限不足故障(ErrorID:95517)Insufficient privileges failure (ErrorID: 95517)

如果选择用来安装移动代理的用户没有管理员权限,则不允许配置服务器/横向扩展进程服务器将移动代理软件复制到源计算机。When the user chosen to install the Mobility agent doesn't have administrator privileges, the configuration server/scale-out process server won't be allowed to copy the Mobility agent software to source machine. 此错误是“拒绝访问”故障导致的。This error is a result of an access denied failure. 确保用户帐户有管理员权限。Ensure that the user account has administrator privileges.

如果想要修改所选用户帐户的凭据,请按照这些说明进行操作。If you wish to modify the credentials of the chosen user account, follow these instructions.

权限不足故障(ErrorID:95518)Insufficient privileges failure (ErrorID: 95518)

如果在尝试登录到源计算机时无法在主域和工作站之间建立域信任关系,则移动代理安装会失败,出现的错误 ID 为 95518。When the domain trust relationship establishment between the primary domain and workstation fails while trying to sign in to the source machine, the Mobility agent installation fails with error ID 95518. 请确保用于安装移动代理的用户帐户具有管理员权限,能够通过源计算机的主域进行登录。Ensure that the user account used to install the Mobility agent has administrative privileges to sign in through primary domain of the source machine.

如果想要修改所选用户帐户的凭据,请按照这些说明进行操作。If you wish to modify the credentials of chosen user account, follow the these instructions.

登录失败(错误 ID:95519、95520、95521、95522)Login failures (ErrorID: 95519, 95520, 95521, 95522)

本部分介绍了凭据和登录错误消息。This section describes credential and login error messages.

用户帐户的凭据已禁用(ErrorID:95519)Credentials of the user account have been disabled (ErrorID: 95519)

在启用复制期间选择的用户帐户被禁用。The user account chosen during enable replication was disabled. 若要启用用户帐户,请参阅此文,或者运行以下命令,将文本 username 替换为实际的用户名。To enable the user account, refer to this article or run the following command by replacing text username with the actual user name.

net user 'username' /active:yes

由于多次登录尝试均失败,凭据已被锁定(ErrorID:95520)Credentials locked out because of multiple failed login attempts (ErrorID: 95520)

在访问计算机时多次重试失败会导致系统锁定用户帐户。Multiple failed retry efforts to access a machine will lock the user account. 失败可能是因为:The failure can be due to:

  • 在配置设置过程中提供的凭据不正确。Credentials provided during configuration setup are incorrect.
  • 在启用复制期间选择的用户帐户不正确。The user account chosen during enable replication is wrong.

根据这些说明修改所选的凭据,然后重试操作。Modify the credentials chosen by following these instructions and retry the operation.

登录服务器在源计算机上不可用(ErrorID:95521)Logon servers aren't available on the source machine (ErrorID: 95521)

登录服务器在源计算机上不可用时,会发生此错误。This error occurs when the logon servers aren't available on the source machine. 如果登录服务器不可用,则登录请求会失败,并且无法安装移动代理。If logon servers aren't available, login requests will fail and the Mobility agent can't be installed. 若要成功进行登录,请确保登录服务器在源计算机上可用,然后启动 Netlogon 服务。For a successful login, ensure that logon servers are available on the source machine and start the Netlogon service. 有关详细信息,请参阅 Windows 登录方案For more information, see Windows Logon Scenarios.

登录服务未在源计算机上运行(ErrorID:95522)Logon service isn't running on the source machine (ErrorID: 95522)

登录服务未在源计算机上运行,导致登录请求失败。The login service isn't running on your source machine and caused failure of the login request. 无法安装移动代理。The Mobility agent can't be installed. 若要解决此错误,请使用以下方法之一在源计算机上启动 Netlogon 服务:To resolve the error, use one of the following methods to start the Netlogon service on the source machine:

  • 若要从命令提示符启动 Netlogon 服务,请运行 net start Netlogon 命令。To start the Netlogon service from a command prompt, run the command net start Netlogon.
  • 从任务管理器中,启动 Netlogon 服务。From Task Manager, start the Netlogon service.

连接失败(ErrorID:95117 和 97118)Connectivity failure (ErrorID: 95117 & 97118)

配置服务器/横向扩展进程服务器尝试连接到源 VM 以安装移动代理。Configuration server/scale-out process server tries to connect to the source VM to install the Mobility agent. 当源计算机因网络连接问题而无法访问时,会发生此错误。This error occurs when the source machine isn't reachable because there are network connectivity issues.

若要解决该错误:To resolve the error:

  • 请确保你能够从配置服务器对源计算机执行 ping 操作。Ensure you can ping your source machine from the configuration server. 如果在启用复制期间选择了横向扩展进程服务器,请确保能够从进程服务器对源计算机执行 ping 操作。If you've chosen the scale-out process server during enable replication, ensure you can ping your source machine from the process server.

  • 从源服务器计算机的命令行中,使用 Telnet 在 HTTPS 端口 135 上对配置服务器或横向扩展进程服务器执行 ping 操作,如以下命令所示。From the source server machine command line, use Telnet to ping the configuration server or scale-out process server on HTTPS port 135 as shown in the following command. 此命令检查是否存在任何网络连接问题或防火墙端口阻止问题。This command checks if there are any network connectivity issues or firewall port blocking issues.

    telnet <CS/ scale-out PS IP address> <135>

  • 此外,对于 Linux VM:Additionally, for a Linux VM:

    • 请检查是否已安装最新的 OpenSSH、OpenSSH Server 和 OpenSSL 包。Check if latest OpenSSH, OpenSSH Server, and OpenSSL packages are installed.

    • 检查并确保安全外壳 (SSH) 已启用且正在端口 22 上运行。Check and ensure that Secure Shell (SSH) is enabled and is running on port 22.

    • SFTP 服务应运行。SFTP services should be running. 若要在 sshd_config 文件中启用 SFTP 子系统和密码身份验证,请执行以下操作:To enable SFTP subsystem and password authentication in the sshd_config file:

      1. root 身份登录。Sign in as root.
      2. 转到 /etc/ssh/sshd_config 文件,找到以 PasswordAuthentication 开头的行。Go to /etc/ssh/sshd_config file, find the line that begins with PasswordAuthentication.
      3. 取消注释该行,并将值更改为 yesUncomment the line, and change the value to yes.
      4. 找到以 Subsystem 开头的行,并取消注释该行。Find the line that begins with Subsystem, and uncomment the line
      5. 重新启动 sshd 服务。Restart the sshd service.
  • 如果一段时间后没有正确的响应,则连接尝试可能已失败,或者由于连接的主机响应失败,已建立的连接失败。A connection attempt could have failed if there are no proper responses after a period of time, or an established connection failed because a connected host failed to respond.

  • 这可能是由连接/网络/域相关问题导致的。It may be a connectivity/network/domain related issue. 这也可能是由 DNS 名称解析问题或 TCP 端口耗尽问题导致的。It could also be because DNS name resolving issue or TCP port exhaustion issue. 请检查域中是否存在任何此类已知问题。Check if there are any such known issues in your domain.

连接失败(ErrorID:95523)Connectivity failure (ErrorID: 95523)

当源计算机所在的网络无法找到、可能已被删除或不再可用时,会发生此错误。This error occurs when the network that the source machine resides isn't found, might have been deleted, or is no longer available. 若要解决此错误,唯一的方法是确保网络存在。The only way to resolve the error is to ensure that the network exists.

检查源计算机上网络共享文件夹的访问权限(ErrorID:95105,95523)Check access for network shared folders on source machine (ErrorID: 95105,95523)

验证虚拟计算机上的网络共享文件夹是否可使用特定凭据从进程服务器 (PS) 进行远程访问。Verify if the network shared folders on your virtual machine, are accessible from Process Server (PS) remotely using specified credentials. 若要确认访问,请执行以下操作:To confirm access:

  1. 登录到进程服务器计算机。Log in to your Process Server machine.

  2. 打开文件资源管理器。Open File Explorer. 在地址栏中,键入 \\<SOURCE-MACHINE-IP>\C$,然后按 Enter。In the address bar, type \\<SOURCE-MACHINE-IP>\C$ and click Enter.

    在 PS 中打开文件夹

  3. 文件资源管理器将提示输入凭据。File explorer will prompt for credentials. 输入用户名和密码,然后单击“确定”。Enter the username and password and click OK.

    提供凭据

    备注

    如果源计算机已加入域,则按 <domainName>\<username> 格式提供域名和用户名。If source machine is domain joined, provide the domain name along with user name as <domainName>\<username>. 如果源计算机位于工作组中,仅提供用户名。If source machine is in work group, provide only the user name.

  4. 如果成功连接,则可以从进程服务器远程查看源计算机的文件夹。If connection is successful, the folders of source machine will be visible remotely from Process Server.

    源计算机上的可见文件夹

如果连接不成功,请检查是否满足所有先决条件。If connection is unsuccessful, please check whether all pre-requisites are met.

文件和打印机共享服务检查(ErrorID:95105 和 95106)File and Printer sharing services check (ErrorID: 95105 & 95106)

进行连接性检查后,验证是否在虚拟机上启用了文件和打印机共享服务。After a connectivity check, verify if the File and Printer sharing service is enabled on your virtual machine. 若要将移动代理复制到源计算机,这些设置是必需的。These settings are required to copy the Mobility agent to the source machine.

对于 Windows 2008 R2 和以前的版本For Windows 2008 R2 and prior versions:

  • 若要通过 Windows 防火墙启用文件和打印共享,To enable file and print sharing through Windows Firewall,

    1. 打开“控制面板” > “系统和安全” > “Windows 防火墙”。 Open Control Panel > System and Security > Windows Firewall. 在左侧窗格的控制台树中选择“高级设置” > “入站规则”。 In the left pane, select Advanced settings > Inbound Rules in console tree.
    2. 找到文件和打印机共享 (NB-Session-In) 以及文件和打印机共享 (SMB-In) 规则。Locate rules File and Printer Sharing (NB-Session-In) and File and Printer Sharing (SMB-In).
    3. 请依次右键单击每个规则,然后单击“启用规则”。For each rule, right-click the rule, and then click Enable Rule.
  • 若要使用组策略来启用文件共享,请执行以下操作:To enable file sharing with Group Policy:

    1. 转到“开始”,键入 gpmc.msc 并搜索。Go to Start, type gpmc.msc and search.

    2. 在导航窗格中,打开以下文件夹:“本地计算机策略” > “用户配置” > “管理模板” > “Windows 组件” > “网络共享”。 In the navigation pane, open the following folders: Local Computer Policy > User Configuration > Administrative Templates > Windows Components > Network Sharing.

    3. 在详细信息窗格中,双击“防止用户共享其配置文件中的文件”。In the details pane, double-click Prevent users from sharing files within their profile.

      若要禁用组策略设置,并允许用户共享文件,请选择“禁用”。To disable the Group Policy setting, and enable the user's ability to share files, select Disabled.

    4. 选择“确定”保存更改。Select OK to save your changes.

    有关详细信息,请参阅使用组策略启用或禁用文件共享To learn more, see Enable or disable File Sharing with Group Policy.

若要为更高版本的 Windows 或 Linux 启用文件和打印机共享,请按照安装移动服务以对 VMware VM 和物理服务器进行灾难恢复中的说明进行操作。To enable file and printer sharing for later versions of Windows or Linux, follow the instructions in Install the Mobility service for disaster recovery of VMware VMs and physical servers .

Windows Management Instrumentation (WMI) 配置检查(错误代码:95103)Windows Management Instrumentation (WMI) configuration check (Error code: 95103)

进行文件和打印机服务检查后,通过防火墙为专用配置文件、公共配置文件和域配置文件启用 WMI 服务。After file and printer services check, enable the WMI service for private, public, and domain profiles through the firewall. 若要在源计算机上完成远程执行操作,这些设置是必需的。These settings are required to complete remote execution on the source machine.

若要启用 WMI,请执行以下操作:To enable WMI:

  1. 转到“控制面板” > “安全”,然后选择“Windows 防火墙”。 Go to Control Panel > Security and select Windows Firewall.
  2. 选择“更改设置”,然后选择“异常”选项卡。 Select Change Settings and then select the Exceptions tab.
  3. 在“异常”窗口中,选中 Windows Management Instrumentation (WMI) 对应的复选框,以启用穿过防火墙的 WMI 流量。In the Exceptions window, select the check box for Windows Management Instrumentation (WMI) to enable WMI traffic through the firewall.

还可以从命令提示符使用以下命令来启用穿过防火墙的 WMI 流量:You can also enable WMI traffic through the firewall from the command prompt with the following command:

netsh advfirewall firewall set rule group="windows management instrumentation (wmi)" new enable=yes

可以在以下文章中找到其他 WMI 故障排除文章。Other WMI troubleshooting articles could be found at the following articles.

不支持的操作系统Unsupported operating systems

另一个常见的失败原因可能是操作系统不受支持。Another common reason for failure could be because of an unsupported operating system. 请使用受支持的操作系统和内核版本,以便成功安装移动服务。Use a supported operating system and kernel version for a successful installation of the Mobility service. 避免使用私有修补程序。Avoid the use of private patches.

若要查看 Azure Site Recovery 支持的操作系统和内核版本列表,请参阅支持矩阵文档To view the list of operating systems and kernel versions supported by Azure Site Recovery, see the support matrix document.

启动磁盘配置不受支持(ErrorID:95309、95310、95311)Unsupported boot disk configurations (ErrorID: 95309, 95310, 95311)

启动和系统分区/卷不是同一磁盘(ErrorID:95309)Boot and system partitions / volumes aren't the same disk (ErrorID: 95309)

在版本 9.20 之前,将启动和系统分区/卷置于不同磁盘上是不受支持的配置。Before the 9.20 version, boot and system partitions/volumes on different disks were an unsupported configuration. 版本 9.20 开始,此配置受支持。Beginning with the 9.20 version, this configuration is supported.

启动盘不可用(ErrorID:95310)The boot disk isn't available (ErrorID: 95310)

无法保护没有启动盘的虚拟机。A virtual machine without a boot disk can't be protected. 启动盘可以确保在故障转移操作期间顺利恢复虚拟机。A boot disk ensures a smooth recovery of a virtual machine during a failover operation. 缺少启动盘会导致故障转移后无法启动计算机。Absence of a boot disk results in a failure to boot the machine after failover. 确保虚拟机包含启动盘并重试该操作。Ensure that the virtual machine contains a boot disk and retry the operation. 另外,不支持同一台计算机上有多个启动盘。Also, multiple boot disks on the same machine aren't supported.

源计算机上存在多个启动磁盘(ErrorID:95311)Multiple Boot disks present on the source machine (ErrorID: 95311)

具有多个启动盘的虚拟机不是受支持的配置A virtual machine with multiple boot disks isn't a supported configuration.

在多个磁盘上进行系统分区(ErrorID:95313)System partition on multiple disks (ErrorID: 95313)

在版本 9.20 之前,将根分区或卷设置在多个磁盘上是不受支持的配置。Before the 9.20 version, a root partition or volume setup on multiple disks was an unsupported configuration. 版本 9.20 开始,此配置受支持。Beginning with the 9.20 version, this configuration is supported.

启用保护失败,因为 GRUB 配置中提到了设备名而非 UUID(ErrorID:95320)Enable protection failed as device name mentioned in the GRUB configuration instead of UUID (ErrorID: 95320)

可能的原因Possible Cause

Grand Unified Bootloader (GRUB) 配置文件(“/boot/grub/menu.lst”、“/boot/grub/grub.cfg”、“/boot/grub2/grub.cfg”或“/etc/default/grub”)可能包含参数 rootresume 的值作为实际设备名而非全局唯一标识符 (UUID)。 The Grand Unified Bootloader (GRUB) configuration files (/boot/grub/menu.lst, /boot/grub/grub.cfg, /boot/grub2/grub.cfg, or /etc/default/grub) may contain the value for the parameters root and resume as the actual device names instead of a universally unique identifier (UUID). Site Recovery 要求使用 UUID 方法,因为设备名称在 VM 重启后可能会发生更改。Site Recovery mandates the UUID approach as the device names may change across reboot of the VM. 例如,VM 在故障转移时可能不会以相同的名称联机,导致出现问题。For example, the VM may not come online with the same name on failover and that results in issues.

例如:For example:

  • 以下行来自 GRUB 文件 /boot/grub2/grub.cfg:The following line is from the GRUB file /boot/grub2/grub.cfg:

    linux /boot/vmlinuz-3.12.49-11-default root=/dev/sda2 ${extra_cmdline} resume=/dev/sda1 splash=silent quiet showopts

  • 以下行摘自 GRUB 文件 /boot/grub/menu.lst:The following line is from the GRUB file /boot/grub/menu.lst:

    kernel /boot/vmlinuz-3.0.101-63-default root=/dev/sda2 resume=/dev/sda1 splash=silent crashkernel=256M-:128M showopts vga=0x314

备注

对于 rootresume 参数,GRUB 行包含实际设备名称而非 UUID。The GRUB lines contain actual device names for the parameters root and resume rather than the UUID.

如何修复How to Fix

设备名应替换为相应的 UUID。The device names should be replaced with the corresponding UUID.

  1. 执行 blkid \<device name> 命令来查找设备的 UUID。Find the UUID of the device by executing the command blkid \<device name>.

    例如:For example:

    blkid /dev/sda1
    /dev/sda1: UUID="6f614b44-433b-431b-9ca1-4dd2f6f74f6b" TYPE="swap"
    blkid /dev/sda2
    /dev/sda2: UUID="62927e85-f7ba-40bc-9993-cc1feeb191e4" TYPE="ext3"
    
  2. 现在请将设备名替换为其 UUID,格式类似于 root=UUID=\<UUID>Now replace the device name with its UUID in the format like root=UUID=\<UUID>. 例如,对于在“/boot/grub2/grub.cfg”、“/boot/grub2/grub.cfg”或“/etc/default/grub”文件中提到的 root 和 resume 参数,如果将设备名称替换为 UUID,则文件中的行将类似于以下行: For example, if we replace the device names with UUID for root and resume parameter mentioned in the files /boot/grub2/grub.cfg, /boot/grub2/grub.cfg, or /etc/default/grub then the lines in the files look like the following line:

    kernel /boot/vmlinuz-3.0.101-63-default root=UUID=62927e85-f7ba-40bc-9993-cc1feeb191e4 resume=UUID=6f614b44-433b-431b-9ca1-4dd2f6f74f6b splash=silent crashkernel=256M-:128M showopts vga=0x314

  3. 重启保护。Restart the protection.

安装移动设备的操作完成,出现重启警告(ErrorID:95265 和 95266)Install Mobility service completed with warning to reboot (ErrorID: 95265 & 95266)

Site Recovery 移动服务有多个组件,其中一个称为筛选器驱动程序。Site Recovery Mobility service has many components, one of which is called filter driver. 筛选器驱动程序只有在系统重启期间才会加载到系统内存中。The filter driver is loaded into system memory only during a system reboot. 实现筛选器驱动程序修复的前提是,在系统重启时加载新的筛选器驱动程序。Filter driver fixes can only be realized when a new filter driver is loaded at the time of a system reboot.

重要

这是一个警告,在新代理更新后,现有复制仍会继续进行。This is a warning and existing replication will work even after the new agent update. 可以选择在需要使用新筛选器驱动程序的时候重启,但如果不重启,则旧筛选器驱动程序仍可继续使用。You can choose to reboot anytime you want to get the benefits of new filter driver but if you don't reboot, the old filter driver keeps on working. 因此,如果在更新后没有重启,则除了筛选器驱动器之外,移动服务中的其他增强功能和修复程序的功能均可实现So, after an update without a reboot, except for the filter driver, benefits of other enhancements and fixes in Mobility service get realized. 不需在每次升级后都重启,虽然我们建议你重启。Although recommended, it isn't mandatory to reboot after every upgrade. 若要了解何时必须重启,请参阅“Azure Site Recovery 中的服务更新”中的升级移动服务后重启部分。For information about when a reboot is mandatory, set the Reboot after Mobility service upgrade section in Service updates in Azure Site Recovery.

提示

有关在维护时段计划升级的最佳做法,请参阅“Azure Site Recovery 中的服务更新”中的对最新操作系统/内核的支持For best practices on scheduling upgrades during your maintenance window, see the Support for latest operating system/kernel in Service updates in Azure Site Recovery.

版本 9.20 提供的 LVM 支持LVM support from 9.20 version

在版本 9.20 之前,仅支持将逻辑卷管理器 (LVM) 用于数据磁盘。Before the 9.20 version, Logical Volume Manager (LVM) was supported for data disks only. /boot 分区应位于磁盘分区上,而不应位于 LVM 卷上。The /boot partition should be on a disk partition and not an LVM volume.

版本 9.20 开始,LVM 上的 OS 磁盘受支持。Beginning with the 9.20 version, the OS disk on LVM is supported.

空间不足(ErrorID:95524)Insufficient space (ErrorID: 95524)

将移动代理复制到源计算机时,需要至少 100 MB 的可用空间。When the Mobility agent is copied to the source machine, at least 100 MB free space is required. 请确保源计算机有必需的可用空间量,然后重试此操作。Ensure that your source machine has the required amount of free space and retry the operation.

系统资源不足Low system resources

出现此问题时,可能看到的错误 ID 有 95572 和 95573。The possible Error IDs seen for this issue are 95572 and 95573. 如果系统内存不足,且无法为移动服务安装分配内存,则会出现此问题。This issue occurs when the system has low available memory, and is not able to allocate memory for mobility service installation. 确保已释放足够的内存,让安装继续进行并成功完成。Ensure that enough memory has been freed up for the installation to proceed and complete successfully.

VSS 安装失败VSS Installation failures

卷影复制服务 (VSS) 安装是移动代理安装的一部分。The Volume Shadow copy Service (VSS) installation is a part of Mobility agent installation. 在生成应用程序一致恢复点的过程中将使用此服务。This service is used in the process to generate application consistent recovery points. VSS 安装过程可能会由于多种原因而失败。Failures during VSS installation can occur due to multiple reasons. 若要查明确切的错误,请参阅 C:\ProgramData\ASRSetupLogs\ASRUnifiedAgentInstaller.log。To identify the exact errors, refer to C:\ProgramData\ASRSetupLogs\ASRUnifiedAgentInstaller.log. 以下部分中重点介绍了一些常见的错误和解决方法步骤。Some of the common errors and the resolution steps are highlighted in the following section.

VSS 错误 -2147023170 [0x800706BE] - 退出代码 511VSS error -2147023170 [0x800706BE] - exit code 511

最常出现此问题的情形是防病毒软件阻止了 Azure Site Recovery 服务的操作。This issue is most often seen when antivirus software is blocking the operations of Azure Site Recovery services.

若要解决此问题,请执行下列操作:To resolve this issue:

  1. 查看防病毒程序中的文件夹排除项列表。Review the list of folder exclusions from Antivirus program.
  2. 按照你的防病毒软件提供商发布的指南在 Windows 中取消阻止 DLL 的注册。Follow the guidelines published by your antivirus provider to unblock the registration of DLL in Windows.

VSS 错误 7 [0x7] - 退出代码 511VSS error 7 [0x7] - exit code 511

此错误是一个运行时错误,是由于内存不足而无法安装 VSS 导致的。This error is a runtime error that's caused because there's insufficient memory to install VSS. 请增大磁盘空间以成功完成此操作。Increase the disk space for successful completion of this operation.

VSS 错误 -2147023824 [0x80070430] - 退出代码 517VSS error -2147023824 [0x80070430] - exit code 517

当 Azure Site Recovery VSS 提供程序服务标记为待删除时会发生此错误。This error occurs when Azure Site Recovery VSS Provider service is marked for deletion. 请尝试通过运行以下命令手动在源计算机上安装 VSS:Try to install VSS manually on the source machine by running the following command:

"C:\Program Files (x86)\Microsoft Azure Site Recovery\agent\InMageVSSProvider_Install.cmd"

VSS 错误 -2147023841 [0x8007041F] - 退出代码 512VSS error -2147023841 [0x8007041F] - exit code 512

当 Azure Site Recovery VSS 提供程序服务数据库被锁定时会发生此错误。请尝试从命令提示符运行以下命令,以便手动在源计算机上安装 VSS:This error occurs when Azure Site Recovery VSS Provider service database is locked.Try to install VSS manually on the source machine by running the following command from a command prompt:

"C:\Program Files (x86)\Microsoft Azure Site Recovery\agent\InMageVSSProvider_Install.cmd"

如果出现故障,请检查是否有任何防病毒程序或其他服务停滞在“正在启动”状态。When there's a failure, check if any antivirus program or other services are stuck in a Starting state. 处于“正在启动”状态的进程可以保留对数据库服务的锁定。A process in a Starting state can retain the lock on database services. 这将导致安装 VSS 提供程序时出现故障。It will lead to failures in installing VSS provider. 请确保没有服务处于“正在启动”状态,然后重试上述操作。Ensure that no service is in a Starting state and then retry the above operation.

VSS 退出代码 806VSS exit code 806

当用于安装的用户帐户无权执行 CSScript 命令时会发生此错误。This error occurs when the user account used for installation doesn't have permissions to execute the CSScript command. 请为用户帐户提供执行此脚本所需的权限,然后重试操作。Provide necessary permissions to the user account to execute the script and retry the operation.

其他 VSS 错误Other VSS errors

请尝试从命令提示符运行以下命令,手动在源计算机上安装 VSS 提供程序服务:Try to install VSS provider service manually on the source machine by running the following command from a command prompt:

"C:\Program Files (x86)\Microsoft Azure Site Recovery\agent\InMageVSSProvider_Install.cmd"

VSS 错误 - 0x8004E00FVSS error - 0x8004E00F

此错误通常出现在移动代理的安装过程中,其原因是 DCOM 出现问题,且 DCOM 处于某种严重状态。This error typically occurs during the installation of the Mobility agent because of issues in DCOM and DCOM is in a critical state.

使用以下过程确定错误原因。Use the following procedure to determine the cause of the error.

检查安装日志Examine the installation logs

  1. 打开位于 C:\ProgramData\ASRSetupLogs\ASRUnifiedAgentInstaller.log 中的安装日志。Open the installation log located at C:\ProgramData\ASRSetupLogs\ASRUnifiedAgentInstaller.log.

  2. 如果存在以下错误,则表示出现了此问题:The presence of the following error indicates this issue:

    Unregistering the existing application...
    Create the catalogue object
    Get the collection of Applications
    
    ERROR:
    
    - Error code: -2147164145 [0x8004E00F]
    - Exit code: 802
    

若要解决问题,请执行以下操作:To resolve the issue:

请联系 Microsoft Windows 平台团队,让他们帮助解决 DCOM 问题。Contact the Microsoft Windows platform team to obtain assistance with resolving the DCOM issue.

解决 DCOM 问题后,从命令提示符使用以下命令手动重新安装 Azure Site Recovery VSS 提供程序:When the DCOM issue is resolved, reinstall the Azure Site Recovery VSS Provider manually using the following command from a command prompt:

"C:\Program Files (x86)\Microsoft Azure Site Recovery\agent\InMageVSSProvider_Install.cmd"

如果应用程序一致性不是一项关键的灾难恢复要求,则可以绕过 VSS 提供程序的安装。If application consistency isn't critical for your disaster recovery requirements, you can bypass the VSS Provider installation.

若要绕过 Azure Site Recovery VSS 提供程序的安装,并在安装后手动安装 Azure Site Recovery VSS 提供程序:To bypass the Azure Site Recovery VSS Provider installation and manually install Azure Site Recovery VSS Provider post installation:

  1. 安装移动服务。Install the Mobility service. 安装将在此步骤失败:安装后配置The Installation will fail at the step: Post install configuration.

  2. 若要绕过 VSS 的安装:To bypass the VSS installation:

    1. 打开位于以下位置的 Azure Site Recovery 移动服务安装目录:Open the Azure Site Recovery Mobility Service installation directory located at:

      C:\Program Files (x86)\Microsoft Azure Site Recovery\agentC:\Program Files (x86)\Microsoft Azure Site Recovery\agent

    2. 添加以下行,修改 Azure Site Recovery VSS 提供程序安装脚本 InMageVSSProvider_Install 和 InMageVSSProvider_Uninstall.cmd,这样就能始终成功:Modify the Azure Site Recovery VSS Provider installation scripts InMageVSSProvider_Install and InMageVSSProvider_Uninstall.cmd to always succeed by adding the following lines:

      rem @echo off
      setlocal
      exit /B 0
      
  3. 手动安装移动代理。Do a manual installation of the Mobility Agent.

  4. 当安装成功并转到下一步骤“配置”时,请删除添加的行。When the installation succeeds and moves to the next step, Configure, remove the lines you added.

  5. 若要安装 VSS 提供程序,请以管理员身份打开命令提示符并运行以下命令:To install the VSS provider, open a command prompt as administrator and run the following command:

    "C:\Program Files (x86)\Microsoft Azure Site Recovery\agent\InMageVSSProvider_Install.cmd"

  6. 在“Windows 服务”中验证 Azure Site Recovery VSS 提供程序是否已安装为一项服务。Verify that the Azure Site Recovery VSS Provider is installed as a service in Windows Services. 打开组件服务 MMC 来确认 VSS 提供程序已列出。Open the Component Service MMC to confirm that the VSS Provider is listed.

  7. 如果 VSS 提供程序安装仍然失败,请与技术支持人员一起解决加密应用程序编程接口 (CAPI2) 中的权限错误。If the VSS Provider install continues to fail, work with technical support to resolve the permissions errors in Cryptographic Application Programming Interface (CAPI2).

在非群集计算机上启用群集服务导致 VSS 提供程序安装失败VSS Provider installation fails because the cluster service being enabled on non-cluster machine

此问题导致 Azure Site Recovery 移动代理安装在 Azure Site Recovery VSS 提供程序安装过程中失败。This issue causes the Azure Site Recovery Mobility Agent installation to fail during the Azure Site Recovery VSS Provider installation. 失败是因为 COM+ 发生了阻止 VSS 提供程序安装的问题。The failure is because there's an issue with COM+ that prevents the VSS provider installation.

识别问题To identify the issue

在配置服务器上的 C:\ProgramData\ASRSetupLogs\UploadedLogs<date-time>UA_InstallLogFile.log 日志中,会看到以下异常:In the log located on configuration server at C:\ProgramData\ASRSetupLogs\UploadedLogs<date-time>UA_InstallLogFile.log you'll find the following exception:

COM+ was unable to talk to the Microsoft Distributed Transaction Coordinator (Exception from HRESULT: 0x8004E00F)

若要解决问题,请执行以下操作:To resolve the issue:

  1. 确认此计算机是一台非群集计算机,并且未使用群集组件。Verify that this machine is a non-cluster machine and that the cluster components aren't being used.
  2. 如果未使用那些组件,请从计算机中删除群集组件。If the components aren't being used, remove the cluster components from the machine.

源服务器上缺少驱动程序Drivers are missing on the source server

如果移动代理安装失败,请检查 C:\ProgramData\ASRSetupLogs 下的日志,以确定某些控制集中是否缺少某些必需的驱动程序。If the Mobility Agent installation fails, examine the logs under C:\ProgramData\ASRSetupLogs to determine if some of the required drivers are missing in some control sets.

若要解决问题,请执行以下操作:To resolve the issue:

  1. 使用 regedit.msc 之类的注册表编辑器打开注册表。Using a registry editor such as regedit.msc, open the registry.

  2. 打开 HKEY_LOCAL_MACHINE\SYSTEM 节点。Open the HKEY_LOCAL_MACHINE\SYSTEM node.

  3. SYSTEM 节点中找到控制集。In the SYSTEM node, locate the control sets.

  4. 打开每个控制集并确认以下 Windows 驱动程序是否存在:Open each control set and verify that following Windows drivers are present:

    • AtapiAtapi
    • VmbusVmbus
    • StorfltStorflt
    • StorvscStorvsc
    • IntelideIntelide
  5. 重新安装所有缺少的驱动程序。Reinstall any missing drivers.

后续步骤Next steps

详细了解如何为 VMware VM 设置灾难恢复。Learn more about how to set up disaster recovery for VMware VMs.