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.
The required bandwidth for transferring the replicated data over TCP Port 1500 should be based on the write speed of the participating SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure. machines. The recommended bandwidth should be at least the sum of the average write speed of all replicated SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure. machines.
Minimal bandwidth = the sum of the write speed of all SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure. machines
For example, suppose you are replicating two SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure. machines. One has a write speed of 5 MBps (meaning it 5 megabytes of data every second), while the other has 7 MBps. In this case, the recommended bandwidth should be at least 12 MBps.
To calculate the required bandwidth for transferring replicated data over TCP Port 1500, you need to know the write speed of your SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure. machines. Use the following tools to find the write speed of your Source machines:
iostat command-line utility, located in the systat package. The iostat utility monitors system input/output device loading and generates statistical reports.iostat utility is installed with yum (RHEL/CentOS), via apt-get (Ubuntu), and via zypper (SUSE.)iostat for checking the write speed of a 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., enter the following:-x - displays extended statistics.<interval> - the number of seconds iostat waits between each report. Each subsequent report covers the time since the previous report.For example, to check the write speed of a machineA physical or virtual computer. every 3 seconds, enter the following command:iostat -x 3
We recommend that you run the iostat utility for at least 24 hours, since the write speed to the disk changes during the day, and it will take 24 hours of runtime to identify the average running speed.
DiskMon application. DiskMon logs and displays all hard disk activity on a Windows system. ©2020 COPYRIGHT CloudEndure - Terms of Service - Privacy Policy - AWS Vulnerability Reporting Guidelines - Report a Security Issue