Last Access Date
|
|
Choose Yes to have StoragePoint record the most recent date that a document is accessed (uploaded, read or edited.) No is the default setting. |
Unused BLOB Retention Policy
|
|
For example, specifying 30 will cause orphaned BLOB files to be removed at least 30 days after being orphaned. The value must be between 1 and 365. |
New Profiles – Automatic scheduling of BLOB Health Analyzer and Unused BLOB Cleanup
When creating a new profile, two timer jobs will be displayed with default settings configured, to run weekly. These two timer jobs are critical to keeping SharePoint and StoragePoint functioning smoothly. Additionally, if these two jobs are run at regular intervals, if there are errors, it will not be as burdensome to isolate the cause. These jobs can be edited at any time; during profile creation or after the profile is saved. For more information, see BLOB Health Analyzer or Unused BLOB Cleanup for more information.
Content Backup Settings
A feature of StoragePoint is the added security of being able to back up the endpoints. The settings must be configured and the timer job must be run for the backup to take place. On the backup endpoint there will be a starting folder with the GUID of the Profile. Within that folder will be more folder structure, depending on whether foldering was enabled on the backup endpoint or not. BLOBs will use their GUID rather than any SharePoint naming conventions, even if those were used in externalization.
|
|
NOTE: If backup settings are enabled, and the backup has not been run, Unused BLOB Cleanup will not delete the unused BLOBs from the primary endpoint that meet the retention settings of the backup service. |
|
|
NOTE: If a new profile is being created, Save the profile before running any backup jobs. |
Click the arrow to expand the Backup Settings on the Storage Profile screen.
|
BLOB Backup Settings Select a backup endpoint from the dropdown. Only endpoints designated as backup will be visible in this dropdown. Selecting None (default) will not backup the primary endpoint. |
The Edit and New links can be used to create new endpoints for the backup. Enter a number of days in the Retain Backup For field to specify how long the BLOBS should remain on the backup endpoint. |
|---|---|
|
|
The backup service is a timer job that duplicates the BLOBS on the primary endpoint, to a backup endpoint. |
|
1.Select the Never, Every, Daily, or Weekly on option. a.For Every, enter the interval in minutes for the timer job to run. b.For Weekly, select the day of the week from the supplied dropdown. c.For Daily or Weekly, 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. 4.Enter the Number of Processing Threads to use during job execution. It will default to one thread per processor core if no value is supplied. 5.Configure job roles. See Controller and Worker Configuration for more information 6.Under the Send Completion Notice: header, select whether the email notification should go out Always, or Only when errors occur. 7.In the To section: a.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. b.In the Additional Contacts box, enter a semi- colon delimited list of other email addresses that should receive the notification. 8.Click Save to save the configured job schedule. If Run BLOB Backup Now is pushed, there will be a message to save the profile first. | |
