Details of EVS Replication failure_detail Values (Deprecated)¶
EVS Replication Pair¶
failure_detail Value | Description | Cause | Solution |
|---|---|---|---|
37100041 | Failed to create the EVS replication pair because the production disk capacity is inconsistent with the DR disk capacity. | The production disk capacity is inconsistent with the DR disk capacity. | Ensure that the capacities of the production and DR disks are consistent before you create the EVS replication pair. |
37100043 | The operation fails because messages failed to be sent to the peer AZ. | A communication error occurred. | Contact technical support to check whether the link status is normal. |
37100044 | Failed to create the EVS replication pair because the specified production disk is a lazyloading EVS disk. | Lazyloading EVS disks cannot be used as member disks of EVS replication pairs. | Wait until the lazyloading process is complete and try again. If the fault persists, contact technical support. |
37100045 | Failed to create the EVS replication pair because the specified DR disk is a lazyloading EVS disk. | Lazyloading EVS disks cannot be used as member disks of EVS replication pairs. | Wait until the lazyloading process is complete and try again. If the fault persists, contact technical support. |
37100048 | Failed to create the EVS replication pair because the specified production disk does not exist. | The specified production disk does not exist. | Specify an existing production disk. |
37100050 | Failed to create the EVS replication pair because the specified DR disk does not exist. | The specified DR disk does not exist. | Specify an existing DR disk. |
37100053 | Failed to create the EVS replication pair because the specified production disk has been used in another EVS replication pair. | The specified production disk is the member disk in another EVS replication pair. | Specify a production disk that has not been used by another EVS replication pair. |
37100054 | Failed to create the EVS replication pair because the specified DR disk has been used in another EVS replication pair. | The specified DR disk is the member disk in another EVS replication pair. | Specify a DR disk that has not been used by another EVS replication pair. |
37100058 | Failed to create the EVS replication pair because the DR disk has been attached to a server and the server is in the Running state. | The specified DR disk has been attached to a server and the server is in the Running state. | Stop the server , or specify a DR disk that has not been attached to any server. |
37100177 | Failed to create the EVS replication pair because the storage pool status of the primary AZ is abnormal. | The storage pool status of the primary AZ is abnormal. | Create the EVS replication pair when the storage pool status is normal. If the fault persists, contact technical support. |
37100178 | Failed to create the EVS replication pair because the storage pool status of the secondary AZ is abnormal. | The storage pool status of the secondary AZ is abnormal. | Create the EVS replication pair when the storage pool status is normal. If the fault persists, contact technical support. |
37000212 | System internal processing failure. | An internal system error occurred. | Contact technical support. |
37000216 | The system is busy. Try again later. | The system is busy. Try again later. | Try again later. If the fault persists, contact technical support. |
Replication Consistency Group¶
failure_detail Value | Description | Cause | Solution |
|---|---|---|---|
37100017 | Failed to create the replication consistency group because the number of replication consistency groups in the primary AZ has reached the upper limit. | The number of replication consistency groups in the primary AZ has reached the upper limit. | Contact technical support. |
37100043 | The operation fails because messages failed to be sent to the peer AZ. | The communication between the primary AZ and secondary AZ fails. | Contact technical support to check whether the link status is normal. |
37100159 | Failed to create the replication consistency group because the number of replication consistency groups in the secondary AZ has reached the upper limit. | The number of replication consistency groups in the secondary AZ has reached the upper limit. | Contact technical support. |
37000212 | System internal processing failure. | An internal system error occurred. | Contact technical support. |
37000216 | The system is busy. Try again later. | The system is busy. Try again later. | Try again later. If the fault persists, contact technical support. |