Skip to content

Commit f7a40d6

Browse files
committed
New issue on bcdr
1 parent 3064486 commit f7a40d6

File tree

2 files changed

+33
-0
lines changed

2 files changed

+33
-0
lines changed

support/windows-365/toc.yml

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -67,3 +67,7 @@ items:
6767
items:
6868
- name: Windows 365 Switch known issues
6969
href: windows-365-switch-known-issues.md
70+
- name: Windows 365 BCDR
71+
items:
72+
- name: Windows 365 BCDR known issues
73+
href: windows-365-bcdr-known-issues.md
Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
title: Windows 365 BCDR known issues
2+
description: This article provides troubleshooting steps for the recent known issues with Windows 365 disaster recovery
3+
author: kaushika-msft
4+
ms.author: kaushika
5+
ms.reviewer: kaushika; aradinger
6+
ms.date: 10/16/2025
7+
ms.topic: troubleshooting-known-issue
8+
ms.service: windows-365
9+
ms.custom: pcy:WinComm User Experience
10+
---
11+
# Windows 365 BCDR known issues
12+
13+
## Summary
14+
15+
This article addresses a known issue related to Windows 365 Business Continuity and Disaster Recovery (BCDR) scenarios.
16+
17+
## classic Outlook corruption after disaster recovery failback and failover
18+
19+
This issue occurs when the Outlook offline cache becomes corrupted after restoring a Cloud PC from a snapshot during a disaster recovery failover or upon failing back to the primary region post-disaster. Users may encounter an error message when starting Outlook.
20+
21+
The root cause lies in the synchronization process between the client and server. During a failover, the client and server become out of sync because the client on the snapshot reflects a past state relative to the server's current status. Although no data is lost, the process of re-synchronizing the Offline Storage Table (OST) file can take time.
22+
23+
### Solution
24+
25+
To resolve this issue, follow these steps:
26+
1. **Short-term solution**:Delete the OST file on the Cloud PC after completing a failover or failback. This action forces Outlook to rebuild the offline cache of the mailbox, along with the search index. No user data will be lost during this process.
27+
2. **Long-term solution**:Switch to the new Outlook app. The new Outlook app uses a different caching mechanism that eliminates this synchronization issue.
28+
29+
By applying these troubleshooting measures, you can address the issue and ensure smoother operation of Outlook in disaster recovery scenarios.

0 commit comments

Comments
 (0)