Deleting a File Share Librarian
There is a Delete button on the bottom of the File Share Librarian configuration page. Clicking Delete will delete the configuration immediately and content on that file share will cease being cataloged into SharePoint.
|
|
NOTE: Deleting the File Share Librarian configuration does NOT delete the Storage Profile or the Storage Endpoint. |
Troubleshooting
Problem: Librarian continues to catalog content that has been deleted in SharePoint
Check the timing of the librarian and Unused BLOB Cleanup timer jobs. If a folder or file has been deleted (moved to the recycle bin), the subsequent running of the librarian timer job will mark that content so that it is not re-cataloged. However, if the file or folder is removed from the recycle bin AND the Unused BLOB cleanup job is run before the Librarian timer job, the content may be re-cataloged.
The content will continue to be re-cataloged as long as it in in the source endpoint for the Librarian configuration. Librarian does not carry through SharePoint deletions to the endpoint.
Problem: Large File Uploads aren't working
The Large File Upload may be displayed bit it may not be operational if the library was created as a result of cataloging content.
Problem: The Scope of the created profile isn't the Web App selected as the destination
If selecting a web app as the destination, the content begins building in the Content Database. As a result, the scope of a resulting profile will be that Content Database. To keep the scope at the web application level, create the profile first and leave externalization disabled, and then create the librarian configuration.
Large File Support
SharePoint does not support the uploading of files greater than 2GB, or in some cases, 10 GB in size. Web Applications also have upload size limits. In SharePoint 2010 and newer, Metalogix StoragePoint has a feature that allows a custom upload interface to circumvent this limitation, if the Document Library is in the scope of an active StoragePoint profile. By dragging the file to the custom upload page, the document is moved to the endpoint, and a link (aspx file) is placed in the document library to access that file. The link will have a content type of StoragePoint Document Link. The BLOB will be externalized to the endpoint.
If for whatever reason StoragePoint is uninstalled, these large file uploads will no longer be available, because the endpoint is no longer available.
Administrators should ALSO know:
·StoragePoint must be present to allow for continued management of Large File content through SharePoint.
·Large File Support can be used with any of the StoragePoint-supported adapters.
·System Cache using the File System adapter is required to enable Large File Support.
·On the Unused BLOB Cleanup timer job, large files are not included by default, but this can be configured for the timer job.
·Bulk Migration operations will move Large File content across endpoints.
·Bulk Recall does not process Large File Content.
·Archiving will only move the .aspx files to the archive endpoint.
·It is recommended that the information in the Large File Upload section of the Administration Guide, or this supplement, be shared with end users if this feature is being enabled.
·Large File Support is not compatible with Microsoft Edge browser.
·Use of the large file upload feature requires at a minimum, the View Application Pages and Add Item permissions. When adding a custom permission level, Add Item will also automatically enable View Items, View Pages, and Open. These permissions are included with the default permissions of "Contribute" and higher. This is important to note if using custom security groups or breaking inheritance with security on lists or libraries.
·Large File Uploads are not compatible with any type of migration within SharePoint or from one farm to another. However, the actual large files can be uploaded from the endpoint, in the destination, since they are complete files.