Load balancing Zadara VPSA Object Storage

Updated on November 25, 2025
Published on March 7, 2023

Benefits of load balancing Zadara VPSA Object Storage

Load balancing Zadara VPSA Object Storage is a crucial part of a highly available and scalable deployment:

  • Enhanced scalability: Load balancing allows you to seamlessly scale your object storage environment. It distributes incoming requests across multiple Virtual Controllers (VCs) in the VPSA cluster. This ensures that as your data and traffic demands grow, you can add more VCs to the cluster, and the load balancer automatically includes them, providing a truly scale-out architecture for both capacity and performance.
  • High Availability (HA) and resilience: Load balancers act as a single, highly available access point, protecting users from underlying infrastructure issues. They continuously monitor the health of all VPSA Object Storage VCs. If a VC fails or becomes unresponsive, the load balancer automatically reroutes traffic to the remaining healthy servers, guaranteeing application uptime and an uninterrupted end-user experience.
  • Improved performance: By distributing the workload intelligently, load balancing prevents performance bottlenecks. It ensures an even distribution of traffic, which avoids a single VC from being overloaded.This leads to reduced response times and lower latency for data retrieval and storage operations, maximizing the utilization of your storage resources.

About Zadara VPSA Object Storage

VPSA Object Storage is Zadara’s object storage service. VPSA Object Storage is provided on Zadara clouds, side by side with the VPSA that provides block and file storage services.

Why Loadbalancer.org for Zadara VPSA Object Storage

Loadbalancer’s intuitive Enterprise Application Delivery Controller (ADC) is designed to save time and money with a clever, not complex, WebUI. 

Easily configure, deploy, manage, and maintain our Enterprise load balancer, reducing complexity and the risk of human error. For a difference you can see in just minutes.

And with WAF and GSLB included straight out-of-the-box, there’s no hidden costs, so the prices you see on our website are fully transparent. 

More on what’s possible with Loadbalancer.org.

How to load balance Zadara VSPA Object Storage

The load balancer can be deployed in four fundamental ways: Layer 4 DR mode, Layer 4 NAT mode, Layer 4 SNAT mode, and Layer 7 Reverse Proxy (Layer 7 SNAT mode).

For Zadara VSPA Object Storage, we recommend using Layer 7 Reverse Proxy. This mode has no network changes are required and SSL termination can be implemented. It also offers high performance and implementation flexibility.

However, because Layer 7 is a reverse proxy, the client source IP address is not visible at the real server. Instead, the IP address of the load balancer is visible at the real server. In order to retain the client source IP address, the load balancer inserts an X-Forwarded-For header into the load balanced traffic, which the VPSA nodes can log for troubleshooting issues while seeing the true source IP address of connecting clients.

VPSA Object Storage architecture

VPSA Object Storage architecture is a scale out cluster of Virtual Controllers that together provide the service. The number Of VCs is automatically determined as needed to serve the capacity and performance of the system.

This figure shows the high-level logical view of VPSA Object Storage. It is a Virtual Object Store cluster, with two distinct layers:

  • Storage Layer that manages individual disks
  • Proxy – REST API Layer that provides a REST API front-end to the Object Storage
DC Zadara, Network Diagram, Loadbalancer.org

Virtual service (VIP) requirements

To provide load balancing for Zadara VPSA nodes the following VIPs are required:

  • VIP 1: OBS Data
  • VIP 2: VPSA GUI
  • VIP 3: VPSA Authentication

Load balancing deployment concept

DC Zadara v2, Network Diagram, Loadbalancer.org