Litebackup backs up SQLite databases from your app machines to your own Azure VM and encrypted object storage. Your app machines can run anywhere.
Create the server
In Azure, create a Linux virtual machine near your app machines. We recommend Debian 13 or Ubuntu 26.04 LTS from its verified publisher in the image picker; RHEL, AlmaLinux, Rocky Linux, and openSUSE Leap images also work. Then select a Dsv5 size or a comparable general-purpose VM, and add your SSH key. Install Litebackup with the command below.
Choose a VM size
| Load | Example workload | VM starting point | Disk starting point |
|---|---|---|---|
| Low | A few machines and dozens of lightly written databases | Standard_D2s_v5, 2 vCPUs / 8 GiB | 128 GiB managed SSD |
| Medium | Several machines and hundreds of tenant or agent databases | Standard_D4s_v5, 4 vCPUs / 16 GiB | 256 GiB managed SSD |
| High | Dozens of machines, thousands of databases, or frequent concurrent syncs | Standard_D8s_v5, 8 vCPUs / 32 GiB | 512 GiB managed SSD |
These are starting recommendations, not database or machine limits: size for your active data, concurrent writes, recent history, and room for restores or bucket downtime. Watch CPU, memory, disk, and sync progress after launch, and choose a Litebackup plan covering your databases and machines.
Use a persistent managed SSD for the server files. Choose a larger disk tier if you need more capacity or disk throughput. Keep data off temporary disks. Connect a supported S3, R2, Google Cloud Storage, or S3-compatible bucket; Azure Blob Storage is not a direct bucket option.
Configure networking
Attach a public IPv4 address. In the network security group, allow inbound TCP 443 and SSH from your administration address. Check both subnet and network-interface security groups, plus any firewall inside the VM.
| Direction | Port | Purpose |
|---|---|---|
| Inbound | TCP 443 | Litebackup clients and the HTTPS console |
| Inbound | TCP 22 | SSH, restricted to your administration address |
| Outbound | HTTPS, DNS, time synchronization | Downloads, registration, bucket access, and a correct clock |
TCP 443 must reach the VM directly. If you enable IPv6, allow the matching traffic there too.
Install Litebackup
SSH into the VM as root or a user with sudo access, then run:
curl -fsSL https://litebackup.com/server.sh | bash
The installer asks for sudo when needed and prints a setup link. The Litebackup service starts once you finish browser setup.
Claim the server and connect a bucket
Open the setup link within 24 hours, sign in, and name your server. Connect a bucket you own, save your recovery kit separately, and choose your retention period. Setup supplies your HTTPS address; no custom domain is needed.
Back up your first SQLite database
On the machine that holds your database, open Machines → Add machine in the Litebackup console and follow its install and join commands. Run them as the user that owns your app's databases, or as root for a system service that reaches every database. Then run, as the same user:
litebackup start /var/lib/app/main.sqlite
litebackup status
Use the path to an existing SQLite file. Continuous backup runs in the litebackup background process. Your app keeps using its usual SQLite driver and file, without waiting for uploads. Keep that file on a durable disk or volume.
Check the console for the server and cloud backup versions. For application integration, see the TypeScript and Go SDKs; for a service with no code changes, see the CLI. Practice a restore into a new file.
Provider reference
Install
Open Azure Marketplace, or compare cloud and Linux installation guides.