Get-VBRTapeRestoreAllContentDependentMedium

In this article

    Short Description

    Returns dependent tapes.

    Applies to

    Platform: VMware, Hyper-V

    Product Edition: Enterprise, Enterprise Plus, Veeam Universal License

    Syntax

    Get-VBRTapeRestoreAllContentDependentMedium -Medium <VBRTapeMedium[]>  [<CommonParameters>]

    Detailed Description

    This cmdlet returns dependent tapes that store other parts of the backup. You may want to run this cmdlet before you start the Start-VBRTapeCopy cmdlet, to get information on the dependent tapes.

    When a backup file does not fit on one tape, it is divided into parts and written to several tapes. These tapes are considered dependent.

    Parameters

    Parameter

    Description

    Type

    Required

    Position

    Accept Pipeline Input

    Medium

    Specifies an array of tapes. The cmdlet will return dependent tapes for the tapes from this array.

    Accepts the VBRTapeMedium[]object. To create this object, run the Get-VBRTapeMedium cmdlet.

    True

    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

    The cmdlet returns the VBRTapeCopyDependentMedium object that defines dependent tapes that store dependent parts of the backup files.

    Examples

    Getting Dependent Tapes for Specified Tape

    This example shows how to get tapes that are dependent on the 0021000C tape.

    $tape = Get-VBRTapeMedium -Name "0021000C"

    Get-VBRTapeRestoreAllContentDependentMedium -Medium $tape

    Perform the following steps:

    1. Run the Get-VBRTapeMedium cmdlet. Specify the Name parameter value. Save the result to the $tape variable.
    2. Run the Get-VBRTapeRestoreAllContentDependentMedium cmdlet. Set the $tape variable as the Medium parameter value.

    Related Commands

    Get-VBRTapeMedium

    I want to report a typo

    There is a misspelling right here:

     

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