Skip to content

Commit e2cf307

Browse files
authored
Merge pull request #206353 from Sharmistha-Rai/main
Time change TSG
2 parents 6c1a7e3 + 642e5c4 commit e2cf307

File tree

2 files changed

+12
-0
lines changed

2 files changed

+12
-0
lines changed

articles/site-recovery/azure-to-azure-troubleshoot-errors.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -571,6 +571,12 @@ Perform the following steps to fix this issue.
571571
`./install -d /usr/local/ASR -r MS -q -v Azure`
572572
6. If the installer succeeds, retry the enable replication job.
573573
574+
## Troubleshoot and handle time changes on replicated servers
575+
This error occurs when the source machine's time moves forward and then moves back in short time, to correct the change. You may not notice the change as the time is corrected very quickly.
576+
577+
**How to fix**:
578+
To resolve this issue, wait till system time crosses the skewed future time. Another option is to disable and enable replication once again, which is only feasible for forward replication (data replicated from primary to secondary region) and is not applicable for reverse replication (data replicated from secondary to primary region).
579+
574580
## Next steps
575581
576582
[Replicate Azure VMs to another Azure region](azure-to-azure-how-to-enable-replication.md)

articles/site-recovery/vmware-azure-troubleshoot-replication.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -208,6 +208,12 @@ This error occurs when trying to enable replication and the application folders
208208
- All the items under the below path -
209209
- *C:\thirdparty\rrdtool-1.2.15-win32-perl58\rrdtool\Release\**
210210

211+
## Troubleshoot and handle time changes on replicated servers
212+
This error occurs when the source machine's time moves forward and then moves back in short time, to correct the change. You may not notice the change as the time is corrected very quickly.
213+
214+
**How to fix**:
215+
To resolve this issue, wait till system time crosses the skewed future time. Another option is to disable and enable replication once again, which is only feasible for forward replication (data replicated from on-premises to Azure) and is not applicable for reverse replication (data replicated from Azure to on-premises).
216+
211217
## Next steps
212218

213219
If you need more help, post your question in the [Microsoft Q&A question page for Azure Site Recovery](/answers/topics/azure-site-recovery.html). We have an active community, and one of our engineers can assist you.

0 commit comments

Comments
 (0)