Self-Hosting

Introduction to Borg Backup

I’ve learned the hard way that having a reliable backup system is crucial for any homelab setup. Borg Backup has been my go-to tool for deduplicating backups, and it’s served me well - until I recently encountered a failed repository. This experience taught me some valuable lessons about recovery and prevention.

Understanding Borg Backup Repositories

Before diving into the recovery process, it’s essential to grasp how Borg Backup repositories work. A repository is the central storage location for all your backups, where Borg stores deduplicated data. When you create a repository, Borg initializes it with a unique ID, ensuring data integrity. I’ve seen this go wrong when the repository index gets corrupted, so it’s crucial to understand how it works.

Introduction to CPU Usage Spikes

I’ve had my fair share of CPU usage spikes on my home server, and I’ve learned that they can be caused by a variety of factors, including resource-intensive applications, misconfigured services, or even malware. The real trick is to identify the root cause of the spike and take corrective action. In my experience, using systemd and ps can be a powerful way to manage CPU usage spikes.

Introduction to Self-Hosting

I’ve spent years running my own Linux servers, and over time, I’ve experimented with a bunch of self-hosted services. Recently, I decided to take a step back and simplify my setup. This involved figuring out what actually works for me and what I’d self-host again on Linux.

Choosing the Right Services

It’s easy to get carried away with all the services available for self-hosting. I’ve seen this go wrong when people try to host too many services at once. The real trick is to prioritize what’s truly necessary. For me, that includes a personal wiki, a photo gallery, and a Git server. These services are crucial for my daily workflow and personal projects.