Resynchronizing Clone

POST /volume/{volume_id}/resync/{backup_volume_id}

Introduction

Starts a Clone resynchronization.

Instructs QuickOPC Session which has already started to restart (copy of the update).

Caution

  • When the Clone resynchronization is created, the state of the Job becomes Success. An differential copy of the physical data is performed in the background. The source and destination volumes are accessible while the physical data is being copied.

  • Write access to the source Volume may be degraded during background copying of differential data.

  • You can check the progress of the background copy of the differential data in "GET /volume/copysession" or "GET /copysession".

  • For tenant users, resynchronization cannot be performed if the copy source volume does not belong to the tenant of the current user.

Request Examples

  • This is an example of starting a Volume ID 100001 Clone (Volume ID 200001) resynchronization.
    $ curl -i -H "Authorization: Bearer g17e4umvwYoHuhkG7yCSee.." -X POST "https://192.168.1.1:5665/api/v1/volume/100001/resync/200001"

Response Examples

{
  "job_id": 8192001,
  "job_href": "/api/v1/job/8192001"
}

Parameters

PATH PARAMETERS

volume_id

(required)

integer

Volume ID.
backup_volume_id

(required)

integer

Volume ID of the backup volume.

Responses

If the job registration is successful, the HTTP status code will be 202 (Accepted) and the response body will respond.

RESPONSE BODY

job_id

integer

Job ID.
job_href

string

Resource link of the job.