Step 2: Failed to create a replication server

Important! The information provided in this section is for general Troubleshooting guidance only. The information is provided on "AS IS" basis, with no guarantee of completeness, accuracy or timeliness, and without warranty or representations of any kind, expressed or implied. In no event will CloudEndure and/or its subsidiaries and/or their employees or service providers be liable to you or anyone else for any decision made or action taken in reliance on the information provided above or for any direct, indirect, consequential, special or similar damages (including any kind of loss), even if advised of the possibility of such damages. CloudEndure is not responsible for the update, validation or support of troubleshooting information.

Possible causes for failure

1. Insufficient permissions in the provided Cloud CredentialsAccount login information, including the Username and Password. (navigate to Setup & Info > Credentials).
2. The subnet configured for the Replication ServersThe CloudEndure Machine to which Staging Disks are attached and to which data is replicated; launched on the Target location. does not exist.
3. You reached the machines number limit in your TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). infrastructure, as defined by the cloud provider.

• Make sure that your IAM policy is correct and that you are not over-quota for ‘t2.small’ instances (AWS) in your Staging AreaA part of the Target location; includes the Replication Servers’ subnet, IPs, and the Replication Servers and their disks. region.