- Newest
- Most votes
- Most comments
Greetings ,
AWS Migration Hub and Migration Hub for Application Discovery Service (ADS) do not provide data replication services themselves. They are only used to monitor and track the status of your migration.
I believe you might be referring to AWS Server Migration Service (SMS) instead, which is a service that automates the process of migrating your on-premises servers to AWS. SMS uses an agent-based approach to replicate your server's data, which includes both the used and free disk space.
When you set up SMS, you select the disks that you want to migrate, and the service will replicate the data on those disks to an Amazon Elastic Block Store (EBS) volume in AWS. This EBS volume is created with the same size as the on-premises disk. However, SMS only replicates the used blocks, not the free blocks.
Therefore, SMS will only take the time necessary to copy the actual data blocks that are being used on your source server. The free blocks are not copied, which saves time and reduces the amount of data that needs to be transferred.
Keep in mind that SMS uses incremental replication, which means that only the changes made to the source server after the initial replication will be copied over to the target server. This ensures that the data on the target server remains in sync with the source server.
Please let me know if that helped your question
Relevant content
- asked 4 years ago
- asked 6 months ago
- asked 2 years ago
AWS OFFICIALUpdated 7 months ago- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
Hello Zokir, Thanks for the response. Yes. I am referring to SMS and my understanding was also the same that SMS agent don't replicates free space blocks. However, what I observe is, server did not go in "Ready for Testing" phase once data replication of "Used Space" is completed. Server was in initial replication stage and when I check replication status of individual disks, it was replicating entire space and not just the used space.
Let me know if any logs I need to check or should I reach out to AWS tech support for this case. Thanks.
hi,
AWS SMS should only replicate used blocks of the source server, not the free space. However, you mentioned that the replication status is showing the entire space being replicated.
Before reaching out to AWS tech support, you can try the following steps:
Verify the replication settings: Double-check the replication settings to ensure that they are configured as intended. Ensure that you have followed the recommendations: www.docs.aws.amazon.com/server-migration-service/latest/userguide/server-migration.html
Review logs: Examine the logs generated by the AWS SMS agent installed on the source server. The logs can be found in the following locations:
Windows: %PROGRAMDATA%\Aws\SmsAgent\logs
Linux: /var/log/aws/sms/ Look for any errors, warnings, or unusual behavior in the logs that may explain the replication behavior you're experiencing.
Check disk configuration: Verify the disk configuration of your source server to ensure that there are no unusual configurations or discrepancies that could be affecting the replication process. For example, check for RAID configurations, disk partitioning, or file system issues. If you're still unable to identify the cause of the issue after trying these steps, it's a good idea to reach out to AWS tech support. Provide them with the relevant details, logs, and your observations, and they can help you investigate the issue further. Please let me know if I answered your question