NetApp is supporting Symantec's thin reclamation API, almost two years after it was announced.
Symantec announced its thin reclamation API as part of a Veritas Storage Foundation update in October 2008, with 3PAR first off the block in supporting it. IBM gave the API the thumbs up a year later. It solves a problem with thinly-provisioned block storage in that when files are deleted by a host server the storage array providing the storage doesn't know anything about it.
With thinly-provisioned storage a host server application only consumes storage as it writes data. Although it has a logical allocation of, say, 10TB, it has written 5TB of data and that is all it's actually given by the storage array, driving up disk utilisation. If that application then deletes a 250GB file it remains allocated by the storage array, sending disk utilisation down again. Cue the host running Veritas Storage Foundation software, and it sends a message to the array, using the thin reclamation API, which then hunts down the deleted file, reclaims the space and returns it to its general storage pool for use elsewhere.
NetApp calls this hole punching and had introduced a host-based deleted file space reclamation facility with SnapDrive for Windows back in 2008. It wanted an industry-standard way of doing this, but that has not come to pass and so now it's going with the Symantec flow.
In these days of focus on general data reduction, having disk capacity occupied by deleted files is just silly. Symantec Storage Foundation users with NetApp arrays will now be able to increase their disk utilisation rate. The larger the IT shop and the higher the file deletion rate the more effective this API will be. ®