Special note about SharePoint volumes

Certain fields must be configured when SharePoint volumes are added.

IBM® StoredIQ® supports the entire sites portion of a Sharepoint URL for the volume /sites/main_site/sub_site in the Volume field when you add a SharePoint volume. However, if the SharePoint volume URL contains spaces, then you must also use the Server, Volume, and Initial directory fields in the Add volume dialog box in addition to the required fields Server type, Server, Connect as, and Password. For example, the SharePoint volume with the URL http://shpt2010.reglab5.local/sitestest/autoteamsite1/Attribute Harvest WikiPages Library/ would require the fields in the following table because of the spaces in the URL.

Table 1. SharePoint volumes as primary volumes: Fields and examples
Primary volume field Example
Server shpt2010.reglab5.local
Volume /sitestest/autoteamsite1
Initial directory Attribute Harvest Wiki Pages Library

Performance conditions for using versions

When you add a primary volume, you define the volume by setting certain properties. If a SharePoint volume is added, you have the option of indexing different versions of data objects on that volume.

Since most versions of any object share full-text content and attributes, the effort in processing them and maintaining an updated context for the version history of an object in the index is duplicated. Additionally, if you enable version feature on a SharePoint volume, the API itself causes extra overhead in fetching data and metadata for older versions.
  • For each object, an extra API call must be made to get a list of all its versions.
  • To fetch attributes for the older versions of an object, an API call must be made for each attribute that needs to be indexed.

Limitations of SharePoint volumes

For SharePoint volumes, these limitations and specific warnings must be carefully considered.
  • If data that is essential to the functioning of the SharePoint site as an application is deleted, the site might become unusable. For example, if you delete stylesheets and forms, you might get errors when you try to display certain pages on the site.
  • It is possible to delete objects that are normally not visible. For example, documents that are filtered by views might not be visible within SharePoint. Regardless of their visibility, these data objects are indexed during harvests and can appear in infosets when responsive.
  • The delete action is supported only for files that are held in document libraries. Other SharePoint object types can be present in an infoset, and they are audited as an unsupported operation. No folders, sites, or document libraries are deleted.
  • Delete occurs at the system-file level. It means that the deletion of an older version or of a contained object results in deletion of all versions and the containing file and all of the objects it contains. The volume index is updated to reflect this change.
  • The delete action can prevent the deletion of items that were accessed or modified since the previous harvest. For SharePoint volumes, this option is ignored. Recently accessed or modified files are deleted.
  • It is not possible to delete files that are currently checked out.