Date: 2022-12-02


Ahsay recommends users and Admins temporarily discontinue use of Microsoft OneDrive for Business as a destination (Backup and Replication) until Microsoft resolves this bug (https://github.com/OneDrive/onedrive-api-docs/issues/1640)

Due to recently discovered Microsoft issue affecting upload of specific files with bytes-sized corresponding to our data Block file [ ~32MB and ~64MB ], Ahsay backup jobs may result in excessive 'retry' until max period is exhausted, resulting job error; or Ahsay replication will fail with similar 'retry' and error; both leading to incomplete Block(s) data transfer. While the issue might not always be hit given varying bytes-size differences in each Ahsay block file [.bak], it is on the side of caution to avoid incomplete backups by using an alternate Destination until this is resolved.

This Microsoft OneDrive for Business bug affects all Ahsay products versions of AhsayCBS , AhsayOBM , AhsayACB.

Any error message to look for ?

HTTP code 500 generalException: General exception while processing

The attempted operation is prohibited because it exceeds the list view threshold.

What if the Destination is currently using OneDrive for Business ?
For Backups, we recommend you pause their Schedules, and create new Backup Sets to alternate destinations. When the Microsoft bug is fixed, you can resume your original Backup Sets.

For Replication, we recommend you choose an alternate destination for storing the replicated data.

Where is this bug filed ?
https://github.com/OneDrive/onedrive-api-docs/issues/1640

How could I confirm this experience ?
You can try to manually upload, via your browser to connect to your Microsoft OneDrive for Business web UI, file sized:

File Bytes size	Result	Comment
67,129,252	OK	64.01944 MB
67,108,800	Transfer error	63.99994 MB
67,108,832	Transfer error	63.99997 MB
33,554,384	Transfer error	31.99995 MB
33,554,327	Transfer error	31.9999 MB
33,554,222	OK	31.9998 MB

NOTE: These are a few examples, other Bytes-size can be affected too.

When is it expected to be fixed?
Our developers do not have a timeframe, as this is not an Ahsay issue.




If you have further inquiry about this, you may open a Support ticket via Ahsay Partner Portal