@AndyD wrote:
For this issue, and due to SharePoint being as complex as it is, it will help to isolate this error to the individual components.
With that said, let's start with SnapDrive for Windows, since that is the service that will create the snapshot.
On the server in your SharePoint farm that is housing the indexes, have the indexes been migrated to a LUN, or do they still reside on the C:\ drive?
If they have been migrated to a LUN, can you open SnapDrive for Windows, right click the LUN, and create a snapshot? Is the snapshot created successfully, or do you receive an error when attempting to do this?
AndyD - I went through the application log and saw the log:
Unable to create a Snapshot copy.
Error message : ZAPI: An attempt to create Snapshot copy '12032014' of the 'SM_Index' volume with 'async' option 'false' failed on the storage system . Error code: 135. Error description: No more snapshots available.
I deleted some snapshots and I was able to create one and also ran a full job and it finished successfully.
Do I enable storage efficency on the volume so that the snapshots can be automatically deleted? Or do I change my snapshot policy?
Do it have to do with the size of the LUN also? Reason why I asked because on my sharepoint central administration. There health check of sharepoint showing that they are drives at risk of running out of space and it was referring to the index drive. its only carved out to be 35 GB. Does it need to be more?