Required. The name of the BackupPlan to create. The name must be unique
for the specified project and location.The name must start with a lowercase
letter followed by up to 62 lowercase letters, numbers, or hyphens.
Pattern, /a-z{,62}/.
Required. The name of the BackupPlan to create. The name must be unique
for the specified project and location.The name must start with a lowercase
letter followed by up to 62 lowercase letters, numbers, or hyphens.
Pattern, /a-z{,62}/.
Required. The BackupPlan project and location in the format
projects/{project}/locations/{location}. In Cloud BackupDR locations
map to GCP regions, for example us-central1.
Required. The BackupPlan project and location in the format
projects/{project}/locations/{location}. In Cloud BackupDR locations
map to GCP regions, for example us-central1.
Optional. An optional request ID to identify requests. Specify a unique
request ID so that if you must retry your request, the server will know to
ignore the request if it has already been completed. The server will
guarantee that for at least 60 minutes since the first request.
For example, consider a situation where you make an initial request and t
he request times out. If you make the request again with the same request
ID, the server can check if original operation with the same request ID
was received, and if so, will ignore the second request. This prevents
clients from accidentally creating duplicate commitments.
The request ID must be a valid UUID with the exception that zero UUID is
not supported (00000000-0000-0000-0000-000000000000).
Optional. An optional request ID to identify requests. Specify a unique
request ID so that if you must retry your request, the server will know to
ignore the request if it has already been completed. The server will
guarantee that for at least 60 minutes since the first request.
For example, consider a situation where you make an initial request and t
he request times out. If you make the request again with the same request
ID, the server can check if original operation with the same request ID
was received, and if so, will ignore the second request. This prevents
clients from accidentally creating duplicate commitments.
The request ID must be a valid UUID with the exception that zero UUID is
not supported (00000000-0000-0000-0000-000000000000).
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-01-28 UTC."],[],[]]