Space usage in Sharepoint
Posted: Mon Apr 15, 2024 8:40 pm
I've been running a sync copying files from a server's shared drive up to SharePoint & the files appear to be taking up too much space.
As I've been investigating the issue, it looks like every file copied up to SharePoint is showing 2 "versions" in it's history.
One version is created moments after the sync starts & the other version happens sometime before the sync completes. It's like Syncovery is creating a marker for the file in SharePoint at the beginning of the copy job and then going back and actually copying the data when it gets to that specific file.
The issue with this is that both versions are showing up in the Snapshot history & taking up space in our SharePoint account. With large syncs this wastes a lot of file space that Microsoft charges for.
Is there any way to prevent Syncovery from "pre-seeding" the files & only copy a file as it's ready?
As I've been investigating the issue, it looks like every file copied up to SharePoint is showing 2 "versions" in it's history.
One version is created moments after the sync starts & the other version happens sometime before the sync completes. It's like Syncovery is creating a marker for the file in SharePoint at the beginning of the copy job and then going back and actually copying the data when it gets to that specific file.
The issue with this is that both versions are showing up in the Snapshot history & taking up space in our SharePoint account. With large syncs this wastes a lot of file space that Microsoft charges for.
Is there any way to prevent Syncovery from "pre-seeding" the files & only copy a file as it's ready?