Start-DatasourceConsistencyCheck

Start-DatasourceConsistencyCheck

Performs a consistency check on the specified data source.

Syntax

Start-DatasourceConsistencyCheck [-ProtectionGroup] <ProtectionGroup> [<CommonParameters>]


Start-DatasourceConsistencyCheck [-Datasource] <Datasource> [-ForcedFullCC <SwitchParameter>] [-HeavyWeight <SwitchParameter>] [-JobStateChangedEventHandler <JobStateChangedEventHandler>] [<CommonParameters>]

Detailed Description

The Check-Consistency cmdlet will perform a consistency check on the specified data source.

If you use -Datasource, DPM will perform consistency check for that data source.
If you use -ProtectionGroup, DPM will run a consistency check on all data sources in that protection group that are in an inconsistent state.

Parameters

-ProtectionGroup

The name of a protection group.

Attributes

Name Value

Required?

true

Accept wildcard characters?

false

Accept Pipeline Input?

true (ByValue)

Position?

0

-Datasource

A Windows file system share or volume, 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.

Attributes

Name Value

Required?

true

Accept wildcard characters?

false

Accept Pipeline Input?

true (ByValue)

Position?

0

-ForcedFullCC

Specific to SharePoint. Forces a heavy-weight consistency check on all the databases in the farm, not just the ones in inconsistent state.

Attributes

Name Value

Required?

false

Accept wildcard characters?

false

Accept Pipeline Input?

false

Position?

named

-HeavyWeight

Indicates that a heavy weight consistency check must be performed. This process checksums the contents of each file. This only affects file servers; consistency check on application servers is always performed as heavy-weight.

Attributes

Name Value

Required?

false

Accept wildcard characters?

false

Accept Pipeline Input?

false

Position?

named

-JobStateChangedEventHandler

The JobStateChangedEventHandler is used along with the -Async parameter so that the user can be informed of the status of the operation. This is useful when building a GUI using cmdlets. It is not used when working with the DPM Management Shell.

Attributes

Name Value

Required?

false

Accept wildcard characters?

false

Accept Pipeline Input?

false

Position?

named

-CommonParameter

This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, ErrorVariable, WarningAction, WarningVariable, OutBuffer, and OutVariable. For more information, see about_CommonParameters.

Input and Return Types

The input type is the type of the objects that you can pipe to the cmdlet. The return type is the type of the objects that the cmdlet emits.

Notes

  • For more information, type "Get-Help Check-Consistency -detailed".
    For technical information, type "Get-Help Check-Consistency -full".

    Additionally, any updated information about the cmdlet will be available at http://go.microsoft.com/fwlink/?LinkId=95130.

Examples