A vDisk is read by multiple VMs. The cluster creates immutable copies of the vDisk.
What are these vDisk copies called?
A vDisk is read by multiple VMs. The cluster creates immutable copies of the vDisk.
What are these vDisk copies called?
When a vDisk is read by multiple VMs and the cluster creates immutable copies of the vDisk, these copies are called Shadow Clones. This feature, particularly used in environments such as Nutanix, allows for efficient distributed caching by marking the vDisk as immutable and enabling each VM to cache the data locally, thus improving read performance.
I think it is D Shadow clones
D. Shadow Clones. Read the bible.
The Answer is D.refer to http://myvirtualcloud.net/nutanix-shadow-clones-explained-and-benchmarked/ #:~:text=Nutanix%20Shadow%20Clones%20allow%20for,'multi%2Dreader'% 20scenario.&text=Once%20the%20disk%20has%20been,making%20read% 20requests%20to%20it.
D is the correct answer! With Shadow Clones, AOS storage monitors vDisk access patterns to determine whether VMs are frequently reading the same data set from multiple nodes in the cluster. If it detects this situation, AOS storage marks the vDisk as immutable.
The Distributed Storage Fabric has a feature called ‘Shadow Clones’, which allows for distributed caching of particular vDisks or VM data which is in a ‘multi-reader’ scenario.
From the Nutanix Bible: With Shadow Clones, DSF will monitor vDisk access trends similar to what it does for data locality. However, in the case there are requests occurring from more than two remote CVMs (as well as the local CVM), and all of the requests are read I/O, the vDisk will be marked as immutable. Once the disk has been marked as immutable, the vDisk can then be cached locally by each CVM making read requests to it (aka Shadow Clones of the base vDisk).
D, Shadow clones
D, Shadow clones
After re-reading the question i'll give U credits guys. Golden is used when you manually execute the clone, if its nutanix genius then it's shadow clones.
SC are activated for specific reasons on clusters executing VDI in certain circumstancies. I'll give more credit on "golden image" even if it's quite strange to use it. https://next.nutanix.com/virtual-desktop-infrastructure-28/os-gold-image-best-practices-ntfs-allocation-unit-size-486
It's Shadow Clones - From the Nutanix Bible: With Shadow Clones, DSF will monitor vDisk access trends similar to what it does for data locality. However, in the case there are requests occurring from more than two remote CVMs (as well as the local CVM), and all of the requests are read I/O, the vDisk will be marked as immutable. Once the disk has been marked as immutable, the vDisk can then be cached locally by each CVM making read requests to it (aka Shadow Clones of the base vDisk).
D, Shadow clones
answer is D. refer to http://myvirtualcloud.net/nutanix-shadow-clones-explained-and-benchmarked/ #:~:text=Nutanix%20Shadow%20Clones%20allow%20for,'multi%2Dreader'% 20scenario.&text=Once%20the%20disk%20has%20been,making%20read% 20requests%20to%20it.
A is correct. Based on nutanixbible.com "When a snapshot or clone is taken, the base vDisk is marked immutable and another vDisk is created as read/write".
I think is C Volume Groups