Backups on Cloud not working

[alisonduarte]

Hello, we are experiencing a problem with backups in the cloud, it always worked and just this morning the error started: Failed to check whether service provider side resource can be allocated.

Everything is working normally, the proxies are all valid, the connections to the Cloud are ok, the credentials are recognized.

In the firewall we have no logs of anything being blocked.

We even tried the famous reboot on the server, but the problem still persists.

Has anyone ever experienced a problem like this?

Thanks

[tyler.jurgens]

Sounds like a great thing to open a ticket with Veeam on. If you work with a Cloud Connect service provider you should be reaching out to them as well.

[MarkBoothmaa]

Are you the service provider or the end user?
I'd say its more than likely an issue with the repository based on what I've experienced previously.

[alisonduarte]

Sounds like a great thing to open a ticket with Veeam on. If you work with a Cloud Connect service provider you should be reaching out to them as well.

Thanks for the tip!
I opened a ticket with Veeam, and I already contacted the person responsible for Cloud.
The Cloud company says they are not the problem, which I suspect it is, all the tests I have done internally do not show any problems.

[alisonduarte]

Are you the service provider or the end user?
I'd say its more than likely an issue with the repository based on what I've experienced previously.

We are the end user.
I believe there is a problem with the contracted Cloud.
The bad thing is that there is nothing or trace of someone with this same problem and what the solution was.
There is only one post, and there are no clues to the solution in it, and I think it was a case in 2017.

[MarkBoothmaa]

It looks like it is the provider having the issue "Failed to check whether service provider side resource can be allocated."

Do you have a managed service from the provider or do they just supply a backup target?
If its a managed service then i would raise the ticket with them and they can raise it with Veeam as they will have access to logs on both sides.

[alisonduarte]

The problem appears to have been resolved.
Right now backups are being sent to the Cloud.
I'm almost certain that the problem was in the target hosting, in the contracted Cloud repository.
Even though they said everything was fine on their side yesterday.

Still, thank you all for your help!
I believe everything is back to normal.

[k00laid]

Hi there. Ive been on both sides of that relationship before. In my experience, the easiest and best way to tell many problems is to simply walk-through the wizard for your service provider properties and see if you get all the way through successfully.

[JustBackupSomething]

Just adding to this covo, for v12 of Veeam Backup and Replication this error also sometimes happens when the storage is unable to "quota" enough space for the backups to complete.
This is a semi known bug from what I have seen and resolution is to either
1. move the tenant / client data from one repository to another - like with - https://helpcenter.veeam.com/docs/backu ... ml?ver=120
2. increase the volume size to accommodate new synthetic full's.

Difficult to say for sure however without logs and further insight.