A complete, copy-paste guide to deploying the Softyz Inc agent across your entire Linux fleet using our official Ansible role — including full sample playbooks, API token authentication, systemd service setup, cron scheduling, and fleet-wide verification from the CLI. Tested on Ubuntu.
If you manage more than a handful of Linux servers, manually installing and configuring a backup agent on each one is not a strategy — it is a liability. Miss one server in your fleet and you have a single point of failure you won’t discover until the worst possible moment.
This guide shows you exactly how to deploy the Softyz backup agent across an entire Linux fleet using Ansible — our official role handles installation, authentication, systemd service registration, folder configuration, and backup scheduling in a single playbook run. The same command that deploys to 5 servers deploys to 500.
Prerequisites — what you need before starting
- Ansible 2.10+ on your control node (local machine or CI/CD system)
- Softyz Business or Enterprise account — a Softyz API token from Account → Settings → API Keys
- SSH access to all target servers with a user that has sudo privileges
- Python 3.8+ on all target nodes (required by Ansible — standard on all modern distros)
- Outbound HTTPS (port 443) from all servers to cloud.softyzinc.com
Supported Linux distributions
Step 1 — Install the Softyz Ansible role
The official Softyz Inc Ansible role is published on Ansible Galaxy. Install it on your control node with a single command:
