zrepl
litestream
Our great sponsors
zrepl | litestream | |
---|---|---|
22 | 165 | |
895 | 9,964 | |
1.2% | - | |
6.8 | 7.5 | |
about 1 month ago | 10 days ago | |
Go | Go | |
MIT License | 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.
zrepl
- Zrepl – ZFS replication
- zrepl: A one-stop, integrated solution for ZFS replication
- PVE Host disk upgrade
-
Void Linux and root-on-ZFS question
Lastly there is zrepl. This is an automatic snapshot creation, pruning and replication daemon. It lets you automate the creation of ZFS snapshots at specific intervals, apply a retention policy to them, and replicate them out to a remote system with ZFS, like a NAS with TrueNAS on it.
- Container Updating Strategies
-
How do you all prepare for a disaster recovery of your nextcloud instance?
I run it in a FreeBSD jail and take frequent ZFS snapshots using zrepl. I’ve had to restore after failed updates and it worked flawlessly.
-
Recommend ZFS automation scripts for off-server backups?
As others have noted, I use syncoid but zrepl is an alternative that could be considered.
-
Imagine You're a Goofball: Dynamic Preventative ZFS Snapshots
I’m going to throw out Zrepl again because it’s amazing: https://zrepl.github.io/
- Using ZFS backup drive for rsync manually
-
Question about best way to do zfs replication to a friends server
Current idea: We offer some form of container each other, where we have that zvol mounted somewhere for the replication use. This would mean that I could create an "inside zfs" where I create a filebased zpool. How is performance on a filebased zpool? (Although it is technically not so important that it performs critically, just trying to find the - or one of - "best" ways). Then we would offer each an ssh endpoint into that container (It doesn't have to be ssh, but it is so far convenient to setup and resilient to be open to the public). And my current plan is to use zrepl (https://zrepl.github.io/) to organise replication from my home server to this "inside" zpool.
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?
sanoid - These are policy-driven snapshot management and replication tools which use OpenZFS for underlying next-gen storage. (Btrfs support plans are shelved unless and until btrfs becomes reliable.)
rqlite - The lightweight, distributed relational database built on SQLite.
zfs_autobackup - ZFS autobackup is used to periodicly backup ZFS filesystems to other locations. Easy to use and very reliable.
pocketbase - Open Source realtime backend in 1 file
zfs - OpenZFS on Linux and FreeBSD
realtime - Broadcast, Presence, and Postgres Changes via WebSockets
lxd-snapper - LXD snapshots, automated
k8s-mediaserver-operator - Repository for k8s Mediaserver Operator project
zfswatcher - ZFS pool monitoring and notification daemon
sqlcipher - SQLCipher is a standalone fork of SQLite that adds 256 bit AES encryption of database files and other security features.
zfsbackup-go - Backup ZFS snapshots to cloud storage such as Google, Amazon, Azure, etc. Built with the enterprise in mind.
litefs - FUSE-based file system for replicating SQLite databases across a cluster of machines