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

Use Breadcrumbs

METALO~1_img48

Yes –During BLOB Migration, Metalogix StoragePoint will leave behind a small BLNK (BLOB Link) file that points to the new BLOB location. (default)

No – Metalogix StoragePoint will leave a full copy of the BLOB behind. This BLOB file will be removed by the Unused BLOB Cleanup Job once its BLOB Retention period has expired.

Customer Improvement Experience Program

The Customer Improvement Experience Program allows Metalogix to collect data that is useful for analyzing how the product is used, where there are improvements to be made, and notification of common errors.

METALO~1_img49

Yes –basic information about how StoragePoint is used can be collected. (default)

No – Usage information will not be shared.

Track Audit Changes

StoragePoint can write all the events to the Windows Application logs by enabling this setting. The default is unchecked.
clip0111

The table below contains all the Windows Event Id and message for the windows event log.

Action

Event Id

                         Message

INSERT ENDPOINT

1001

the EndPoint: [EndPoint Name] was inserted at [DateTime] by [SharePoint User]

UPDATE ENDPOINT EVENT

1002

the EndPoint :[EndPoint Name] was updated at [DateTime] by [SharePoint User]

DELETE ENDPOINT EVENT

1003

the EndPoint: [EndPoint Name] was deleted at [DateTime] by [SharePoint User]

INSERT PROFILEENDPOINT EVENT(Add EndPoint to the Profile)

2004

the ProfileEndPoint : [EndPoint Name] was inserted to the Profile:[Profile Name] at time [DateTime] by: [SharePoint User]

UPDATE PROFILEENDPOINT EVENT (update EndPoint to belong a Profile)

2006

the ProfileEndPoint :[EndPoint Name] was updated in the Profile:[Profile Name] at time : [DateTime] by: [SharePoint User]

DELETE PROFILEENDPOINT EVENT (delete  EndPoint to belong Profile)

2005

the ProfileEndPoint :[EndPoint Name] was deleted to the Profile:[Profile Name] at time : [DateTime] by: [SharePoint User]

INSERT PROFILE EVENT

2001

the Profile :[Profile Name] was inserted at [DateTime] by [SharePoint User]

UPDATE PROFILE EVENT

2002

the Profile :[Profile Name] was updated at [DateTime] by [SharePoint User]

DELETE PROFILE EVENT

2003

the Profile :[Profile Name] was deleted at [DateTime] by [SharePoint User]

JOB RUN EVENT(ContentMigrator)

3006

the Job : ContentMigrator has been run by  [SharePoint User] at time : [DateTime]

JOB RUN EVENT(Capacity)

3009

the Job :Capacity has been run by [SharePoint User] at time : [DateTime]

JOB RUN EVENT(LogFilesCollector)

3015

the Job :LogFilesCollector has been run by  [SharePoint User] at time : [DateTime]

JOB RUN EVENT(BreadcrumbOptimization)

3010

the Job :BreadcrumbOptimization has been run by  [SharePoint User] at time : [DateTime]

JOB RUN EVENT(SystemAuditReport)

3031

the Job :SystemAuditReport has been run by  [SharePoint User] at time : [DateTime]

JOB RUN EVENT(SystemHealthReport)

3023

the Job :SystemHealthReport has been run by  [SharePoint User] at [DateTime]

JOB RUN EVENT(OrphanBLOB)

3012

the Job :OrphanBLOB has been run by  [SharePoint User] at [DateTime]

JOB RUN EVENT(BlobRefScan)

3014

the Job :BlobRefScan has been run by [SharePoint User] at [DateTime]

JOB RUN EVENT(Externalize)

3001

the Job :Externalize has been run by  [SharePoint User] at [DateTime]

JOB RUN EVENT(Migrate)

3003

the Job :Migrate has been run by  [SharePoint User] at  [DateTime]

JOB RUN EVENT(Aging)

3005

the Job :Aging has been run by [SharePoint User] at  [DateTime]

JOB RUN EVENT(BackupSync)

3016

the Job :BackupSync has been run by  [SharePoint User] at [DateTime]

JOB RUN EVENT (Recall)

3002

the Job :Recall has been run by  [SharePoint User] at [DateTime]

JOB RUN EVENT(PerServerMaintenance)

3024

the Job :PerServerMaintenance has been run by [SharePoint User] at  [DateTime]

 

[Profile Name] = “Profile Name inserted, updated or deleted in the StoragePoint DB”

[EndPoint Name] = “EndPoint Name inserted, updated or deleted in the StoragePoint DB”

[DateTime] = “Date Time that the action was performed”

[SharePoint User] = “SharePoint user who performed the action”

 

All the Events  have level=Information and task Category = None.

MinRole Topology

Allows StoragePoint timer jobs to process on servers that by default of SharePoint 2016 configuration, do not run timer service instances.

Checking the box shows the servers in the farm. Select the servers where StoragePoint timer services will be allowed to run. This will support Master/Worker configurations.

MinRoleTopology

After clicking Save on General Settings, it may be necessary to wait for or manually run the Farm Wide Maintenance Timer job, which will be found in SharePoint Timer Job Definitions. By default, Farm Wide Maintenance runs every hour.

Related Documents