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"}}}">

无法在簇之间进行SVMotion

C
徽章 +2
我们是Nutanix的新手。我们在单独的数据中心中有两个分开的群集。我们的目标是能够根据需求和资源在集群之间移动工作负载。

我们正在使用VMware 5.5，除了从群集到群集移动外，一切似乎都按计划使用。

我们拥有集群A和集群B。我们正在使用Metro可用性来同步群集A到集群B的数据，这似乎可以正常工作。

当我尝试执行从群集A到集群B的冷迁移时，我会收到以下错误：重新安排虚拟MachineArteMiscloneFile/vmfs/vmfs/columes/ec936530-956aa-9ac/artemisclone/artemisclone.-VMDK。

从集群B到群集A的冷迁移正常。白名单在两个集群上都是相同的。

VMware并没有太大的帮助，因为他们的答复就是浏览数据存储，然后将其添加到群集B中的服务器上的库存中

    \nWe are using VMware 5.5 and everything seems to work as planned with the exception of the moving from cluster to cluster.

    \nWe have cluster A and cluster B. We are using metro availability to sync the data from cluster A to cluster B at this time and that seems to work correctly.

    \nWhen I attempt to perform a cold migration from cluster A to cluster B I get the following error:Relocate virtual machineArtemisCloneFile\/vmfs\/volumes\/ec936530-956aa-9ac\/ArtemisClone\/ArtemisClone.-vmdk was not found

    \ncold migration from cluster B to cluster A works fine. the whitelists are identical on both clusters.

    \nVMWare isn't really much help as their reply is to just browse the datastore and add it to inventory on a server in cluster B","quoteUsername":"cgbullock","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    该主题已关闭以供评论

    7个答复

    乔恩
    秩
    UserLevel 6
    徽章 +29
    您可以在portal.nutanix.com上提交支持票，以便我们可以跳上Webex并与您锤击吗？



    谢谢，

    乔恩
    乔恩·科勒（Jon Kohler）|Nutanix工程技术总监|Nutanix NPX＃003，VCDX＃116 |@jonkohler |如果有用的话，请荣誉！

    \n

    \nThanks,

    \nJon","quoteUsername":"Jon","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    CBROWN
    秩
    UserLevel 3
    徽章 +15
    欢迎来到Nutanix！



    我强烈建议打开一个Nutanix支持案例进行调查 - 这里有很多变量，可以通过电话进行哈希更容易。







    （有或没有案例）将有帮助的一些信息：


    1. 您是否正在尝试在地铁容器中进行SVMotion？
    2. 您有一个比1个地铁容器更多吗？
    3. 地铁关系是活跃还是脱钩？
    4. 如果活动，哪个站点处于活动状态？
    5. 网站之间的延迟是什么？
    6. 只是失败的冷迁移吗？
    7. 如果您只做VMotion，它会失败吗？


    基本上，这些问题的目标是解开问题，并找到进一步解决问题的确切分解。一旦缩小，支持将能够挖掘出适当的日志，并弄清楚从那里去哪里。

    \n

    \nI would highly recommend opening a Nutanix Support case to investigate - there's a ton of variables here that would be much easier to hash out over the phone.

    \n

    \n

    \n

    \nSome information that will be helpful to have (with or without a case):

    \n

      \n
    1. Are the VMs you're trying to svmotion in the metro container?
      \n
    2. Do you have more then 1 metro container?
      \n
    3. Is the metro relationship active or decoupled?
      \n
    4. If active, which site is active?
      \n
    5. What is the latency between sites?
      \n
    6. Is it only cold migration that fails?
      \n
    7. Does it fail if you only do a vMotion?<\/ol>

      \nBasically the goal with these questions is to untangle the problem and find what exactly is breaking down to troubleshoot that further. Once narrowed down, Support will be able to dig into the approprate logs and figure out where to go from there.","quoteUsername":"cbrown","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    C
    徽章 +2
    我有一张带有Nutanix的积极票。我将回复该票，并要求使用Webex
    C
    徽章 +2
    我们与支持合作，发现您无法使用启用Metro可用性的容器中的VMOTION/SVMOTION VM。令人失望，但我想我明白了。
    乔恩
    秩
    UserLevel 6
    徽章 +29
    嘿，您是说您有两个簇，有一个拉伸的容器，而在那里不允许使用VMOTINE的VM？



    如果是这样，那是不正确的，您可以绝对可以vMotion和SVMotion进出地铁容器，我会亲自亲自进行。



    也就是说，我绝对相信您有某种问题，而我唯一能想到的是，我的头顶是，如果您有两个簇，则每个群集都有一个容器名称，并且正在尝试在它们和地铁之间进行vmotion / svmotion不是实际启用或以其他方式不起作用。



    发生这种情况（不启用的集装箱名称和地铁冲突）时，ESX会对其拉动和将文件推向何处并给出类似的错误感到困惑。
    乔恩·科勒（Jon Kohler）|Nutanix工程技术总监|Nutanix NPX＃003，VCDX＃116 |@jonkohler |如果有用的话，请荣誉！

    \n

    \nIf so, that is incorrect, you can absolutely vMotion and svMotion in and out of metro containers, I've done it myself first hand.

    \n

    \nThat said, I definitely believe you're having some sort of issues, and the only thing I could think of, off the top of my head, is if you had two clusters, in the same vCenter, each with a container with the same name, and are trying to vMotion \/ svMotion in between them and metro is either not<\/b><\/i> actually enabled or otherwise not working.

    \n

    \nWhen that happens (conflicting container names and metro not being enabled), ESX gets confused about where its pulling and pushing files to, and gives errors like these.","quoteUsername":"Jon","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    C
    徽章 +2
    这几乎就是场景。

    两个簇：群集A具有容器tier1，tier2，testDev，tier1b和tier2b testdevb

    群集B具有完全相同的命名容器，我们需要在安装过程中被告知，以便以Metro供应工作。在集群B上的Tier1上的Tier1上的TIER1，群集B上的TIER2，群集A Metros上的TIER2到TIER2 CLUSTERB。et塞德拉。





    这是每个支持的分辨率：

    群集也有其他容器，例如：

    事物

    thingb

    其他

    其他b



    非B容器集群之间的Metro关系。





    采取的步骤：

    由于“ B”容器不是通过Metro同步的，因此集群A正在尝试将数据写入其testDevb，并且群集S不看到它，因此丢弃了错误。



    为了实现此功能，我们必须在A和B上创建一个新的数据存储，该数据存储通过集群A的VIP指出B群B的TestDevb容器。现在，存储VMOTION正在起作用（尽管已知的Nutanix上的SVMotion问题缓慢）。

    \nTwo clusters: cluster A has container Tier1, Tier2, TestDev, Tier1B and Tier2B TestDevB

    \nCluster B has the exact same named containers, which we were told during install was required in order for metro availability to work. Tier1 on cluster A metros over to Tier1 on Cluster B, Tier2 on cluster A metros over to Tier2 ClusterB. et cedera.

    \n

    \n

    \nHere is the resolution per support:

    \nClusters also have other containers like:<\/b><\/i>

    \nThing<\/b><\/i>

    \nThingb<\/b><\/i>

    \nOther<\/b><\/i>

    \nOtherb<\/b><\/i>

    \n <\/b><\/i>

    \nMetro relationship between clusters for non-b containers.<\/b><\/i>

    \n <\/b><\/i>

    \n <\/b><\/i>

    \nSteps Taken:<\/b><\/i>

    \nBecause the \"b\" containers are not sync'd via metro, cluster A is trying to write the data to its TestDevb and cluster S does not see it, thus throwing the error.<\/b><\/i>

    \n <\/b><\/i>

    \nTo get this working, we had to create a new datastore on both A and B that points to cluster B's TestDevb container via cluster A's VIP. Now the storage vMotion is working (albeit slowly due to known issues with svMotion on Nutanix).<\/b><\/i>","quoteUsername":"cgbullock","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    乔恩
    秩
    UserLevel 6
    徽章 +29
    啊！好的，我们现在在同一页面上。一旦获得所有人的东西，双方都将100％提高，您应该能够像想象的那样使用东西。
    乔恩·科勒（Jon Kohler）|Nutanix工程技术总监|Nutanix NPX＃003，VCDX＃116 |@jonkohler |如果有用的话，请荣誉！
    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