Recently active topics

Does anyone know if there are any valid exam vouchers currently available for an NCP MCI 7.5 exam?I'm looking for a voucher that can be used. Any information on available vouchers, discounts, academic offers, or promotional codes would be appreciated.Thanks!

From Business RTO/RPO to Nutanix DR Architecture: Where Should the Design Really Start? Should we start designing Disaster Recovery by choosing a replication technology, or by understanding what the business actually needs to recover?In enterprise DR architecture, achieving a technical replication objective does not automatically mean achieving business continuity.A successful DR design must translate business recovery requirements into appropriate protection strategies, recovery orchestration, infrastructure capacity, and validated application recovery procedures.Let's consider a simplified, fictional enterprise scenario.The Business ScenarioAn organization has three critical workload groups with different recovery objectives:Workload Required RPO Required RTO Core Banking 0 minutes 15 minutes ERP 15 minutes 2 hours Internal HR 4 hours 8 hours These values are hypothetical business requirements, not guaranteed Nutanix recovery performance.Although all three workloa

I am not able to test drive any more. What has happened to my account? Will someone fix this?

 100% of your VMs are back online. But your customers still cannot complete a single transaction. How is that possible?Imagine a Disaster Recovery test where:✅ All protected VMs are successfully recovered.✅ Nutanix Recovery Plan execution completes successfully.✅ The infrastructure dashboard reports healthy VMs.❌ The business application remains unavailable. The infrastructure recovered. The business service did not.This is a challenge that goes beyond replication technology and VM boot sequencing.It raises a fundamental architecture question: Did we design the recovery process around virtual machines or around business service dependencies? 1. The Scenario: Mobile Banking on Nutanix AHV Consider a fictional banking environment with a Mobile Banking application consisting of: Identity and DNS Services Database Tier Middleware and API Services Application Servers Load Balancers External Payment and Authentication Integrations During DR failover, the application VMs are started

 Hello Nutanix Community,I'm trying to expand an existing 3-node Nutanix cluster by adding a fourth node, but the expansion process fails during the pre-expansion checks with the following error:Failure in pre expand-cluster tests.Errors:Precheck: test_cassandra_ssd_size_check failed.SSD tier on nodes ['172.22.129.4'] is not sized to accommodate expected metadata growth on cluster.Refer KB-8842 for more details.Environment Details: Platform: Cisco UCS C240 M7 AOS Version: 7.0 Storage Type: Hybrid Existing Cluster: 3 Nodes New Node: 1 Node (4th node) Additional Information: The new node has the same SSD and HDD configuration as the existing nodes. The SSD capacity on the affected node (172.22.129.4) is identical to the other cluster nodes. The issue occurs during the pre-expansion validation stage. My Questions: What could cause this error if all nodes have identical SSD configurations and capacities? What troubleshooting steps would you recommend to identify the root caus

We do scheduled restarts on VM’s monthly. We have several hundred VM’s.I want to be able to reboot a group of servers at say 9am, then another group of servers at 9:15am. I feel the easiest way would be to tie group 1 to a category (MaintGroup1), and group 2 to a separate category (MaintGroup2), then utilize Intelligent Operations to run the VM Reboot actions on the categories at the specified times.My primary issue is that I don’t see a way to assign the operation to a category. It gives me the list of all my VM’s, but again, with hundreds of VM’s it would be very time consuming to add them all to the reboot operation individually.Is there a way to do this besides manually adding each one?

Hi I recently added a second CPU and expanded the memory in each node of a two-site Nutanix AHV environment running Metro Availability. Each site has its own three-node cluster and Prism Central instance.The CPU upgrade increased each node from 16 to 32 physical cores, so each cluster went from 48 to 96 cores. The customer purchased additional NCI Pro and Advanced Replication licenses to cover the extra 48 cores per cluster.After the physical upgrade I followed the manual licensing workflow: Exported the Cluster Summary File (CSF) from Prism Central Uploaded it to the Nutanix Support Portal under Licensing → Manage Licenses and selected the new licenses Downloaded the generated License Summary File (LSF) and uploaded it back to the same Prism Central instance I repeated the same process for both Prism Central but they still report the clusters as out of compliance, with 96 physical cores detected and 48 licensed on each cluster.Notice that when checking the portal licensing final s

Buenas a tod@s, Aquí os dejo algunos links interesantes que hemos trabajado durante unos meses.  Los artículos están en Español, se entienden bien. ;-) 1. Building hybrid environments with Nutanix Cloud Clusters (NC2) on AWShttps://aws.amazon.com/es/blogs/aws-spanish/creando-entornos-hibridos-con-nutanix-cloud-clusters-nc2-sobre-aws/ 2. Moving workloads to AWS without refactoring using Nutanix NC2https://aws.amazon.com/es/blogs/aws-spanish/como-mover-cargas-de-trabajo-a-aws-sin-refactorizar-con-nutanix-nc2/ 3. Managing a hybrid Kubernetes fleet with NKP and Amazon EKS (Part 1)https://aws.amazon.com/es/blogs/aws-spanish/gestionar-una-flota-hibrida-con-nutanix-kubernetes-platform-y-amazon-eks-parte-1/ 4. Managing a hybrid Kubernetes fleet with NKP and Amazon EKS (Part 2)https://aws.amazon.com/es/blogs/aws-spanish/gestionar-una-flota-hibrida-con-nutanix-kubernetes-platform-y-amazon-eks-parte-2/

En este video, con Andrés Rey tienes la oportunidad de profundizar en Nutanix Cloud Clusters (NC2) a través de una demo breve en la que puedes ver cómo llevar la experiencia de #Nutanix a entornos cloud públicos como AWS y Azure.🎥https://lnkd.in/egE55WBa

公式ドキュメントを見ても見つからなかったので、教えていただきたいのですが2ノードクラスタ＋Witnessで構築する予定でいます。シングルノードクラスタ上にWitness VMを設けるつもりでいるのですが、Witness VMはVM単位のライセンスが必要となりますでしょうか？下記に該当するか否かが見つかりませんでしたので、見識のある方がいらっしゃったらご教示いただけると助かります。ライセンス: NCI-Edge Starter（VM単位）を想定。CVM/PCVM/FSVMはライセンス不要の記載ありhttps://www.nutanix.com/ja/products/cloud-platform/software-options 宜しくお願い致します。

Hello Nutanix Community,I am currently evaluating a Nutanix Two-Node Cluster deployment for a small environment and have been reviewing the official documentation, including the Prism Web Console Guide and the Data Protection Guide.Unfortunately, I have not been able to obtain clear technical guidance regarding Two-Node Cluster deployments from my local Nutanix sales representatives and SE teams in Japan and Singapore. As a result, I am trying to better understand the official requirements and supported deployment models directly from the community and Nutanix experts.I would appreciate clarification on the following topics:1. Witness VM deployment requirementsIs a dedicated physical host required for the Witness VM when no remote datacenter is available? If the Witness is deployed in the same site, what conditions must be met to satisfy the "separate failure domain" requirement? Is a separate rack, power circuit, UPS, and network path sufficient?2. Supported Witness hosting platformsT

Hi Nutanix Team,We are planning to run Windows/Linux VMs on Nutanix AHV with the following environment: Cisco UCS X210C M8 Nutanix AHV Dell PowerMax 2500 25GbE network Can a Windows/Linux Guest OS running on AHV use its native iSCSI initiator to directly access an external Dell PowerMax storage LUN?The architecture is:Guest OS → iSCSI Initiator → AHV/OVS → 25GbE → Dell PowerMaxIf yes, is this officially supported by Nutanix? Could you please provide the relevant documentation?Thank you.

Phase 1: Foundation Orchestration & Pre-Imaging Preparation1. Foundation Session InitializationFoundation does not immediately image the server. It first creates and activates its internal imaging workflow.Foundation associates the imaging workflow with a NodeConfig object representing the target CVM and spins up local CherryPy/Flask microservices on your laptop or deployment machine to handle the imaging tasks.2. Node DiscoveryFoundation attempts to locate the physical nodes. It broadcasts over the local Layer 2 network segment using IPv6 link-local multicast (via the WS-Discovery protocol). It listens for replies from factory-fresh nodes or unconfigured hardware listening on the network.Foundation is using its internal RPC mechanism to resolve information from the node before applying the final configuration.3. Network Provisioning & VerificationFoundation begins constructing the network configuration that will ultimately be applied to the target environment. It subsequently

We operate a hybrid VDI environment: Windows 10 on vSphere and Windows 11 on Nutanix AHV(Horizon 2603/2606).While vSphere works flawlessly, we face two critical blockers on Nutanix AHV that force inefficient manual workarounds.We request feature parity with vSphere. Issue 1: Manual Pool Registration LimitProblem: When deploying VMs from a master image with Horizon Agent pre-installed, only one VM successfully registers in a Manual Desktop Pool on Nutanix AHV.Current Workaround: To register multiple VMs, we must exclude the Horizon Agent from the master image and install it individually on every single VM after provisioning.Expectation: Nutanix AHV should support standard golden image deployment (Agent pre-installed) allowing multiple VMs to register simultaneously, just like vSphere. Issue 2: Persistent Black Console After DisconnectProblem: After a user disconnects a session, the VM's console screen remains Black. Administrators can not view the desktop state or perform maintenance vi

What’s a vTPM?The vTPM module is the virtual equivalent of a physical TPM chip. It securely stores cryptographic keys used for BitLocker drive encryption, Windows Secure Boot, measured boot, and attestation features. Each vTPM holds unique cryptographic material, and without those keys, a VM may not be able to decrypt its disks or boot securely.Why Does Protection Domain (PD)-Based DR Fail with vTPM VMs?Legacy Protection Domains were built before vTPM was introduced, so PDs replicate only VM disks and metadata, not the vTPM device or its secure state. vTPM keys are encrypted and tied to the local cluster’s KMS. During PD-based replication, those keys cannot be transferred to the DR site. As a result, a vTPM-enabled VM may fail to boot or lose access to encrypted volumes after DR failover.Why Does Protection Policy (PP)-Based DR Support vTPM VMs?Modern Protection Policy-based DR introduces full vTPM awareness. It replicates vTPM state and keys alongside VM data. It integrates with Nutan

While enabling the Microservices Infrastructure (CMSP) on Nutanix Prism Central, the deployment failed during the post-deployment prechecks with an error indicating that Prism Central was not compatible with enabling Microservices Infrastructure.* Root Cause Analysis:When CMSP is enabled, Prism Central deploys an internal Kubernetes-based platform to host Nutanix microservices. For CMSP deployment on Prism Central, the internal CMSP services use the following default networks: 192.168.5.0/24 – Kubernetes infrastructure network 10.100.0.0/16 – Kubernetes Pod network 10.200.32.0/24 – Kubernetes Services network The upstream network environment must not overlap with these network ranges. Since Kubernetes cannot differentiate between internal container traffic and the production management network, CMSP prechecks intentionally block the deployment to prevent potential routing conflicts.* Solution:If the environment requires using these subnet ranges in the upstream network, you must cha

Register for a Live Webinar on Nov 17th at 11am PT / 2pm ET via https://virtualizationreview.com/webcasts/2026/11/nutanix-database-security-in-the-age-of-ai.aspx AI is changing the security equation. Threats are becoming more frequent and more severe, as tools such as Mythos surface vulnerabilities that attackers can exploit. Yet many organizations still rely on manual database patching processes that leave known gaps open—even when fixes are available. The consequences are significant: 60% of data breaches are attributed to known vulnerabilities*, with average costs of $4.8 million globally and $10.2 million in the United States**.In this webinar, database experts from Alinma Bank, one of the largest and fastest growing banks in Saudi Arabia and top 10 largest bank in the Middle East, and Nutanix will discuss the practical realities of securing database environments. They will explain how NDB helps teams move beyond manual, one-instance-at-a-time processes with centralized lifecycle m

Here is a link to a recent NDB upgrade steps - super easy but more importantly none disruptive and zero impact to users or business! https://justaserverengineer.blogspot.com/2026/10/ndb-upgrade-how-easy-can-it-be.html

When I hear the words clean room, my mind goes straight to Dexter — the TV show about a forensic blood spatter analyst who moonlights as a vigilante. His clean room is meticulous: sealed in plastic, no trace evidence, no contamination, nothing gets in or out. In some ways, it makes perfect sense as a metaphor. Dexter was in the business of containing and eliminating threats — and in the IT world, so are we. We are just going after ransomware actors instead of murderers. The plastic sheeting is a little different, but the principle is the same: isolate the threat completely before you do the work. Ransomware recovery used to mean one thing: restore from backup and hope for the best. That approach has a serious flaw — if your recovery environment connects to the same infected infrastructure you are restoring from, you risk reinfecting your clean data before you ever flip a switch. The answer is not faster backups. It is a clean room: an isolated, air-gapped environment where you can vali

What actually happens?Traditional backups copy entire files or virtual disks, which takes time and slows down your system. Nutanix uses a Redirect-on-Write (RoW) architecture combined with instantaneous metadata pointers.1️⃣ 𝘛𝘩𝘦 𝘗𝘰𝘪𝘯𝘵𝘦𝘳𝘴 𝘍𝘳𝘦𝘦𝘻𝘪𝘯𝘨 (𝘐𝘯𝘴𝘵𝘢𝘯𝘵):- Instead of copying your data blocks, Nutanix copies the metadata map (the index or map that tells the system where your data blocks live on the physical disks).* The Process: The system takes a snapshot of this map, which takes milliseconds because metadata is incredibly small.* The Result: The original data blocks become read-only for that specific point in time.2️⃣ 𝘛𝘩𝘦 𝘙𝘦𝘥𝘪𝘳𝘦𝘤𝘵-𝘰𝘯-𝘞𝘳𝘪𝘵𝘦 𝘔𝘦𝘤𝘩𝘢𝘯𝘪𝘴𝘮 (𝘕𝘰 𝘖𝘷𝘦𝘳𝘩𝘦𝘢𝘥):- The moment after the recovery point is created, your Virtual Machine (VM) keeps running and writing new data.* Old Data: Stays exactly where it was, safely frozen as your recovery point.* New Data: Instead of overwriting old data, any new changes are written t

What actually happens?Traditional backups copy entire files or virtual disks, which takes time and slows down your system. Nutanix uses a Redirect-on-Write (RoW) architecture combined with instantaneous metadata pointers.1️⃣ 𝘛𝘩𝘦 𝘗𝘰𝘪𝘯𝘵𝘦𝘳𝘴 𝘍𝘳𝘦𝘦𝘻𝘪𝘯𝘨 (𝘐𝘯𝘴𝘵𝘢𝘯𝘵):- Instead of copying your data blocks, Nutanix copies the metadata map (the index or map that tells the system where your data blocks live on the physical disks).* The Process: The system takes a snapshot of this map, which takes milliseconds because metadata is incredibly small.* The Result: The original data blocks become read-only for that specific point in time.2️⃣ 𝘛𝘩𝘦 𝘙𝘦𝘥𝘪𝘳𝘦𝘤𝘵-𝘰𝘯-𝘞𝘳𝘪𝘵𝘦 𝘔𝘦𝘤𝘩𝘢𝘯𝘪𝘴𝘮 (𝘕𝘰 𝘖𝘷𝘦𝘳𝘩𝘦𝘢𝘥):- The moment after the recovery point is created, your Virtual Machine (VM) keeps running and writing new data.* Old Data: Stays exactly where it was, safely frozen as your recovery point.* New Data: Instead of overwriting old data, any new changes are written t

The deployment of AHV/AOS through Phoenix ISO on a Hyper-V host failed before the actual imaging process could begin. During the Hyper-V customization stage, Phoenix terminated as it cannot find the required FAT32 partition. The deployment therefore stopped before Phoenix could continue with the normal AHV/AOS installation workflow.💡 𝗥𝗼𝗼𝘁 𝗖𝗮𝘂𝘀𝗲 𝗔𝗻𝗮𝗹𝘆𝘀𝗶𝘀:- The underlying issue was related to the existing storage/partition metadata on the Hyper-V host.- Phoenix's Hyper-V customization logic was evaluating the existing disk layout and detecting the disk as having a previous partition structure.- The customize_hyperv.py script specifically flags sdo as your host boot disk. It triggers a function called Mounting Hyper-V FAT32 partition to search for a pre-existing staging partition.- Because /dev/sdo only contains standard Windows OS layout partitions (with an EFI system partition of only 99MB), it fails the hardcoded check for a size >= 1GB and triggers the FATAL halt.

LOCAL BACKUP AND FILE RESTORE USING NUTANIX SNAPSHOTS=====================================================Platform: Nutanix Prism ElementGuest OS: Microsoft Windows ServerProtection Method: Local application-consistent snapshotsRestore Method: Nutanix Self Service Restore (SSR)1. END-TO-END WORKFLOW----------------------Start  |  vLog in to Nutanix Prism Element  |  vSelect the Windows VM  |  vVerify Nutanix Guest Tools (NGT)  |  vEnable Self Service Restore (SSR)  |  vEnable VSS / Application-Consistent Snapshots  |  vCreate an Async DR Protection Domain  |  vAdd Windows VM to a Consistency Group  |  vEnable Application-Consistent Snapshots  |  vCreate Local Snapshot Schedule  |  vConfigure Snapshot Retention  |  vCreate Test Folder and Test File in Windows VM  |  vTake a Manual Application-Consistent Snapshot  |  vRecord the Snapshot ID  |  vDelete the Test Folder to Simulate File Loss  |  vOpen Nutanix SSR Portal on the Windows VM  |  vSelect the Required Snapshot  |  vMount Disk 0