Chat now with support
Chat with Support

Metalogix StoragePoint 5.8 - Reference Guide

Planning the Metalogix StoragePoint Implementation Backup/Restore and Disaster Recovery Synchronous versus Asynchronous Setting up Metalogix StoragePoint Default Values General Settings Managing Storage and Backup Endpoints Managing Storage Profiles
Creating a New Storage Profile Editing an Existing Storage Profile Converting a Profile to RBS Copying a Profile Delete an Existing Storage Profile Storage Profile Timer Jobs
Metalogix StoragePoint Timer Job Monitoring File Share Librarian Large File Support Dashboard User Experience Activating the Software Appendix A: Import\Export Tool Appendix B: Feature Matrix

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.

Users should know:

·A user with the ability to edit document properties should not change the content type from ‘StoragePoint Document Link’.

·The aspx file will not be subject to metadata requirements normally placed on a document content type; there can be list data fields, but changing the content type to get those fields is not supported.

·Open or download can only be performed by clicking on the name of the document.

·Previous versions can only be accessed from the Large File Details Download link.

·The option to ‘download a copy’ is not supported.

·Office Web Applications are not supported.

·The file does not need to be large to use this interface, but files smaller than the upload limit for the web application (usually 50MB) will not generate a link; they will be externalized to the endpoint like a regular upload.

·The recommended maximum number of files to be used with the Large File Upload interface is 100.

Enabling Large File Support

To enable large file support, select ‘yes’ on the dropdown, on the General Settings page. Large file support will be enabled on any Document Libraries under the scope of an active storage profile.

Large File Support

METALO~1_img47

Large files may be linked into a SharePoint Document Library.

System Cache, using File System Adapter, is required to enable Large File Support. There will be a link available to edit System Cache if it is not already created.

Large File Support and Unused BLOB Cleanup Timer Job

METALO~1_img167

Select Yes or No for Include Large File Scanning. Yes will include the BLOBs and stubs created while using the Large File Upload in the scan for content to be removed. No (default) will ignore them.

If Large File Support is enabled, the Unused BLOB Cleanup job scans all content for orphaned BLOBs. If a Site Collection has recently been deleted, SharePoint doesn’t delete it until the Gradual Site Delete timer job has been run. The Unused BLOB Cleanup job may return errors until the deleted site collection is removed by SharePoint. It is recommended that the Gradual Site Delete timer job be run manually, after deleting a Site Collection.

Related Documents