Operations: advanceRelocateBucket

Initiates thefinal synchronization of abucket relocation operation that requires a write downtime. The server makes a best effort toproceed with the operation, but success is not guaranteed.

Users can useOperations: get to check the status of the operation.

Required permissions

You must have thestorage.buckets.relocate IAM permission on the bucket to initiate the final synchronization step.

You might also need the following permissions on the bucket:

  • storage.bucketOperations.get
    You need this permission to view the status of the bucket relocation operation.
  • storage.bucketOperations.list
    You need this permission to view the list of bucket relocation operations.
  • storage.bucketOperations.cancel
    You need this permission to cancel the bucket relocation operation.
  • storage.bucket.get
    You need this permission to view the metadata of a bucket during the final synchronization of the bucket relocation operation.
  • storage.objects.list andstorage.objects.get
    You need these permissions to view the list of objects in a bucket that you want to relocate to another location.

Request

HTTP request

POST https://storage.googleapis.com/storage/v1/b/bucket/operations/operationId/advanceRelocateBucket

In addition tostandard query parameters, the following query parameters apply to this method.

To see an example of how to include query parameters in a request, see theJSON API Overview page.

Parameters

Parameter nameValueDescription
Path parameters
bucketstring Name of a bucket.
operationIdstring

The ID of theBuckets: relocate long-running operation that initiated the bucket relocation. For example,AbCJYd8jKT1n-Ciw1LCNXIcubwvij_TdqO-ZFjuF2YntK0r74

Request body

In the request body, supply any one of the following properties:

Property nameValueDescriptionNotes
Optional parameters
ttlstring The Time to live (TTL) for the write downtime phase during a relocation process. It is expressed as a string, such as12h for 12 hours. Thettl duration determines the maximum allowed duration for the write downtime phase. If the write downtime exceeds this limit, the relocation process automatically reverts to the initate bucket relocation step, and write operations to the bucket are re-enabled. The value must be within the range of6h (6 hours) to48h (48 hours). If not specified, the default value is12h (12 hours).Writable
expire_timestring If the final synchronization fails, theexpire_time determines how long the process tries before switching back to the initiate bucket relocation step. The format ofexpire_time is a string in RFC 3339 format, such as2024-08-15T01:30:15.01Z.Writable

Response

If successful, this method returns an empty response body.

For information about status and error codes returned by this API, see thereference page.

Try it!

Use the APIs Explorer below to call this method on live data and see the response.

Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2026-02-19 UTC.