Disable-VBRCapacityExtentSealedMode

Short Description

Disable sealed mode for the capacity extent.

Applies to

Product Edition: Standard, Enterprise, Enterprise Plus, Veeam Universal License

Syntax

Disable-VBRCapacityExtentSealedMode -CapacityExtent <VBRCapacityExtent[]> [-RunAsync]  [<CommonParameters>]

Detailed Description

This cmdlet disables sealed mode for the capacity extent of the scale-out backup repository.

Run the Enable-VBRCapacityExtentSealedMode cmdlet to enable the sealed mode for the capacity extent of the scale-out backup repository.

Parameters

Parameter

Description

Type

Required

Position

Accept Pipeline Input

CapacityExtent

Specifies a capacity extents of scale-out backup repository. The cmdlet will disable sealed mode for the specified capacity extent.

Accepts the VBRCapacityExtent[] object. To get this object, run the Get-VBRCapacityExtent cmdlet.

True

Named

True (ByValue, ByPropertyName)

RunAsync

Indicates that the command returns immediately without waiting for the task to complete.

SwitchParameter

False

Named

False

<CommonParameters>

This cmdlet supports Microsoft PowerShell common parameters. For more information on common parameters, see the About CommonParameters section of Microsoft Docs.

Output Object

None

Examples

Disabling Sealed Mode for Capacity Extent

This example shows how to enable sealed mode for the specified capacity extent of the scale-out backup repository.

$repository = Get-VBRBackupRepository -ScaleOut

$extent = Get-VBRCapacityExtent

Disable-VBRCapacityExtentSealedMode -CapacityExtent $extent

Perform the following steps:

  1. Run the Get-VBRBackupRepository cmdlet. Provide the ScaleOut parameter. Save the result to the $repository variable.
  2. Run the Get-VBRCapacityExtent cmdlet. Save the result to the $extent variable.
  3. Run the Disable-VBRCapacityExtentSealedMode cmdlet. Set the $extent variable as the CapacityExtent parameter value.

Related Commands

I want to report a typo

There is a misspelling right here:

 

I want to let the Veeam Documentation Team know about that.