.png)
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.
An AWS bug in the NVM drivers on C5 and M5 instance types may cause replication issues in source machines hosted on AWS. Users who experience the bug will have Data ReplicationThe process of copying all data blocks from selected disks on a Source Machine to Staging Disks. stuck at 0% on the CloudEndure User ConsoleCloudEndure SaaS User Interface. A web-based UI for setting up, managing, and monitoring the Migration and Disaster Recovery solutions..
To verify if the NVM drivers are working properly on 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. run:
Get-Disk | Select Number,SerialNumber | Sort-Object Number
Ensure that the output matches the output shown in the AWS documentation.
If there is a driver issue, the output will only contain zeros.
If there's a problem the output will contain only zero's -
Number SerialNumber
------ ------------
0 0000_0000_0000_0000.
1 0000_0000_0000_0000.
2 0000_0000_0000_0000.
3 0000_0000_0000_0000.
4 0000_0000_0000_0000.
5 0000_0000_0000_0000.
6 0000_0000_0000_0000.
If this is the case, then something is not functioning correctly on the machineA physical or virtual computer. as it does not felt the proper EBS volume IDs.
You can fix this issue by reinstalling the NVM drivers.
Once the issue is fixed and the expected output is returned, Data ReplicationThe process of copying all data blocks from selected disks on a Source Machine to Staging Disks. will start.
©2020 COPYRIGHT CloudEndure - Terms of Service - Privacy Policy - AWS Vulnerability Reporting Guidelines - Report a Security Issue