5 Essential Tips for Maximizing Your Experience at Nutanix .NEXT for Bloggers
I opened a thread a month ago about Cloud Connect S3 consumption and when checking on it today I found that it was closed to comments.https://next.nutanix.com/nutanix-disaster-recovery-29/aws-cloud-connect-s3-consumption-issue-41499?postid=63137#post63137There was no explanation for this action in the thread or via PM to me. Can someone let me know why this was done?
We bought several Nutanix clusters in 2019 and on two of them, we deployed a cloud connect appliance in AWS via Prism element so that we could backup our VMs to the cloud. We setup retention to 7 snaps locally and 62 on the remote (AWS) side. The question I have for everyone that uses Cloud Connect for backups is, does the S3 bucket that gets created by Cloud Connect ever stop growing in size. On our HQ Nutanix cluster, that Cloud Connect S3 bucket is currently sitting at 164TB and 177 million objects. This is a small 3 node cluster with only 10 VMs being backed up to the Cloud Connect appliance. Current allocated space for those VMs is 3TB. Actual consumed by them as reported by Prism is about half of that. Looking at the S3 bucket created by cloud connect, I see that a lifecycle rule was created to move objects to infrequent access after 30 days. I see nothing to expire old objects and there are objects in the bucket dating all the way back to 2019. So at first glance, it doesn’t loo
The upgrade process for the VCSA from a major release to another is as follows:A new VCSA with a temp IP is created in the vSphere host/cluster by the upgrade process. The upgrade process migrates the config/data from the old VCSA to the new one. The Old VCSA is shutdown and the new VCSA is renamed/re-ip with the values of the old VCSA. New VCSA is then rebooted.At this point the new VCSA should have the old VCSA name and IP address. My question for those that have done this already is, how does the Nutanix cluster Prism element reacts to this in regards to its vcenter registration? Will all this be transparent to it or will it see the new VCSA as a new device and create a duplicate entry? I assume the migration process will copy SSH keys and certs from the old VCSA to the new one so Prism won’t bat an eye, but I just wanted to confirm.
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.
