Snapshot Spilling
My focus is on managing and configuring cutting-edge storage solutions, including NetApp and Dell EMC. We've enhanced data protection and integrity through innovative tools like Snapshot and Commvault, ensuring robust client support.
My educational foundation in Information Technology from Maharshi Dayanand University complements my hands-on experience, where I've honed skills in NAS and VMware ESXi. These competencies, paired with AWS certifications, drive my commitment to excellence in storage administration.
Snapshot Reserve: The area in volume that is reserved exclusively for the Snapshot copies.\
This reserved space is booked only for the snapshot copies not for the user data metadata of the volume.
The size of snapshot reserve is a specific percentage of the current volume size. Usually, 5% of the size of the volume.
How Snapshot actually works?
1. When a snapshot is created, it uses pointers to reference the active data blocks in the volume.
2. When changes are made to the active data, the snapshot continues to reference the unchanged blocks, while the new changes are written to new locations.
3. This mechanism ensures that the snapshot remains a static view of the data at the time it was taken.
Now, comes a situation where Snapshot Spilling concept is introduced here.
If the snapshot reserve is full but active file system hasn’t fill yet then it starts using the users data space, this concept is known as the snapshot spilling in NetApp.
