[Walter Soyka] “Tape is just not as convenient as true nearline storage.”
I agree with Weiss and Soyka. I use a similar pattern, in my case RAID 5 (CalDigit), hard drives, and LTO-3. Although the software (Retrospect) with which I copy to LTO-3 has very good indexing, it is true that for ease of retrieval, hard drives are the backup of choice. My Mac Pro’s three internal “extra” SATA drives are a wonderful way to make and park quick backups of critical material, when I have “drop-dead”-lines and can’t afford to lose an hour.
I am looking forward, when it gets a bit less expensive, to switching to LTO-5 or LTO-6. But even then, tape presents a dilemma as to just how to organize the backups. Currently, I backup by project or client. That makes it much easier to reload the material, because when I do have to reload data, it is always for a given project. But it is a lot less efficient to do the backup that way, which means I wind up NOT doing tape backups as often as I would like. Due to the limited capacity of LTO-3 tape, I think I’m locked into that method for now. But for people like Walter, with LTO-5, do you just have the tape system backup everything that is new, every day? And if so, do you find that to be crippling when it comes to retrieval of data, in a pinch? Because I have several projects happening at once, and if I were to backup daily, the material for any one project might be spread over several tapes, and the material for any one CLIENT would be spread over many, many tapes.
Reloading material is a regular requirement, even if your RAID never fails. Whenever I reload material from an LTO tape, it is because I thought the project was finished, and had deliberately deleted it from the RAID — and not once because the RAID had failed. My CalDigit has been fantastic; when a drive died, I had a new one ready to pop in and it rebuilt the RAID redundancy in a couple of hours.
Bob C