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.
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.