Sendense Documentation

Infrastructure Requirements

Planning requirements for appliances, repositories, platform access, and recovery targets.

Documents Home

Guide

Infrastructure Requirements

Planning requirements for appliances, repositories, platform access, and recovery targets.

ReadyCurrentrequirementsplanningdeployment

Plan Before Deployment

  • Choose where SHA will run and how administrators will reach the GUI.
  • Decide how many SNAs are needed for expected backup concurrency and fault tolerance.
  • Plan EBA repository capacity, retention, immutability, legal hold, and cleanup policy.
  • Plan source infrastructure credentials and discovery for each protected platform.
  • Decide site groupings for appliances, protected infrastructure, and recovery infrastructure.
  • Confirm destination platform prerequisites for controller-backed replication where DR targets are used.

Connectivity

Each SNA maintains a single always-on outbound encrypted connection to SHA, by default over outbound TCP 443. This lets an SNA enroll with SHA across routed networks and over the Internet where the deployment design permits it.

Each SNA still needs access to the protected or recovery infrastructure for its assigned workflows, and appliances and agents are enrolled and approved before they participate in workflows.

SNA Sizing

Customers commonly deploy multiple SNAs for load balancing and fault tolerance.

As an initial planning guide, use roughly one SNA for every five concurrent backup jobs, then refine sizing for workload size, storage performance, network capacity, recovery workflows, and resilience requirements.

Sites

Sites group appliances, protected infrastructure, and recovery infrastructure into logical locations. They help operators understand which appliances belong together, which infrastructure they can reach, and which recovery or replication workflows they support.

You choose or confirm a site during:

  • SNA enrollment.
  • snagent host-agent installer generation.
  • EBA repository placement where applicable.
  • Replication pattern target placement.
  • Restore-to-server destination routing.
  • Controller-backed failover planning.

CloudStack KVM Notes

For CloudStack KVM, snagent is used by default only when the configured backend is QCOW NFS, ZFS, or LINSTOR DRBD and the host-agent path is available. RAW Block does not use snagent; it uses the full-source-read EBA path.

What This Page Does Not Cover

  • It is not a full sizing guide. Refine capacity for your workloads and recovery objectives.
  • It is not a network port matrix, and it does not replace platform-specific installation steps.
  • Not every deployment includes every component. The required mix depends on protected platforms, recovery objectives, provider model, and DR requirements.

Related Docs