Join us for a virtual Nutanix User Group meeting with Jarian Gibson as he covers Nutanix Cloud Clusters (NC2) on Azure and AWS with Citrix. <\/span><\/p>

Jarian will take a deep dive into NC2 on Azure architecture and Citrix on NC2 on Azure\u00a0that helps you strengthen your business continuity and disaster recovery position. He\u2019ll also provide the latest updates for NC2 on AWS.<\/span><\/p>

Plus, we're\u00a0giving away a Nutanix suitcase to one lucky winner!\u00a0Opt-in when you register\u00a0to be entered to win.\u00a0<\/p>","author":{"id":113632,"url":"\/members\/karlie-beil-113632","name":"Karlie Beil","avatar":"https:\/\/uploads-us-west-2.insided.com\/nutanix-us\/icon\/200x200\/1581aab3-bcf6-49f4-b2fb-3d11e8c010dc.png","userTitle":"Community Manager","rank":{"isBold":false,"isItalic":false,"isUnderline":false,"name":"Community Manager","color":"#0873ba"},"userLevel":4},"type":"Webinar","url":"https:\/\/next.nutanix.com\/events\/global-nug-nc2-on-azure-and-aws-with-citrix-151","image":"https:\/\/uploads-us-west-2.insided.com\/nutanix-us\/attachment\/f9693b5b-436b-427a-9b98-531b4040ff24_thumb.png","location":"","startsAt":1678298400,"endsAt":1678302000,"contentType":"event","attendees":[],"attendeeCount":0,"isLoggedInUserAttendee":false,"createdAt":"1675974969"},"phrases":{"Forum":{"{n} year|{n} years":"{n} year|{n} years","{n} month|{n} months":"{n} month|{n} months","{n} day|{n} days":"{n} day|{n} days","{n} hour|{n} hours":"{n} hour|{n} hours","{n} minute|{n} minutes":"{n} minute|{n} minutes","just":"just now","{plural} ago":"{plural} ago"}}}">

VMware Horizo​​n async DR


徽章 +1
嗨,我们正在运行20个具有AOS 5.0.1和ESXI 6.0的NUTANIX节点,而Hypervisor分裂为2个簇(每个群集10个节点),它们在两个不同的vCenter中运行(Vcenter Server Appliance 6.0.0.0.20100构建编号4632154)和两个不同的位置。所有VM都将成功关闭,并将成功地迁移(未注册在本地vCenter服务器上并在第二个vCenter Server上注册)。认识到VM已从一个vCenter移到另一个vCenter。因此,我们不可能在第二侧连接到此VDI。有人可以帮助我们找到解决这个问题的解决方案吗?

该主题已关闭以供评论

3个答复

UserLevel 6
徽章 +29
Mstauder- 这些持续的台式机吗?非持久桌面?您能多描述您的VDI池设置吗?这将决定解决方案。
徽章 +1
嗨,我们必须到不同的位置。在每个位置,我们都有一个nutanix群集(每个10节点)。我们在VDI基础架构中运行不同的工作负载,因此我们使用链接的克隆桌面,每次登录后将被销毁,并且持久的完整克隆桌面。灾难,我们将在Outlive位置上推出一些更多链接的克隆台式机,因此对于这种情况,不需要采取任何措施。但是对于我们的完整克隆桌面池,我们设置了两个保护域,将每120分钟复制一次VM,地点。两个位置均处于活动状态,因此没有主要位置或次要位置。因此,来自网站A的完整克隆桌面将被复制到站点B,另一方面将重复。我们的地平线基础架构简而.-在每个位置,我们都有一个vCenter服务器设备运行,该设备在VDI用户的登录过程中管理Local Nutanix群集(VMware 6.0),如果连接服务器在vCenter中运行的VM(如果其VM)在vcenter a(a)中获取信息(Site A) or vCenter b (Site and will redirect the session to the correct Site.When we will migrate the VMs from Site A to Site B, Prism will shutdown the VMs, will do a last sync, unregister the VM from the ESXi Host and register the VM on an ESXi Server at Site B. So this step is working well, the only Feature we miss, is that all migrated VMs are in the Power State "off". It will be nice if the Power State at the time of the recovery will be recovered.For our Scenario it will not be necessary that the VMs will be powered on automatically because normally the connection server will power on the VMs by itself, if they are powered off. But in our case the connection server did not recognize, that the VM from Site A with vCenter A was moved to Site B with vCenter B, so the Power On action will be send to the wrong vCenter, we see that from the VMware ESXi Task and Event Logs. This Task will be send every few seconds to the "old" vCenter until the VM was powered on manually and the Desktop Agent within the VM will send a "up and running" Status to the connection Server. From now on the User can login to his VM, but only if the vCenter from Site A and all ESXi Host from Site A will be available and all migrated VMs will be listed as orphaned.The connection server still things the VM is located within Site A, but in case that the Desktop Agent is alive, the connection will directly redirected to the VM.But from the moment we delete the orphaned VMs within vCenter A, or we shutdown the vCenter and all Hosts within Site A to simulate a complete outage from Site A, there is no connection to the VDI Desktop VM possible.I fact, we have successfully migrated all VMs without any data lose from Site A to Site B, or in case of a disaster with a maximum delta of 120 minutes to the other side, but we are not able to use the migrated Desktop VDI VMs.I hope this will help you to understand my situation.If you have any further questions, please feel free to ask.ThanksMarkus
徽章 +5
我认为,您唯一能够使用迁移的VM的方法就是在博士侧创建一个新的手动池并手动将恢复的VM添加到其中。



我们也有类似的要求(2个站点,活动/活动),但是我们使用Metroavailablity,而不是使用异步。这意味着,当我们有2个单独的NTNX群集时,我们有一个vSphere群集,因此视图不知道VM的任何网站都没有问题...显然,这还有一些其他开销(您需要一个好的WAN链接,我们的纤维在〜1.5毫秒的延迟下都有深色纤维),使管理VM的管理更加困难(您不能如果所有主机看不到,则在非米特罗数据存储上链接的克隆作为视图将不会显示数据存储。但是对我们来说,总体解决方案效果很好。
Learn more about our cookies.<\/a>","cookiepolicy.button":"Accept cookies","cookiepolicy.button.deny":"Deny all","cookiepolicy.link":"Cookie settings","cookiepolicy.modal.title":"Cookie settings","cookiepolicy.modal.content":"We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.<\/a>","cookiepolicy.modal.level1":"Basic
Functional","cookiepolicy.modal.level2":"Normal
Functional + analytics","cookiepolicy.modal.level3":"Complete
Functional + analytics + social media + embedded videos"}}}">
Baidu