3 ms·
> For "write once, read many" workloads, like archival or backups. My backup drive gets written to nightly, but reads are very rare (only in case of data loss)
by auxym 7y ago
> For "write once, read many" workloads, like archival or backups.
My backup drive gets written to nightly, but reads are very rare (only in case of data loss).
- wtallis 7y agoThe key aspect of WORM here is that the data you write is not modified in-place or overwritten in part; it stays put until deleted. That's true of most backup strategies, whether or not they generate a lot of read traffic to compute incremental backups. The "read many" part of WORM is usually never about how many actual reads are performed, but about the capability to handle them better than multiple writes.
- ngcc_hk 7y agoYou are right but the guy you replied highlight a strong point, we want to write once very quickly just to archive something and chance of reading those is low. But we would need to write it. (He did it every night. I just archive it and recycle the storage in my NAS, but not as frequent as every night.). If I want archive reading in the very long term, should use tape or as you say WORM. But not for hard disk usage. Low cost write quickly. That is the 5400 coming in but not this. But the key is to tell us so we can choose. Not as scandal like to get such knowledge and still hiding.