Litebackup backs up SQLite databases from your app machines to your own Compute instance and encrypted object storage. Your app machines can run anywhere.
Create the server
Create an OCI Compute instance near your app machines. We recommend Ubuntu 26.04 LTS from Canonical, or an official Debian 13 image where available; AlmaLinux and Rocky Linux images from the OCI Marketplace also work. Add your SSH key. On an AMD Flex shape, set the OCPU and memory values below; one AMD OCPU provides two vCPUs. 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 | AMD Flex, 1 OCPU / 4 GB | 80 GB persistent block storage |
| Medium | Several machines and hundreds of tenant or agent databases | AMD Flex, 2 OCPUs / 8 GB | 160 GB persistent block storage |
| High | Dozens of machines, thousands of databases, or frequent concurrent syncs | AMD Flex, 4 OCPUs / 16 GB | 320 GB persistent block storage |
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 persistent boot or block volumes for the server files and review their deletion settings when replacing an instance. Choose a supported S3, R2, Google Cloud Storage, or S3-compatible bucket. Setup tests a bucket before accepting it, including the conditional writes needed to store backups safely.
Configure networking
Use a public subnet with an internet-gateway route and assign a public IPv4 address. Add the inbound rules below to the instance network security group or subnet security list. Check any host firewall too.
| 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 Oracle Cloud Marketplace, or compare cloud and Linux installation guides.