You are currently on IBM Systems Media’s archival website. Click here to view our new website.

MAINFRAME > Administrator > Backup and Recovery

Five Points to Consider When Preparing for Backup and Recovery

Backup and Recovery

Planning for IT outages, whether instigated by Mother Nature, human error, system issues or a sly hacker, is no small feat for businesses. While the causes of unplanned outages vary, a strategy to manage outages can be standardized.

Harry Batten, executive IT architect, IBM, lists five common points companies should consider while crafting a backup and recovery plan:

  1. The importance of the data on your system
  2. How often the data changes
  3. The lifecycle of this data
  4. If this data is required for system recovery
  5. When this data should be backed up

Identify Data Importance

According to Batten, an important first step toward achieving a successful backup and recovery plan is to understand your data and its various unique requirements. While this may sound daunting, he says it’s not a challenging task for clients who truly understand their businesses.

He recommends examining the data from a failure perspective: Clients should first consider what would happen if their data became corrupted or lost. What’s needed to get the data back online, and what is the recovery point objective? Logged data, for example, could require restoring the last backup, applying log files and performing a forward-recovery that places the data at a point just before the outage occurred. Likewise, the loss of non-logged data could require restoring to the last-known successful backup, which may have occurred several days prior to the outage.

“It’s a good idea even in a static environment to look at what is being backed up, as well as how and where it’s stored on an annual basis at least.”
—Harry Batten, executive IT architect, IBM

Much has changed since the early days of computing, when anything and everything was regularly backed up. With the recent explosion of data, companies must now tag the data to indicate whether it should be backed up and, if so, to use the most appropriate method. Once it’s decided the data should be backed up, it’s necessary to determine whether the backup is for compliance or recovery reasons. The government dictates the number of years companies must store compliance data, and requires this data to be stored using a method that can’t be easily modified.

“In most [IBM] z Systems* environments, most of the critical data is already vaulted via a disaster recovery plan,” Batten says. “The backups we are talking about here are for easy recovery of day-to-day operations. Compliance data is self-explanatory—the government tells us that we need to retain this information for x number of years. Not all remaining data sets need to be backed up; however, there are almost always system data sets such as work files. “A question we ask

is, ‘What would be the result of losing or corrupting this data set?’ If we aren’t sure whether it should be backed up, it’s fairly easy to put it in a management class that will migrate it, then delete it after x days of non-usage.”

Lifecycle Considerations

Clients must consider whether their data is static (i.e., little chance exists of this data changing on a regular basis) or dynamic (i.e., records within the data are regularly added, modified or deleted). The type of data dictates the type of backup methodology that should be used. “For more static data,” Batten says, “we could use a generation data group, while dynamic data would benefit from an incremental method.”

While the actual exercise of backing up data may be relatively simple, Batten notes understanding when backups are no longer current—or even usable—is a more challenging, but imperative, task. Data that was backed up years ago and is no longer pertinent can be taking up valuable storage space on backup disk or tape. Identifying this data and understanding its lifecycle is a step toward being able to automate the backup and recovery process.

“Once the lifecycle is understood, it’s a good idea to use automated methods, such as data facility storage management subsystems with properly defined management classes and automatic class selection routines,” Batten says. “The currently available tooling for products like hierarchical storage management and tape management will allow the user to produce reports that can show when a particular data set was backed up and when it was last accessed. Even a simple listing of a backup volume can show this information.”

Caroline Vitse is a freelance writer based in Rochester, Minnesota.



2019 Solutions Edition

A Comprehensive Online Buyer's Guide to Solutions, Services and Education.


Active/Active Sites Helps Distribute Workloads During Outages

IBM Systems Magazine Subscribe Box Read Now Link Subscribe Now Link iPad App Google Play Store
Mainframe News Sign Up Today! Past News Letters