An administrator has a VM that consumes large amounts of storage and has the following characteristics:
✑ Create large / sequential writes
✑ Data must be kept for years
✑ Data is normally only accessed at the end of the year to run report
The administrator decides to use Erasure Coding to save space.
Which feature should the administrator utilize to save space for this VM?
Given the characteristics of the VM that performs large sequential writes and requires data to be kept for years, leveraging a feature that optimizes storage efficiency is crucial. Inline Compression is ideal, as it compresses data in real-time during write operations without any discernible performance hit, effectively saving space immediately. Additionally, it works well with large sequential writes which fits the characteristics of the described VM. While Post-Process Compression can also save space, it doesn't offer the same immediate space-saving benefits during data writes and is more suited for 'cold' data introduced after the fact.
A. Inline Compression is enabled by default, administrator does not need to do anything D. For cold data (no read/write for 3 days). As data cools, LZ4HC further compresses it to improve the compression ratio. https://portal.nutanix.com/page/documents/solutions/details?targetId=TN-2032-Data-Efficiency:TN-2032-Data-Efficiency
Inline compression is correct.
Answer is A
Agreed. Almost always use inline compression (compression delay=0) because this setting only compresses larger or sequential writes and does not impact random write performance. In fact, inline compression typically increases effective performance by increasing the usable size of the SSD tier. In addition, when the system replicates larger or sequential data for protection, it can send compressed data, further increasing performance because less data crosses the wire. Inline compression also pairs perfectly with erasure coding.