This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(310.4, 80%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ER%3C/text%3E%3C/svg%3E)
All of our online recovery points within Azure Backup Server on prem have been failing recently.
The description of the failed job is as follows: DPM skipped cloud backup for <DatasourceType> <DatasourceName> on <ServerName> because the latest disk backup is already backed up to cloud. (ID 33344)
To me this is very strange behaviour as the recovery points (local disk back-ups) are running just fine.
It seems to me that MABS is not recognizing any changes within the local back-ups compared to the back-ups in Azure.
When I run a consistency check on these back-ups and manually run an online recovery point back-up, the online recovery back-up will run succesfully.
Am I missing anything here or might this be a bug?
We are currently running MABS on version 14.0.46.0.
Any help would be greatly appreciated.
Hello @Radu Thank you for reaching out to us on Microsoft Q&A platform. Happy to help!
Based on the information you provided, I understand that your MABS backup is failing with "The description of the failed job is as follows: DPM skipped cloud backup for <DatasourceType> <DatasourceName> on <ServerName> because the latest disk backup is already backed up to cloud. (ID 33344)" You need not worry about the error message. Actually, the backup job failed because there were no changed occurred on disk backup hence the online will also not have changes. Since, MABS depends on latest healthy available disk replica, if the replica blocks were not updated then online will send that message.
You may want to observe if there are any changes occurred on the disk. If yes, the online backup will be successful.
I suggest you wait for next schedule backup and see if online backups happen as expected.
Hope this helps. Let us know if you hit a roadblock.
This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
@SadiqhAhmed-MSFT Thank you for reaching out to me on such short notice! Thank you for the information you have provided. I'll keep an eye out on the back-up over the weekend and I'll let you know what I see.
@Radu Let us know how it goes!
@SadiqhAhmed-MSFT Good morning! It seems that the online recovery has been running a bit more frequent now. I do want to note that I changed the local disk back-up schedule from every 2 hours to every 4 hours before I made this post. This was more or less a test to see if this would change anything. (perhaps it did?) I see that DPM made one online recovery point on 6-15-2024 at 9:00 PM and one on 6-16-2024 at 10:00PM, but the last one has sadly failed with description "operation failed. (ID 120002)".
Online I can read that this ID would mean Change passphrase - "Cause: This error occurs when security settings are enabled, or when you try to change the passphrase when you're using an unsupported version."
I suppose I will have to check the host and see if I can find anything.
If you have any advise then do please let me know!
Thank you in advance.
@Radu For now, I would wait for your response. You check your host and see if there is anything you find that guides you to troubleshoot the issue further.
The "operation failed. (ID 120002)" issue ended up resolving itself after a few hours.
The eventual solution to my main issue seemed to have been the fact that I changed the schedule of the local disk back-up (recovery point) from every 2 hours to every 4 hours.
After this change my online recovery points have been a lot more consistent.
@Radu Thanks for the update! Glad to hear that the issue is resolved :)