sanoid
litestream
Our great sponsors
sanoid | litestream | |
---|---|---|
118 | 165 | |
2,872 | 9,964 | |
- | - | |
7.1 | 7.5 | |
7 days ago | 9 days ago | |
Perl | Go | |
GNU General Public License v3.0 only | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
sanoid
- ZFS took full backup (send/receive) without snapshots but now what to prevent another full transfer?
-
ZFS for Dummies
I’m on the other end of the spectrum. I like knowing the flags and settings I use to create the pools.
For snapshots and replication take a look at sanoid (https://github.com/jimsalterjrs/sanoid).
-
Automatic container snapshots? cv4pve or zfs for a small homelab?
I use a combo of PBS and ZFS with Sanoid. The ZFS snapshots are nice because you define it all in a config file with frequent, hourly, daily, weekly, monthly snaps retained however you want. Importantly I use that on the root pool as well as my data pools. With PBS I have a custom retention config and have it backing up VMs and LXCs every couple hours. The PBS dedupe functionality makes it possible to keep full backups going back ages with minimal storage consumption, just the changed blocks. PBS is running inside a VM yes, but it’s storage is on another pool.
- [QUESTION] Dataset level replication
-
YSK: You can 'zfs send' over SSH to the cloud
[3] https://github.com/jimsalterjrs/sanoid/
-
New to ZFS, what layout to choose for 4x20TB drives?
No, it's written by the developer of Sanoid and Syncoid. The foremost open source ZFS snapshotting tool. He contributes on this sub all the time.
- Python Port of 600 Line Bash Script: rsync-time-machine.py for Rsync Backups
-
Some questions about the limitations of ZFS send.
Hi there! Not so much to answer your questions, but are you aware of Sanoid and syncoid? It does backup and remote Sync in the most seamless way. Perhaps this would solve some of your concerns...
- Help me understand zfs send for incremental send AND replication?
- Ask HN: Why isn't BTRFS the default FS in home-oriented Linux distributions?
litestream
-
Ask HN: SQLite in Production?
I have not, but I keep meaning to collate everything I've learned into a set of useful defaults just to remind myself what settings I should be enabling and why.
Regarding Litestream, I learned pretty much all I know from their documentation: https://litestream.io/
-
How (and why) to run SQLite in production
This presentation is focused on the use-case of vertically scaling a single server and driving everything through that app server, which is running SQLite embedded within your application process.
This is the sweet-spot for SQLite applications, but there have been explorations and advances to running SQLite across a network of app servers. LiteFS (https://fly.io/docs/litefs/), the sibling to Litestream for backups (https://litestream.io), is aimed at precisely this use-case. Similarly, Turso (https://turso.tech) is a new-ish managed database company for running SQLite in a more traditional client-server distribution.
-
SQLite3 Replication: A Wizard's Guide🧙🏽
This post intends to help you setup replication for SQLite using Litestream.
-
Ask HN: Time travel" into a SQLite database using the WAL files?
I've been messing around with litestream. It is so cool. And, I either found a bug in the -timestamp switch or don't understand it correctly.
What I want to do is time travel into my sqlite database. I'm trying to do some forensics on why my web service returned the wrong data during a production event. Unfortunately, after the event, someone deleted records from the database and I'm unsure what the data looked like and am having trouble recreating the production issue.
Litestream has this great switch: -timestamp. If you use it (AFAICT) you can time travel into your database and go back to the database state at that moment. However, it does not seem to work as I expect it to:
https://github.com/benbjohnson/litestream/issues/564
I have the entirety of the sqlite database from the production event as well. Is there a way I could cycle through the WAL files and restore the database to the point in time before the records I need were deleted?
Will someone take sqlite and compile it into the browser using WASM so I can drag a sqlite database and WAL files into it and then using a timeline slider see all the states of the database over time? :)
-
Ask HN: Are you using SQLite and Litestream in production?
We're using SQLite in production very heavily with millions of databases and fairly high operations throughput.
But we did run into some scariness around trying to use Litestream that put me off it for the time being. Litestream is really cool but it is also very much a cool hack and the risk of database corruption issues feels very real.
The scariness I ran into was related to this issue https://github.com/benbjohnson/litestream/issues/510
-
Pocketbase: Open-source back end in 1 file
Litestream is a library that allows you to easily create backups. You can probably just do analytic queries on the backup data and reduce load on your server.
https://litestream.io/
- Litestream – Disaster recovery and continuous replication for SQLite
- Litestream: Replicated SQLite with no main and little cost
-
Why you should probably be using SQLite
One possible strategy is to have one directory/file per customer which is one SQLite file. But then as the user logs in, you have to look up first what database they should be connected to.
OR somehow derive it from the user ID/username. Keeping all the customer databases in a single directory/disk and then constantly "lite streaming" to S3.
Because each user is isolated, they'll be writing to their own database. But migrations would be a pain. They will have to be rolled out to each database separately.
One upside is, you can give users the ability to take their data with them, any time. It is just a single file.
[0]. https://litestream.io/
-
Monitor your Websites and Apps using Uptime Kuma
Upstream Kuma uses a local SQLite database to store account data, configuration for services to monitor, notification settings, and more. To make sure that our data is available across redeploys, we will bundle Uptime Kuma with Litestream, a project that implements streaming replication for SQLite databases to a remote object storage provider. Effectively, this allows us to treat the local SQLite database as if it were securely stored in a remote database.
What are some alternatives?
zrepl - One-stop ZFS backup & replication solution
rqlite - The lightweight, distributed relational database built on SQLite.
zfs-auto-snapshot - ZFS Automatic Snapshot Service for Linux
pocketbase - Open Source realtime backend in 1 file
znapzend - zfs backup with remote capabilities and mbuffer integration.
realtime - Broadcast, Presence, and Postgres Changes via WebSockets
zfs_autobackup - ZFS autobackup is used to periodicly backup ZFS filesystems to other locations. Easy to use and very reliable.
k8s-mediaserver-operator - Repository for k8s Mediaserver Operator project
zfs - OpenZFS on Linux and FreeBSD
sqlcipher - SQLCipher is a standalone fork of SQLite that adds 256 bit AES encryption of database files and other security features.
UrBackup - UrBackup - Client/Server Open Source Network Backup for Windows, MacOS and Linux
litefs - FUSE-based file system for replicating SQLite databases across a cluster of machines