Skip to content

Install Litebackup on openSUSE

Run continuous SQLite backups on openSUSE with your own server and encrypted object storage.

Use a maintained openSUSE Leap or Tumbleweed release with systemd running, on amd64 or arm64. You need root or an account with sudo access, a public IP, and persistent SSD storage. For a new small deployment, start with 2 vCPUs and 4 GB RAM, then size the disk for your databases and recent history. Choose a provider guide for low, medium, and high workload examples.

Litebackup also runs on Debian, Ubuntu, Fedora, RHEL, Rocky Linux, AlmaLinux, Amazon Linux, and Arch Linux.

Prepare the host

Run these over SSH on the server. If you are already root, omit sudo from the commands.

sudo zypper install -y bash curl ca-certificates coreutils shadow glibc systemd

Use a conventional Leap or Tumbleweed host with systemd. MicroOS and transactional installations need their own package and service provisioning; these commands assume a standard writable system.

Check the architecture and systemd before installing:

uname -m
systemctl is-system-running

x86_64 is amd64; aarch64 is arm64. Systemd should report running or degraded; inspect existing failures if it reports degraded.

Allow HTTPS

Allow inbound TCP 443 in your provider firewall and any firewall on the host. Restrict SSH access to your administration address. Leave outbound HTTPS, DNS, and time synchronization available.

If firewalld is active, find the zone for your public interface, then allow HTTPS in that zone:

sudo firewall-cmd --get-active-zones
# Replace public if your interface uses another zone.
sudo firewall-cmd --zone=public --permanent --add-service=https
sudo firewall-cmd --reload

If IPv6 is enabled, check its rules too.

Install the server

curl -fsSL https://litebackup.com/server.sh | bash

The installer verifies its download, requests sudo when needed, and prints your 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.

Check the server

Finish browser setup before expecting clients to sync. If the HTTPS address cannot be reached, check the public IP, provider firewall, and host firewall first.

Install

Read the openSUSE documentation, compare cloud and Linux guides, or continue with the CLI and SDK.