A manuscript can represent months or years of irreplaceable work. I learned that lesson the expensive way in 2012, when my computer reported that its hard drive had failed. I believed my files were syncing to an online service, but the backup had not been working properly for roughly two months. Some work existed in email attachments. Much of it appeared to be gone.
Originally published April 26, 2012. Substantially revised and expanded July 2026.
What Went Wrong
The problem was not simply that a hard drive failed. Drives fail. Computers are lost, damaged, or replaced. The larger problem was that I trusted one backup system without verifying it.
A synchronization service is useful, but syncing and backing up are not identical. If a file is accidentally deleted, corrupted, or overwritten, that change may also synchronize. A dependable system keeps separate copies and gives you a way to recover earlier versions.
Use More Than One Location
A common data-safety principle is to keep multiple copies in different places. For a writer, that might include:
- Your working copy on the computer or device you normally use
- A local backup on an external drive that is not permanently connected
- An off-site copy in secure cloud storage or another physical location
The goal is to avoid a single event destroying every copy. A stolen laptop should not take the external backup sitting inside the same bag. A house accident should not destroy the only two drives. An account problem should not erase the only copy of the manuscript.
Back Up Often
How much work could you tolerate losing? That answer determines the schedule. If losing a week would be devastating, a weekly backup is not enough.
- Save the working document frequently.
- Use automatic version history when available.
- Create a dated copy at major milestones.
- Back up active projects daily or after every substantial session.
- Archive finished drafts rather than keeping only the newest file.
Dated filenames can be simple: Novel_Title_2026-07-21.docx. A consistent naming system prevents “final,” “final-new,” and “really-final-this-time” from becoming your only version control.
Verify the Backup
A backup you have never tested is only a hope. Periodically open the backup location and confirm that recent files are present. Restore a test file. Make sure you remember the password and know how account recovery works.
Automatic systems can stop because a drive is full, a subscription expires, a password changes, the application loses permission, or a computer goes offline. A monthly five-minute check can prevent months of false confidence.
Protect More Than the Manuscript
Writers often remember the novel but forget the materials needed to publish and promote it. Include these in your backup plan:
- Research and source notes
- Character and world-building documents
- Cover files and original artwork
- Audiobook recordings and project files
- Contracts, permissions, and tax records
- Website exports and mailing-list records
- Formatting and layout files
What to Do After a Failure
- Stop using the failed device if continued use could overwrite recoverable data.
- List every other place where files may exist: email, shared folders, old devices, collaborators, editors, or printouts.
- Preserve the damaged drive rather than experimenting recklessly.
- Consult a reputable recovery professional when the lost material justifies the cost.
- Build a verified backup system before resuming normal work.
The files on my failed drive felt priceless because they represented time I could not recreate exactly. The experience changed the way I think about creative work: finishing a writing session includes protecting what I produced.
For more practical guidance for writers, visit Fiction Fundamentals. For help preparing manuscripts, covers, layouts, and other publishing assets, explore Professional Creative Services.


2 responses to “How Writers Can Prevent Data Loss: Lessons from a Hard-Drive Crash”
An anonymous and satirical submission for your choir handbook:My ward choir was going top-notch until we had a wave of well-meaning but untalented amateurs. These would-be choir members could not sight-read, struggled to sing a capella, and made it impossible to focus on the finer nuances I wanted to address. Fortunately, they quickly realized they were under-qualified and stopped coming. To speed things up, I made sure we did not practice any hymns. Having the choir perform or even warm up with a hymn is like water for the weeds, it gives these common-folk the impression that participating in the choir will be fun and manageable. Also, by using only unfamiliar and difficult material, you provide an excellent opportunity for the choir pianist to magnify her calling.
Haha, wow, have a ever been there. Leading a ward choir can be extremely frustrating at times. That's part of the reason I'm attempting this project. Thanks for putting a knowing smile on my face.