Azure Site Recovery 复制 - 无法选择现有目标密钥保管库进行磁盘加密

发布于 2025-01-11 17:09:24 字数 668 浏览 0 评论 0原文

我正在尝试为 ADE 加密的 Azure VM(Windows Server 2019 Datacenter)设置 ASR 复制(Azure 到 Azure),引用 MS 文档:https://learn.microsoft.com/en-us/azure/site-recovery/azure-to-azure-how-to-enable-replication-ade-vms

根据文档,我们可以自定义“目标磁盘加密密钥保管库”,但目标资源组中的现有密钥保管库未填充在可供选择的列表中。我已验证我对目标 keyvault 的访问权限,如文档中所述。

自定义目标密钥保管库

我可以自定义其他目标,例如资源组、vnet、缓存存储帐户可用性集;问题似乎仅与密钥库有关。

查看复制目标

I am trying to setup ASR replication (Azure to Azure) for ADE encrypted Azure VM (Windows Server 2019 Datacenter) referencing MS documentation: https://learn.microsoft.com/en-us/azure/site-recovery/azure-to-azure-how-to-enable-replication-ade-vms

As per the documentation we can customize "Target disk encryption key vault" but the existing key vault in the target resource group is not populating in the list to select. I have verified my access on the target keyvault as mentioned in the documentation.

customize target key vault

I am able to customize other targets like resource group, vnet, cache storage account availability set; issue seems with the key vault only.

review targets for replication

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

娇女薄笑 2025-01-18 17:09:25

目标位置是源虚拟机数据所在的位置
复制。 Site Recovery 提供了合适目标区域的列表
基于所选机器的位置。我们建议您使用
与恢复服务保管库位置相同的位置

按照@piotr.gradzinksi的建议,确保 Key Vault 与您的目标位于同一区域。

尝试复制源区域上具有 Key Vault 的虚拟机。

确保您拥有源区域密钥保管库的所有权限

我通过遵循您提到的同一文档得到结果。

这可能是因为您创建的虚拟机与 Key Vault 位于不同资源组区域中。如果仍然遇到相同的问题,我建议您按照相同的文档来确认您的资源组位于哪个区域。

The target location is where your source virtual machine data will be
replicated. Site Recovery provides a list of suitable target regions
based on the selected machine's location. We recommend that you use
the same location as the Recovery Services vault's location

As suggested by @piotr.gradzinksi make sure to have Key Vault in the same region as your target.

Try to replicate a virtual machine that has key vault on a source region.

Ensure you have all the permissions on the source region key vault.

I’m getting the results by following the same document that you have mentioned.

This may be the issue with virtual machine which you are creating is in different resource group region compared to key vault. If still getting the same issue I would suggest you follow the same document to confirm which region your resource group is in.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文