Sparse attributes for 'file-name' cannot be backed up correctly because the volume from which the file is backed up does not support sparse files.
If the volume from which a file is backed up does not support sparse files, then the allocated ranges for the sparse file cannot be backed up. This is true even if a file has its sparse attribute set. One example where this can occur is if a sparse file is created on a NAS volume, but the volume is backed up over CIFS, where CIFS does not support sparse files.
The sparse attribute and allocated ranges for the file are not backed up. If the file is restored, the restored file will not be sparse.
No action is required if you do not need the sparse attribute and allocated ranges backed up. If you require backup of the file's sparse attribute and allocated ranges, then the volume from which IBM® Tivoli® Storage Manager backs up the file must support sparse files.