AWS drs documentation change
Summary
Updated rescan documentation to provide detailed causes of rescans and OS support information
Security assessment
The changes clarify rescan behavior and triggers but do not address security vulnerabilities or introduce security features. The content focuses on operational aspects of replication processes.
Diff
diff --git a/drs/latest/userguide/Replication-Related-FAQ.md b/drs/latest/userguide/Replication-Related-FAQ.md index 9c4c30a39..5e209d1e3 100644 --- a//drs/latest/userguide/Replication-Related-FAQ.md +++ b//drs/latest/userguide/Replication-Related-FAQ.md @@ -5 +5 @@ -Can we set specific IP addresses for the replication server or conversion server in the AWS DRS staging area?What do Lag and Backlog mean during replication?Is the replicated data encrypted?How is the replication server provisioned and managed in the Staging Area? What type of replication server is utilized in the Elastic Disaster Recovery Staging Area? Does AWS Elastic Disaster Recovery compress data during replication? Are events that are generated by the AWS Elastic Disaster Recovery servers logged in Cloudtrail in AWS? How many snapshots does Elastic Disaster Recovery create? Does Elastic Disaster Recovery delete snapshots?How much capacity is allocated to the staging area? Why is 0.0.0.0:1500 added to inbound rules in the Staging Area? How long does a rescan take?Is the Elastic Disaster Recovery replication crash consistent? How can I perform an SSL connectivity and bandwidth test? +Can we set specific IP addresses for the replication server or conversion server in the AWS DRS staging area?What do Lag and Backlog mean during replication?Is the replicated data encrypted?How is the replication server provisioned and managed in the Staging Area? What type of replication server is utilized in the Elastic Disaster Recovery Staging Area? Does AWS Elastic Disaster Recovery compress data during replication? Are events that are generated by the AWS Elastic Disaster Recovery servers logged in Cloudtrail in AWS? How many snapshots does Elastic Disaster Recovery create? Does Elastic Disaster Recovery delete snapshots?How much capacity is allocated to the staging area? Why is 0.0.0.0:1500 added to inbound rules in the Staging Area? What should I know about rescans?Is the Elastic Disaster Recovery replication crash consistent? How can I perform an SSL connectivity and bandwidth test? @@ -75 +75,15 @@ AWS Elastic Disaster Recovery uses TCP Port 1500 for replication between the sou -## How long does a rescan take? +## What should I know about rescans? + +During a rescan, the agent on the source server rereads the data on all replicated disks and transmits any differences from the previously replicated data. A rescan is similar to the initial sync but is faster because only changes are replicated. The rescan speed depends on factors such as the size of the source disks and disk performance. A rescan is functioning normally as long as it’s progressing. + +Causes of rescans include: + + * Hard reboots/crashes. + + * Adding or removing disks or modifying the size of disks on the source server. + + * The OS is not supported for the no-rescan feature. Learn more in [Supported Windows operating systems](./Supported-Operating-Systems-Windows.html) and [Supported Linux operating systems](./Supported-Operating-Systems-Linux.html). + + * Writing data to disks while the Replication Agent driver is unhooked. + + @@ -77 +90,0 @@ AWS Elastic Disaster Recovery uses TCP Port 1500 for replication between the sou -A rescan may occur after a reboot of the source server. The rescan time will vary depending on the size of the source disks. The time depends on the performance of the disks (linear read), staging area disk performance, and the rate of write operations on the source server (which are sent in parallel with the rescan). The rescan is functioning normally as long as its moving forward and is not "stuck".