Skip to content
Technical Guides

Service provider training

Run Sendense for your tenants, one short video at a time: deploy a shared pool of Sendense Node Appliances (SNAs), onboard a tenant, see what they see, and test a failover. Work through it in order, or go straight to what you need.

Videos
7 videos
Running time
16 minutes
Parts
5 parts

Set up your platform · Video 1 of 17

Host agents: what snagent does and how to add one

1:44Provider guideCaptions included

See what the Sendense host agent does, when you need it, and how to add one to a KVM host.

Read the transcript

In this video you'll see what the Sendense host agent does, when you need it, and how to add one to a KVM host. On some storage types, backups depend on it. The host agent, also called snagent, runs on a CloudStack KVM host. It is not installed in your VMs, and it is not a kernel driver. At backup time, it snapshots each disk on the host and works out which blocks changed.

Then the SNA, the Sendense appliance that reads VM disks and moves the data, reads only those blocks. You need it for four storage types: QCOW2 on NFS, ZFS, Linstor, and native Ceph. Without it, QCOW2, ZFS and Linstor backups fail. You switch native Ceph on per site; the Native Ceph backups video shows how. Raw block and StorPool volumes don't use it.

To add a host, generate an install command. Choose the host's site, how long the command stays valid, and a change-record note. Copy the command, and share it only with the people installing those hosts. When the install finishes, the host checks in here. Check each host's name, version, site and recent check-in. You've seen what the host agent does, and how to add one to each KVM host that uses QCOW2 on NFS, ZFS, Linstor or native Ceph.

Next up: The shared SNA pool. Thanks for watching.