I have a few questions if anyone could help, that would be great.

1. IS there a way to stop the 6 hour timeout on replications to azure?

2. Is there a way for me to find out what is causing excessive replica sizes? I have an exchange 2013 server with both roles whacking out about 4gb every 15 minutes at least. this can go up to 14gb. There are only 200 mailboxes on the server and kaspersky antivirus / antispam.

3. What should i do about the page file? Should i create a seperate VHD and use that and exclude it from the replicas, or should the page file be left as is?

Thanks in advance for any help.

Hi,

#1 If the network bandwidth is there replication won't timeout. Can you please elaborate which 6 hour timeout are you referring to?

#2 Suggest to post the query in exchange forum.

#3 In one of our local test runs we observed that pagefile churn rate isn't that high for a Windows Server SKUs. I would suggest to resolve the exchange churn there-after focus on the pagefile. To further add to this - today ASR doesn't allow excluding VHDs though Hyper-V replica allows that - we are working on this. Please vote for the feature here so that we can prioritize the ask.

Thanks

Hi,

#1 If the network bandwidth is there replication won't timeout. Can you please elaborate which 6 hour timeout are you referring to?

#2 Suggest to post the query in exchange forum.

#3 In one of our local test runs we observed that pagefile churn rate isn't that high for a Windows Server SKUs. I would suggest to resolve the exchange churn there-after focus on the pagefile. To further add to this - today ASR doesn't allow excluding VHDs though Hyper-V replica allows that - we are working on this. Please vote for the feature here so that we can prioritize the ask.

Thanks

• Marked as answer by Ruturaj DhekaneMicrosoft employee, Owner 23 minutes ago

Hi,

#1 If the network bandwidth is there replication won't timeout. Can you please elaborate which 6 hour timeout are you referring to?

#2 Suggest to post the query in exchange forum.

#3 In one of our local test runs we observed that pagefile churn rate isn't that high for a Windows Server SKUs. I would suggest to resolve the exchange churn there-after focus on the pagefile. To further add to this - today ASR doesn't allow excluding VHDs though Hyper-V replica allows that - we are working on this. Please vote for the feature here so that we can prioritize the ask.

Thanks

• Marked as answer by Ruturaj DhekaneMicrosoft employee, Owner 29 minutes ago

Hi,

#1 If the network bandwidth is there replication won't timeout. Can you please elaborate which 6 hour timeout are you referring to?

#2 Suggest to post the query in exchange forum.

#3 In one of our local test runs we observed that pagefile churn rate isn't that high for a Windows Server SKUs. I would suggest to resolve the exchange churn there-after focus on the pagefile. To further add to this - today ASR doesn't allow excluding VHDs though Hyper-V replica allows that - we are working on this. Please vote for the feature here so that we can prioritize the ask.

Thanks

• Marked as answer by Ruturaj DhekaneMicrosoft employee, Owner Wednesday, July 15, 2015 6:49 AM

Hi,

#1 If the network bandwidth is there replication won't timeout. Can you please elaborate which 6 hour timeout are you referring to?

#2 Suggest to post the query in exchange forum.

#3 In one of our local test runs we observed that pagefile churn rate isn't that high for a Windows Server SKUs. I would suggest to resolve the exchange churn there-after focus on the pagefile. To further add to this - today ASR doesn't allow excluding VHDs though Hyper-V replica allows that - we are working on this. Please vote for the feature here so that we can prioritize the ask.

Thanks

• Marked as answer by Ruturaj DhekaneMicrosoft employee, Owner Wednesday, July 15, 2015 6:49 AM

Hi,

#1 If the network bandwidth is there replication won't timeout. Can you please elaborate which 6 hour timeout are you referring to?

#2 Suggest to post the query in exchange forum.

#3 In one of our local test runs we observed that pagefile churn rate isn't that high for a Windows Server SKUs. I would suggest to resolve the exchange churn there-after focus on the pagefile. To further add to this - today ASR doesn't allow excluding VHDs though Hyper-V replica allows that - we are working on this. Please vote for the feature here so that we can prioritize the ask.

Thanks

• Marked as answer by Ruturaj DhekaneMicrosoft employee, Owner Wednesday, July 15, 2015 6:49 AM

Hi,

#1 If the network bandwidth is there replication won't timeout. Can you please elaborate which 6 hour timeout are you referring to?

#2 Suggest to post the query in exchange forum.

#3 In one of our local test runs we observed that pagefile churn rate isn't that high for a Windows Server SKUs. I would suggest to resolve the exchange churn there-after focus on the pagefile. To further add to this - today ASR doesn't allow excluding VHDs though Hyper-V replica allows that - we are working on this. Please vote for the feature here so that we can prioritize the ask.

Thanks

• Marked as answer by Ruturaj DhekaneMicrosoft employee, Owner Wednesday, July 15, 2015 6:49 AM

For #1 you can also refer to the below KB to increase the bandwidth usage.

https://support.microsoft.com/en-us/kb/3056159

https://www.petri.com/microsoft-azure-site-recovery-bandwidth-requirements

I have the same "6 hour" timeout with replication.  Here in Australia where bandwidth is not great, it is not easy to get Expressroute connections to Azure.  If an incremental runs for more than 6 hours for a single VM, it will pause replication until it is manually reinstated.