Start-DPMDatasourceConsistencyCheck
Start-DPMDatasourceConsistencyCheck
Performs a consistency check on a DPM data source.
Syntax
Parameter Set: Datasource
Start-DPMDatasourceConsistencyCheck [-Datasource] <Datasource> [[-AdhocJobsContext] <AdhocJobsContext> ] [-ForcedFullCC] [-HeavyWeight] [-JobStateChangedEventHandler <JobStateChangedEventHandler> ] [-Confirm] [-WhatIf] [ <CommonParameters>]
Parameter Set: ProtectionGroup
Start-DPMDatasourceConsistencyCheck [-ProtectionGroup] <ProtectionGroup> [[-AdhocJobsContext] <AdhocJobsContext> ] [-Confirm] [-WhatIf] [ <CommonParameters>]
Detailed Description
The Start-DPMDatasourceConsistencyCheck cmdlet performs a consistency check on a System Center 2012 – Data Protection Manager (DPM) data source. You can run consistency checks on a specific data source or on all data sources in a protection group that are in an inconsistent state.
Parameters
-AdhocJobsContext<AdhocJobsContext>
Specifies the context details of the ad hoc job. Do not use this parameter from the Windows PowerShell command line.
Aliases |
none |
Required? |
false |
Position? |
2 |
Default Value |
none |
Accept Pipeline Input? |
false |
Accept Wildcard Characters? |
false |
-Datasource<Datasource>
Specifies a data source object for which this cmdlet starts a consistency check. A data source can be a file system share or volume for the Windows operating system, Microsoft SQL Server database, Microsoft Exchange Server storage group, Microsoft SharePoint farm, Microsoft Virtual Machine, DPM database, or system state that is a member of a protection group.
Aliases |
none |
Required? |
true |
Position? |
1 |
Default Value |
none |
Accept Pipeline Input? |
True (ByValue) |
Accept Wildcard Characters? |
false |
-ForcedFullCC
Indicates that this cmdlet performs a heavyweight consistency check on all databases in the farm, not just on the databases in an inconsistent state. This option is specific to SharePoint.
Aliases |
none |
Required? |
false |
Position? |
named |
Default Value |
none |
Accept Pipeline Input? |
false |
Accept Wildcard Characters? |
false |
-HeavyWeight
Indicates that the cmdlet performs a heavyweight consistency check. A heavyweight consistency check creates a checksum for the contents of each file. This parameter affects only file servers. The cmdlet always performs heavyweight consistency checks on application servers.
Aliases |
none |
Required? |
false |
Position? |
named |
Default Value |
none |
Accept Pipeline Input? |
false |
Accept Wildcard Characters? |
false |
-JobStateChangedEventHandler<JobStateChangedEventHandler>
Specifies an event handler for Job.StateChanged events. Use this parameter to build a graphical user interface based on cmdlets. Do not use this parameter in the DPM Management Shell.
Aliases |
Handler |
Required? |
false |
Position? |
named |
Default Value |
none |
Accept Pipeline Input? |
false |
Accept Wildcard Characters? |
false |
-ProtectionGroup<ProtectionGroup>
Specifies a protection group which contains data sources on which this cmdlet runs a check. To obtain a ProtectionGroup object, use the Get-DPMProtectionGroup cmdlet.
Aliases |
none |
Required? |
true |
Position? |
1 |
Default Value |
none |
Accept Pipeline Input? |
True (ByValue) |
Accept Wildcard Characters? |
false |
-Confirm
Prompts you for confirmation before running the cmdlet.
Required? |
false |
Position? |
named |
Default Value |
false |
Accept Pipeline Input? |
false |
Accept Wildcard Characters? |
false |
-WhatIf
Shows what would happen if the cmdlet runs. The cmdlet is not run.
Required? |
false |
Position? |
named |
Default Value |
false |
Accept Pipeline Input? |
false |
Accept Wildcard Characters? |
false |
<CommonParameters>
This cmdlet supports the common parameters: -Verbose, -Debug, -ErrorAction, -ErrorVariable, -OutBuffer, and -OutVariable. For more information, see about_CommonParameters (https://go.microsoft.com/fwlink/p/?LinkID=113216).
Inputs
The input type is the type of the objects that you can pipe to the cmdlet.
Outputs
The output type is the type of the objects that the cmdlet emits.
Examples
Example 1: Start a consistency check on a data source
The first command gets the protection groups from the server named TestingServer by using the Get-DPMProtectionGroup cmdlet. The command stores them in the $PGroup variable.
The second command gets the data source for the first protection group in $PGroup, and then stores the data source in the $Ds variable.
The third command runs a consistency check on the data source that is stored in $Ds.
PS C:\> $PGroup = Get-DPMProtectionGroup -DPMServerName TestingServer
PS C:\> $PObject = Get-DPMDatasource $PGroup[0]
PS C:\> Start-DPMDatasourceConsistencyCheck -Datasource $PObject