Remove-VBRGoogleCloudAccount

In this article

    Short Description

    Removes Google Cloud credentials records from Veeam Backup & Replication.

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

    Syntax

    Remove-VBRGoogleCloudAccount -Account <VBRGoogleCloudAccount> [-WhatIf] [-Confirm]  [<CommonParameters>]

    Detailed Description

    This cmdlet removes Google Cloud credentials records from Veeam Backup & Replication.

    Parameters

    Parameter

    Description

    Type

    Required

    Position

    Accept
    Pipeline
    Input

    Account

    Specifies Google Cloud credentials records that you want to remove.

    Accepts the VBRGoogleCloudAccount object. To create this object, run the Add-VBRGoogleCloudAccount cmdlet.

    True

    Named

    True (ByValue, ByPropertyName)

    WhatIf

    Defines whether the cmdlet writes a message that describes the effects of running the cmdlet without actually performing any action.

    SwitchParameter

    False

    Named

    False

    Confirm

    Defines whether the cmdlet displays a prompt that asks if the user is sure that they want to continue.

    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

    Removing Google Cloud Credentials Record

    This example shows how to remove a Google Cloud credentials record.

    $creds = Get-VBRGoogleCloudAccount -AccessKey "ABCDEFGHIGKLMNOP"

    Remove-VBRGoogleCloudAccount -Account $creds

    Perform the following steps:

    1. Run the Get-VBRGoogleCloudAccount cmdlet. Save the result to the $creds variable.
    2. Run the Remove-VBRGoogleCloudAccount cmdlet. Set the $creds variable as the Account parameter value.

    Related Commands

    Get-VBRGoogleCloudAccount

    I want to report a typo

    There is a misspelling right here:

     

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