You might think the problem of concurrent access to a shared file is addressed by using the OneDrive sync client to have a local copy of PSTs synchronized with the master copy in SharePoint.
A PST (Personal Storage Table) is for email storage. Versioning is good, so what’s the problem with PSTs? Before addressing that question, we should ask about why PST storage in SharePoint Online or OneDrive for Business comes about. Why PSTs End up in SharePoint and OneDrive Without versions, it would not be possible to do this. The number of versions kept in a document library is defined in library settings (Figure 1) in a range of 300 to 50,000.īoth SharePoint Online and OneDrive for Business also support options to restore a library to a point in time over the previous 30 days. In some cases, such as when editing Office documents using Autosave, a single edit session might generate twenty or thirty versions, depending on the number of changes made. In a nutshell, as users make changes to files in document libraries, they create versions of the files. Instead, it’s about controlling PST storage in SharePoint Online by limiting the number of versions kept for PST files stored in SharePoint Online and OneDrive for Business document libraries. On May 17, Microsoft published message center notification MC256835 to advise tenants about the introduction for what they call a “PST version retention policy.” This has nothing to do with retention labels or retention policies.
0 kommentar(er)
