vault backup: 2026-05-16 08:29:40
This commit is contained in:
@@ -0,0 +1,14 @@
|
||||
---
|
||||
created: 2026-05-16T08:17:10
|
||||
up:
|
||||
- "[[Library]]"
|
||||
title: PracticalZFS.com
|
||||
source: https://discourse.practicalzfs.com/
|
||||
author:
|
||||
published:
|
||||
topics:
|
||||
---
|
||||
a very good resource for all things
|
||||
- [[OpenZFS|zfs]]
|
||||
- [[Sanoid and Syncoid|sanoid/syncoid]]
|
||||
|
||||
+1
-1
@@ -1,8 +1,8 @@
|
||||
---
|
||||
category:
|
||||
- "[[Note]]"
|
||||
- "[[Software]]"
|
||||
type:
|
||||
- "[[Linux]]"
|
||||
title: Docker
|
||||
created: 2026-05-15T07:19:07
|
||||
tags:
|
||||
|
||||
@@ -36,7 +36,7 @@ Purchased 10 of these as a job lot off eBay
|
||||
|
||||
### Details
|
||||
|
||||
I've checked 8 of the drives and they're all the same, output from one of the drives is below
|
||||
I've checked 8 of the drives and they're all the same, output from one of the drives is below (logged smart data is [[2026-05-11 1237 HGST 4TB SAS drive smart data|here]]).
|
||||
|
||||
output from `smartctl -i /dev/sdb`
|
||||
```
|
||||
|
||||
+6
-3
@@ -1,14 +1,17 @@
|
||||
---
|
||||
category:
|
||||
- "[[Note]]"
|
||||
- "[[Software]]"
|
||||
type:
|
||||
- "[[Linux]]"
|
||||
- "[[CLI]]"
|
||||
title: OpenZFS
|
||||
created: 2026-05-14T14:17:36
|
||||
tags:
|
||||
- project
|
||||
---
|
||||
## resources
|
||||
|
||||
- [forum](https://discourse.practicalzfs.com/)
|
||||
|
||||
## zfs commands
|
||||
|
||||
### zfs snapshot management
|
||||
@@ -45,7 +48,7 @@ clear partial download on dataset
|
||||
zfs something -A <pool/dataset>
|
||||
```
|
||||
|
||||
## OpenZFS delegation
|
||||
## openZFS delegation
|
||||
|
||||
[[2026-05-16 0701 Improve Replication Security With OpenZFS Delegation|Improve Replication Security With OpenZFS Delegation]]
|
||||
|
||||
|
||||
@@ -1,12 +1,20 @@
|
||||
---
|
||||
category:
|
||||
- "[[Note]]"
|
||||
- "[[Software]]"
|
||||
type:
|
||||
title: " Sanoid and Syncoid Setup"
|
||||
created: 2026-05-12T21:09:25
|
||||
tags:
|
||||
- project
|
||||
---
|
||||
## resources
|
||||
|
||||
- [github](https://github.com/jimsalterjrs/sanoid)
|
||||
- [forum](https://discourse.practicalzfs.com/)
|
||||
|
||||
## intro
|
||||
|
||||
I've set this up on on a [[Proxmox]] backup machine, it creates the [[OpenZFS|zfs]] snapshots on the remote machine and them pulls them into it's own zfs pool.
|
||||
|
||||
## initial setup
|
||||
@@ -51,3 +59,17 @@ systemctl stop timer.sanoid.service
|
||||
systemctl disable time.sanoid.service
|
||||
```
|
||||
|
||||
## on zfs bookmarks
|
||||
|
||||
The creator of sanoid, Jim Salter, gave a good overview of bookmarks [here](https://discourse.practicalzfs.com/t/can-sanoid-leave-bookmarks-behind-after-deleting-snaphots/4381/4)
|
||||
|
||||
> [!NOTE] Jim Salter
|
||||
> Bookmarks are only useful in a **single** scenario:
|
||||
>
|
||||
> When you already have a common snapshot between source and target–note, you must **already** have the common snapshot on both sides–you may first create a bookmark **on the source** and then destroy the snapshot **on the source** without breaking the replication chain.
|
||||
>
|
||||
> However, the snapshot still has to be present **in full** on the target.
|
||||
>
|
||||
> ...
|
||||
>
|
||||
> This allows you to more easily keep much shallower archive depth on a source system with a few (or one) small, fast drives, while keeping much deeper archives on a target system with many more, or larger drives.
|
||||
Reference in New Issue
Block a user