Ticket #04321730 Backup to cloud

[kubimike]

Hi, could I get a hand with the ticket referenced above? It appears the cloud team is very busy and this ticket has been open for awhile.
Heres a brief description of the issue. I have a backup copy job that is configured as "Immediate copy", what Im seeing is when SQL transaction logs need to be sent I get a job failure. Other aspects of this job never fail, only when it comes to SQL logs.
The error I get is

Code: Select all

"8/18/2020 11:44:08 AM :: No cloud gateways are available: some gateways are not reachable over the network "

I have 5 other backup copy jobs going to the same cloud provider none of them give me any issues. The other jobs are not setup as "Immediate copy" if that helps.

Veeam Version 10.0.0.4461 P2 on Win 2016

[Natalia Lupacheva]

Hi Mike,

I see you've had a remote session with Support and needed to upload the logs.
Support asked for logs at 14th of August but I don't see any response from you.
Please keep working with Support, we are waiting for the logs from your side.

Thanks!

[kubimike]

Sorry but the logs were sent the day the ticket was created. I've now tried to log back in to send them again and the credentials don't work.

[foggy]

Hi Mike, please ask your engineer for a new FTP location then.

[kubimike]

I did "Talk to a Manager" Natalia was wrong, here was the issue with the ticket

Code: Select all

Hello Mike,

 

I apologize for the delay in response. It seems that the messages you sent were being classified as automated messages when clearly they were not. I have notified the engineer to continue working with you on this case

 

Please keep an eye out from communication on the case and let us know if there is anything else we can do to assist.

 

Jakob Cooney

[Natalia Lupacheva]

Hi Mike,

thank you for the update! Maybe that's why I didn't see these messages in your case.
Please keep working with Support to figure out what happened.

Thanks!

[AlwaysLearning]

Did you find a resolution to this?

[Vitaliy S.]

Hi Rob,

Based on what I see from the ticket notes the issue was network-related. To understand what is causing this in your situation, it is recommended to open a support ticket.

Thanks!