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.
Users may see changes in Windows drive letter assignments (ex. Drive D changed to E) on TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). machines launched by CloudEndure.
This happens because Windows sometimes re-configures the drive letters when a machineA physical or virtual computer. comes up on a new infrastructure, for example, if the Source machineThe computer, physical or virtual machine that needs to be protected by replication (Disaster Recovery) or migrated (Migration) The CloudEndure Agent is installed on the Source machine. had a drive letter mapped to a disk that was not replicated (such as a network drive). You can solve this issue by re-mapping the drive letters on the Target machineThe Machine created during Test, Cutover or Recovery. correctly after it has been launched, either manually or using the CloudEndure post_launch functionality.
©2020 COPYRIGHT CloudEndure - Terms of Service - Privacy Policy - AWS Vulnerability Reporting Guidelines - Report a Security Issue