Skip to content

Commit 093933f

Browse files
committed
Edits
1 parent 02f4bd2 commit 093933f

1 file changed

Lines changed: 10 additions & 8 deletions

File tree

support/windows-365/windows-365-bcdr-known-issues.md

Lines changed: 10 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -7,24 +7,26 @@ ms.topic: troubleshooting-known-issue
77
ms.service: windows-365
88
ms.custom:
99
- pcy:WinComm User Experience
10-
- sap:
10+
- sap:Windows 365 Enterprise Edition\Cloud PC Recovery\Disaster Recovery Issues
1111
---
1212
# Windows 365 BCDR known issues
1313

1414
## Summary
1515

16-
This article addresses a known issue related to Windows 365 Business Continuity and Disaster Recovery (BCDR) scenarios.
16+
This article addresses a known issue that's related to Windows 365 Business Continuity and Disaster Recovery (BCDR) scenarios.
1717

18-
## classic Outlook corruption after disaster recovery failback and failover
18+
## Classic Outlook is corrupted after disaster recovery failback and failover
1919

2020
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.
2121

2222
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.
2323

24-
### Solution
24+
### Workaround
2525

26-
To resolve this issue, follow these steps:
27-
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.
28-
2. **Long-term solution**:Switch to the new Outlook app. The new Outlook app uses a different caching mechanism that eliminates this synchronization issue.
26+
After you complete a failover or failback operation, delete the Cloud PC's OST file.
2927

30-
By applying these troubleshooting measures, you can address the issue and ensure smoother operation of Outlook in disaster recovery scenarios.
28+
This action forces Outlook to rebuild the search index and the offline cache of the mailbox. No user data is lost during this process.
29+
30+
### Resolution
31+
32+
Switch to the new Outlook app. The new Outlook app uses a different caching mechanism that eliminates this synchronization issue.

0 commit comments

Comments
 (0)