Large File Considerations for Externalizing
There are a number of things to consider when planning the StoragePoint implementation to handle large files. Here are a few:
1.We recommend using a 64bit operating system to host the SharePoint web front-ends. While we have seen problems with files over 200mb on 32bit Windows operating systems, we have not encountered any issues on 64bit Windows operating systems.
2.Review Microsoft knowledgebase article number 925083 for information on setting up SharePoint and IIS to handle large file operations (upload, check-in, etc.).
3.Use multi-file upload vs. single-file upload.
BLOB Externalization
This job externalizes content BLOBs from existing SharePoint content databases to the location specified in the associated storage profile. It can be scheduled to run on a certain day and time or it can be run immediately by clicking Externalize Now.
|
|
NOTE: This job does not need to be run on a regular basis, as new content is externalized in real-time. |
Please see Externalize and Recall Job consideration before performing timer jobs.
To Configure BLOB externalization job:
1.Note the Timer Job Scope (at the top of the page) of the Storage Profile selected.
2.Enter a date in the Schedule this process to run box or click the calendar icon to pick the date from a calendar.
3.Select a time from the supplied time dropdowns.
4.(Optional) On the on Server dropdown list, select the WFE server to run the job on.
5.(Optional) Click the Show link next to the Advanced Job Settings to view notification settings.
6.(Optional) 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.
7.(Optional) Configure job roles. See Controller and Worker Configuration for more information.
8.Under the Send Completion Notice: header, select whether the email notification should go out Always, or Only when errors occur.
9.(Optional) 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.
10.(Optional) Click Analyze and Estimate to display an estimate of the space savings that will result from running the externalize job. (See below.)
11.Click Save to save the configured job schedule.
12.(Optional) Click Externalize Now to run the job immediately.
Externalization – Analyze & Estimate
To display an estimate of the space savings that will result from externalizing the content database:
1.Click Analyze and Estimate.
2.The estimates for all content databases covered by the scope of the profile will be displayed.
3.Click Back to return to the Timer Jobs screen.
BLOB Recall
This job returns externalized content BLOBs to their associated SharePoint content database. It can be scheduled to run on a certain day and time or it can be run immediately by clicking Recall Now.
|
|
NOTE: Content does not need to be recalled before deleting a profile. Deleting the profile will automatically schedule a Recall job for the profile. |
|
|
CAUTION: 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. |
BLOB Recall does not process Large File content. Please see Large File Support for more information.
Please see the Externalize and Recall Job Considerations before performing the timer jobs.
To configure the BLOB Recall job:
1.Note the Timer Job Scope (at the top of the page) of the Storage Profile selected.
2.Enter a date in the Schedule this process to run box or click the calendar icon to pick the date from a calendar.
3.Select a time from the supplied time dropdowns.
4.(Optional) On the on Server dropdown list, select the WFE server on which to run the job.
5.(Optional) Click the Show link next to Job Filter to specify which profile endpoints should be included in the recall job, and to specify a file size filter for the recall.
6.(Optional) Click the Show link next to Job Filter. Click Change to open the scope selection window. By default the entire scope of the profile is included. Select a scope from within the profile scope to narrow down the amount of data the timer job will have to process. Click Ok.
Use the Change link to modify a filter and the Clear link to remove a filter. Note that this feature will not be available if Single Instancing is enabled on the profile. Please contact support for assistance if Single Instancing needs to be disabled.
7.(Optional) Click the Show link next to the Advanced Job Settings to view notification settings.
8.(Optional) 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.
9.(Optional) Configure job roles. See Controller and Worker Configuration for more information.
10.Under the Send Completion Notice: header, select whether the email notification should go out Always, or Only when errors occur.
11.(Optional) 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.
12.Click Save to save the configured job schedule.
13.(Optional) Click Recall Now to run the job immediately.