Microsoft constantly pushes out changes, and sometimes these changes break things for 3rd party vendors. After a recent change, we […]
If you’ve recently upgraded to Veeam Backup & Replication 12.1 and have begun seeing your Linux jobs fail with the
A recent Microsoft change to the Serialized Property of Exchanges items have caused “Invalid ‘serialized stream, unknown opcode found: 4’”
Recently we have begun seeing the “Failed to backup item: FILEPATH, Download request retry timeout exceeded” error appear in jobs
During early December we began noticing two errors pop up. The messages “There is an error in XML document” and
Veeam will display the error message “Backup proxy is missing C++ runtime components” for a different reason depending if you
The generic “There is not enough space on the disk” error message is a fairly common and easy issue to
The nuisance error, “The remote server returned an error: (429)” in Veeam Backup for Microsoft 365 indicates that you have
We have run into an issue when a job starts reporting the “The given key was not present in the
The “Failed to find Team mailbox owner account” error can be caused by the owner of the mailbox being moved,
