5 Essential Tips for Maximizing Your Experience at Nutanix .NEXT for Bloggers
Your CVMs can upload log bundles directly to Nutanix for an open case, and this can speed case resolution especially if the alternative is the two-step process of pulling multiple GiB over WiFi to download and THEN upload. With common security restrictions around FTP or SFTP leaving the datacenter this may require explicit firewall rules. The logbay command to collect and upload logs looks like this: logbay collect --dst=sftp://nutanix -c <case_number> That destination “nutanix” isn’t helping us with that firewall rule, so where is the upload going? The software is really just automating the old manual methods described in this KB: Uploading Files for Nutanix Support Using FTP, SFTP or the Customer Portal. Referencing that article, we can see the DNS name for FTP uploads is ftp.nutanix.com . The IP address varies by region and might change, so I’d suggest using the URL. To allow log upload, you’ll need to allow port 22 for SFTP. You could also allow port 21 for FTP, but if it nee
There are many situations when you might need to abort an ongoing disaster recovery replication job on your Nutanix cluster. You may be deleting the protection domain or maybe you added a large VM to an existing protection domain and now you don’t want to include this new VM’s baseline replication in the existing job, at least not before the weekend. Maybe the destination is running short of space and we need to stop adding to the problem. You can see the replication in Prism, but there’s no button to pause or cancel it. To abort the replication we will need to go to the CLI. This process is covered in https://portal.nutanix.com/kb/3272 SSH to a CVM in the cluster as the user ‘nutanix’, then run ‘ncli’ to get into this interactive CLI. First, list current ongoing replications with this command. You’ll need the Protection Domain name and ID from this output for the next command. <ncli> pd ls-repl-status You’ll need the Protection Domain name and ID from this output for th
It’s five-o’clock on Friday and the database admin has just let you know they’re working on a problem and need to keep last week’s Friday afternoon snapshot until further notice. If you do nothing that backup will expire in about an hour due to the protection domain schedule. How can we make sure this snapshot sticks around? Don’t worry! There‘s an NCLI command for this. You can change that snapshot’s expiration time to indefinite, and it will wait around until you delete it manually later. See the solution in the KB article here: https://portal.nutanix.com/kb/8594 First, you need the snapshot ID and the protection domain name. You can get this from the Prism UI, or from NCLI. To capture these details from Prism go to the Data Protection dashboard, Table view, Async DR tab, and select the protection domain from the table here. In the lower panel click on Local Snapshots and find the snapshot with the right Create Time. The number in the ID column is the snapshot ID you need, alo
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.
