The Cost of Not Backing Up
September 23, 2009 Hey, Joe
I’m performing a disaster recovery review for a client. The client backs up only i5/OS user libraries daily. He doesn’t back up program libraries, QUSRSYS, QGPL, or QSYS2. He doesn’t process the SAVSECDTA, SAVCFG, SAVDLO, or SAV commands daily or weekly, either. He’s adamant that he has enough libraries to perform a successful system recovery. And it gets worse. . . .
The user only does a complete system save if he loads cumulative PTFs or does a hardware upgrade. He didn’t perform a complete system save before the last hardware upgrade, and he used an old tape to perform the system restore. He didn’t perform any post-upgrade system backups until four weeks after the upgrade. He won’t perform regular full system backups, even though I’ve often pushed monthly saves. I think he’s setting himself up for a disaster. What do you think?
System i and iSeries system backups are a duty, not an option. The critical question is: How do you make system backups easier to sell and perform? While your client performs nightly data backups, he is missing other critical backup pieces, including:
The iSeries is an incredibly reliable machine, but this mindset doesn’t make sense. If you need to sell the need to perform regular backups, here are some ideas to seal the deal.
Remember, there’s a cost associated with not performing proper backups. The key lies in making a business case for why regular system backups beyond data backup are critical. If the manager doesn’t listen, maybe there are others who can help make the case. It’s best if the manager is convinced to run regular backups before a disaster convinces him the hard way.
Editor’s Note: What do you think? Have you worked with anyone who treats i5/OS system backups as a suggestion instead of a requirement? Send me your stories about the cost of not backing up. I’ll forward them to Ray as additional suggestions. I may also print them in a future column. Email me via the IT Jungle Contact page.