参数名称 | 类型 | 必填 | 描述 |
---|
Action | String | 是 | 公共参数,本接口取值:AddVmIntoDataGuard。 |
Version | String | 是 | 公共参数,本接口取值:2016-03-04。 |
DataGuardId | String | 是 | 容灾分组ID 示例值:1dd1832f-219d-4d40-9997-3033b9e2ce21 |
InstanceId.N | String | 是 | 实例ID 示例值:13536cc1-0dbd-4741-87d3-f7abbb0db328 |
参数名称 | 类型 | 描述 |
---|
DataGuardResult | Object | |
Flag | Boolean | 示例值:true |
InstanceId | String | 示例值:802b09f4-7c54-4bb1-b47e-796dfa2ebab7 |
Message | String | |
RequestId | String | 示例值:8c7270da-daf1-41e6-93e6-ad44b1f8f7cf |
Return | Boolean | 示例值:true |
JSON格式
以下仅列出了接口业务逻辑相关的错误码,其他错误码详见公共错误码
错误码 | 错误信息 | Http状态码 | 描述 |
---|
DataGuardIdInvalid | DataGuardId is invalid | 400 | 容灾分组ID无效 |
ChargeTypeInvalidParameterValue | An invalid or out-of-range value was supplied for the "ChargeType" parameter. | 400 | “计费类型”参数的取值无效或者超出有效范围 |
NotSupportAddToDataGuard | The vm that has joined the dataGuard does not support joining again. | 400 | 已加入容灾分组的虚机不支持再次加入 |
VmStatusNotSupportAddToDataGuard | This VM status is not support add to dataGuard. | 400 | 此状态的云服务器不支持加入容灾组功能 |
DataGuardNotSupportStopCharging | 暂无 | 400 | 暂无 |
VMCountGreaterThanDataGuardCount | Create instance fail, because Data Guard Groups ({0}) has insufficient room | 400 | 创建失败,容灾组({0})的可用容量不足,请选择其他容灾组 |
VMNotSupportAddDamainDataGuard | 暂无 | 400 | 暂无 |
InstanceStateNotSupportedMigrate | The current status of the resource does not support this operation. | 400 | 本操作执行时“实例状态”不支持 |
ProductTypeInvalid | productType is invalid . | 400 | 产品类型无效 |
InstanceIdRequired | InstanceId is required | 400 | InstanceId必传 |
DataGuardIdRequired | DataGuardId is required | 400 | 容灾 8082 |
InstanceOpLockNotObtain | InstanceOpLockNotObtain | 400 | 当前实例在操作处理中,请稍后重试 |
InstanceOrderMustInUse | The "InstanceOrder" parameter must be used when calling directly from console. | 400 | 使用控制台调用必须传递“实例订单”参数 |
InstanceOrderNotInUse | The "InstanceOrder" parameter should not be used when calling directly from SDK or OpCenter. | 400 | 使用SDK或者运营平台调用不应该传递“实例订单”参数 |
纯净模式