The StoragePoint Content Database Backup Cleanup job is used to purge expired content database backups that were created by the StoragePoint Content Database Backup Service. The cleanup service should be run at least once a week, or as often as content database backups are created, to maintain an optimally performing SharePoint environment.
1.Select the Never, Daily, or Weekly on option.
a.For Weekly, select the day of the week from the supplied dropdown.
b.Select the start window time from the between dropdowns and the end window time form the and dropdowns.
2.On the on Server dropdown list, select the WFE server on which to run the job.
3.Click the Show link next to the Advanced Job Settings to view notification settings.
a.Under the Send Completion Notice: header, select whether the email notification should go out Always, or Only when errors occur.
b.In the To section:
c.Check the Default Notifications Contacts box to have a completion email sent to the email address entered in General Settings. Note that for this feature to work, the Default Notification field on General Settings must contain a valid email address.
d.In the Additional Contacts box, enter a semi- colon delimited list of other email addresses that should receive the notification.
4.Click Save to save the configured job schedule.
5.Click Remove Expired Content Database Backups Now to begin the timer job immediately.
There may be a note about creating a master encryption key. If the scope of the profile covers a content database and uses RBS, this will be required for SQL server.
Enter a password, and click Create Key.
Click Close. Note the name of the content database that is covered by this encryption key.
The page will be locked until the operation is complete. This operation can take several minutes as it will need to iterate all site collections within the scope of the profile.
If this page appears when saving an existing profile, note whether the profile has a librarian configuration. If so, the master key encryption is completed on the first save of the profile, rather than when the librarian configuration is saved.
When using the File Share adapter, an additional check may be seen when saving the profile:
This screen displays when editing an existing profile if:
·the Externalize Content BLOBs setting is Yes;
·there is at least one FileSystem endpoint;
·and the Web Application in the scope of the profile has at least one connected SharePoint (IIS Web) Service Application account that cannot access one of the FileSystem endpoints.
·The Web Application is connected (through proxy) to at least one service application, i.e. User Profile Service.
This screen displays when creating a NEW profile or copying a profile if:
·there is at least one FileSystem endpoint;
·The Web Application is connected (through proxy) to at least one service application, i.e. User Profile Service;
·All service accounts associated with profile web application do not have file system access permissions (Read, Write, Modify, Delete, DeleteSubdirectoriesAndFiles, CreateDirectories, CreateFiles) on all FileSystem endpoints AND db_owner role on all content databases associated with the profile.
When a new Content Database Profile is created, the associated web application pool account registered on SQL server will get two additional Database Role memberships:
·For SharePoint 2007 and SharePoint 2010, the web application pool account will get Public and db_owner.
·For SharePoint 2013 and SharePoint 2016, the web application pool account will get Public and SPDataAccess.
This check can be run manually by clicking the Check File share and Content Database Rights button beneath the list of endpoints on the profile.
Correct any permission issues before externalizing data. Use the Copy to Clipboard button to note which accounts need permission.
The Storage Profiles page will be displayed with the newly-created storage profile showing up in the list.
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.