-
- Lurker
- Posts: 1
- Liked: 1 time
- Joined: Aug 14, 2020 3:15 pm
- Full Name: Courtney Underwood
- Contact:
Issues with Backups failing recently
This started in the last couple of weeks where 3 jobs will fail to backup even though the snapshot is successful. They were working fine until the end of July. Other jobs are working perfectly.
Currently running 2.0.0.600. I have opened a support case, but figured I would try to get some insight here as well.
Case #04334227.
The error message is consistent on all 3 of the jobs:
[SQSCloudMsgStream] Timeout awaiting message: message has not been received from sqs
Any help would be appreciated.
Currently running 2.0.0.600. I have opened a support case, but figured I would try to get some insight here as well.
Case #04334227.
The error message is consistent on all 3 of the jobs:
[SQSCloudMsgStream] Timeout awaiting message: message has not been received from sqs
Any help would be appreciated.
-
- Product Manager
- Posts: 5618
- Liked: 1177 times
- Joined: Jul 15, 2013 11:09 am
- Full Name: Niels Engelen
- Contact:
Re: Issues with Backups failing recently
We have a few more support cases like this at the moment regarding the sqs service. I would advise to wait for support. We will monitor the case as well from our side. Thanks!
Personal blog: https://foonet.be
GitHub: https://github.com/nielsengelen
GitHub: https://github.com/nielsengelen
-
- Product Manager
- Posts: 5618
- Liked: 1177 times
- Joined: Jul 15, 2013 11:09 am
- Full Name: Niels Engelen
- Contact:
Re: Issues with Backups failing recently
Hi @cunderwood29, looks like the case is still in progress. Please keep working with our support so we can provide a fix to this message.
Personal blog: https://foonet.be
GitHub: https://github.com/nielsengelen
GitHub: https://github.com/nielsengelen
-
- Product Manager
- Posts: 5618
- Liked: 1177 times
- Joined: Jul 15, 2013 11:09 am
- Full Name: Niels Engelen
- Contact:
Re: Issues with Backups failing recently
Update on this specific error/issue. As this is related to the network configuration setup, please contact Veeam support for assistance to get it resolved.
Personal blog: https://foonet.be
GitHub: https://github.com/nielsengelen
GitHub: https://github.com/nielsengelen
-
- Novice
- Posts: 3
- Liked: never
- Joined: Feb 15, 2017 12:52 am
- Full Name: Lee
Re: Issues with Backups failing recently
If you are finding yourself here like me, then the fix for the error above as from my tech support case:
Troubleshooting:
-Run the Permissions validator.
-Ensure KB3197 is followed for the VPC setup and Endpoint creation: https://www.veeam.com/kb3197
-Ensure The SQS Endpoint security policy is set to receive and send all traffic from and to everywhere.
Those are the exact notes from the tech.
I followed that Endpoint creation setup doc KB3197 and made my endpoints for an S3 backup. For any inline IAM policy info that the endpoint wizard wanted to create, I used the default Allow * everything. I bound all of the endpoints to a new Security Group that had Allow All Traffic Inbound/Outbound to the Security Groups that my other instances were in (and visa-versa: with those security groups having allow all in/out to this new Security Group). Then I threw in an allow all for the whole subnet where my SSM appliance and VMs were located, and I also threw in the Prefix Lists for good measure. I'm sure I could have locked the SG and IAM down further, but I just wanted it working.
Troubleshooting:
-Run the Permissions validator.
-Ensure KB3197 is followed for the VPC setup and Endpoint creation: https://www.veeam.com/kb3197
-Ensure The SQS Endpoint security policy is set to receive and send all traffic from and to everywhere.
Those are the exact notes from the tech.
I followed that Endpoint creation setup doc KB3197 and made my endpoints for an S3 backup. For any inline IAM policy info that the endpoint wizard wanted to create, I used the default Allow * everything. I bound all of the endpoints to a new Security Group that had Allow All Traffic Inbound/Outbound to the Security Groups that my other instances were in (and visa-versa: with those security groups having allow all in/out to this new Security Group). Then I threw in an allow all for the whole subnet where my SSM appliance and VMs were located, and I also threw in the Prefix Lists for good measure. I'm sure I could have locked the SG and IAM down further, but I just wanted it working.
-
- Product Manager
- Posts: 5618
- Liked: 1177 times
- Joined: Jul 15, 2013 11:09 am
- Full Name: Niels Engelen
- Contact:
Re: Issues with Backups failing recently
Thanks for sharing @LeeGC. Do keep in mind that there may also be other things causing this but it is a good start to follow the provided steps.
Personal blog: https://foonet.be
GitHub: https://github.com/nielsengelen
GitHub: https://github.com/nielsengelen
Who is online
Users browsing this forum: No registered users and 1 guest