You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The **Start-DedupJob** starts a new data deduplication job for one or more volumes.
27
-
The data deduplication job can queue if the server is running another job on the same volume or if the computer does not have sufficient resources to run the job.
28
-
The server marks the queued jobs that you start with this cmdlet as manual jobs and gives the manual jobs priority over scheduled jobs.
27
+
28
+
The `Start-DedupJob` starts a new data deduplication job for one or more volumes. The data
29
+
deduplication job can queue if the server is running another job on the same volume or if the
30
+
computer does not have sufficient resources to run the job. The server marks the queued jobs that
31
+
you start with this cmdlet as manual jobs and gives the manual jobs priority over scheduled jobs.
29
32
The server returns a **DeduplicationJob** object for each job that you start with this cmdlet.
30
33
31
-
For multi-volume data deduplication jobs, you can use the **Preempt** parameter to move a job to the top of the job queue and cancel the current job.
34
+
For multi-volume data deduplication jobs, you can use the **Preempt** parameter to move a job to the
Runs the cmdlet in a remote session or on a remote computer.
68
-
Enter a computer name or a session object, such as the output of a [New-CimSession](/powershell/module/cimcmdlets/new-cimsession) or [Get-CimSession](https://go.microsoft.com/fwlink/p/?LinkId=227966) cmdlet.
69
-
The default is the current session on the local computer.
76
+
77
+
Runs the cmdlet in a remote session or on a remote computer. Enter a computer name or a session
78
+
object, such as the output of a [New-CimSession](/powershell/module/cimcmdlets/new-cimsession) or
79
+
[Get-CimSession](https://go.microsoft.com/fwlink/p/?LinkId=227966) cmdlet. The default is the
Indicates that garbage collection jobs free up all deleted or unreferenced data on the volume, if you specify the value GarbageCollection for the **Type** parameter.
100
-
If you do not specify this parameter, garbage collection jobs free up space after a system threshold of delete data is exceeded.
101
-
We recommend that you run garbage collection regularly without specifying this parameter, and then once a month specify this parameter and run garbage collection again.
102
111
103
-
If you specify the value Scrubbing for the **Type** parameter, this parameter indicates that scrubbing jobs validate the integrity of all data on the volume.
104
-
If you do not specify this parameter, the scrubbing job validates only critical metadata and data integrity issues that data deduplication previously encountered.
105
-
We recommend that you run scrubbing regularly without specifying this parameter, and then once a month specify this parameter and run scrubbing again.
112
+
Indicates that garbage collection jobs free up all deleted or unreferenced data on the volume, if
113
+
you specify the value `GarbageCollection` for the **Type** parameter. If you do not specify this
114
+
parameter, garbage collection jobs free up space after a system threshold of delete data is
115
+
exceeded. We recommend that you run garbage collection regularly without specifying this parameter,
116
+
and then once a month specify this parameter and run garbage collection again.
117
+
118
+
If you specify the value `Scrubbing` for the **Type** parameter, this parameter indicates that
119
+
scrubbing jobs validate the integrity of all data on the volume. If you do not specify this
120
+
parameter, the scrubbing job validates only critical metadata and data integrity issues that data
121
+
deduplication previously encountered. We recommend that you run scrubbing regularly without
122
+
specifying this parameter, and then once a month specify this parameter and run scrubbing again.
Specifies the maximum percentage of physical computer memory that the data deduplication job can use.
163
182
164
-
For optimization jobs, we recommend that you set a range from 15 to 50, and a higher memory consumption for jobs that you schedule to run when you specify the **StopWhenSystemBusy** parameter.
165
-
For garbage collection and scrubbing jobs, which you typically schedule to run in off hours, you can set a higher memory consumption, such as 50.
183
+
Specifies the maximum percentage of physical computer memory that the data deduplication job can
184
+
use.
185
+
186
+
For optimization jobs, we recommend that you set a range from `15` to `50`, and a higher memory
187
+
consumption for jobs that you schedule to run when you specify the **StopWhenSystemBusy** parameter.
188
+
For garbage collection and scrubbing jobs, which you typically schedule to run in off hours, you can
Indicates that the deduplication engine moves the job to the top of the job queue and cancels the current job.
181
-
After the server cancels the current job, the deduplication engine cannot run the preempting job if the server does not have enough memory to run the job.
182
204
183
-
This parameter applies to manual data deduplication jobs only and is ignored for scheduled jobs.
184
-
You can preempt only deduplication jobs on multiple volumes.
205
+
Indicates that the deduplication engine moves the job to the top of the job queue and cancels the
206
+
current job. After the server cancels the current job, the deduplication engine cannot run the
207
+
preempting job if the server does not have enough memory to run the job.
208
+
209
+
This parameter applies to manual data deduplication jobs only and is ignored for scheduled jobs. You
210
+
can preempt only deduplication jobs on multiple volumes.
Specifies the maximum number of concurrent operations that can be established to run the cmdlet.
249
-
If this parameter is omitted or a value of `0` is entered, then Windows PowerShell® calculates an optimum throttle limit for the cmdlet based on the number of CIM cmdlets that are running on the computer.
250
-
The throttle limit applies only to the current cmdlet, not to the session or to the computer.
279
+
280
+
Specifies the maximum number of concurrent operations that can be established to run the cmdlet. If
281
+
this parameter is omitted or a value of `0` is entered, then Windows PowerShell® calculates an
282
+
optimum throttle limit for the cmdlet based on the number of CIM cmdlets that are running on the
283
+
computer. The throttle limit applies only to the current cmdlet, not to the session or to the
This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
375
+
376
+
This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable,
0 commit comments