AWS drs documentation change
Summary
Multiple typo fixes and minor text corrections in the Agent-Related FAQ, including grammar fixes and removal of duplicate punctuation
Security assessment
These are purely editorial changes fixing typos and grammar. No security-related content was added, removed, or modified. The changes include fixing 'data no longer in memory' to 'data is no longer in memory', removing duplicate question marks, and correcting 'underline' to 'underlying'. None of these changes indicate security fixes or security feature documentation.
Diff
diff --git a/drs/latest/userguide/Agent-Related-FAQ.md b/drs/latest/userguide/Agent-Related-FAQ.md index 7599bce85..8eee8e7bb 100644 --- a//drs/latest/userguide/Agent-Related-FAQ.md +++ b//drs/latest/userguide/Agent-Related-FAQ.md @@ -7 +7 @@ -What does the AWS Replication Agent do?What kind of data is transferred between the Agent and the AWS Elastic Disaster Recovery Service Manager?Can a proxy server be used between the source server and the Elastic Disaster Recovery Console?What are the pre-requisites needed to install the AWS Replication Agent?What ports does the AWS Replication Agent utilize?What kind of resources does the AWS Replication Agent utilize?Can Elastic Disaster Recovery migrate containers?Does the AWS Replication Agent cache any data to disk?How is communication between the AWS Replication Agent and the Elastic Disaster Recovery Service Manager secured?Is it possible to change the port the AWS Replication Agent utilizes from TCP Port 1500 to a different port?How do I manually uninstall the Elastic Disaster Recovery Agent from a server?When do I need to reinstall the Agent?How much bandwidth does the AWS Replication Agent consume?How many disks can the AWS Replication Agent replicate?Is it possible to add a disk to replication without a complete resync of any disks that have already been replicated??Which Windows and Linux OSs support no-rescan upon reboot?No-Rescan Upon Reboot LimitationsHow do temporary credentials work?Where can I find the AWS DRS Replication Agent logs +What does the AWS Replication Agent do?What kind of data is transferred between the Agent and the AWS Elastic Disaster Recovery Service Manager?Can a proxy server be used between the source server and the Elastic Disaster Recovery Console?What are the pre-requisites needed to install the AWS Replication Agent?What ports does the AWS Replication Agent utilize?What kind of resources does the AWS Replication Agent utilize?Can Elastic Disaster Recovery migrate containers?Does the AWS Replication Agent cache any data to disk?How is communication between the AWS Replication Agent and the Elastic Disaster Recovery Service Manager secured?Is it possible to change the port the AWS Replication Agent utilizes from TCP Port 1500 to a different port?How do I manually uninstall the Elastic Disaster Recovery Agent from a server?When do I need to reinstall the Agent?How much bandwidth does the AWS Replication Agent consume?How many disks can the AWS Replication Agent replicate?Is it possible to add a disk to replication without a complete resync of any disks that have already been replicated?Which Windows and Linux OSs support no-rescan upon reboot?No-Rescan Upon Reboot LimitationsHow do temporary credentials work?Where can I find the AWS DRS Replication Agent logs @@ -85 +85 @@ Elastic Disaster Recovery does not write any cache or do any sort of journalling -The Agent then acts as a sort of write filter and will replicate changed blocks directly from memory to the replication server. In cases where the data no longer in memory, the Agent will read the block from the volume directly. This is the case where you may see backlog in the Elastic Disaster Recovery Console. The cause of this is the volume of change is greater than the bandwidth available. +The Agent then acts as a sort of write filter and will replicate changed blocks directly from memory to the replication server. In cases where the data is no longer in memory, the Agent will read the block from the volume directly. This is the case where you may see backlog in the Elastic Disaster Recovery Console. The cause of this is the volume of change is greater than the bandwidth available. @@ -122 +122 @@ The Agent can replicate up to 50 disks from a single server. Ensure that the rep -## Is it possible to add a disk to replication without a complete resync of any disks that have already been replicated?? +## Is it possible to add a disk to replication without a complete resync of any disks that have already been replicated? @@ -126 +126 @@ When you add a disk to a source server, AWS Elastic Disaster Recovery will autom -This feature is activated automatically for newly added servers. [Learn how to deactivate or reactivated this feature.](./volumes-drs.html#auto-replicate) +This feature is activated automatically for newly added servers. [Learn how to deactivate or reactivate this feature.](./volumes-drs.html#auto-replicate) @@ -132 +132 @@ A shutdown (from the OS menu or CLI) of any supported Linux or Windows source se -Rescans can still happen following a hard reboot, crashes, or when you add or remove disks to or from the source server. In addition, a rescan will occur if the underline Storage types do not use static [DUIDs ](https://learn.microsoft.com/en-us/windows-hardware/drivers/storage/device-unique-identifiers--duids--for-storage-devices) (such as 3PARdata). Supported OSs include: +Rescans can still happen following a hard reboot, crashes, or when you add or remove disks to or from the source server. In addition, a rescan will occur if the underlying Storage types do not use static [DUIDs ](https://learn.microsoft.com/en-us/windows-hardware/drivers/storage/device-unique-identifiers--duids--for-storage-devices) (such as 3PARdata). Supported OSs include: