5 Essential Tips for Maximizing Your Experience at Nutanix .NEXT for Bloggers
That is pretty much the scenario. Two clusters: cluster A has container Tier1, Tier2, TestDev, Tier1B and Tier2B TestDevB Cluster 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. Here is the resolution per support: [i][b]Clusters also have other containers like:[/b][/i] [i][b]Thing[/b][/i] [i][b]Thingb[/b][/i] [i][b]Other[/b][/i] [i][b]Otherb[/b][/i] [i][b] [/b][/i] [i][b]Metro relationship between clusters for non-b containers.[/b][/i] [i][b] [/b][/i] [i][b] [/b][/i] [i][b]Steps Taken:[/b][/i] [i][b]Because 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] [i][b] [/b][/i] [i][b]To get this working, we had to create a new datastore on both A and B that points to cluster B's TestDe
We worked with support and found that you are not able to vmotion/svmotion VMs that live in a container that has metro availability enabled. Disappointing, but I guess I see the point.
I have an active ticket with Nutanix. I will reply to that ticket and ask for a WebEx
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.