StoragePoint 6.0 - PowerShell and API Reference Guide

Set-UnusedBLOBCleanupJob

This command schedules an Unused BLOB clean-up job for a specified profile.

Parameters

·Profile (p): The name or Id of the profile in which to run the job under. REQUIRED.

·Type (schedtype): The type of schedule to use when setting up this job. Valid values are OneTime, Daily, and Weekly. If not specified, the timer job will run immediately.

·DayOfWeek (dow):  The day of the week to run the job when the schedule type is set to Weekly.

·JobStartDate (startdate): The start date/time. The time portion is used to set the start time for Daily and Weekly jobs.

·JobEndDate (enddate):  The end date/time. Not used for OneTime jobs. The time portion is used to set the end time for Daily and Weekly jobs.

·EndpointFilter (ef): Specify specific endpoints which the timer job should analyze.

·RunNow: If specified (-RunNow), then run the job immediately. Ignores any scheduling options provided.

·EmailDefault: If specified (-EmailDefault), send status email to the default notification group setup in General Settings.

·NotificationEmailOther (email): Other email addresses (not in default notification group) to send status emails to.

·EmailOnErrorOnly: If specified (-EmailOnErrorOnly), then send status email only if an error occurs when running the job.

·IncludeLargeFiles (ilf): If indicated, the Large File Uploads will also be removed by the unused BLOB cleanup job.

·OnlyLargeFiles (olf): Only large files will be analyzed and removed by the unused BLOB cleanup job.

·JobServer (jobsrv): Server name to run the job. REQUIRED for scheduled jobs.

·JobScope: See parameter definitions in Timer Job Scope Parameter.

Examples

The following example will run the Unused BLOB Cleanup Job immediately.

Set-UnusedBLOBCleanupJob -p MainProfile1 -RunNow

The following example schedules the job on a recurring weekly schedule, and includes large files.

Set-UnusedBLOBCleanupJob -p MainProfile1 -schedtype Weekly -dow Saturday -startdate “12/26/2009 3:00” –enddate “12/26/2009 6:00” –EmailDefault -email someone@example.com -IncludeLargeFiles

The following example runs the job immediately and has LIST scope.

Set-UnusedBLOBCleanupJob -p MainProfile1 -RunNow -JobScope 'wa:61993f69-a1fa-47ae-a037-f19bb65e1341/cdb:8e3b4665-672c-4655-a41b-861c8f4e86b5/s:054de887-db61-4407-8322-564531dbefc4/w:74b8d00f-f6f5-4233-b372-05a0f267533a/l:c4dfbdba-21c6-44d1-8e5e-41be2b11079f'

Set-BLOBExternalizationJob

This command schedules externalization job for a specified profile. The job may be run immediately (-RunNow) or at a specified date/time (-JobStartDate).

Parameters

·Profile (p): The name or Id of the profile in which to run the job under. REQUIRED.

·JobStartDate (startdate): The start date/time to run the job.

·NumberOfThreads (threads): Number of threads to run the job with.

·RunNow: If specified (-RunNow), then run the job immediately. Ignores any scheduling options provided.

·JobRole (JobServerRole): Values allowed: Controller, Standalone

·Workers (ws): Servers that will act in the worker role of a controller-worker configuration.

·EmailDefault: If specified (-EmailDefault), send status email to the default notification group setup in General Settings.

·NotificationEmailOther (email): Other email addresses (not in default notification group) to send status emails to.

·EmailOnErrorOnly: If specified (-EmailOnErrorOnly), then send status email only if an error occurs when running the job.

Example

This example schedules an externalization job to run immediately.

Set-BLOBExternalizationJob –p MainProfile1 –threads 20 –EmailDefault –RunNow

Set-BLOBRecallJob

This command allows a user to schedule a recall job for a particular profile scope.

Parameters

·Profile (p): The name or Id of the profile in which to run the job under. REQUIRED.

·JobStartDate (startdate): The start date/time to run the job.

·NumberOfThreads (threads): Number of threads to run the job with.

·RunNow: If specified (-RunNow), then run the job immediately. Ignores any scheduling options provided.

·JobRole (JobServerRole): Values allowed: Controller, Standalone

·Workers (ws): Servers that will act in the worker role of a controller-worker configuration.

·EmailDefault: If specified (-EmailDefault), send status email to the default notification group setup in General Settings.

·NotificationEmailOther (email): Other email addresses (not in default notification group) to send status emails to.

·EmailOnErrorOnly: If specified (-EmailOnErrorOnly), then send status email only if an error occurs when running the job.

·EndpointFilter (ef): Filter on which BLOBs to recall by endpoint (*=All Endpoints or EP1,EP2).

·SizeFilter (sf): Filter on which BLOBs to recall by size (>= or <=). Use 'Default' to clear this filter.

·JobScope: See parameter definitions in Timer Job Scope Parameter.

Example

This example schedules a recall job to run immediately.

Set-BLOBRecallJob –p MainProfile1 –threads 20 –EmailDefault –RunNow

This example schedules a recall job and has filters applied.

Set-BLOBRecallJob –p MainProfile1 –threads 20 –EmailDefault -ef EP1 -sf ">=50"

Set-BLOBMigrateJob

This command allows a user to schedule a migrate job for a specified profile. When run, the job will migrate BLOBs from the source endpoint to the target endpoint.

Parameters

·Profile (p): The name or Id of the profile in which to run the job under. REQUIRED.

·SourceEndpoint: The source endpoint's name/Id. REQUIRED.

·TargetEndpoint: The destination endpoint's name/Id. REQUIRED.

·JobStartDate (startdate): The start date/time to run the job.

·NumberOfThreads (threads): Number of threads to run the job with.

·RunNow: If specified (-RunNow), runs the job immediately.

·JobRole (JobServerRole): Values allowed: Controller, Standalone

·Workers (ws): Servers that will act in the worker role of a controller-worker configuration.

·EmailDefault: If specified (-EmailDefault), send status email to the default notification group setup in General Settings.

·NotificationEmailOther (email): Other email addresses (not in default notification group) to send status emails to.

·EmailOnErrorOnly: If specified (-EmailOnErrorOnly), then send status email only if an error occurs when running the job.

·FilterScopes: add the scope to migrate BLOB job. This is a site collection, content database or web application ID. Get-siteCollectionId or Get-ContentDBId can be used in conjunction.

·FilterScopesOp : Include or Exclude Option.

·JobScope: See parameter definitions in Timer Job Scope Parameter.

Example

This example schedules a migration job to run immediately.

Set-BLOBMigrateJob –p MainProfile1 -SourceEndpoint Endpoint1 –TargetEndpoint Endpoint2 –threads 20 –EmailDefault –RunNow

This example schedules a migration job to run at a specified time.

Set-BLOBMigrateJob –p MainProfile1 -SourceEndpoint Endpoint1 –TargetEndpoint Endpoint2 -startdate "08/20/2015 10:10" –threads 20 –EmailDefault

This example schedules a migration job to run at a specified time with filters enabled.

Set-BLOBMigrateJob –p MainProfile1 -SourceEndpoint EP1 –TargetEndpoint EP2 -startdate "09-09-2015 11:55"  -FilterScopes "s:42154fb7-176d-4ff6-b16f-3cb3554a4118" -FilterScopesOp include