While the `isMeta` flag will solve this in the future, the current state requires us to filter out all meta and dirmeta files, even historically. --- #### Does this PR need a docs update or release note? - [x] ✅ Yes, it's included #### Type of change - [x] 🐛 Bugfix #### Issue(s) * #1970 #### Test Plan - [x] ⚡ Unit test - [x] 💚 E2E
1.1 KiB
Known issues
Below is a list of known Corso issues and limitations:
-
Only supports Exchange (email, calendars, contact) and OneDrive (files) M365 data. Additional data types and services will be added in subsequent releases.
-
Backups of Exchange email may not include changes to the read status of an email if no other changes to the email have been made since the previous backup.
-
Restores are non-destructive to a dedicated restore folder in the original Exchange mailbox or OneDrive account. Advanced restore options such as in-place restore, or restore to a specific folder or to a different account aren't yet supported.
-
Restoration of Nested attachments within Exchange Mail or Calendars aren't yet supported.
-
Folders and Calendars containing zero items or subfolders aren't included in the backup.
-
Provides no guarantees about whether data moved, added, or deleted in M365 while a backup is being created will be included in the running backup. Future backups run when the data isn't modified will include the data.
-
OneDrive files ending in
.metaor.dirmetaget omitted from Details and Restore commands.