5 Essential Tips for Maximizing Your Experience at Nutanix .NEXT for Bloggers
@apiwat_sangYou can definitely do this. At least it works for me on old hardware.Download the AOS tar.gz and put it on a CVM in a directory you create within /home/nutanix. For example, create /home/nutanix/upgrd, put it in there with WinSCP, or scp. Then SSH to the CVM and do:$ cd /home/nutanix/upgrd$ tar xvf nutanix_installer_package-release…..tar.gz$ /home/nutanix/upgrd/install/bin/cluster --ignore_preupgrade_tests -i /home/nutanix/upgrd/install upgrade Edit: this might not be right. let me check and get back to you. I have to find the exact command.
Doing the slow removal and replacing is the safer way.Sure, you can yank a disk and just replace it, but during that process, your data is not resilient. When you pull the disk, the system will alert and begin “healing.” During this time, you are at a higher risk of data loss should another disk or node fail. It may save you time, but there will be hours that go by that you are at an elevated risk, whereas if you do the slow removal and addition, the cluster will always be in a resilient state.
Are you using a single AG for the two sites or is it two AGs within a distributed AG? Also, in my experience, Era does not have a whole lot to offer if you’re not using it to actually deploy. To get always-on with Era, I have multi cluster setup in Era, as well as a multi cluster network profile. Then I deploy an always-on db, and at the screen where it’s asking about the nodes, change the cluster they reside on, with the DR node being async. Then deploy. At that point it will deploy a single AG (which is why i was asking above) spread across the clusters/sites. One thing i also noticed is that you have to have the IP space the same on both sides or it won’t work by default. It will deploy but when you try to failover, it will not work. To work around this, add a second IP to the listener that’s for the other site. It won’t work when using the primary, but when failing over, it will work.I’ve not tried to register an existing always-on SQL deployment, but maybe you will need to have bo
hostssh should be run from the CVM, not from the host. It sounds like doing so would accomplish what you want. cvm$ hostssh command_you_want_to_run
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.
