add known issue about deleted library restore (#3390)
#### Does this PR need a docs update or release note? - [x] ✅ Yes, it's included #### Type of change - [x] 🗺️ Documentation #### Issue(s) * #3382
This commit is contained in:
parent
f8aa37b822
commit
4dc9bf9d64
@ -27,6 +27,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
||||
### Known Issues
|
||||
- Restore operations will merge duplicate Exchange folders at the same hierarchy level into a single folder.
|
||||
|
||||
### Known Issues
|
||||
- SharePoint document library data can't be restored after the library has been deleted.
|
||||
|
||||
## [v0.7.0] (beta) - 2023-05-02
|
||||
|
||||
### Added
|
||||
|
||||
@ -20,7 +20,7 @@ Below is a list of known Corso issues and limitations:
|
||||
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 `.meta` or `.dirmeta` get omitted from Details and Restore commands.
|
||||
|
||||
* Exchange Calender Event instance exceptions (changes to a single event within a recurring series) aren't
|
||||
included in backup and restore.
|
||||
|
||||
* SharePoint document library data can't be restored after the library has been deleted.
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user