20
Sat, Apr
5 New Articles

10 Issues for the Administration of System i Backups, Part 1

High Availability / Disaster Recovery
Typography
  • Smaller Small Medium Big Bigger
  • Default Helvetica Segoe Georgia Times

This article is an excerpt from the book System i Disaster Recovery and Planning.

 

Many backup best practices seem basic, but accomplishing them isn't always easy. They depend on appropriate reporting and measurement capabilities, and staff competency within the organization. If you can't accomplish all of the best practices, try to address the most critical. If time and resources are the issue, develop a plan to justify them. Against these hurdles, you must measure the acceptable risk of unrecoverable data during any major outages.

 

Here are two key points to remember when developing a data recovery strategy:

  • Back up all critical data. Ask yourself, are you backing up the right stuff?

  • Backups are the backbone to any recovery situation. In most recovery situations, the backups are not adequate, so excessive time is spent recreating parts of the operating system.

Issue 1: My backups run on the night shift, so I never hear about any issues!

The key element to recovery of your system in a disaster is the completeness of the backups. If your backups are incomplete or flawed prior to the disaster, then the disaster recovery plan simply will not work, no matter how many experts you recruit. Having a process in place means a lot more than simply signing your name to it. With a sign-off, the process implies correctness. It means you have adhered to all the necessary steps in verifying that the backups are fully complete. That means 100% complete. This is especially important as it pertains to your backups.

 

Many backup solutions are partially broken. I often observe graphs posted in IT shops stating things like, "We have a 96% backup success rate. We observe all standards to ensuring your data is backed up." A 96% on a math exam is amazing. A 96% in backups implies failure. This means that 4% of the time, the server isn't backed up completely. On a yearly calendar, you have 14 days with incomplete backups. Is this acceptable to your business? My guess is no.

 

Customer Backup Log Sample

  • System not in restricted state, SAVSYS processing completed with errors.

  • Starting SAVDLO of folder *ANY to devices TAP01.

  • 2,574 document library objects saved.

  • Starting save of list *LINK to devices TAP01.

  • 43,917 objects saved. 342 not saved.

  • Save of list *LINK completed with errors.

  • Starting save of media information at level *OBJ to device TAP01.

  • 18 objects saved from library QUSRBRM.

  • Save of BRM media information at level *OBJ complete.

  • DAILY *BKU 0070 *EXIT CALL PGM(BBSYSTEM/ENDDAYBU.

  • Control group DAILY type *BKU completed with errors.

 

In this example, 342 objects were not saved on this web server. The response was, "Oh, we always get this message. It's no big deal." Backup is signed off as successful.

 

Was the backup really successful? Of course not. The backup could not get a lock on 342 objects, which probably means they were in use. If these 342 objects are in use, they must be critical to the function of this application. You need 100%.

 

The person responsible for managing the backups is under pressure to report only the good. So, if no one asks . . . hey, no one asked. Backups are typically managed by a junior staffer and on an off-shift. Many times, backup failures are not reported to management because the people performing the backups think if they tell anyone how bad the backups are, they'll be fired. They're betting that the backups will work the next night, or everything will be captured with the weekly full system option 21 save.

 

Examine your own house and see just how well your backups are really running.

Issue 2: Develop a backup plan.

Backups are just one component of data protection. Backup planning should be a fundamental part of every backup and recovery program's design. Your backup solution must always consider a process for rolling out new applications, adding additional partitions or guest operating systems, and being able to manage disk growth. A proper backup plan enables the system administrators to fully understand the application needs and any additional business requirements.

Issue 3: Establish a backup lifecycle program.

An effective backup strategy requires certain tasks to be completed successfully each and every day. In addition, there are weekly, monthly, and even yearly tasks that are vital to your business. An effective backup lifecycle program demands that all tasks are documented and performed on a regular, published, and agreed-upon schedule. This also lends itself to ITIL and SOX compliance.

 

Daily tasks are the operational fundamentals that most backup administrators are familiar with. They include items such as these:

  • Backup monitoring

  • Success/failure reporting

  • Problem analysis and resolution

  • Tape handling and library management

  • Offsite tape storage

  • Scheduling of special saves

  • Weekly, monthly, and long-term backups

  • Archiving data

  • Capacity backup planning for disk and tape drives

  • Review of backup policies

  • Recovery testing and verification

 

Evaluate your daily/weekly/monthly tasks as needed. Document them, and make sure they're recorded and signed off. All this will seem very tedious at first, but as you automate these processes, you will immediately come to realize the benefits.

Issue 4: Review backup logs daily.

A review of backup job logs or BRMS reports and the QSYSOPR message queue is a key daily task, but one that's not routinely performed. It can be time-consuming, but it does pay dividends for ensuring backup completeness. DSPLOGBRM provides you with the BRMS activities per date, interactively. You can see today's history, yesterday's, last week's, or as long as you keep the history.

 

Backup issues tend to manifest themselves. How many times has one backup event resulted in a series of subsequent failures? A weekly backup gets run instead of a daily, thus shutting down all subsystems, including QINTER. A very angry group of users is less than impressed. Then, you put the weekly job schedule entry on hold and forget to release it later. Now you have missed the weekend save. The system administrator responsible never informed anyone about putting the weekly backup job on hold.

 

It takes considerable skill to troubleshoot backup failures. It is therefore important to verify everything works. When it does not, determine the root cause rather than guess based on some symptom.

Issue 5: Protect your manual tape backup database or BRMS catalog.

BRMS backup control groups maintain a database or catalog that is absolutely critical to the recovery of your system from the backup tapes. Having no access to the BRMS catalog or, worse, a corrupted catalog means you have lost your ability to restore anything from your backup tapes.

 

Every backup performed through control groups automatically writes the catalog to the tape. The following objects will permit the catalog to be retrieved:

 

Saved                                                   Seq

Control         Item     Type Name     Number Date    Time Saved

Saved   Number  Group

   ---------- ----- ---------- ----- -------- -------- -------

------- --------- ---------- ----------

__ QBRM        *FULL *SYSBAS  00001  xx    xx      MTHLY

__ QMSE        *FULL *SYSBAS  00001  xx    xx      MTHLY

__ Q1ABRMSF    *FULL *SYSBAS  00001  xx    xx      MTHLY

__ Q1ABRMSF01  *FULL *SYSBAS  00001  xx    xx      MTHLY

__ QUSRBRM     *FULL *SYSBAS  00001  xx    xx      MTHLY

__ QUSRBRM     *QBRM *SYSBAS  00033  xx    xx      DAILY

 

If you do not have a tape management software solution, how do you know what data is on which tapes? Many clients manually record volume information in Microsoft Excel or Word and store the information on a local PC. The key to remember is to get this information offsite, so that it does not go down in flames with the rest of your infrastructure.

Richard Dolewski

Richard Dolewski is a certified systems integration specialist and disaster recovery planner. He has extensive experience in Server Enterprise Availability, Disaster Recovery Planning (DRP), Business Continuity Planning (BCP), High Availability, and Backup and Recovery program design. Richard has supported 18 computer room disasters and conducted over 200 disaster recovery tests. He is an award-winning speaker at technical conferences, including IBM, COMMON, IBM Europe, IT Executive events, Quest, NEMA, and local user groups. Richard has held positions as subject matter expert at IBM and COMMON, a member of the Advisory Committee for IBM Business Resiliency, and president of local user groups. He also regularly contributes to several technical newsletters.


MC Press books written by Richard Dolewski available now on the MC Press Bookstore.

System i Disaster Recover Planning System i Disaster Recovery Planning
Don’t miss this step-by-step guide to developing an effective, workable plan.
List Price $64.95

Now On Sale

BLOG COMMENTS POWERED BY DISQUS

LATEST COMMENTS

Support MC Press Online

$0.00 Raised:
$

Book Reviews

Resource Center

  • SB Profound WC 5536 Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application. You can find Part 1 here. In Part 2 of our free Node.js Webinar Series, Brian May teaches you the different tooling options available for writing code, debugging, and using Git for version control. Brian will briefly discuss the different tools available, and demonstrate his preferred setup for Node development on IBM i or any platform. Attend this webinar to learn:

  • SB Profound WP 5539More than ever, there is a demand for IT to deliver innovation. Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects. The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the company are not aligned with the current IT environment.

  • SB HelpSystems ROBOT Generic IBM announced the E1080 servers using the latest Power10 processor in September 2021. The most powerful processor from IBM to date, Power10 is designed to handle the demands of doing business in today’s high-tech atmosphere, including running cloud applications, supporting big data, and managing AI workloads. But what does Power10 mean for your data center? In this recorded webinar, IBMers Dan Sundt and Dylan Boday join IBM Power Champion Tom Huntington for a discussion on why Power10 technology is the right strategic investment if you run IBM i, AIX, or Linux. In this action-packed hour, Tom will share trends from the IBM i and AIX user communities while Dan and Dylan dive into the tech specs for key hardware, including:

  • Magic MarkTRY the one package that solves all your document design and printing challenges on all your platforms. Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product. Make sure your data survives when catastrophe hits. Request your trial now!  Request Now.

  • SB HelpSystems ROBOT GenericForms of ransomware has been around for over 30 years, and with more and more organizations suffering attacks each year, it continues to endure. What has made ransomware such a durable threat and what is the best way to combat it? In order to prevent ransomware, organizations must first understand how it works.

  • SB HelpSystems ROBOT GenericIT security is a top priority for businesses around the world, but most IBM i pros don’t know where to begin—and most cybersecurity experts don’t know IBM i. In this session, Robin Tatam explores the business impact of lax IBM i security, the top vulnerabilities putting IBM i at risk, and the steps you can take to protect your organization. If you’re looking to avoid unexpected downtime or corrupted data, you don’t want to miss this session.

  • SB HelpSystems ROBOT GenericCan you trust all of your users all of the time? A typical end user receives 16 malicious emails each month, but only 17 percent of these phishing campaigns are reported to IT. Once an attack is underway, most organizations won’t discover the breach until six months later. A staggering amount of damage can occur in that time. Despite these risks, 93 percent of organizations are leaving their IBM i systems vulnerable to cybercrime. In this on-demand webinar, IBM i security experts Robin Tatam and Sandi Moore will reveal:

  • FORTRA Disaster protection is vital to every business. Yet, it often consists of patched together procedures that are prone to error. From automatic backups to data encryption to media management, Robot automates the routine (yet often complex) tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:

  • FORTRAManaging messages on your IBM i can be more than a full-time job if you have to do it manually. Messages need a response and resources must be monitored—often over multiple systems and across platforms. How can you be sure you won’t miss important system events? Automate your message center with the Robot Message Management Solution. Key features include:

  • FORTRAThe thought of printing, distributing, and storing iSeries reports manually may reduce you to tears. Paper and labor costs associated with report generation can spiral out of control. Mountains of paper threaten to swamp your files. Robot automates report bursting, distribution, bundling, and archiving, and offers secure, selective online report viewing. Manage your reports with the Robot Report Management Solution. Key features include:

  • FORTRAFor over 30 years, Robot has been a leader in systems management for IBM i. With batch job creation and scheduling at its core, the Robot Job Scheduling Solution reduces the opportunity for human error and helps you maintain service levels, automating even the biggest, most complex runbooks. Manage your job schedule with the Robot Job Scheduling Solution. Key features include:

  • LANSA Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.

  • LANSAWhen it comes to creating your business applications, there are hundreds of coding platforms and programming languages to choose from. These options range from very complex traditional programming languages to Low-Code platforms where sometimes no traditional coding experience is needed. Download our whitepaper, The Power of Writing Code in a Low-Code Solution, and:

  • LANSASupply Chain is becoming increasingly complex and unpredictable. From raw materials for manufacturing to food supply chains, the journey from source to production to delivery to consumers is marred with inefficiencies, manual processes, shortages, recalls, counterfeits, and scandals. In this webinar, we discuss how:

  • The MC Resource Centers bring you the widest selection of white papers, trial software, and on-demand webcasts for you to choose from. >> Review the list of White Papers, Trial Software or On-Demand Webcast at the MC Press Resource Center. >> Add the items to yru Cart and complet he checkout process and submit

  • Profound Logic Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application.

  • SB Profound WC 5536Join us for this hour-long webcast that will explore:

  • Fortra IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn: