As I mentioned in the post about my backup system, I run
regularly, to test the integrity of my backup. It has never reported any error
in my repository. It performs a quick, shallow check, and does not verify that
all the data is intact. I also restore a random file, whenever I run
restic check, to test recoverability.
Shortly after I wrote the previous post, I decided to run
restic check --read-data for the first time ever. This reads every file in the repository
and simulates a full restore. To my utter horror, it reported many errors like
Pack ID does not match, want 5e66c2ac, got e80051de pack d64be86d contains 1 errors: [Blob ID does not match, want 8ebf2c10, got 350f6ba1]
Computing devices and online services can fail catastrophically and take our data with them. It is crucial that we have a robust system to backup and restore our data, to protect against such events. This post details what I wanted from the backup system for my personal data and the tools I use to achieve them. This system has served me well over the last 5 years, across fat-fingerings and disk failures.
At a previous job, we had several instances of Ruby on Rails applications connecting to PostgreSQL through PgBouncer. The services and databases were deployed on bare-metal servers and chugged along fine. We then decided to migrate to AWS. Upon migration, we noticed that PgBouncer started leaking connections to PostgreSQL like a sieve, leading to exhaustion of the maximum number of connections configured in RDS.
Vim offers many ways to use the command-line tools available on your system when editing. You can:
This is third in the series of posts describing how I use GnuCash to manage my finances. In previous posts, I had discussed how I organize my accounts, record transactions and handle taxation in GnuCash. In this post I’ll show how GnuCash can be configured to fetch the current NAV of mutual funds from the Internet.
Older Posts →
All opinions are my own. Copyright 2005 Chandra Sekar S.