StoragePoint 6.1 - Advanced Installation Guide

Planning the Metalogix StoragePoint Implementation

Preparation

Metalogix StoragePoint is installed as a SharePoint solution on a single SharePoint web front-end (WFE), making for simple installation and deployment to the SharePoint farm. This section will outline the necessary software and security prerequisites needed to install Metalogix StoragePoint.

Before configuring Metalogix StoragePoint there are few things to consider and understand. This section will touch on each of these and provide some guidance and best practices.

Minimum Server Software Requirements

SharePoint (pick one)

Server Hardware Requirements

Metalogix StoragePoint does not have any hardware requirements beyond what is prescribed by Microsoft SharePoint. For reference, those can be reviewed here:

2019 - https://docs.microsoft.com/en-us/sharepoint/install/hardware-and-software-requirements-2019

2016 - https://technet.microsoft.com/en-us/library/cc262485(v=office.16).aspx

2013 - https://docs.microsoft.com/en-us/sharepoint/install/hardware-software-requirements-2013

Security Requirements

The User Account used to perform the install must be a SharePoint Farm Administrator.

Also review FileShare and Content Database Rights in the StoragePoint Reference Guide>Managing Storage Profiles, when a profile is created.

Screen Resolution Requirements

Metalogix StoragePoint requires a minimum screen resolution of 1024 x 768 for optimizing the user interface on the StoragePoint pages that are linked from the main menu on Application Administration in Central Administration.

Internet Browser Requirements

Microsoft Internet Explorer is the recommended browser for use with StoragePoint interface. Other browsers may work, but are not verified as supported for all functions.

Temporary Storage Requirements

The amount of temporary storage needed to support the timer jobs depends on the number of threads being used for the timer job. It is recommended that 10GB per thread, for each timer job running concurrently, be available on the server running the timer job. Most timer jobs can use a Controller/Worker configuration to spread this over multiple servers. The temporary storage location can be configured on General Settings or during installation to use something other than the default (%appdata/local/temp).

SharePoint 2019 Modern UI considerations

SharePoint 2019 introduced a new look and feel for the user interface. StoragePoint links will work on this new user interface, but some additional configuration is necessary.

A Site Collection Feature will be deployed to SharePoint 2019 farms as of the 5.9.1 release. This feature should be enabled on the site collection for full StoragePoint user interface functionality.

Before activating the Site Collection Feature, an App Catalog must be configured for the web application, as well as an App Management service application.

Please reference the following articles for provisioning these resources.

https://docs.microsoft.com/en-us/sharepoint/administration/configure-an-environment-for-apps-for-sharepoint#configure-the-subscription-settings-and-app-management-service-applications

https://docs.microsoft.com/en-us/sharepoint/administration/manage-the-app-catalog

There are some PowerShell script examples in the PowerShell and API Guide for provisioning these resources.

When these steps are done, open the Site Collection Features (Gear Icon>Site Info>View All Site Settings), scroll to StoragePoint Custom Actions and SPFx Extension for SharePoint 2019 and click Activate.

Metalogix StoragePoint Database Sizing

The Metalogix StoragePoint database is used to track all BLOB activity for all profiles in the farm. This means that the Metalogix StoragePoint database will have many rows, and it will grow at a rate proportional to the number of documents added to the content databases in the farm. The Unused BLOB Cleanup and BLOB Health Analyzer timer jobs (found on the Profiles page) are critical for keeping the database size to a minimum.

To size the Metalogix StoragePoint database appropriately, use the following formula:

    (400 * (number_of_blobs_in_content_db) / 1,048,576  * 2 ) + 50 = Ideal Size of Metalogix StoragePoint DB (in MB)

where number_of_blobs_in_content_db is the number of documents and versions in all the externalized content databases and 50 represents the size (in MB) of an empty Metalogix StoragePoint database and accounting for a reasonable amount of configuration data (i.e. Storage Profile and Endpoint definitions).

So, as an example, for a farm with 1 million total documents and versions, this would come out to 813 MB. This figure includes a considerable amount of slack and room for future growth.

It is advisable to also set the Metalogix StoragePoint database to auto-grow in SQL Server. This will ensure that Metalogix StoragePoint keeps functioning if the allocated space is exceeded.

Additionally, Microsoft has restrictions on database sizing that must be followed.

Advanced Installation