Hermann.Brauer/miyagi-pbs-zfs
1
0
Fork 0
mirror of https://github.com/bashclub/miyagi-pbs-zfs.git synced 2025-12-06 06:28:43 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
Chriz
2024-04-29 11:49:34 +02:00
committed by GitHub
parent fa7a181c79
commit c0f0880448
1 changed files with 19 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

30
README.md
View File

@@ -1,9 +1,12 @@
# miyagi-pbs-zfs # miyagi-pbs-zfs
Secure Proxmox PVE with Proxmox Backup Server PBS and ZFS Pull Replication with a mostly turned off System Secure Proxmox PVE with Proxmox Backup Server PBS and ZFS Pull Replication with a mostly turned off System
Optimize Processes without colliding Replications, Backups, Monitorings or Scrubs
Save lot of Money with less performant Hardware
What it does What it does
Miyagi says, best Defense, not be present Miyagi said, best defense, no be there
Usecase
Proxmox Backupserver is running unnecessarly 24/7 Proxmox Backupserver is running unnecessarly 24/7
ZFS Replication is usually done by a zfs send, so its a push ZFS Replication is usually done by a zfs send, so its a push
@@ -14,23 +17,28 @@ Consider not using a Gateway, use Routes!
What we do... What we do...
Turning on the Computer with a @reboot Cron Turning on the Computer with a @reboot Cron
Pulling all Datasets with ZFS
Reporting ZFS Replication with 100% certainty to backuped PVE Host using Check_MK and checkzfs.py from #bashclub
Regarding to the Weekday doing Maintenance on Proxmox Backup Server for getting Space @reboot /root/pbs-zfs-daily.sh -c 200-ssd.conf && /root/pbs-zfs-daily.sh -c 200-hdd.conf
Triggering a Push (only Way to do) Backup to PBS and checking Exitcode for Report
So Miyagi at this point can pull two ZFS-Datastores to one Target Datastore, using the full Path of ZFS for Naming.
If you have multiple Target Datasets, please run multiple Configs and disable Proxmox Backup Server!
Miyagi will tag your Source for Replication with Zsync!
Replicating by a Pull with https://github.com/bashclub-zsync
Pushing a Report to Proxmox Source Host, monitored by Check_MK unsing https://github.com/bashclub/checkzfs
The Report will be found by Check_MK´s built in Autdiscovery for new Services.
Data will be valid vor about one Day (90000s) bevore it expires.
So there nothing can go wrong!
Regarding to the Weekday doing Maintenance on Proxmox Backup Server for getting more free Space.
Triggering a Push Backup with PBS (only Way to do) Backup to PBS and checking Exitcode for Report
Reporting PBS Result with 100% certainty in compact OK/WARN State to backuped PVE Host using Check_MK Reporting PBS Result with 100% certainty in compact OK/WARN State to backuped PVE Host using Check_MK
Verifying older Backups Verifying older Backups
Protecting the PBS Backups with a ZFS Snapshot Protecting the PBS Backups with a ZFS Snapshot
Updating the Host and PBS
TURNING OFF THE MACHINE!!! TURNING OFF THE MACHINE!!!
ToDo:
Prio1: Replace bashclub-zfs with bashclub-zsync:)
Test Targets Tank if less than 75% free, otherwise report to Check_MK Test Targets Tank if less than 75% free, otherwise report to Check_MK
Test Disks after PBS Maintenance, before shutdown with SmartCTL Short Test and report to Check_MK Test Disks after PBS Maintenance, before shutdown with SmartCTL Short Test and report to Check_MK
Support multiple Sources Support multiple Sources
Move Env Variables to Config File