As a OneDrive administrator, you may receive reports that the file restore feature does not include changes made in the last few hours for shared libraries. This happens because the restore point generation for shared libraries follows a different schedule than for personal OneDrive libraries. The default restore point is created once per day, so any edits made after that point are not captured. This article explains the technical reason behind this gap and provides a checklist to help you verify restore points, adjust expectations, and implement workarounds for shared libraries.
Key Takeaways: Restore Points for Shared Libraries
- Microsoft 365 admin center > SharePoint > Active sites > Shared library > Restore: Shows the list of available restore points and their timestamps.
- OneDrive admin center > Restore OneDrive > Select a date: Restore points for personal libraries are generated every 30 minutes; shared libraries get one per day.
- Version history on a file in the shared library: Captures every save but is independent of the file restore feature and can be used to recover recent changes.
Why File Restore Misses Recent Changes for Shared Libraries
The file restore feature in OneDrive and SharePoint creates snapshots of the library at specific intervals. For personal OneDrive libraries, Microsoft generates a restore point every 30 minutes for the past 30 days. For shared libraries, also known as SharePoint document libraries, the restore point is generated once per day. This difference exists because shared libraries often contain larger amounts of data and more users, making frequent snapshots resource-intensive. When a user restores a shared library to a point in time, any changes made after the last daily snapshot are lost. The restore operation does not warn about this gap. The user sees only the files that existed at the snapshot time, and all edits, uploads, and deletions after that moment are missing.
How Restore Points Are Created
A restore point is a full copy of the library metadata and file versions at a given time. Microsoft triggers these snapshots automatically. The schedule is not configurable by administrators. For personal OneDrive libraries, the snapshot runs every 30 minutes. For shared libraries, the snapshot runs once every 24 hours. The exact time of the daily snapshot depends on the region and server load. You cannot force an immediate restore point. If a user edits a file at 3:00 PM and the daily snapshot occurred at 2:00 AM, the restore point contains the file version from 2:00 AM, not the 3:00 PM version.
Confusion Between Version History and File Restore
Version history is a separate feature that tracks every save of a single file. It is not affected by restore point schedules. A user can open version history for any file and restore an earlier version, even if the file restore feature would skip that change. The file restore feature works at the library level and does not use version history. It uses the snapshot. When an admin or user runs a file restore, the entire library is rolled back to the snapshot state. Any files that were added or changed after the snapshot are removed or reverted. Version history for those files remains intact, but the file itself is replaced with the snapshot version. This distinction is often the source of confusion when recent changes appear to be missing.
Checklist: Verify and Address Missing Restore Points for Shared Libraries
Use this checklist to confirm the restore point schedule, identify the gap, and recover recent changes for shared libraries.
- Open the file restore interface for the shared library
Go to the SharePoint site that hosts the shared library. Select the library in the navigation. Click the gear icon and choose Library settings. Under Permissions and Management, click Restore this library. The page shows a calendar with available restore points. Each date with a restore point is highlighted. Click a date to see the exact timestamp of the snapshot. - Compare the restore point timestamp to the time of the missing changes
Note the timestamp shown on the restore page. If the user reports missing changes from 2 hours ago and the restore point is from 20 hours ago, the gap is confirmed. The restore point does not include those changes. Do not proceed with the restore if the goal is to recover only recent edits. - Check version history for the affected files
Navigate to the file that was edited. Right-click the file and select Version history. A list of all saved versions appears, including the most recent one. The version timestamp shows the exact time of the save. If the version exists, the data is not lost. You can restore that version without affecting other files in the library. Click the three dots next to the version and choose Restore. - Use the OneDrive admin center to view restore points for personal libraries
If the shared library is a team site library and some users also have personal OneDrive libraries, check the personal restore points. Go to the OneDrive admin center. Under Health, click Restore OneDrive. Enter the user email and click Check. The page shows restore points every 30 minutes. This confirms that personal libraries have more granular restore points than shared libraries. - Communicate the restore point schedule to users
Inform users that shared libraries have a single daily restore point. Provide the approximate time of the snapshot for their site. Explain that version history is the correct tool for recovering recent individual file changes. Create a short guide or link to Microsoft documentation about version history. - Test a restore on a non-critical shared library
Create a test shared library with a few files. Make an edit. Wait until the next day after the daily snapshot. Run the file restore to a date before the edit. Verify that the edit is missing. Then use version history on the test file to restore the edit. This confirms the behavior and helps you explain it to users.
If File Restore Still Misses Changes After the Main Fix
Even after understanding the restore point schedule, you may encounter situations where expected restore points are missing entirely or where version history does not contain the recent change. The following subsections cover those specific failure patterns.
No restore point appears for the shared library at all
If the restore page shows no dates highlighted, the library may have been created recently or may have no file activity. Restore points are generated only when the library contains files. If the library is empty, no restore point exists. Upload at least one file and wait 24 hours. The next day, a restore point should appear. If it does not, check that the site is not in read-only mode and that the library is not exceeding the 5,000-item limit for restore point generation.
Version history shows the file but the file restore removed it
If you ran a file restore and the file disappeared, the file was created after the restore point snapshot. The restore operation deleted it because it was not in the snapshot. The version history for that file still exists in the site recycle bin. Go to the site recycle bin, find the file, and restore it. After restoring, the file returns with its version history intact. Then use version history to restore the most recent version.
User insists on a more recent restore point for a shared library
No administrative setting can change the restore point frequency for shared libraries. Microsoft Support cannot force an immediate snapshot. The only workaround is to use version history for individual files or to copy the current state of the library to another location before performing the restore. For example, export the library content to a local folder, run the restore, and then merge the exported files back manually.
| Item | Personal OneDrive Library | Shared Library (SharePoint Document Library) |
|---|---|---|
| Restore point frequency | Every 30 minutes | Once per day |
| Retention period | 30 days | 30 days |
| Version history availability during restore | Preserved but file is reverted to snapshot | Preserved but file is reverted to snapshot |
| Recovery of recent changes without version history | Possible if within 30 minutes of snapshot | Not possible; use version history or manual backup |
| Administrator control over snapshot schedule | None | None |
You now know that the file restore feature for shared libraries uses a daily snapshot and cannot capture changes made after that snapshot. Use version history to recover individual recent edits. For complete library recovery, communicate the snapshot schedule to users and encourage them to save critical changes through version history or manual backups. As an advanced tip, consider using Microsoft Power Automate to create a daily export of the shared library content to a separate location, giving you an additional recovery point that is not dependent on the automatic restore point schedule.