Approximately 24 hours ago I switched over to my PC and fired up Nuke because I needed to re-render a couple precomps on which I needed to do some lightsaber roto. One wasn’t rendered with the correct overscan and another shot wasn’t rendered at all. I opened the first script and was greeted with a watermark from Reel Smart Motion Blur, which was needed for said precomp.

I figured my license server was off.. again. Recently it’s just been powering down for no reason. I went into my network closet to turn it back on and over the next few minutes, began to panic as I watched it kinda-sorta try to turn on and then fail. Status light would flicker a few times, I caught a glimpse of the startup screen once, and then it was just dead.

Dead Server

Fantastic. Not only does this stupid little mini-PC serve my RSMB license, but my DaVinci Resolve Project Server also lives on it. I do occasional backups of those libraries to my Synology, but discovered my last backup was from JUNE 2025. BAD COW, VERY BAD COW.

So today, I took it to the PC repair shop my brother works at, hoping it was just a faulty power cable. But it was not. So we cracked it open and took the M.2 drive out, and shoved it into their data recovery system (wish I had a photo of that; it’s glorious; just a motherboard and various IO hanging on a wall). Luckily we were able to boot right into the Windows 11 install that was on it, and I could get into the Resolve Project Server UI and export backups.

Restoring Resolve

Actively experiencing this xkcd comic, as one does in these situations, we just logged into my Synology dashboard, which I had bookmarked on the server, using my credentials saved in 1Password, which was also installed; yippee! Uploaded the Resolve backups to a safe place back home, then trekked home to sort that out.

Turned out you can’t just go from a project server setup to your local database, as the Project Server uses PostgreSQL and the local database uses some disk database setup. So after a few failed attempts and poking around, I ultimately just installed the Project Server software directly on my Mac Studio, and then restored the backup files and re-added them in the network tab in Resolve. The Mac is basically just looking at itself for “network” projects. Whatever. It’s working again.

Floating License Fun!

Next I figured I should get the RSMB floating license sorted out during normal business hours in case I needed to get support involved (spoiler: I did). Scouring their FAQ, I discovered this would involve a $49.95 license transfer fee. And I’d have to run a node lock remover tool on the old system and then send a text file that generates back to their sales department.

So back to the shop I went, and we fired up the server and downloaded the tool… only to have it not work at all. I don’t know why, but it simply wouldn’t do anything but flash the outline of a terminal window for half a second and then do nothing else. So I opted to just gather whatever information I could. Turns out I had screenshots of the license server and the original system ID prompt that it gave me back when I set it up. I threw those onto the Synology and went home again.

Emailing RE:Vision Effects, I explained the situation and provided them the system ID of my old server and that of my Mac Studio. Within 2 hours, they sent back an updated license file and waived the transfer fee, since it was a machine failure–YAY!

So wins all around, but quite an involved hiccup to deal with in a pressing time on a project I’m trying to get wrapped up. One perk: I no longer have to worry about that stupid Windows 11 server staying running in the closet. I was wanting to switch it out for a Linux server eventually… so now at least it’s out of the picture. The main lesson here is I need to be way more diligent about Resolve project library backups. An automated way to do so would be great…

Okay, back to roto.