Just repeating what NetApp support advised:
"
I have found our answer in bug 931439. It is new and very much still under investigation but Ill outline whats going on. When you do a copy in this manor Windows tries to create a SIS link instead of rehydrating the file immediately.
We can see that this is the case from the trace in packet 1842.
.... .... .... .... .... ..1. .... .... = Sparse: A SPARSE file
.... .... .... .... .... .1.. .... .... = Reparse Point: Has an associated REPARSE POINT
Here is more on reparse points.
https://msdn.microsoft.com/en-us/library/windows/desktop/aa365503(v=vs.85).aspx
"
I questioned this with the respective person and was advised to follow the bug and read the article.
I too questioned that but was told to read the above link.