Skip to content

Commit ff142f4

Browse files
authored
Updated the details for time required to reprotect premium disks
Added more rows to highlight the differences between different types of disks (standard vs. premium) and different levels of populated data on the disks.
1 parent 2a11e0b commit ff142f4

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

articles/site-recovery/azure-to-azure-how-to-reprotect.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -82,8 +82,12 @@ The following conditions determine how much data is replicated:
8282

8383
|Example situation | Time taken to reprotect |
8484
|---|---|
85-
|Source region has 1 VM with 1 TB standard disk.<br/>Only 127 GB data is used, and the rest of the disk is empty.<br/>Disk type is standard with 60 MiB/S throughput.<br/>No data change after failover.| Approximate time: 45 minutes – 1.5 hours.<br/>During reprotection, Site Recovery will populate the checksum of all data that will take 127 GB/ 45 MBs, approximately 45 minutes.<br/>Some overhead time is required for Site Recovery to auto scale, approximately 20-30 minutes.<br/>No Egress charges. |
86-
|Source region has 1 VM with 1 TB standard disk.<br/>Only 127 GB data is used and rest of the disk is empty.<br/>Disk type is standard with 60 MiB/S throughput.<br/>45 GB data changes after failover.| Approximate time: 1 hour – 2 hours.<br/>During reprotection, Site Recovery will populate the checksum of all data that will take 127 GB/ 45 MBs, approximately 45 minutes.<br/>Transfer time to apply changes of 45 GB that is 45 GB/ 45 MBps, approximately 17 minutes.<br/>Egress charges would be for 45 GB data changes, not for the checksum. |
85+
|Source region has 1 VM with 1 TB standard disk.<br/>Only 127 GB data is used, and the rest of the disk is empty.<br/>Disk type is standard with 60 MBps throughput.<br/>No data change after failover.| Approximate time: 60-90 minutes.<br/> During reprotection, Site Recovery will populate the checksum of all data. This operates at 45MBps, so the total time that it will take is 127 GB/45 MBps, approximately 45 minutes.<br/>Some overhead time is required for Site Recovery to auto scale, approximately 20-30 minutes. |
86+
|Source region has 1 VM with 1 TB standard disk.<br/>Only 127 GB data is used and rest of the disk is empty.<br/>Disk type is standard with 60 MBps throughput.<br/>45 GB data changes after failover.| Approximate time: 2.5-3 hours.<br/> During reprotection, Site Recovery will populate the checksum of all data. This operates at 45MBps, so the total time that it will take is 127 GB/45 MBps, approximately 45 minutes.<br/>Transfer speed is approximately 16% of throughput, or 9.6MBps. Therefore, transfer time to apply changes of 45 GB that is 45 GB/9.6 MBps, approximately 80 minutes.<br/>Some overhead time is required for Site Recovery to auto scale, approximately 20-30 minutes. |
87+
|Source region has 1 VM with 1 TB standard disk.<br/>Only 20 GB data is used and rest of the disk is empty.<br/>Disk type is standard with 60 MBps throughput.<br/>The initial data on the disk immediately after failover was 15 GB. There was 5 GB data change after failover. Total populated data is therefore 20 GB.| Approximate time: 1-1.5 hours.<br/>Since the data populated in the disk is less than 10% of the size of the disk, we perform a complete initial replication.<br/> Transfer speed is approximately 16% of throughput, or 9.6MBps. Therefore, transfer time to apply changes of 20 GB that is 20 GB/9.6 MBps, approximately 36 minutes.<br/>Some overhead time is required for Site Recovery to auto scale, approximately 20-30 minutes. |
88+
|Source region has 1 VM with 1 TB premium disk.<br/>Only 127 GB data is used, and the rest of the disk is empty.<br/>Disk type is premium with 200 MBps throughput.<br/>No data change after failover.| Approximate time: 45-60 minutes.<br/>During reprotection, Site Recovery will populate the checksum of all data. This operates at 80MBps, so the total time that it will take is 127 GB/80 MBps, approximately 27 minutes.<br/>Some overhead time is required for Site Recovery to auto scale, approximately 20-30 minutes. |
89+
|Source region has 1 VM with 1 TB premium disk.<br/>Only 127 GB data is used and rest of the disk is empty.<br/>Disk type is premium with 200 MBps throughput.<br/>45 GB data changes after failover.| Approximate time: 1.5-2 hours.<br/>During reprotection, Site Recovery will populate the checksum of all data. This operates at 80MBps, so the total time that it will take is 127 GB/80 MBps, approximately 27 minutes.</br>Transfer speed is approximately 16% of throughput, or 32MBps. Therefore, transfer time to apply changes of 45 GB that is 45 GB/32 MBps, approximately 24 minutes.<br/>Some overhead time is required for Site Recovery to auto scale, approximately 20-30 minutes. |
90+
|Source region has 1 VM with 1 TB premium disk.<br/>Only 20 GB data is used and rest of the disk is empty.<br/>Disk type is premium with 200 MBps throughput.<br/>The initial data on the disk immediately after failover was 15 GB. There was 5 GB data change after failover. Total populated data is therefore 20 GB| Approximate time: 30-45 minutes.<br/>Since the data populated in the disk is less than 10% of the size of the disk, we perform a complete initial replication.<br/>Transfer speed is approximately 16% of throughput, or 32MBps. Therefore, transfer time to apply changes of 20 GB that is 20 GB/32 MBps, approximately 11 minutes.<br/>Some overhead time is required for Site Recovery to auto scale, approximately 20-30 minutes |
8791

8892
When the VM is re-protected after failing back to the primary region (i.e., if the VM is re-protected from primary region to DR region), the target VM and associated NIC(s) are deleted.
8993

0 commit comments

Comments
 (0)