Most of what I know about backing up a session I learned the hard way, well past midnight, watching a drive spin up and make a sound I’d never heard it make before. That session was a remix of a Hilda Garman track I’d been chopping for three weeks. The drive died halfway through the bounce. I got lucky: a half-finished copy was sitting on the system disk and I lost about four hours instead of a month. After that I stopped treating backups as a chore and started treating them as part of the job.
These are the habits that have stuck. None of them are clever. All of them have bailed me out at least once.
Export the multitrack before you touch a single plugin
The single rule I will not break. When a session leaves its original shape (a generator export, a collaborator’s bounce, a remix pack), I pull a full multitrack before I do anything else. A stereo file cannot be un-baked. This is the same reasoning that shows up in the AI-song writeups: split stems are not stems, and stem-separation software cannot recover what was never separate. Run a rough mix through a splitter and you get the same smeared performances with separation artifacts on top.
So the habit is: the moment a song lands in my folder, I export every individual track at the source’s native rate and bit depth, drop it in a dated folder, and archive it before I open an EQ. Even the parts I think are trash. Especially those. The ugly, mid-range-bloated pad is the one I’ll reach for six months later when the section feels empty.
Two drives, two locations, and a third that lives offline
I keep the working drive, a mirrored copy on a second internal disk, and a USB drive that only gets plugged in when I’m backing up. The offline one is not paranoia. It is the only copy that cannot be eaten by a failed controller, a bad driver, or me accidentally deleting the wrong folder at 1am. External enclosures and USB controllers fail in weird ways, and a drive that is plugged in is a drive that can be formatted.
Date the folder, not the file
Old habit, still the best one I have. Every session lives in a folder named with an ISO date: 2024-11-08_hilda_remix. Files inside keep their own names. I never rely on “final”, “final2”, or “FINAL_really”. When I need to find the version that still had the cleaneredis edit before I mangled it, I sort by folder name and I’m there in seconds. It also means the newest folder is always the one at the bottom of the list, which sounds trivial until it saves you.
Keep a render of the rough mix in every session folder
A 24-bit WAV of the current rough mix, dropped straight into the session folder before I close it. Not a stem. Not a master. Just the last state that worked. When I come back after two weeks and can’t remember why I liked the arrangement, I play the rough and remember. And if the plugin state gets corrupted somewhere, the rough tells me what I was aiming for.
Freeze and render the irreplaceable parts
Some sounds live only inside a plugin that may not load next year. The oddball old electro bass, the specific chorus on a stab. If a part depends on a plugin I’m not confident about (a discontinued installer, a dongle that lives on another machine), I render it to audio and mute the original. Not delete. Mute. The audio is my insurance, the plugin stays available if I need to change the part.
This one is closer to archiving than backup, but it’s saved me twice when a driver update killed a plugin’s authorization and I needed to finish a mix that night.
Back up the plugin list and the driver notes
The audio files are the obvious part. The less obvious part is the text file that explains how the session was made: which plugins, which versions, which driver mode, which ASIO buffer setting, which machine. When I rebuild a session on a new PC I don’t want to rediscover that the old template needs a specific driver config to behave. I keep a plain-text notes file next to every serious project, and a separate running document for the machine itself. It’s the least glamorous file in the studio and I’ve read it more times than any plugin manual.
Archive the source packs alongside the session
If a session uses a sample library or a stem pack, I archive the source folder with the project. Not a link. The actual files. Sample library vendors change their content, retire versions, and sometimes stop distributing a product entirely. A session that depends on a sample that no longer exists is a session that won’t load cleanly. The curated libraries have a workflow advantage because they don’t pull you out to browse folders and websites; the trade-off is that when the vendor disappears, your project has to survive on its own. Backups are how it survives.
One archive rule for the whole library
The habit that took longest to build: a single top-level archive that looks the same year to year. Projects/ with dated subfolders, Renders/ with rough mixes and finals, Source/ with the original packs, Notes/ with the text files. No clever directory structure, no symlinks, no cloud-only folders. It’s boring on purpose. When a drive dies I don’t need to remember where anything is, because the archive is already in the shape I expect.
Test the restore, not just the backup
A backup that’s never been put through a restore is a hunch, not a backup. Once a year, ideally more, I pull a random session off the offline drive and load it on a clean machine. If it opens, plays, and finds its files, I trust the archive. If it doesn’t, I find out on a quiet Tuesday instead of on a deadline. This is the habit everyone skips and the one that matters most.
Version-control the template separately
The template is the thing I touch most and the thing most likely to break. I keep dated copies of the template itself, not just sessions built from it. A 2019 template that still loads cleanly is worth more than a fancy rebuild that fights the DAW on launch, and I want to be able to go back to the older one when the new one misbehaves. The template is a project in its own right and it gets backed up like one.
When a mix leaves the machine, ship the stems
Every time a mix goes out for mastering, a remix, or a collaborator, I send the full multitrack plus a readme that lists the tempo, the key, the sample rate, and the names of every plugin chain worth preserving. If the recipient has the multitrack, they can do the work properly; if all they get is a stereo file, the session is over. The AI-session writeups make the same point for a different reason: export the multitrack, keep every file it gives you, even the ones you think you won’t need. Same rule, no exceptions.
None of this is archive-grade professionalism. It’s just the routine that lets me open a folder and find a song I forgot I had, on a machine I barely recognize, and still finish the mix.