It is purely a problem where SharePoint reports the incorrect file length. We can confirm, through meticulous testing, there is no problem with the files on SharePoint themselves, nor is it caused by open files. The problem we observe is that sporadically, SharePoint reports the incorrect length of the file in the cloud. If this sanity check fails, then we mark the file as an error.
internet outages, even if there are only a few seconds of downtime.Īfter downloading each file, BackupAssist 365 performs a “sanity check” to make sure the downloaded file has the same file length as the cloud copy. internal server errors at the cloud storage provider end – including load balancing issues, “temporarily unavailable” issues. Hundreds or thousands of failures on cloud storage – for which we find two main causes:. Zero failures from local storage (unless your hard drive has bad sectors). Sidenote: despite what cloud vendors say, the cloud storage is not as reliable as you might be told, especially compared to a local hard drive.įor example, if we issue a million requests to cloud storage or local storage, we commonly see: #2 How does BackupAssist 365 self-correct this?īackupAssist 365 was designed to deal with the unreliability of cloud services.Īny files that are not backed up in your first backup will be attempted when the next backup runs. This is because BackupAssist 365 performs a differential backup – it compares the data in the cloud to the data in the local backup, and downloads the deltas. This is because the first backup will download thousands of files. Most frequently, it happens on your first full backup. OneDrive for Business user storage accounts. This issue happens if you back up SharePoint sites – and because SharePoint is the underlying store for multiple services, then it also includes: If you get the same error repeatedly (the same files cannot be backed up several times in a row) then please contact our Technical Support department by submitting a support ticket, from the ‘Get support’ tab in the software. We plan on releasing an update which will retry these failed files at the end of the first backup, so the chances of encountering this problem will be minimized. 
It occurs because a verification check failed – which we believe is a sporadic bug in Office 365, and not a problem with your data itself.If a file is skipped in your first backup, then the second backup will try it again. This issue is self-correcting in BackupAssist 365.This issue typically happens on your first backup, where thousands of files are downloaded.
0 kommentar(er)
