---
title: "POST /v2/{+parent}/backups:copy"
method: POST
path: "/v2/{+parent}/backups:copy"
tags: ["projects"]
---

# POST /v2/{+parent}/backups:copy

`POST /v2/{+parent}/backups:copy`

Copy a Cloud Bigtable backup to a new backup in the destination cluster located in the destination instance and project.

## Path parameters

- `parent` string, required

## Request body

- CopyBackupRequest — The request for CopyBackup.
  - `sourceBackup` string — Required. The source backup to be copied from. The source backup needs to be in READY state for it to be copied. Copying a copied backup is not allowed. Once CopyBackup is in progress, the source backup cannot be deleted or cleaned up on expiration until CopyBackup is finished. Values are of the form: `projects//instances//clusters//backups/`.
  - `backupId` string — Required. The id of the new backup. The `backup_id` along with `parent` are combined as {parent}/backups/{backup_id} to create the full backup name, of the form: `projects/{project}/instances/{instance}/clusters/{cluster}/backups/{backup_id}`. This string must be between 1 and 50 characters in length and match the regex _a-zA-Z0-9*.
  - `expireTime` string, google-datetime — Required. Required. The expiration time of the copied backup with microsecond granularity that must be at least 6 hours and at most 30 days from the time the request is received. Once the `expire_time` has passed, Cloud Bigtable will delete the backup and free the resources used by the backup.

## Response `200`

Successful response

---

[API](https://skmtc.net/google/apis/bigtableadmin.md) · [All operations](https://skmtc.net/google/apis/bigtableadmin/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/google/bigtableadmin/versions/d59c83bbbf1e/schema)