Skip to content

[Reference feedback]: CLI command to initiate adhoc backup documented to have rule name as required and others are optional which seems to be wrong #31183

@jeevanions

Description

@jeevanions

Type of issue

Other (describe below)

Reference command name

Command I used

az dataprotection backup-instance adhoc-backup \
    --rule-name "$BACKUP_POLICY_DEFAULT_RULE_NAME" \
    --resource-group "$VAULT_RG" \
    --vault-name "$VAULT_NAME" \
    --name "$BACKUP_INSTANCE"

I validated the parameter passed to this command and all are valid. Please advice which parameter is having issue. I tried to re-run this command with debug enabled after some time and still getting the blocked error message. I will update the debug log once Azure unblocks me.

This is so annoying that the error message are not providing any assistance.

Feedback

As per the documentation the ad-hoc backup command requires only the rule name and other parameters are marked as optional. The command doesnt work with just the rule name and the doc confuses even more.

I am using azure cli to trigger the adhoc backup and getting below error where it doesn't provide any clue which input has the issue.

(BMSUserErrorInvalidInput) Input provided for the call is invalid
Code: BMSUserErrorInvalidInput
Message: Input provided for the call is invalid
Additional Information:Type: UserFacingError
Info: {
    "message": "Input provided for the call is invalid",
    "recommendedAction": [
        "Please check the required inputs"
    ],
    "code": "BMSUserErrorInvalidInput",
    "target": "",
    "isRetryable": false,
    "isUserError": false,
    "properties": {
        "ActivityId": "a58d1782-0fdc-11f0-a975-4689437afdb3"
    }
}

On repeated attempts now ended up being blocked with below error message

(CloudDosTimeboudLimitReached) The operation is blocked, as a security precaution, since multiple attempts were made beyond an internal limit.
Code: CloudDosTimeboudLimitReached
Message: The operation is blocked, as a security precaution, since multiple attempts were made beyond an internal limit.
Additional Information:Type: UserFacingError
Info: {
    "message": "The operation is blocked, as a security precaution, since multiple attempts were made beyond an internal limit.",
    "recommendedAction": [
        "Please retry after few hours"
    ],
    "details": null,
    "code": "CloudDosTimeboudLimitReached",
    "target": "",
    "innerError": null,
    "isRetryable": false,
    "isUserError": false,
    "properties": {
        "ActivityId": "fb751cac-0fdd-11f0-9063-4689437afdb3"
    }
}

I am trying to take a backup of the Azure postgresql flexible server and could trigger a backup from Azure portal.

Command I used

az dataprotection backup-instance adhoc-backup \
    --rule-name "$BACKUP_POLICY_DEFAULT_RULE_NAME" \
    --resource-group "$VAULT_RG" \
    --vault-name "$VAULT_NAME" \
    --name "$BACKUP_INSTANCE"

I validated the parameter passed to this command and all are valid. Please advice which parameter is having issue. I tried to re-run this command with debug enabled after some time and still getting the blocked error message. I will update the debug log once Azure unblocks me.

This is so annoying that the error message are not providing any assistance.

Page URL

https://learn.microsoft.com/en-us/cli/azure/dataprotection/backup-instance?view=azure-cli-latest#az-dataprotection-backup-instance-adhoc-backup

Content source URL

https://github.com/MicrosoftDocs/azure-docs-cli/blob/main/docs-ref-autogen/Latest-version/latest/dataprotection/backup-instance.yml

Author

@mikefrobbins

Document Id

0567f838-4a61-00e0-fc9c-5348e1ce0fcf

Metadata

Metadata

Assignees

No one assigned

    Labels

    Data ProtectionService AttentionThis issue is responsible by Azure service team.customer-reportedIssues that are reported by GitHub users external to the Azure organization.needs-triageThis is a new issue that needs to be triaged to the appropriate team.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions