Any idea how to create a WORM test cases
I am assuming that you are after “what is WORM semantics”, which will then implicitly define what you need to test for.
The simple definition is that after you have written a complete stream of bytes (the object) to a storage device you can no longer change it. No partly update of the stored object or completely delete or overwrite of the stored object by a user or the device itself.
In case the storage device makes use of read/write media and WORM is implemented through its firmware or operating system, there is the expectation that “change” or “deletion” of the object must be protected by secure and audit-able mechanisms like object retention, object authentication checks and repair capabilities. The firmware or operating systems may be locked down such that testing these mechanisms may be difficult at best.
I'm not sure I understand the question....?
There are a number of WORM test cases and a number of WORM technologies....
I will move this question on WORM (Write Once, Read Many) over to the Object Storage Platform space under Solution and Product Forums to make it visible to experts on HCP and HNAS.
Retrieving data ...