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. A data source may be a file system share or volume for Windows, Microsoft SQL Server database, Microsoft Exchange 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 the 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 checksums 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>
Indicates that the cmdlet displays the status of the to the user. Use the JobStateChangedEventHandler parameter along with the Async parameterto build a graphical user interface (GUI) by using cmdlets. Do not use it when you work with the DPM Management Shell.
Aliases |
none |
Required? |
false |
Position? |
named |
Default Value |
none |
Accept Pipeline Input? |
false |
Accept Wildcard Characters? |
false |
-ProtectionGroup<ProtectionGroup>
Specifies a protection group object.
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
This example starts a consistency check on a data source.
The first command gets the protection groups from the server named TestingServer and stores them in the variable named $Pg.
The second command gets the data source for the first protection group (stored in position 0) in $Pg and stores the data source in the variable named $Ds.
The third command runs a consistency check on the data source that is stored in $Ds.
PS C:\> $Pg = Get-ProtectionGroup –DPMServerName TestingServer
PS C:\> $Ds = Get-Datasource $Pg[0]
PS C:\> Start-DPMDatasourceConsistencyCheck -Datasource $Ds
Related topics
Get-Datasource
Get-ProtectionGroup