dvd+r dl discs are the best thing for long term data storage?
In '23, I copied a lot of data off a big pile of old (some ancient) discs I had, both CD and DVD. After getting everything copied over and backed up, I vowed I would never return to optical media storage ever again.
Well, that's changed.
I bought a 50-pack of DVD+R DL discs. DL means Dual Layer. A regular DVD+R holds 4.7GB while a DL holds 8.5GB. In this day and age, 8.5GB doesn't sound like much, but that's well more than enough to hold thousands of documents and photos. It's not a BDXL level of optical storage, but I'll get to that in a minute.
The bitter truth about flash drives
You can get 512GB flavors all day for real cheap. That used to be over $100, then it was $50, and now well below that.
It's very tempting to just stuff everything on a flash drive, put it in a box or whatever, forget about it, then retrieve it later when you want the files on the thing.
Bad idea.
The flash cells over time will bleed charge. If the flash storage sits too long unused, guess what? Dead drive. And yes, this can happen with SSD as well.
What you're supposed to do is periodically plug in the drive even if no files are read or written to charge the thing. This is annoying because it means you have remember to do this. You go get the flash media out of storage, plug it in for 20 minutes, disconnect properly afterward, put back in storage, repeat once a month.
But let's say you do the exact opposite and use the flash drive all the time, reading and writing files to it as you normally would. Everything is good, right? Wrong. That decreases the lifespan of the memory and you can (and most likely will) end up with a dead USB stick.
Ideally, a USB stick is best used sometimes. Use it a few times a week and no more than that to make the drive last as long as possible. The cells keep a charge, and file system remains stable... hopefully. But trying to figure how much use is too much or too little is also annoying. What's the correct amount of use? Nobody knows.
What this basically means is that flash media absolutely sucks for long term data storage, and this leads to...
The DVD+R DL disc
DVD+R DL has been around since 2004, so it's obviously a very mature storage technology. If you have an optical drive, it probably already has the ability to read and write DVD+R DL discs, especially if it was made in 2012 or later.
In Windows, a freeware utility you can download called Nero InfoTool will tell you the media types your optical drive will support. It's old, but still works.
In Linux, libcdio (and probably libcdio-utils) needs to be installed so you get the cd-drive command line utility.
Run that, and right near the top it states yes, the drive does have DVD+R DL support.
If I had some seriously crusty old optical drive that didn't have DVD+R DL support, plenty of external USB DVD burner drives are out there for cheap.
Why bother with DVD+R DL?
DVD+R DL is, as far as I can tell, the cheapest way to get long term data storage that actually works.
What do I mean by long term? Ten years.
Why use the disc and not a CMR hard drive like a Seagate Barracuda Pro? CMR HDD is an option, but with DVD of the non-RW variety, the files cannot be messed with once written. Once they're there, it's permanent. Also, the only thing you have to do to store DVDs properly is put them in a cool, dry place. DVD is a true "put away and forget it" media.
And one other thing. If a CMR hard drive just outright dies, your only option to get that data back is to send the drive to a data recovery service, pay a big chunk of money, and hope for the best. If an optical drive dies, the data can be moved physically. Take the disc out, use another drive that works.
Why not Blu-ray?
There is archival grade M-DISC BDXL media, but it is not cheap. At the time I write this, it's over $10 per disc. True, each disc can hold 100GB. But you need a Blu-ray burner with M-DISC support, which is also not cheap. But even if you have the burner and the discs, any time a burn doesn't go quite right, you're out 10 bucks each time that happens.
The alternative cheaper media for Blu-ray is BD-R and BD-R DL discs. With BD-R you get 25GB per disc, and BD-R DL bumps that to 50GB/disc.
Blu-ray at cheapest is the BD-R 25GB flavor, and that roughly translates to 90 cents/disc if you bought a 50-pack of them.
DVD+R DL is about 60 cents/disc when bought as a 50-pack.
But then there's the cost of the drive. Getting multiple drives for DVD is way, way cheaper compared to Blu-ray. 60 vs. 90 cents per disc isn't much, but $30 for a DVD burner vs. $100+ for a decent external Blu-ray burner can add up real quick. There are ones cheaper than $100, but they won't last. External DVD drives are the better deal.
What can fit on DVD+R DL?
Everything but video.
Video files are, by far, the largest thing anybody has on their drive(s). Take away the video, and what you're left with images and documents for the most part.
Without video files taken into consideration, 8.5GB/disc actually ends up being plenty of space to back up photos and documents.
To put this in perspective, a big digital photo is about 4MB. You can fit over 2,000 photos that size on a single DVD+R DL. As for documents, a really big PDF over 100 pages long would be anywhere from 25 to 50MB. Yes, MB, not GB.
Aside from entire-system backups, video is pretty much the only reason anybody buys big-capacity data storage in the first place.
If you have tons of video, sure, get one or two 8TB Barracuda Pro CMR HDDs (the 8TB is the best deal going at the moment).
But for everything else that's for long term data storage? DVD+R DL all day.
Yeah, DVD+R DL is old tech, but proven, reliable, and most importantly there's no periodic maintenance required. Write the disc, verify to make sure it took, store, put away, done.
Now for some nerdy notes to ensure maximum compatibility for burned data discs.
Here's the 101 to ensure maximum compatibility with any DVD burned. This mainly concentrates on Linux, but also applies to Windows and probably macOS as well. All of this is optional. You can choose to follow it or not.
The decidedly ancient Yellow Book CD-ROM Mode 1 data standard all the way back from 1984 is what to use when you want your burned data discs to read everywhere. There are rules to follow, and they're fortunately easy.
Before I get into that, if you don't follow the rules, there's the possibility your burned discs will only read in certain operating systems and even certain optical drives but not others. In my personal experience, I had it happen where I burned a DVD in Linux, brought it over to an older Windows 10 laptop with a DVD-ROM (yes, ROM, meaning no write capability), and the disc absolutely would not read. The reason? I didn't use Yellow Book Mode 1.
What I found is that if I keep any individual file under 2GB, I can get away with multi-dot files (like file.whatever.ext) and long file names, provided I use both Rock Ridge (for Linux) and Joliet (for Windows) extensions.
Confused? I'll make it slightly easier.
If you don't feel like looking at all your files to check for over-2GB stuff, put everything in a split 7z archive. 7-Zip makes it stupidly easy to create archives that auto-split into 2GB chunks on creation.
7z a stuff.7z -v2g folder-with-all-my-crap
The above literally means "Launch 7-Zip, add to archive stuff.7z, auto-split to 2GB volumes, put everything in folder-with-all-my-crap into the archive".
Both will create stuff.7z.001, stuff.7z.002 and so on until completed. When you double-click the .001 file, if all the other pieces are present, it auto-joins and opens as if it were a single file. At that point you choose whether to extract it somewhere or not.
As for the Rock Ridge and Joliet extensions, for most people this is only a thing to take into consideration when using Linux to burn discs.
The Joliet extension is something any Windows disc burning software should automatically use since Microsoft has been directly supporting that since Windows 95. The Rock Ridge extension is for UNIX/Linux use to allow for things like very long file names, inclusion of per-file permissions, and so on.
Typically, Linux users use genisoimage to create an ISO first, then wodim to burn a disc with. (If you don't want to mess around with Terminal, scroll down to "Is there an easier way for Linux?" below.)
Using these terminal commands below will create an ISO and then burn a disc using both Rock Ridge and Joliet so it can be read in Linux or Windows with no issues:
genisoimage -rJ -V disc-name-not-over-32-chars -o /path/to/my-dvd-name.iso /path/to/dir-with-files
sudo wodim dev=/dev/srX -v -data -eject /path/to/my-dvd-name.iso
Note that /dev/srX in wodim is an example drive path. You need to run lsblk -p to determine the actual drive path. If using an external USB burner drive, it will most likely be something like /dev/sr0 or /dev/sr1.
Also note that /path/to/ is something you have to figure out. If you have the folder with all the files you want to put to ISO on the Desktop, then the path would be something like /home/your-username/Desktop/dir-with-files. If you also want the generated ISO on the Desktop, the path for that would be /home/your-username/Desktop/my-dvd-name.iso.
Explanation:
For genisoimage, -rJ is "Rock Ridge and Joliet", -V is the disc name you make up with no spaces that doesn't exceed 32 characters in length, -o is the output and ISO name of your choice, dir-with-files is where the files are that you want in the ISO. You may want to type that as /path/to/dir-with-files.
For wodim, find your DVD drive path first with lsblk -p. If it's an external DVD drive over USB (which it probably will be), it will most likely be /dev/sr0 or /dev/sr1. The -v outputs a little extra info while burning the disc, -eject automatically ejects the tray on completion, and lastly the ISO name tells wodim what to burn to disc.
Is there an easier way for Linux?
Yes. Use Xfburn - especially if you plan on using Blu-ray.
For whatever package manager you use, search for that and it should be available as it's in a whole bunch of different distros. You can burn direct-to-disc or make ISOs with it.
Xfburn is also smart enough to where if you drop in over-2GB files, it will give a soft warning that the disc may be incompatible with other systems (which basically means "probably won't work in Windows"). However, to ensure maximum compatibility, type in a volume name that's under 32 characters with no spaces just like you would with wodim.
And like I said, use Xfburn if you plan on doing the Blu-ray thing, since the software has built-in BD disc support.
Now for some even more nerdy notes about making super-ultra compatible CDs for vintage DOS computers.
Making super-ultra compatible CDs that will work with MS-DOS
In this scenario, you're using CD and not DVD, and the instructions below is my best guess on how to make the most super-ultra compatible CD for use on a vintage PC. Why just a best guess? I don't have an actual vintage MS-DOS PC to test with. But I do remember enough about MS-DOS to where this will most likely work.
ISO 9660 is understood by MS-DOS, so as far as I'm aware, the only real thing to look out for are directory and file name considerations.
Any file or directory follows 8.3 rules, which means 8 case-insensitive characters and optionally one dot followed by 3 case-insensitive characters. The allowed characters are A through Z and 0 through 9.
Allowed special characters are all these _^$~!#%&-{}@`'() and if DOSBox is to be believed, that actually works.
To avoid complications, I wouldn't bother with that and just stick with A-Z and 0-9.
One of the easier ways to get a bunch of files to CD for MS-DOS use other than just copying them over is using a ZIP. Other archive types exist, but ZIP is by far the easiest.
In Linux, zip gives you the optional -k flag, which in man zip is described as:
Attempt to convert the names and paths to conform to MSDOS, store only the MSDOS attribute (just the user write attribute from Unix), and mark the entry as made under MSDOS (even though it was not); for compatibility with PKUNZIP under MSDOS which cannot handle certain names such as those with two dots.
This means all you have to do in Linux is put all your files in a folder (and you can include subdirectories, also with files in them), navigate to that folder in Terminal, and run this:
cd /path/to/files
zip -r -k archive.zip *
All files and folders in the ZIP will be converted over to 8.3 that DOS can understand.
If the archive is too big, use the split utility in Linux to break it up, then CHUNK in DOS (search for "dos chunk file splitter" in your search engine of choice) to combine the files.
Splitting for DOS CHUNK use in Linux using 700k pieces (you can specify any size you want in b for byte, k for kilobyte, m for megabyte, whatever):
split -a 3 -b 700k -d archive.zip archive.
Yes, the dot has to be at the end. This will create archive.000, archive.001, archive.002 and so on.
This should go without saying, but I'll mention it anyway. Any utilities I mention below should be in PATH. If you don't know what that is.. um.. learn to DOS.
In DOS, put all the files in a folder and run CHUNK to combine and get the ZIP. If you put everything in C:\SPLIT, it would look like this:
C:
CD\SPLIT
CHUNK /C ARCHIVE ARCHIVE.ZIP
Preview the ZIP using PKZIP for DOS:
PKZIP -VM ARCHIVE.ZIP
Once satisfied with what you see, delete the old split files afterward:
DEL *.00*
Make a folder, go to it, use PKZIP for DOS to unzip that extracts folders along with any subdirectories and files within:
MD \EXTRACT
CD\EXTRACT
PKUNZIP -D \SPLIT\ARCHIVE.ZIP
Ultimately, whether you choose to write files as-is outright to CD, use ZIPs or split ZIPs, everything has to be to 8.3 spec if the intent is to use those files in MS-DOS. If all the data is "8.3'd" and the CD is written as Yellow Book data mode 1, DOS should be able to read and understand that without issue. I believe even an ancient MPC compliant PC like the Tandy Sensation should be able to read the disc.
Published 2025 Feb 25