We have had an error message when backing up Office365 for 2 days
JetError -528, JET_errMissingLogFile, Current log file missing
We backup to a NAS
The backup repository has the same error message, but the NAS is fully accessible and our normal Veeam Backup & Repository continues to back up to the same NAS
Does anyone have an idea?
Best answer by Stefesbau
Yes, we use SMB, and the instructions don't say anything about it being experimental, it just says best practice for iSCSI. It has worked for 7 months so far. This error only appears all of a sudden, there are still 1.2 TB free on the NAS but that doesn't seem to be enough, I just freed 2 TB on the NAS and the error is gone.
But it's crazy that 1.2 TB of free memory is not enough for him and that's why he gets the jet error. We use the latest version 7.1.0.2031
+5Hey, do you use a SMB Repo on your NAS? This variant is not recommended for M365 and only experimental support.
If your repo can use iSCSI i would use this ;) if you backup more than 200-300 users it’s strongly recommended to use object Storage as target.
Matze
+20Hi
According to the below forums post, you might not have enough Repo space for your O365 backup, but is a slightly different error:
This post suggests a known bug:
Both are slightly different error #’s than yours. If all looks ok, may be best to open a case. You can also look in: C:\ProgramData\Veeam\Backup\<job-name>.log and see if anything shows in the job log to help you.
+21Also which version of VB365 are you using for backups? That will also help with suggestions.
Yes, we use SMB, and the instructions don't say anything about it being experimental, it just says best practice for iSCSI. It has worked for 7 months so far. This error only appears all of a sudden, there are still 1.2 TB free on the NAS but that doesn't seem to be enough, I just freed 2 TB on the NAS and the error is gone.
But it's crazy that 1.2 TB of free memory is not enough for him and that's why he gets the jet error. We use the latest version 7.1.0.2031
+21Yes, we use SMB, and the instructions don't say anything about it being experimental, it just says best practice for iSCSI. It has worked for 7 months so far. This error only appears all of a sudden, there are still 1.2 TB free on the NAS but that doesn't seem to be enough, I just freed 2 TB on the NAS and the error is gone.
But it's crazy that 1.2 TB of free memory is not enough for him and that's why he gets the jet error. We use the latest version 7.1.0.2031
The JET databse needs more space than using something like Object Storage where just metadata is on block storage so it is something to always keep in mind. Glad to see freeing more space fixed the issue.
+5https://helpcenter.veeam.com/docs/vbo365/guide/br_smb.html?ver=70
+21https://helpcenter.veeam.com/docs/vbo365/guide/br_smb.html?ver=70
Yes this is the line on that page.
+20Yes, we use SMB, and the instructions don't say anything about it being experimental, it just says best practice for iSCSI. It has worked for 7 months so far. This error only appears all of a sudden, there are still 1.2 TB free on the NAS but that doesn't seem to be enough, I just freed 2 TB on the NAS and the error is gone.
But it's crazy that 1.2 TB of free memory is not enough for him and that's why he gets the jet error. We use the latest version 7.1.0.2031
Glad freeing up more space did the trick. Thanks for sharing what worked for you.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
