Expanding a MongoDB Replica Set with Everpure Fusion

So far in this series I’ve been rebuilding members on arrays I already had. In my reseed post, I rebuilt aen-mongo-06 from a replicated snapshot of the primary. This time I wanted to grow the replica set onto a fourth array. That’s usually where you open a storage ticket, wait for someone to pick an array and carve some volumes, and then start an initial sync that copies every document over the network. Two waits, and the second one gets longer every time your database grows.

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.

When You Need fsyncLock: Restoring a MongoDB Replica Set from Local Snapshots on Every FlashArray

In my reseed post, I spent a lot of time convincing you that you don’t need fsyncLock. One crash-consistent snapshot of the primary, replicated to every array, rebuilt every secondary in the set, under load, with no pause in writes. That’s still what I reach for when I’m rebuilding members.

Then I asked myself the obvious follow-up: what if I want to put every member back to the same known moment, each one from its own array’s local snapshot? That’s the one case in this series where I do reach for the lock. It’s also the Python version of my 2025 post on app-consistent snapshots across multiple FlashArrays, this time for a replica set instead of a sharded cluster.

Where FlashBlade Fits When MongoDB Lives on FlashArray

Every copy of MongoDB data I’ve made so far in this series lives on a FlashArray. The snapshots sit on the same array as the volumes they protect, and even the replicated ones land on another FlashArray as the same kind of block copy. That’s exactly what you want for fast recovery. It’s also the thing that nags at me. If every copy you have lives on the same kind of system as the live data, a bad day for that system is a bad day for your backups too. So I wanted a copy somewhere else, in a format that doesn’t care what storage produced it.

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