backups
Differences
This shows you the differences between two versions of the page.
| backups [2026/11/02 23:46] – created scott | backups [2026/11/02 23:47] (current) – scott | ||
|---|---|---|---|
| Line 5: | Line 5: | ||
| A good backup infrastructure can mean many things depending on the scale, size, and criticality of data. | A good backup infrastructure can mean many things depending on the scale, size, and criticality of data. | ||
| - | In the case of my lab, I treat it as a production-grade hypervisor with RTO of within 24 hours and RPO of within 24 hours. This means that I run my backups once daily and find it acceptable to lose up to 24 hours of data between backups (Recovery Point Objective) as well as that should I need to recover from a failure, I can restore within 24 hours(Recovery Time Objective.) In most environments the RTO would be significantly lower but I run on a very limited budget. | + | In the case of my lab, I treat it as a production-grade hypervisor with RTO of within 24 hours and RPO of within 24 hours. This means that I run my backups once daily and find it acceptable to lose up to 24 hours of data between backups (Recovery Point Objective) as well as that should I need to recover from a failure, I can restore within 24 hours(Recovery Time Objective.) In most environments the RTO would be significantly lower but I run on a very limited budget. I have before worked on environments with <5min RTO/RPO goals. |
| As this is treated as production-grade it needs a proper 3-2-1 backup strategy. For this I use both TrueNas and Proxmox Backups Server (PBS.) | As this is treated as production-grade it needs a proper 3-2-1 backup strategy. For this I use both TrueNas and Proxmox Backups Server (PBS.) | ||
backups.txt · Last modified: by scott
