ASR VM复制/更新问题 [英] ASR VM replication/update issue

问题描述

最近，我通过ASR进程/配置服务器更新了9.29版本，从9.29开始更新到9.21再到9.23。

Recently, I updated by ASR process/config server with version 9.24 from 9.19, first to 9.21 and then to 9.23.

我将服务器更新到9.21然后到9.23之后，我使用来自ASR门户的推送技术将移动性更新到我的5个复制虚拟机中的每个虚拟机。虽然它成功完成了更新，但它要求我重启ASR流程服务器，我做了
。

After I updated the server to 9.21 and then to 9.23 after which I updated the mobility to each of my 5 replicated VMs using the push technology from the ASR portal. While it did the update successfully, it asked me to reboot the ASR process server which I did.

安装完成后，我的两个虚拟机显示了关键状态和应用程序崩溃测试一致性没有更新。

After the install, two of my VMs showed critical status and the app and crash test consistency is not updated.

在我的ASR门户中，我看到有另一个最新版本的ASR，我在流程服务器中更新并重新启动它。在ASR门户网站上，它向我展示了更新的移动版本，但是当我使用推送技术更新相同时，它显示
我只有3个虚拟机而不是5个。

In my ASR portal, I saw there is another latest version of ASR which I updated in the process server and rebooted it. On the ASR portal, it showed me that there is an updated mobility version but when I went to update the same using push technology, it showed me only 3 VMs instead of 5.

我的进程/配置服务器可以从两台机器上访问。

My process/config server is accessible from both the machines.

我检查了两个有效的写入状态使用VSSADMIN列表编写器的虚拟机没有发现任何错误。

之前是否有人遇到此问题，如何确保受影响的计算机复制回ASR。

Did anyone experience this issue before and how can I make sure the effected machines replicate back to ASR.

谢谢。

推荐答案

我收到以下错误ASR日志中的消息：C：\Program Files（x86）\ Microsoft Azure Site Recovery \agent

I'm getting below error message in the ASR logs at C:\Program Files (x86)\Microsoft Azure Site Recovery\agent

＃〜> （04-29-2019 04:44:22）：  ALWAYS  32628 29372 109483 VxService :: StartVacp：vacp已成功启动，processid = 35352

＃〜> （04-29-2019 04:44:22）：   错误  32628 29372 109484进程InMageAgentVacp with pid 35352退出，退出代码为-2147483501。

＃〜> （04-29-2019 04:44:28）：  ALWAYS  32628 29372 109485 VxService :: StartVacp：forking vacp C：\Program Files（x86）\ Microsoft Azure Site Recovery\agent\vacp  -systemlevel -parallel -vtoa  -cc

＃〜> （04-29-2019 04:44:28）：  ALWAYS  32628 29372 109486 VxService :: StartVacp：vacp已成功启动，processid = 35564

＃〜> （04-29-2019 04:44:28）：   错误  32628 29372 109487进程InMageAgentVacp with pid 35564退出，退出代码为-2147483501。

＃〜> （04-29-2019 04:44:31）：   错误  32628 33468 109488无法更新Azure组件的CS地址，但异常boost :: filesystem :: rename：进程无法访问该文件，因为它正由另一个进程使用："C：\ProgramData \ Microsoft *
Azure Site Recovery \fingerprints / 172.22.18.57_443.fingerprint"，" C：\ProgramData \ Microsoft Azure Site Recovery \fingerprints / 172.22.18.57_443.fingerprint.bak-20190429T084431.556506"

#~> (04-29-2019 04:44:22):  ALWAYS  32628 29372 109483 VxService::StartVacp: vacp successfully started, processid=35352
#~> (04-29-2019 04:44:22):   ERROR  32628 29372 109484 process InMageAgentVacp with pid 35352 exited with exit code -2147483501.
#~> (04-29-2019 04:44:28):  ALWAYS  32628 29372 109485 VxService::StartVacp: forking vacp C:\Program Files (x86)\Microsoft Azure Site Recovery\agent\vacp  -systemlevel -parallel -vtoa  -cc
#~> (04-29-2019 04:44:28):  ALWAYS  32628 29372 109486 VxService::StartVacp: vacp successfully started, processid=35564
#~> (04-29-2019 04:44:28):   ERROR  32628 29372 109487 process InMageAgentVacp with pid 35564 exited with exit code -2147483501.
#~> (04-29-2019 04:44:31):   ERROR  32628 33468 109488 Failed to update CS address for Azure components with exception boost::filesystem::rename: The process cannot access the file because it is being used by another process: "C:\ProgramData\Microsoft Azure Site Recovery\fingerprints/172.22.18.57_443.fingerprint", "C:\ProgramData\Microsoft Azure Site Recovery\fingerprints/172.22.18.57_443.fingerprint.bak-20190429T084431.556506"

如果有人能指出我正确的方向，我将不胜感激。谢谢。

I would appreciate if anyone could point me in the right direction. Thank you.

这篇关于ASR VM复制/更新问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！