Unable to perform Manual Backup in Prisma Cloud Compute when Console is behind Load Balancer
6972
Created On 11/20/21 10:10 AM - Last Modified 04/28/22 03:51 AM
Symptom
Unable to perform Manual Backup in Prisma Cloud Compute when Console is behind Load Balancer, with the following error message in Console Logs:
"ERRO 2021-09-14T06:47:42.933 route_handler.go:9578 Operation failed: uri=/api/v1/backups?project=Central+Console; error=error copying file data to tarball. EOF"
Environment
- Prisma Cloud Compute
- Public Cloud (AWS, GCP, Azure)
Cause
- One of the most common reasons, behind manual backup operation failure in Prisma Cloud Compute when Console is behind Load Balancer, is shorter idle timeout setting on the Load Balancer.
- Most Load Balancers have a default timeout configured.
- For Example, AWS Load Balancer Default Idle Timeout is 60 seconds.
Resolution
Increase the Load balancer idle timeout setting in Public Cloud environment.
Example: On AWS Load Balancer, the ideal timeout is increased from 60 seconds to 300 seconds.
Additional Information
For more information, refer the following :
- Prisma Cloud Compute Backup and Restore: Backup and Restore
- AWS: Load Balancer Attribute
- Azure: Load Balancer TCP Idle Timeout
- GCP: Load Balancing
- F5 LTM: K7606: Overview of BIG-IP idle session timeouts