Once a profile is saved, archiving, records and holds management can be added to the profile. Endpoint filters can also be modified for asynchronous operations.
Click the name of the storage profile to edit.
Make note of any notifications at the top of the page:
Do not change the Endpoint Selection mode on the profile that have a File Share Librarian configuration, which will be indicated in the Filter column.
To temporarily prevent externalization to an endpoint, switch the Online selection to No. This only affects this endpoint for this profile. It does not affect the endpoint's use on other profiles.
Make the necessary changes, including endpoint filters, noting that the profiles scope and name cannot be changed, nor can endpoints that are associated with a File Share Librarian configuration be removed.
When complete, click Save to apply the changes.
The Storage Profiles page will display.
It is recommended that an IISRESET and a SharePoint Timer Job reset be performed on each web front end if changes were made to the storage profile.
Archiving can be setup to move BLOBs to different storage tiers, as content is aged, versions are retained or when changes in metadata are detected. The rules can be configured on different scopes of content, but there can only be one rule per scope. The most granular rule is the only rule that will ever get evaluated.
The levels of granularity are as follows, from the least to the most granular:
4.Site Content Type
6.List Content Type
So, for example, if the metadata change rule is more granular than the versions rule, then the versions rule will never get evaluated for an item within the scope of the metadata change rule.
1.Versions rule on site
2.Metadata change rule on list
3.Versions rule will never be evaluated for an item within the list in 2.
If large file support is enabled, only the aspx file is moved to the archive endpoint.
Profiles with File Share Librarian Configurations should not add Archiving to the profile. The archiving option won't be available for new profiles.
To configure archiving, open the profile and click the arrow of the Archiving bar.
Yes Archiving will be enabled for this scope.
No Archiving will NOT be enabled for this scope. (default)
Allow IMP Configuration
Yes Site administrators will have the ability to set granular archiving rules.
No Site administrators will NOT have the ability to set granular archiving rules. (default)
Endpoints to Show in IMP Configuration
Show All Endpoints Site collection administrators will see all online storage endpoints and can set rules using them. (default)
Show Select Endpoints The Administrator can select which endpoints to make available to the site collection owners. If no endpoints are selected, this field will revert to Show All Endpoints when the changes are saved.
Click New Rule to open the New Archiving Rule window. See for more information.
The Archiving Aging section is used to schedule when the Archive Aging job will run, and to run it immediately if necessary.
Only one rule can be created per scope. The archiving scope cannot be broader than the profile scope.
1.Expand the Archiving Configuration section on the profile. Click New Rule.
2.Click the Change link to select the scope (i.e. site collection, site, list, or content type).
3.Enter part or all of the URL to search for a scope or drill down in the hierarchy to select the scope, and click OK.
NOTE: If Allow IMP configuration is set to Yes, rules must be created at the Content Type level of a List or Library in order for Site Collection Administrators to view them on the IMP page. Site Collection Administrators will not see rules created at a broader level.
4.Note the selection in the Selected Rule Scope section.
5.Select the type of Rule Definition:
a.None No changes will be saved.
b.Aging Rule This rule looks for content that has aged beyond the defined time period(s) and triggers the content to be moved to different storage endpoint(s). See below.
c.Metadata Change Rule This rule captures changes in an items metadata and triggers the content to be moved to different storage endpoint(s). See below.
d.Retained Versions Rule This rule causes retained versions within the specified boundaries or all versions except current to be moved to a different storage endpoint(s). See below.
The scope of a rule cannot be edited once it is saved. To change the scope, delete the rule and recreate the rule with the corrected scope and rule definitions.
1.From the New Archiving Rule page, click the Aging Rule option.
2.Select the Date Property (i.e. Created, Modified, or some user defined data/time property) to be used to calculate the age of the content.
3.Click the New Condition link.
4.On the New Aging Rule Condition page, select as Date Property (Created, Last Accessed, or Modified) that this rule will be based on.
NOTE: Last Access Date only works if it has been enabled on the profile. See for more details. However, the archiving condition can be configured and then enable the Last Access Date on the Profile.
5.Enter the time period (duration and interval) that needs to elapse before the content is moved.
6. (Optional) Select a Property in the MetaData Criteria section, and specify a value. This condition creates a compound archiving rule, and content will only be archived if both conditions are true.
7.Select the archive endpoint from the dropdown or click New or Edit as needed. See for steps.
8.Check if Major and/or Minor versions should be included when migrating items covered by the rule.
9.Click OK. (Click Cancel to return to the New Archiving Rule page without saving changes.) The New Archiving Rule page is displayed.
10.Click New Condition to add additional rules or click OK to return to the Archiving Configuration page once all of the rules are configured.
11.Click Save on the Archiving Configuration page once all rules are created.
NOTE: Make sure to configure the timer job if Aging Rule Conditions are created. A notice is displayed.