All Products
Search
Document Center

Server Migration Center:CutOverReplicationJob

Last Updated:Oct 29, 2024

Stops an incremental migration job that periodically runs. After you call this operation to stop an incremental migration job, the migration job is complete.

Operation description

Usage notes

  • The incremental migration job must be in the Waiting state.
  • After you call this operation, the incremental migration job no longer periodically runs. In the meantime, Server Migration Center (SMC) determines whether to perform a full data migration for the last time based on the value of the SyncData parameter. If you set the SyncData parameter to false, SMC releases intermediate resources without data migration before the migration job is complete. If you set the SyncData parameter to true, SMC performs a full data migration and releases intermediate resources before the migration job is complete.

Debugging

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

Authorization information

The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:

  • Operation: the value that you can use in the Action element to specify the operation on a resource.
  • Access level: the access level of each operation. The levels are read, write, and list.
  • Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
    • The required resource types are displayed in bold characters.
    • If the permissions cannot be granted at the resource level, All Resources is used in the Resource type column of the operation.
  • Condition Key: the condition key that is defined by the cloud service.
  • Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
OperationAccess levelResource typeCondition keyAssociated operation
smc:CutOverReplicationJobupdate
  • All Resources
    *
    none
none

Request parameters

ParameterTypeRequiredDescriptionExample
JobIdstringYes

The ID of the incremental migration job.

j-bp1fnx5y3djc4cop****
SyncDatabooleanNo

Specifies whether to migrate full data for the last time. Valid Values:

  • true: migrates full data for the last time.
  • false: does not migrate full data for the last time.

Default value: false.

false

Response parameters

ParameterTypeDescriptionExample
object

The request ID.

RequestIdstring

The request ID.

473469C7-AA6F-4DC5-B3DB-A3DC0DE3C83E

Examples

Sample success responses

JSONformat

{
  "RequestId": "473469C7-AA6F-4DC5-B3DB-A3DC0DE3C83E"
}

Error codes

HTTP status codeError codeError messageDescription
400ReplicationJob.InvalidStatusThe specified replication job status: %s is invalid. This operation can only be performed in the following status: %s.The specified replication job status: %s is invalid. This operation can only be performed in the following status: %s.
400ReplicationJob.InvalidBusinessStatusThe specified business status: %s of the replication job is invalid. This operation can only be performed in the following status: %s.The specified business status: %s of the replication job is invalid. This operation can only be performed in the following status: %s.
400SourceServerState.InvalidThe specified source server status: %s is invalid. This operation can only be performed in the following status: %s.The specified source server status: %s is invalid. This operation can only be performed in the following status: %s.
500InternalErrorAn error occurred while processing your request. Please try again. If the problem still exists, please submit a ticket.An error occurred while processing your request. Please try again. If the problem still exists, please submit a ticket.

For a list of error codes, visit the Service error codes.

Change history

Change timeSummary of changesOperation
2024-03-22The Error code has changedView Change Details