Replacing the MongoDB Replica Set Initial Sync with FlashArray Snapshots

In my last post, I restored every member of a replica set from one snapshot on the same array. In real life, you usually lose one member: a host dies, someone rebuilds the wrong VM, a member’s data gets damaged. And each member of a replica set is most likely on a different array. MongoDB rebuilds a member from nothing with an initial sync, the job every DBA dreads, and I wanted to see how much of that job I could hand off to the storage tier.

Snapshot Recovery of a MongoDB Replica Set on a Single FlashArray

I’ve been running MongoDB on Everpure FlashArray in my lab, and the first thing I wanted to prove is the simplest one. Can I snapshot an entire replica set while it’s taking writes, drop a database, and get everything back just by overwriting volumes?

In this post, I’m going to show you exactly that: a three-member replica set, one mongod per node, every member on volumes from the same FlashArray, four writers and an updater hammering away during the snapshot, and no fsyncLock. If you’ve read my intro to this series, this is the first hands-on post. If protection groups, the oplog, or crash consistency are new to you, the terms list in the intro defines them in plain words. Let’s go.

Why Run MongoDB on Everpure FlashArray?

I’ve spent a lot of years around SQL Server on shared storage, and lately I’ve been spending that time with MongoDB. The database engine couldn’t be more different, but the storage conversation sounds very familiar. How do I protect it? How do I grow it? How do I get another copy of it somewhere else, and how long is all of that going to take?

This is the first post in a series where I run MongoDB replica sets on Everpure FlashArray in my lab, with the commands and the real output in every post. In this post, I’m going to show you why you’d run MongoDB this way at all: what MongoDB asks of storage, where disks inside every node start to hurt, what changes when the volumes come from a FlashArray, and a map of the rest of the series. There’s no lab output in this one, just the reasoning. Let’s go.

SQL Server Linux Container Images Got Smaller: Image Size and Startup Time Across Cumulative Updates

This week I was at PASS Data Community Summit in Seattle, and I attended a session called “An Inside Look at How Microsoft Builds SQL Features, by Bob Ward, Naveen Prakash, and Travis Wright, all of whom are on the SQL Server team. In this session, Travis mentioned that they reduced the SQL Server container image size by a meaningful amount using AI agents that helped discover unused code in the image, but details on how much and when were lost when the conversation moved on to the next topic. So I set out to find out exactly which SQL Server build this came out in, and I also wanted to measure how much we saved. They also mentioned that startup times were better now.

Installing and Configuring containerd as a Kubernetes Container Runtime

This post shows you how to install containerd as the container runtime for Kubernetes and configure it to use the systemd cgroup driver. The commands below were tested on Ubuntu Server 24.04 with containerd 2.2.1 from the Ubuntu updates repository. The exact Ubuntu package revision can change as updates are published. See the Kubernetes container runtime documentation for more about runtime requirements.

Prepare the host

Kubernetes expects swap to be disabled by default. Turn it off now and comment out any swap entries in /etc/fstab so it stays off after a reboot.

Automated SQL Server Benchmarking with HammerDB and Docker: A Complete Testing Framework

I’m excited to announce the release of a new open-source project that fully automates HammerDB benchmarking for SQL Server using Docker. If you’ve ever needed to run TPC-C or TPC-H benchmarks multiple times, you know how time-consuming the manual setup can be. This project removes the hassle and gets you up and running a single command: ./loadtest.sh.

Updated for HammerDB 6.0

What’s new since I first wrote this:

  • Every run writes a JSON report and HTML charts, not just console output.
  • Response times are broken out per stored procedure, with p99 through p25.
  • You can tag runs with a PROFILE_ID and diff two configurations directly.
  • loadtest.sh runs through the whole lifecycle of a load test.

Why I Built This

In my work, I frequently benchmark SQL Server configurations, whether I’m comparing versions, testing new hardware, or validating performance tuning changes. Setting up HammerDB manually each time became a significant time bottleneck (see what I did there! ;). I needed an automated solution that would work consistently across different environments and reduce the time required to get test results.

Ten Years of PowerShell

Ten years ago today, I filmed a Pluralsight Play by Play on open source PowerShell. I was standing between Jason Helmick and Jeffrey Snover, trying very hard not to look like the guy who had learned PowerShell six weeks earlier. I later wrote about that experience, but that day was the beginning of a much longer story.

Jason Helmick, Jeffrey Snover, and Anthony Nocentino during the 2016 PowerShell Play by Play

Building a DBA Agent for Your SQL Server Estate with MCP

Yesterday I gave a talk for MSSQLTips called “Building a DBA Agent for Your SQL Server Estate”. Which you can watch here. What I want to do here is pull the whole thing together in writing: the demos, what I actually ran against a live SQL Server estate, and the argument I’m making when I say an AI agent can be trusted near production.

If you’ve been following along, this is the third post in what’s turned into a series. In Giving AI Agents Visibility Into SQL Server with MCP, I built sql-mcp-server, a custom MCP server that gives an agent real DMV access. I said at the end of that post that skill files were coming in a follow-up also in Using Claude Code as a Database SRE Agent, I showed a skill file catching a silently unprotected DR instance against the Everpure Fusion fleet API and how to build compliance and observability reports quickly. So here we are.

Cleaning Up My Blog's SEO and AEO with Claude in GitHub Copilot

I’ve been running this blog on Hugo for a long time, and like most blogs with real history, it’s accumulated some tech debt. Some of it is my own fault. This blog started on WordPress, where it ran for seven years, and I migrated it to Hugo back in 2021. That migration exported those seven years of posts straight from WordPress’s database into raw Markdown, HTML tags, inline styles, and all. I am not a good HTML programmer, and it showed. Broken tags, stray   entities, image markup that only sort of worked, all of it scattered across dozens of WordPress migrated posts.

Asynchronous Replication of Snapshots from an ActiveCluster Pod to a Third Array

I’ve been rebuilding my three-site SQL Server demo lab, and I ran into something I’ve wanted for a long time. If you’ve ever designed a SQL Server environment on ActiveCluster, you know the pattern: two FlashArrays running a synchronously replicated pod for zero RPO between sites, and a third array somewhere else for a longer retention, disaster recovery copy. The problem was that you couldn’t get the data to that third array directly from the pod. Protection groups inside a stretched pod simply couldn’t have an array target.