AWS mgn: Add troubleshooting for too many volumes selected for replication
Summary
Adds a new troubleshooting section explaining the 'too many volumes selected for replication' error (63-disk limit) and fixes minor grammar in existing troubleshooting text.
Security assessment
The change documents a replication limit and corrects grammar; it has no authentication, encryption, or vulnerability content.
Evidence
+The AWS Replication Agent can replicate up to 63 disks from a single source server. To resolve this error, select 63 or fewer disks for replication and rerun the Agent Installer file.
Diff
diff --git a/mgn/latest/ug/Troubleshooting-Agent-Issues.md b/mgn/latest/ug/Troubleshooting-Agent-Issues.md index ec3bd894a..43ae6ec87 100644 --- a//mgn/latest/ug/Troubleshooting-Agent-Issues.md +++ b//mgn/latest/ug/Troubleshooting-Agent-Issues.md @@ -27,0 +28,10 @@ This type of error means that the agent was not installed on the source server, +### Error: too many volumes selected for replication + +Installation fails with an error similar to the following when you select more disks than the AWS Replication Agent supports: + + + The devices you entered span over more than 63 volumes. Up to 63 volumes are supported per machine. + Installation failed. + +The AWS Replication Agent can replicate up to 63 disks from a single source server. To resolve this error, select 63 or fewer disks for replication and rerun the Agent Installer file. + @@ -44 +54 @@ If it says 32-bit operating system, x86-based processor, then your computer does -If your OS is indeed 64-bit, then there may be other elements blocking the installation of your agent. The block is actually coming from the Windows Operating System itself. You would need to identify what the cause is. One of the way is running [sfc scan](https://support.microsoft.com/en-au/topic/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system-files-79aa86cb-ca52-166a-92a3-966e85d4094e). +If your OS is indeed 64-bit, then there may be other elements blocking the installation of your agent. The block is actually coming from the Windows Operating System itself. You would need to identify what the cause is. One of the ways is running [sfc scan](https://support.microsoft.com/en-au/topic/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system-files-79aa86cb-ca52-166a-92a3-966e85d4094e). @@ -271 +281 @@ If the AWS Replication Agent installation fails on Windows with the following er -Attempt to rerun the installer with PowerShell instead of CMD. At times, when the installer is ran in CMD, the AWS Secret Key does not get pasted properly into the installer and causes installation to fail. +Attempt to rerun the installer with PowerShell instead of CMD. At times, when the installer is run in CMD, the AWS Secret Key does not get pasted properly into the installer and causes installation to fail.