Miscellaneous - My reference
- Deduplication Compression Erasure Coding
- Deduplication - fingerprints using sha-1
- Compression - lz4(inline) lz4ha(postprocess)
- EC - generally post process. Logic built inside the system initiates migration from RF2/RF3 to EC.
- For frequently access data avoid deduplication and compression as both of them are resource intensive
- VDI workload and backup good for dedupliaction
- regular files good for compression
- CAD files bad for compression
- High IO requirement do not use EC.
- For EC minimum 4 nodes. vSAN implemented only in All-Flash Nutanix is implemented with hybrid as well. Same is true with compression and deduplication.
- For large block say 16KB(Nutanix) it is less resource intensive to perform deduplication than 4KB (like solidfire and NetApp)
- RF2-FTT1 2 copies of data is maintained and 3 copies of metadata and configuration is maintained. Can withstand 1 disk or node failure.
- RF3-FTT3 3 copies of data is maintained and 5 copies of metadata and configuration is mainatained. Can withstand 2 disk or 2 node failure. (For nutanix with RF3 storage container can be Replication factor of 2 or Replication factor of 3. No RF changes to EC enabled storage container)
- FTT 1 Raid 1 - minimum 3 nodes
- EC Raid 5 - minimum 4 nodes
- ESXi and NTNX boot partition remain unencrypted. SEDs support encrypting individual disk partitions selectively using the “BAND” feature (a range of blocks).
No comments:
Post a Comment