I remember when I moved from Windows to macOS and I wasn’t used to how things run in the new environment. I had backups of all my projects on an external hard drive, and that was my whole backup strategy.<\/p>\n\n\n\n
At one point, I wanted to restore a few projects from my external backup drive back to my main drive. In the past, when Windows asked whether I want to merge<\/em> the folders and their contents or not, I simply clicked \u201cYes\u201d and all went well. When my new macOS machine asked me if I want to replace<\/em> the files, I simply agreed to it. My old Windows habit of clicking \u201cYes\u201d lead me to delete every song I had ever written. ALL OF THEM.<\/p>\n\n\n\n After spending some time sulking that I had lost my songs, I moved on. Hey, things happen. The time spent sulking meant not writing for another year and a half or so. Good thing nowadays I\u2019m a mixing and mastering guy, eh?<\/p>\n\n\n\n So, don’t you put off sorting out your backup situation like I did. Procrastinating is always a bad idea. There are two more disaster stories at the end of this article, and if this one didn\u2019t do it, they will most likely convince you to save your future self a lot of time, frustration and money.<\/p>\n\n\n\n Be your future self\u2019s best friend, will ya?<\/p>\n\n\n\n The way you arrange your files in your system is very important for your peace of mind and overall efficiency. Proper file management and keeping track of where every file lives will end up saving you a lot of time over the course of a year. For instance, a simple organization strategy would be like this: Create two parent folders, named \u201cIn Progress\u201d and \u201cFinished Projects.\u201d Each time you begin a new project, simply create a subfolder in the \u201cIn Progress\u201d folder named for the artist, client or project. After you finish the project, move that artist folder to the \u201cFinished Projects\u201d folder. This method makes finding particular projects very simple. Naming files and folders is also an important consideration and we will get to that in a bit. For my music projects, I have a dedicated \u201cWork Drive\u201d that houses three parent folders:<\/p>\n\n\n\n Folder 1: <\/strong>A_Work_In_Progress<\/p>\n\n\n\n This folder contains subfolders such as:<\/p>\n\n\n\n \t\u2022 Mastering<\/p>\n\n\n\n \t\u2022 Mixing<\/p>\n\n\n\n \t\u2022 Practice<\/p>\n\n\n\n \t\u2022 Production<\/p>\n\n\n\n \t\u2022 Recording<\/p>\n\n\n\n Folder 2: <\/strong>Finished<\/p>\n\n\n\n This folder, unsurprisingly, is where I archive finished projects. This folder contains the same subfolders as A_Work_In_Progress.<\/p>\n\n\n\n At the end of every project I create some files to be archived and possibly delivered to the client:<\/p>\n\n\n\n \t1. Bounced\/rendered\/exported stems<\/p>\n\n\n\n \t2. All tracks in the session are frozen\/committed<\/p>\n\n\n\n \t3. All related project folders are moved into the main project folder<\/p>\n\n\n\n \t4. The project folder is compressed so that no audio files get misplaced.<\/p>\n\n\n\n Folder 3: <\/strong>On_Hold<\/p>\n\n\n\n This folder has random projects that are on hold for one reason or another. Self-explanatory, I know.<\/p>\n\n\n\n In my case, each of the three parent folders contains artist folders labeled with the artist or contact person\u2019s name. Inside each artist folder I have subfolders labeled for the year I received the project. Each year folder contains folders for each month in which I had a project. I number the month folders sequentially to make it easier to find them. Below is an example of my folder structure (Don\u2019t judge me, one can dream):<\/p>\n\n\n\n BAND NAME<\/em> > YEAR<\/em> > MONTH<\/em> > PROJECT NAME > SESSION<\/em><\/p>\n\n\n\n Phil Collins > 2019 > 05 May > Album 9 > Song_1 Example folder structure:<\/p>\n\n\n\n Consistency is an important element of organization, so I stay consistent with my folder structure and how all my files are named. To that end, I use NameChanger<\/a> for my batch renaming needs within macOS, and AdvancedRenamer<\/a> when working in Windows. Here are some of my batch renaming actions:<\/p>\n\n\n\n How to properly backup: The 3-2-1 Rule<\/p>\n\n\n\n Follow the 3-2-1 backup rule. The 3-2-1 backup rule is an acronym for a sure-fire strategy to keeping your data safely backed up.<\/p>\n\n\n\n \t\u2022 Keep at least 3 <\/strong>current <\/strong>copies of your data<\/p>\n\n\n\n \t\u2022 Store 2<\/strong> copies on different storage media<\/p>\n\n\n\n \t\u2022 1<\/strong> of the copies must be stored offsite<\/p>\n\n\n\n 3 copies of your data means that you have your primary <\/em>data and two backup copies. Remember that all storage devices fail at some point and using different types of storage media decreases the likelihood that multiple backup copies will fail at the same time. Therefore, the two backup copies should be different storage types, like external SSD or cloud storage.<\/p>\n\n\n\n Disasters such as fire, theft and floods can destroy all local backups. This means you must store one of your backups offsite. Cloud storage subscription with companies like Backblaze, Carbonite and IDrive provide secure, offsite storage plans with automated backup options. Alternatively, your offsite backup can simply be a drive that you take home with you each night. If you work at home, you could keep that drive at a family member\u2019s home or in a secure storage area in a separate building, like your garage.<\/p>\n\n\n\n For audio professionals, your backup strategy could look something like this:<\/p>\n\n\n\n \u2022 Your audio\/session drive should be a separate drive from your system drive\u2013don\u2019t cheat on this, even if you work on a laptop.<\/p>\n\n\n\n \u2022 Your audio\/session drive should be synced to a cloud-based backup service that is constantly backing up your data.<\/p>\n\n\n\n \u2022 Create a backup schedule with Carbon Copy Cloner or ChronoSync to clone your work drive to a backup drive, which is attached to your system or your local network.<\/p>\n\n\n\n Here is how I setup my system and backup workflow:<\/p>\n\n\n\n Backup 1<\/strong><\/p>\n\n\n\n CarbonCopyCloner<\/a> backs up the entire A_Work_In_Progress folder, hourly, to my local Google Drive folder. As you might expect, my Google Drive folder automatically syncs and uploads to Google\u2019s cloud servers.<\/p>\n\n\n\n Backup 2<\/strong><\/p>\n\n\n\n CarbonCopyCloner also clones A_Work_In_Progress to my \u201cWork Backup\u201d drive.<\/p>\n\n\n\n Backup 3<\/strong><\/p>\n\n\n\n Backblaze<\/a> online backup is set to continually backup A_Work_In_Progress folder to a secure cloud storage server.<\/p>\n\n\n\n While the 3-2-1 backup rule is not 100% fail-safe, it is the best practice recommended by US government authorities such as the United States Computer Emergency Readiness Team<\/a>. IT security experts also recommend this strategy as the best way to keep your data safe from disappearing off the face of the Earth.<\/p>\n\n\n\n You could backup manually, but this means you must remember to do it. Automating the backup process with a software solution ensures consistent backups and reduces the stress of having to remember to backup. I use CarbonCopyCloner<\/a> on the Mac to automate all my backing up.<\/em> Acronis True Image<\/a> looks like the comparable software for Windows.<\/p>\n\n\n\n It\u2019s very important that your backup solution maintains multiple versions of your files; meaning older versions are kept, even when newer versions are backed up. What if you accidentally delete an important file before you backup or simply wish to go back to an older version of your project? Versioning to the rescue!<\/p>\n\n\n\n Backing up your project data is vital; however, do not neglect to backup your system drive. Backup programs like CarbonCopyCloner<\/a> and Chronosync<\/a> can create a bootable clone of your system drive. A bootable clone can be a godsend if your system drive fails or becomes corrupt. If you have a bootable backup, you can simply swap your boot drive, restart, and you\u2019re back to work.<\/p>\n\n\n\n For both versioning and system restore, one could use Apple\u2019s built-in Time Machine utility. For things like restoring previous copies of a file, I find Time Machine easy to use, surpassing both Backblaze<\/a> and CarbonCopyCloner<\/a>. However, Time Machine will not create a bootable backup of your system drive and is not the most efficient solution for backing up audio drives.<\/p>\n\n\n\n Spend the time to develop an organized drive and folder structure.<\/p>\n\n\n\n (Re)name your files so that they work for<\/em> you, and not against<\/em> you.<\/p>\n\n\n\n Most important of all, is to backup properly, using the 3-2-1 rule.<\/p>\n\n\n\n Do not wait until disaster strikes before you take this seriously.<\/p>\n\n\n\n Retrieving old sessions for a client not only adds value to your services but also earns you some brownie points. In fact, you\u2019ll earn brownie points even if you charge for the service!<\/p>\n\n\n\n Please backup. Now. Be your future self\u2019s best friend, will ya?<\/em><\/p>\n\n\n\n Once upon a time, there was this super awesome music producer called Patch. He was asked to record a few songs for the incredibly talented Nicola Brown so he called upon some of his most trusted engineer friends, Kevan and Tiki. Together they recorded a beautiful sounding drum kit – one of the best sounds ever captured by anyone, ever.<\/p>\n\n\n\n Patch, being the lovely, caring person he is, decided to collect the session files the following day as it was late and everyone wanted to go home. Alas, on his return he found no trace of the Pro Tools project recorded the previous evening. Gone were the 6 hours worth of audio. Gone was the best drum sound ever. Gone was some nice sounding acoustic and electric guitars. Gone was Patch’s happiness.<\/p>\n\n\n\n Close to tears, he booked the studio for the following week and re-tracked the whole EP. It sounded much better but was still a huge headache. So remember kids, always backup your sessions, no matter what. – Patch Boshell<\/a><\/p>\n\n\n\n A few months ago I got an external hard drive specifically to transfer work between my office computer and my laptop. At first, I was copying and pasting the work between the computers and the external hard drive, effectively creating 3 backups. As time went by I got lazy and started working directly from the external hard drive instead.<\/p>\n\n\n\nKeep Your Drives Organized<\/strong><\/h4>\n\n\n\n
Folder Hierarchy<\/strong><\/h4>\n\n\n\n
<\/p>\n\n\n\n![\"\"\/](\"https:\/\/blog-uploads.imgix.net\/2019\/07\/img_5d3030d982383.png?auto=compress%2Cformat\")
<\/figure>\n\n\n\nFile Naming Conventions<\/strong><\/h4>\n\n\n\n
\n
Putting It All Together<\/h4>\n\n\n\n
Manual vs. Automatic Backups<\/strong><\/h4>\n\n\n\n
Keep Older Versions of Your Files<\/strong><\/h4>\n\n\n\n
System Drive Backup<\/h4>\n\n\n\n
In Conclusion<\/h4>\n\n\n\n
Story #2<\/h4>\n\n\n\n
Story #3<\/h4>\n\n\n\n