Daily Encrypted Seedbox Backups with Pikkumies
Back up your seedbox's settings every night: after a one-time connection and a passphrase you save yourself, one plain sentence to Pikkumies schedules a daily encrypted archive to your Pulsed Media Storage Box, makes one right away and reads it back to prove it decrypts. In the test run below that was one request, about 5 minutes and 29,513 AI credits (about 3 euro cents).
Each archive is made on the seedbox, encrypted there with gpg and streamed over ssh, so the Storage Box only ever holds encrypted files. This is not zero-knowledge: the passphrase is kept on the seedbox, where the seedbox's administrators could read it; with the Storage Box also at Pulsed Media, one company runs both ends. For backups that nobody but you can read, use Zero-Knowledge Backups with Pikkumies from your own Linux machine.
Recorded on Pulsed Media test accounts: one plays your seedbox (shown as you@seedbox), a second plays the Storage Box (shown as boxuser@storagebox). The seedbox had a fresh Pikkumies install and a few settings files. The passphrase was saved off screen between the first two clips, and long waits are shortened; each caption says by how much.
What you need
- A seedbox with Pikkumies (see Pikkumies on PMSS).
- An ssh login on the machine that will keep the backups. A Pulsed Media Storage Box includes one; any Linux machine with an ssh password login and
shworks too.
Step 1: Connect the Storage Box, in your own terminal

Setup logs in to the Storage Box once with its password, and never again:
read -rs PIKKUMIES_REMOTE_PASSWORD && export PIKKUMIES_REMOTE_PASSWORD php ~/pikkumies/tools/backup/remote/remote.php setup STORAGEBOX_HOST BOX_USER --human unset PIKKUMIES_REMOTE_PASSWORD
read -rsreads the password without showing it, so it stays off the screen and out of your shell history. In the clip the host and user name were in two shell variables set beforehand.- Setup records the box's host key and prints its fingerprint. Every later connection checks that key and stops if it changes.
- It makes a new ssh key for this one job and adds it to the box's
~/.ssh/authorized_keyswithrestrictand a fixed command. That key can only store, list and fetch archives in one folder and ask for free space; it cannot open a shell. Setup tests this; if the box would give the key a shell, setup deletes the key on the seedbox and names the line to remove on the box. - Change the Storage Box password afterwards: the key works without it.
You can also give the login to Pikkumies in a chat ("set up backups to HOST, account USER, password ..."). That works, but the password then goes to the AI model and into the session history. Setup's closing note says this; typed in your own terminal as above, it stays on your seedbox.
Step 2: Save the passphrase
Setup makes a random passphrase on the seedbox and encrypts every archive with it. Without a copy, no archive can be decrypted if the seedbox is lost. Run this in your own terminal and keep the passphrase in a password manager or on paper, away from the seedbox and the Storage Box. Then type your copy back, so a typo shows now and not on the day you need it:
php ~/pikkumies/tools/backup/remote/remote.php passphrase php ~/pikkumies/tools/backup/remote/remote.php passphrase --confirm-saved
The first command prints the passphrase as 12 groups of four characters, and only in your own terminal: run through Pikkumies it refuses, and Pikkumies is blocked from running it or reading the passphrase file. That block is a safety filter, not a guarantee, since the file sits in your account. Until you confirm your copy, each Pikkumies session starts with one line saying the archives cannot be decrypted if the seedbox is lost.
Step 3: One request
pikkumies "Back up my seedbox settings to my storage box every night at 03:30, run one backup now and check that it can be read back. Keep it short."

What Pikkumies did with that one request, in the order the clip shows (before most steps it searched its own notes):
- Checked the backup state: the Storage Box was already set up and your passphrase copy confirmed.
run --mode meta: made the archive, encrypted it and sent it.schedule --daily 03:30 --mode meta: one tagged line in your crontab, logging to~/pikkumies/local/backup-remote.log(the crontab shows the same file under~/.mcxPikkumies/pikkumies/, where~/pikkumiespoints).statsandcheck: check fetched the newest archive back, decrypted it and counted 1,397 entries, without writing the archive anywhere.- Saved a short note for itself and answered.
What a nightly archive holds
| Mode | What it holds | When to use it |
|---|---|---|
meta |
Your torrent clients' settings and session state (rTorrent, Deluge, qBittorrent, ruTorrent), ~/.config without caches, top-level dotfiles, ~/.lighttpd, Pikkumies' settings and its agent memory (not the notes it saves under ~/pikkumies/memory), and a list of the files in your home (path, size, date, owner and mode; caches and secrets left out) |
Every day: small, and enough to rebuild the setup and see what was there |
full |
The whole home on its own disk, without other mounts | When you ask for everything. Above 100 GiB, or when the size cannot be measured within 2 minutes, it needs --allow-large, which Pikkumies adds only when you ask for it after hearing the size
|
Never in an archive: ~/.cache, ~/.bin, shell history files named ~/.*_history (they can hold a typed password), the AI key files and their saved copies, and Pikkumies' secrets and logs. Settings files can hold passwords (a client's web login, for one); those are in the archive, encrypted. Before sending, the run compares the uncompressed size with the free space the box reports, and stops if it would not fit.
Each time a new archive arrives, the receiver script setup installed on the box removes archives older than 30 days (the default; setup's --keep-days changes it), but always keeps the newest 3 of each mode, even when they are older.
What the Storage Box sees
The same archive seen from the Storage Box, logged in as the box's own account: one file in ~/pikkumies-backups/, in a folder named after the seedbox's host and account, and the backup key's line, limited to the receiver script. The file is gpg-encrypted (AES-256); the passphrase that opens it never reaches the box.

Restore
List the archives and restore one into a new folder; nothing is written over your files:
php ~/pikkumies/tools/backup/remote/remote.php list --human php ~/pikkumies/tools/backup/remote/remote.php restore ARCHIVE_NAME --target ~/restore-20261117
Paths keep their place relative to your home, so a file comes back as ~/restore-20261117/.config/.... Move what you need back with mv -n, which never overwrites.
If the seedbox is lost
restore works on the seedbox that made the archives. A new seedbox gets a new passphrase and its own folder at setup, so for archives of a lost seedbox, use the Storage Box login and gpg on any Linux machine:
ssh BOX_USER@STORAGEBOX_HOST ls pikkumies-backups ssh BOX_USER@STORAGEBOX_HOST ls -l pikkumies-backups/OLD_FOLDER scp BOX_USER@STORAGEBOX_HOST:pikkumies-backups/OLD_FOLDER/ARCHIVE_NAME . mkdir ~/restore-old gpg -d ARCHIVE_NAME | tar -xzf - -C ~/restore-old
The first command lists the folders; the lost seedbox's is named after its short host name and account, joined by a hyphen. The second lists its archives, named by their UTC time and mode, such as 20261117T033000Z.meta.tgz.gpg. At gpg's prompt, type your saved passphrase without the spaces between the groups.
Troubleshooting
- the backup machine's identity (its host key) is not the one pinned at setup: nothing is sent. Check with whoever runs the box, then run setup again with
--fingerprint SHA256:...and the box's real fingerprint. - the backup machine has N GiB free, less than ...: free space on the box, or use
meta. - the new key is not limited to the backup receiver (or does not log in), so it was deleted here: the box does not honour
restrictorcommand=inauthorized_keys, or the key could not log in. Setup names the line to remove there. - passphrase_saved_by_user is no (false without
--human) instats: Step 2 is not done yet.
No Storage Box yet? A Pulsed Media Storage Box comes with the ssh login this guide needs, and like your seedbox it earns AI credits from the invoices you pay, the credits Pikkumies runs on.
See also
- Zero-Knowledge Backups with Pikkumies: backups only you can read, from your own Linux machine
- Encrypted Backups from Your Seedbox with Pikkumies: borg backups of seedbox files, with deduplication
- Restoring Files from a Restic Backup with Pikkumies: one file back from a restic backup with one request
- Encrypted rclone Copies to a Storage Box with Pikkumies: rclone crypt copies, encrypted before they leave your machine
- Storage Boxes: plans and the protocols a box speaks