A 5-node Replication Factor 3 Nutanix cluster is hosting a Files instance, which archive images generated by a Picture archiving and communication system.
The cluster is running out of space and the administrator needs to find a viable solution to address the issue.
Which option could solve the problem?
Enabling compression at the share level can help optimize storage space utilization by reducing the size of the stored data. This can be particularly effective for image files, which are often highly compressible. Compression helps in maximizing the available storage without the need for additional nodes or complex configurations.
Something is wrong with this question because: A - cannot be because once you enabled RF3 you cannot go back to RF2 C - cannot be because it is saying 5 node rf3 . to enable erasure coding you need 6 nodes as per links below https://portal.nutanix.com/page/documents/details?targetId=Web-Console-Guide-Prism-v6_8:wc-erasure-coding-overview-wc-c.html https://portal.nutanix.com/page/documents/details?targetId=Prism-Central-Guide-vpc_2023_4:wc-erasure-coding-best-practices-requirements-wc-c.html D - you cannot just delete VMs So we remain with B .. and maybe is referring cu post compression (which again is not clearly stated) But most probably there is something wrong with the question.
Your remark about A is wrong, KB-4853 clear states how to reverse from RF3 to RF2 on storage containers. A is the correct one https://portal.nutanix.com/page/documents/kbs/details?targetId=kA00e000000XeHLCA0
C. Enable Erasure Coding at storage container level. Erasure coding is a data protection method that can help optimize storage space utilization by providing redundancy and fault tolerance with less overhead compared to traditional replication. By enabling erasure coding at the storage container level, you can reduce the storage overhead required for redundancy while still ensuring data integrity and availability.
But it needs 6 nodes we have only 5
Your general statement is true, however the question clearly states there are only 5 nodes and RF3 is the configured replication factor, therefore answer option letter C must be ruled out, per standard process of elimination.
Nutanix KB 000004853
After checking carefully, yes the relevant correct answer is B. Because of RF3 with erasure coding requires six nodes. < Erasure coding is supported on clusters with a minimum of 4 nodes when using RF2 and a minimum of 6 nodes when using RF3.>
A - KB-4853 clear states how to reverse from RF3 to RF2 on storage containers. That's the correct one. B- applying compression is not recommended on compressed datasets such as images C- EC-X can't be applied on a 5-node cluster with Rf3 D- Not Applicable if you don't have any VM to delete https://portal.nutanix.com/page/documents/kbs/details?targetId=kA00e000000XeHLCA0
Reverting to RF2 is not possible because Nutanix Files requires RF3 for high availability and data protection. Additionally, enabling Erasure Coding at RF3 requires a minimum of six nodes, whereas the cluster has only five. A viable solution would be to enable compression at the share level, as this can help optimize storage utilization without requiring additional nodes
C is correct. Erasure Coding requires a minimum of four nodes not six nodes.
Min of four nodes is required for RF2, min of 6 nodes required for RF3. Check the documentation on Erase Coding, this is explained/defined very clearly in the data efficiency solutions documentation.
This question is bad: https://portal.nutanix.com/page/documents/solutions/details?targetId=TN-2032-Data-Efficiency:compression.html "We recommend compression for almost all use cases except the following workloads: Encrypted datasets Compressed datasets (images, audio, and video)"
I found researching all four answer options very interesting & educational. I ruled out answer B for two reasons, based on my research, one of which you identified in your comment. The correct answer in this scenario is A. (Reference Nutanix KB article 000004853 and you'll see that the question is both 'good' and highly relevant information for the average Nutanix SysAd, as space issues are a very common issue when Nutanix Files is involved.
'CONTAINER' is specified, not cluster, answer A is correct in this specific scenario. Evaluate this DIRECT quote copied from Nutanix KB article 000004853, due to its relevance for question 77. "This KB article describes how to change an RF3 container to an RF2 container to reduce the replication factor and reclaim the physical storage space. Note that this KB discusses the method to change the replication factor of the storage container and not the 'cluster' RF, which remains as RF3 (FT=2)."