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

Records Management

Records Management is a feature that identifies BLOBs to be migrated to a specified endpoint when the item is declared or undeclared as a Record.  BLOBs are migrated when the Content Queue Migrator job is run. Because SharePoint creates a new BLOB when an item is declared a record, the records management features can only be used on asynchronous profiles. (SharePoint 2010 and 2013 only.)

1.Open an existing profile, and navigate to the Records Management section.
records managment

2.Select Yes from the Enable Records Management dropdown.

3.Define the scope for the rule by clicking the Change link. Use the URL search field to find a location down to the Site Level, or select the location from the hierarchy displayed in the window.

4.Check the Declared as Record checkbox, and select the endpoint from the dropdown, or create a new endpoint using the New link. An endpoint has to be selected if the feature is enabled and the checkbox is checked.

5.(Optional) Check the Undeclared as Record checkbox, and select the endpoint from the dropdown, or create a new endpoint using the New link.

6.(Optional) To migrate the BLOBs of content that are already declared a record, select Immediate in the Process Existing window, or schedule the job by clicking the Scheduled radio button and defining a date and time for the timer job.
records and hold process exisitng

NOTE: Save the Records Management configuration before running the Process Existing Records timer job.

 

·The Records Management feature is not supported with Synchronous profiles.

·The Process Existing Records option only moves records to the Declared as Record Endpoint; it will not move items that have been undeclared to the Undeclared as Record Endpoint.

·If nothing is configured for Undeclared as a Record, then the BLOB will go through standard externalization rules and go to either an endpoint on the profile or to the content database.

·Once an item is undeclared a record, it will immediately move to the selected endpoint. If an archiving rule is defined for this scope, the item will be migrated to the endpoint based on the archiving rule. Once a document is undeclared a record, it does not get special treatment and is treated like any other item in SharePoint.

·Items that are declared as a record are not subject to StoragePoint archiving rules.

·Items that are declared (or undeclared, if an endpoint is configured) a record, are not subject to externalization filter rules (size, type, hierarchy, etc.).

·Once an item has been declared a record, any subsequent versions or updates will also go to the Declared as Record endpoint.

Holds Management

Holds Management is a feature that identifies BLOBs to be migrated to a specified endpoint when an item is put in a hold.  BLOBs are migrated when the Content Queue Migrator job is run. Because SharePoint creates a new BLOB when an item is put in a hold, the records management features can only be used on asynchronous profiles. (SharePoint 2010 and 2013 only.)

1.Open an existing profile, and navigate to the Holds Management section.
holds management

2.Select Yes from the Enable Holds Management dropdown.

3.Define the scope for the rule by clicking the Change link. Use the URL search field to find a location down to the Site Level, or select the location from the hierarchy displayed in the window.

4.Check the On Hold checkbox, and select the endpoint from the dropdown, or create a new endpoint using the New link. An endpoint has to be selected if the feature is enabled and the checkbox is checked.

5.(Optional) Check the Removed from Hold checkbox, and select the endpoint from the dropdown, or create a new endpoint using the New link.

6.(Optional) To migrate the BLOBs of content that are already in hold, select Immediate in the Process Existing window, or schedule the job by clicking the Scheduled radio button and defining a date and time for the timer job.
records and hold process exisitng

NOTE: Save the On Holds configuration before running the Process Existing Records timer job.

 

·The Holds Management feature is not supported with Synchronous profiles.

·The Process Existing Records option only moves items in hold to the On Hold Endpoint; it will not move items that have been taken out of hold to the Removed from Hold Endpoint.

·If nothing is configured for On Hold, then the BLOB will go through standard externalization rules and go to either an endpoint on the profile or to the content database.

·Once an item is taken out of hold, it will immediately move to the selected endpoint. If an archiving rule is defined for this scope, the item will be migrated to the endpoint based on the archiving rule. Once a document is removed from hold, it does not get special treatment and is treated like any other item in SharePoint.

·Items that are in hold are not subject to StoragePoint archiving rules.

·Items that are moved into or out of hold are not subject to externalization filter rules (size, type, hierarchy, etc.).

·Once an item has been placed in hold, any subsequent versions or updates will also go to the On Hold endpoint.

Archive, Record and Hold Priority

Content may meet all or some conditions that would move it from its original endpoint to a second endpoint. When the content is analyzed by the Content Queue Migration job, the priority of which endpoint to select will be as follows:

1.Holds

2.Records

3.Archiving

oHolds will always take precedence.

oPutting an item in Hold will move the BLOB from a Records or Archiving endpoint when Content Queue Migrator is run.

oMarking an item as a Record will move a BLOB from an Archiving endpoint,  but will not move it from a Hold endpoint.

oAn item marked as a Record, or in Hold, will not be migrated to an Archiving endpoint even if it meets archiving conditions.

 

For example, if a file is uploaded and migrated to the main profile endpoint, then meets archiving conditions, it will go to the archiving endpoint. If the item is then declared as a record, it will move to the records management endpoint when Content Queue Migrator is run. If the item is then put in Hold, it will be moved to the holds management endpoint.

 

Conversely, if a file is uploaded and moved to the main profile endpoint, but then put in hold, it will move to the holds management endpoint. If the file meets archiving conditions or is declared a record, it will not be moved to the archiving or records management endpoints, respectively.

 

Converting a Profile to RBS

This feature is only available on SharePoint 2010. If a profile was initially configured to use EBS, there will be a link allowing for a one-time upgrade.

1.On the Edit Storage Profile page, click the Upgrade from EBS to RBS link.
METALO~1_img109
A new window will open.

There are a few scenarios that could be encountered, keeping in mind that site collection scoped profiles can only use EBS.

If the profile is site collection scoped:

·and there is no parent profile (Content Database or Web Application scoped), then a new profile must be created that uses RBS and covers the scope of the site collection.

·and there is an EBS parent profile, that parent profile will be converted to RBS, the site collection profile will be inactivated and hidden, and the site collection will now fall under the scope of that parent profile.

·and there is an RBS parent profile, the site collection profile will be inactivated and hidden, and the site collection will now fall under the scope of that parent profile.

If the profile is Content Database or Web Application scoped, it will be converted to RBS. Any Site Collection scoped profiles that are children to the converted profile will be inactivated and hidden. Any Content Database profiles that are children will be converted, but will not be deactivated.

All content within the scope of the profile will be converted automatically.

Converted content will not be moved to the parent or grandparent profile endpoint. That can be done with a Bulk Migration job.

Converting a SC scoped profile with an EBS Parent profile.

Converting a SC scoped profile with an EBS Parent profile.

 

Converting a CDB scoped profile with a child SC profile.

Converting a CDB scoped profile with a child SC profile.

2.Click Convert.

3.Click OK on the prompt to confirm.
METALO~1_img111

4.Click OK on the confirmation prompt.
METALO~1_img112

5.The page is returned to the profile page. Note the change to the profile scope.
METALO~1_img113

6.On the Job Summary page, there will be an entry for the EBS to RBS Conversion timer job. This summary will show how many BLOBs were converted.
METALO~1_img114
EBSRBS job summary

Related Documents