Connecting Cloud Innovators: Building Community at .NEXT 2024
Hello Takhagi, It should be fixed, you may want to try to create the sizer scenario again. I am now able to get through the error message now.ThanksBest regardsElroy
Hi, There is a best practice documentation . Hope it helps.https://portal.nutanix.com/page/documents/solutions/details?targetId=BP-2045-Commvault-with-Nutanix:BP-2045-Commvault-with-Nutanix
Hi, Did you try with standalone foundation VM?
Hi, Not sure if this would helphttps://portal.nutanix.com/page/documents/kbs/details?targetId=kA0600000008ZBnCAM However, if you plan to run along without any valid support entitlement, probably I would consider reimage the node at some point if there is not much direction and it needs to bring back up in a timely manner.
Hi, A physical switch would still be needed for a two-nodes-cluster. Potentially it isn’t necessarily spilt the cluster and user VM traffic in this size, a single bridge should suffice the requirement. For the failback, it will follow the same procedure as from a normal clusterhttps://portal.nutanix.com/page/documents/details?targetId=Prism-Element-Data-Protection-Guide-v5_20:wc-protection-domain-failback-disaster.html
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.