Quote:
Originally Posted by CRussel
Well, let's just say that I wrote the backup chapter of every book we wrote. That's a lot of reinforcement of good practice!! (That's more than 3 dozen books, but probably only 2 dozen of them had a backup chapter.)
Also, the only person I ever actually fired was for not doing backups. And lying about it.
Besides all that, this is my intellectual property. That's worth a bit of care and caution!
|
Now comes the fun question: are you doing regular restore tests from your backups? As one friend of mine found out, just because the backups are happening doesn't mean any recoverable data is being written. In his case, their nice new LTO-6 backup tape library had a firmware glitch where all the data was being written to (and verified from) one tape instead of all tapes in the library. It was about 3 months later when they went to restore a file and found that it wasn't recoverable that the glitch was found. They were fortunate in that the missing file was not mission critical and a firmware update was available that corrected the issue. For me, the humour was that a notice about the firmware update marked critical had been received and filed by the IT manager about a week after the backup system went live. His mantra was if it ain't broke, don't fixpak it.