A quick way to create profiles is to use the copy feature. This takes a snapshot of a profile, and except for the scope, copies all the configuration information into a new profile. This can save time in
·configuring timer jobs,
·setting up archiving, backup, and records management,
·and other configuration steps.
It is more comprehensive than relying on the Default Settings, and will likely be more customized to reflect settings already widely used for other parts of the SharePoint farm.
1.At the bottom of the profile page is a Copy button to copy the setup of an existing profile. Click Copy.
2.A summary will be displayed of the profile configuration. Click Copy to make a copy of this configuration.
3.A new profile screen opens, and the Name indicates that it is a copy. Update the name, select the scope of this new profile, which has been cleared, and make any other changes to the profile before saving.
Items to make special note of:
·The Start folder of the endpoint, especially if this reflects the profiles name.
·Any filters for asynchronous profiles. Make sure they still apply to the content of the new scope. Metadata and hierarchical filters are not copied.
·Librarian endpoints are not copied.
·Anything that used a hierarchical scope (filtering, archiving) needs to be corrected.
·A profile reboot may be needed after saving to enable the links on the SharePoint content within the scope of the new profile. To do this, open the profile, disable externalization, save the profile, open and enable externalization on the profile, and save.
While safeguards are in place to prevent externalized content from becoming irretrievable, deleting a storage profiles is still an operation that should be carefully planned and executed.
NOTE: Deleting the profile will automatically schedule a Bulk Recall and an Unused BLOB Cleanup job for the profile.
NOTE: Deleting a profile with a librarian configuration is not possible. A warning will be displayed to delete the Librarian configuration first. Perform a Bulk Recall job for the profile, BEFORE deleting the librarian configuration. This will prevent errors when the bulk recall is performed at the time of profile deletion.
If there was a File Share Librarian configuration that was associated with the profile, the content on that endpoint is also pulled into the content database by the bulk recall job when the profile is deleted. In this case, just change the Externalize Content BLOBS to No, instead of deleting the profile. This will leave the librarian file share intact.
It is strongly recommended that an Unused BLOB Cleanup Timer Job be run so that there is no confusion as to why there may be some BLOBs remaining after the Recall Job is performed. Once the Storage Profile is gone, there is no access to the Unused BLOB Cleanup Timer Job.
1.Click the name of the storage profile to open it.
2.Click Delete at the bottom of the page.
3.A deletion confirmation page is displayed.
4.Check the Default Notification Contacts checkbox, or enter other email addresses that should receive the completion notice.
5.Check the Delete Content Database Backups if those should be deleted as well.
6.Click Delete to continue with the deletion process or Cancel to return to the previous page.
A Recall job will be scheduled for the storage profile. Upon successful completion of that job the storage profile will be deleted. Until then, the storage profile will be in a deleting state and will not be editable. Additional timer jobs will also be unavailable for running or scheduling.
If there is a broader scoped profile available at the time of selecting Delete on the profile page, the only option will be to retire the profile, and select a successor profile. For example, if the profile being deleted covers a content database, but there is still an existing web application profile that covers that content database, the option to retire will be displayed but Delete will be greyed out.
If Retire is selected, the content will still be recalled, but a subsequent bulk externalization job will externalize the recalled content to the endpoint on the broader scoped profile. The Bulk Externalization job will need to be run manually if there are any errors in the Bulk Recall job. An Unused BLOB Cleanup Job will also be run for the retiring profile.
Backed up BLOBS can be moved to the Backup Endpoint of the successor profile, if the 'Retire BLOBs Backups' is checked, and there is a backup endpoint on the successor profile. (A backup endpoint can be selected for the successor profile at the time of profile retirement, using the dropdown.) They will be backed up by the successor profile's backup synchronization job, after they are externalized. Otherwise, backed up BLOBs from the retired profile will be cleared.
As with all bulk recall jobs, archived content will also be recalled. Archiving may need to be reconfigured for the successor profile, and it may be necessary to perform a Process Existing operation to re-archive content, if desired.