AS/400-iSeries Starter Kit

Backup, Recovery and Media Services (BRMS) is IBM's strategic backup and recovery product for the iSeries and AS/400. Packaged as licensed program 5769-BR1 (V4R5) or 5722-BR1 (V5R1), BRMS is a comprehensive tool for managing the backup, archive, and recovery environment for one or more systems in a site or across a network in which data exchange by tape is required.

BRMS lets you simplify and automate backups as well as manage your tape inventory. It keeps track of what you've saved, when you saved it, and where it is saved so that when recovery is necessary, BRMS restores the correct information from the correct tapes in the correct sequence.

This conceptual introduction to BRMS and some of its many features will help you determine whether BRMS is right for your backup strategy.

An Introduction to BRMS

BRMS lets you easily define, change, and execute simple, medium, or complex backup procedures. It offers full-function backup facilities, including

• keywords to match the OS/400 save keywords (e.g., *AllUsr, *IBM)
• exit commands to allow processing of user-defined routines
• full, incremental, and noncumulative incremental saves
• saves to save files
• save-while-active processing

BRMS even provides support for backing up spooled files, a save/restore feature sorely missing from OS/400.

You may be wondering, "What could be simpler than backing up the entire system every night?" Nothing is simpler, but not everyone can afford the outage that this type of save requires. BRMS is an effective solution in backing up only what's really required. BRMS also lets you easily schedule a backup that includes a SavSys (Save System) operation, which isn't so easy using just OS/400.

In addition to these capabilities, BRMS offers step-by-step recovery information, printed after backups are complete. Recovery no longer consists of operators clenching the desk with white knuckles at 4:00 a.m., trying desperately to recover the system in time for the users who'll arrive at 8:00 a.m., without any idea what's going on or how long the process will take. With native OS/400 commands, the only feedback that recovery personnel get is the occasional change to the message line on line 25 of the screen as the recovery takes place. BRMS changes this with full and detailed feedback during the recovery process — with an auto-refresh screen, updated as each library is restored.

Following are some of the features that contribute to the robustness of BRMS:

• Data archive — Data archive is important for organizations that must keep large volumes of history data yet don't require rapid access to this information. BRMS can archive data from DASD to tape and track information about objects that have been archived. Locating data in the archives is easy, and the restore can be triggered from a work-with screen.
• Dynamic data retrieval — Dynamic retrieval for database files, document library objects, and stream files is possible with BRMS. Once archived with BRMS, these objects can be automatically restored upon access within user applications. No changes are required to user applications to initiate the restore.
• Media management — In a large single- or multisystem environment, control and management of tape media is critical. BRMS allows cataloging of an entire tape inventory and manages the media as they move from location to location. This comprehensive inventory-management system provides many reports that operators can use as instructions.
• Parallel save and restore — BRMS supports parallel save and restore, reducing the backup and recovery times of very large objects and libraries by "spreading" data across multiple tape drives. This method is in contrast to concurrent save and restore, in which the user must manage the splitting of data. With parallel save and restore, operations end at approximately the same time for all tape drives.
• Lotus Notes Servers backup — BRMS supports backup of online Lotus Notes Servers, including Domino and Quickplace Lotus Notes Servers.
• Flexible backup options — You can define different backup scenarios and execute the ones appropriate for particular circumstances.
• Spooled file backup — Unlike OS/400 save and restore functions, BRMS provides support for backing up spooled files. Spooled file backup is important to a complete backup, and BRMS lets you tailor spooled file backup to meet your needs.
• Storage alternatives — You can save to a tape device, a Media Library device, a save file, or a Tivoli Storage Manager server (previously known as an ADSM server).

It is these features, and more, that make BRMS a popular solution for many installations. Later, we'll take a closer look at some of these capabilities.

Getting Started with BRMS

BRMS brings with it a few new save/restore concepts as well as some new terminology. For instance, you'll find repeated references to the following terms when working with BRMS:

• media — a tape cartridge or save file that will hold the objects being backed up
• media identifier — a name given to a physical piece of media
• media class — a logical grouping of media with similar physical and/or logical characteristics (e.g., density)
• policy — a set of commonly used defaults (e.g., device, media class) that determine how BRMS performs its backup
• backup control group — a grouping of items (e.g., libraries, objects, stream files) to back up

You're probably thinking that "media" and "media identifier" aren't such new terms. True, but most people don't think of save files as media, and media identifier is typically thought to mean volume identifier.

Policies and backup control groups are concepts central to BRMS in that they govern the backup process. IBM provides default values in several policies and control groups. You can use these defaults or define your own for use in your save/restore operations.

Policies are templates for managing backups and media management operations. They act as a control point for defining operating characteristics. The standard BRMS package provides the following policies:

• System Policy — The System Policy is conceptually similar to system values. It contains general defaults for many BRMS operations.
• Backup Policy — The Backup Policy determines how the system performs backups. It contains defaults for backup operations.
• Recovery Policy — The Recovery Policy defines how the system typically performs recovery operations.
• Media Policies — Media Policies control media-related functionality. For instance, they determine where BRMS finds tapes needed for a backup.
• Move Policies — Move Policies define the way media moves through storage locations from creation time through expiration.

In pre-V5R1 releases of OS/400, BRMS is shipped with two default backup control groups, *SysGrp (system group) and *BkuGrp (backup group). The *SysGrp control group backs up all system data, and the *BkuGrp control group backs up all user data. You can back up your entire system using these two control groups, but doing so requires two backup commands, one for each group. To back up your entire system using a single control group, you can create a new backup control group that includes the following BRMS special values as backup items:

The time required to back up the system using this full backup control group is less than that required to use a combination of the *SysGrp and *BkuGrp backup control groups. The *SysGrp control group contains the special value *SavSys, which saves the licensed internal code, OS/400, user profiles, security data, and configuration data. The *BkuGrp control group contains the special values *SavSecDta and *SavCfg, which also save user profiles, security data, and configuration data. If you use the two control groups *SysGrp and *BkuGrp, you save the user profiles, security data, and configuration data twice. This redundancy in saved data contributes to the additional backup time when using control groups *SysGrp and *BkuGrp. Starting with V5R1, BRMS includes a new, full-system default backup control group, *System, that combines the function of groups *SysGrp and *BkuGrp.

Note that none of the full backup control groups discussed so far saves spooled files. If spooled files are critical to your business, you'll need to create a backup list of your spooled files to be included in your full backup control group (more about how to do this later).

Saving Data in Parallel with BRMS

As I mentioned, BRMS supports parallel save/restore function. This support is intended for use with large objects and libraries. Its goal is to reduce backup and recovery times by evenly dividing data across multiple tape drives.

You typically define parallel resources when you work with backup control groups. You specify both a maximum number of resources (devices) and a minimum number of resources to be used during the backup. For example, you could specify 32 for maximum resources and 15 for minimum resources. When the backup is submitted, the system checks for available tape resources. If it can't find 32 available tape devices, the backup will be run with the minimum of 15. It's not a requirement that the number of devices used for the backup be used on the restore. However, to reduce the number of tape mounts, it's best to use the same number of tape devices on the restore.

Starting with V5R1, the special values *AllProd, *AllTest, *AllUsr, *ASP01-*ASP99, and *IBM are supported on BRMS parallel saves, with the objects being "spread" at the library level. Restores for objects saved in parallel with these special values are still done in a serial mode.

Online Backup of Lotus Notes Servers with BRMS

In today's working environment, users demand 24x7 access to their mail and other Lotus Notes databases, yet it's also critical that user data be backed up frequently and in a timely way. BRMS Online Lotus Notes Servers Backup support meets these critical needs.

With this support, you can save Lotus Notes databases while they're in use, without requiring users to exit the system. Prior save-while-active support required ending applications to reach a checkpoint or the use of commitment control or journaling. Another alternative was to invest in an additional server, replicate the server data, and perform the backup from the second server. Online Lotus Notes Servers Backup with BRMS avoids these requirements.

Installation of BRMS automatically configures control groups and policies that help you perform online backup of your Lotus Notes Servers. The Online Lotus Notes Servers Backup process allows the collection of two backups into one entity. BRMS and Domino or Quickplace accomplish this using a BRMS concept called a package. The package is identified by the PkgID (Package identifier) parameter on the SavBRM (Save Object using BRM) command.

Domino or Quickplace will back up the databases while they are online and in use. When the backup is completed, a secondary file is backed up and associated with the first backup using the package concept. The secondary file contains all the changes that occurred during the online backup, such as transaction logs or journaling information.

When you need to recover a Lotus Notes Server database that was backed up using BRMS Online Backup, BRMS calls Domino or Quickplace through recovery exits that let Domino or Quickplace apply any changes from the secondary file backup to the database that was just restored. This recovery process maintains the integrity of the data.

Restricted-State Saves Using BRMS

You can use the console monitor function of BRMS to schedule unattended restricted-state saves. This support is meaningful because with OS/400 save functions, restricted-state saves must be run interactively from a display in the controlling subsystem.

BRMS's support means you can run an unattended SavSys operation to save the OS/400 licensed internal code and operating system (or other functions you want to run in a restricted state). You simply specify the special value *SavSys on the StrBkuBRM (Start Backup using BRM) command or within a BRMS control group to perform a SavSys. You can temporarily interrupt the console-monitoring function to enter OS/400 commands and then return the console to a monitored state.

Console monitoring lets users submit the SavSys job to the job scheduler instead of running the save interactively. You can use the Submit to batch parameter on the StrBkuBRM command to enter *Console as a value, thereby performing your saves in batch mode. Thus, you don't have to be nearby when the system save is processed. However, you must issue this command from the system console because BRMS runs the job in subsystem QCtl. If you try to start the console monitor from your own workstation, BRMS sends a message indicating that you're not in a correct environment to start the console monitor.

Backing Up Spooled Files with BRMS

With BRMS, you can create a backup list that specifies the output queues you want to save. You can then specify this backup list on your backup control groups.

You create a spooled file backup list using command WrkLBRM (Work with Lists using BRM). You simply add a list, specifying

• *Bku for the Use field
• a value for the List name (e.g., SaveSplF)
• *Spl for the Type field

When you press Enter, the Add Spooled File List panel (Figure 16.1) is displayed. (The figure shows the panel after backup information has been entered.)

Including Spooled File Entries in a Backup List

Now, you can update the backup list by adding the output queues you want to save. Within a spooled file list, you can save multiple output queues by selecting multiple sequence numbers. When you add an output queue to the list, you can filter the spooled files to save by specifying values for spooled file name, job name, user name, or user data. For example, if you want to save only spooled files that belong to user A, you can specify user A's name in the User field. Generic names are also allowed.

The sample setup in Figure 16.1 saves output queue Prt01 in library QUsrSys. If you leave the Outq field at its default value *All, BRMS saves all spooled files from all output queues in library QUsrSys. To exclude an output queue, you can use the *Exc value. Once you set up your backup list, you can add it to your daily, weekly, or monthly backup control group as a backup item with a list type of *Spl.

Note that BRMS doesn't support incremental saves of spooled files. If you specify an incremental save for a list type of *Spl, all spooled files in the list are saved. BRMS doesn't automatically clear the output queues after the spooled files are successfully saved.

After you've successfully saved your spooled files, you can use the WrkSplFBRM (Work with Spooled Files using BRM) command to display the status of your saves. The WrkSplFBRM panel displays your spooled files in the order in which they were created on the system.

Restoring Spooled Files Saved Using BRMS

BRMS doesn't automatically restore spooled files when you restore your user data during a system recovery. To restore saved spooled files, use the WrkSplFBRM command and select option 7 (Restore spooled file) on the resulting screen. From the Select Recovery Items panel that appears, you can specify the spooled files you want to restore.

By default, BRMS restores spooled file data in the output queue from which the data was saved. If necessary, you can change any of the BRMS recovery defaults by pressing F9 on the Select Recovery Items screen.

During the save and restore operations, BRMS retains spooled file attributes, names, user names, user data fields, and, in most cases, job names. During the restore operation, OS/400 assigns new job numbers, system dates, and times; the original dates and times aren't restored.

Be aware that BRMS saves spooled files as a single folder, with multiple documents (spooled members) within the folder. During the restore, BRMS searches the tape label for the folder and restores all the documents. If your spooled file save happens to span multiple tape volumes, you'll be prompted to load the first tape to read the label information before restoring the documents on the subsequent tapes. To help with recovery, consider saving your spooled files on a separate tape using the *Load exit in a control group, or split your spooled file saves so you use only one tape at a time.

The BRMS Operations Navigator Interface

With V5R1, BRMS has an Operations Navigator (OpsNav) interface that makes setting up and managing your backup and recovery strategy even easier. Using wizards, you can simplify the common operations you need to perform, such as creating a backup policy, adding tape media to BRMS, preparing the tapes for use, adding items to a backup policy, and restoring backed-up items.

If you're currently using BRMS, you may not find all the functionality in OpsNav that you have with the green-screen version. However, watch for additional features in future releases of BRMS Operations Navigator. You may still want to use the graphical interface to perform some of the basic operations. If so, you'll need to be aware of some differences between the green-screen and the OpsNav interfaces.

Terminology Differences

The OpsNav version of BRMS uses some different terminology than the green-screen BRMS. Here are some key terms:

Functional Differences

As of this writing, the current version of BRMS Operations Navigator lets you

• run policies shipped with BRMS
• view the backup history
• view the backup and recovery log
• create and run a backup policy
• back up individual items
• restore individual items
• schedule items to be backed up and restored
• print a system recovery report
• customize user access to BRMS functions and components
• run BRMS maintenance activities
• add, display, and manage tape media

Some functions unavailable in the current release of BRMS Operations Navigator but included in the green-screen interface include

• move policies
• tape library support
• backup to save files
• backup of spooled files
• parallel backup
• networked systems support
• advanced functions, such as hierarchical storage management (HSM)
• BRMS Application Client for Tivoli Storage Manager

Backup and Recovery with BRMS OpsNav

BRMS Operations Navigator is actually a plug-in to OpsNav. A plug-in is a program that's created separately from OpsNav but, when installed, looks and behaves like the rest of the graphical user interface of OpsNav.

Backup Policies

One ease-of-use advantage offered by BRMS OpsNav is that you can create backup policies to control your backups. A backup policy is a group of defaults that controls what data is backed up, how it is backed up, and where it is backed up. Once you've defined your backup policies, you can run your backup at any time or schedule your backup to run whenever it fits into your backup window.

Three backup policies come with BRMS:

• *System — backs up the entire system
• *SysGrp — backs up all system data
• *BkuGrp — backs up all user data

If you have a simple backup strategy, you can implement your strategy using these three backup policies. If you have a medium or complex strategy, you create your own backup policies.

When you back up your data using a BRMS backup policy, information about each backed-up item is stored in the backup history. This information includes the item name, the type of backup, the date of the backup, and the volume on which the item is backed up. You can specify the level of detail you want to track for each item in the properties for the policy. You can then restore items by selecting them from the backup history. You also use the backup history information for system recoveries.

Creating a BRMS Backup Policy

You can use the New Backup Policy wizard in OpsNav to create a new BRMS backup policy. To access the wizard:

1. Expand Backup, Recovery and Media Services.
2. Right-click Backup policies, and select New policy.

The wizard gives you the following options for creating your backup policies:

After creating a backup policy, you can choose to run the backup policy immediately or schedule it to run later. If you want to change the policy later, you can do so by editing the properties of the policy. Many customization options that aren't available in the New Backup Policy wizard are available in the properties of the policy. To access the policy properties, right-click the policy and select Properties.

Backing Up Individual Items

In addition to using backup policies to back up your data, you can choose to back up individual files, libraries, or folders using the OpsNav hierarchy. You can also choose to back up just security or configuration data. Using OpsNav, simply right-click the item you want to back up and select Backup.

Restoring Individual Items

If a file becomes corrupted or accidentally deleted, you may need to restore individual items on your system. If you use backup policies to back up items on your system, you can restore those items from the backup history. When you restore an item from the backup history, you can view details about the item, such as when it was backed up and how large it is. If there are several versions of the item in the backup history, you can select which version of the item you want to restore.

You can also restore items that you backed up without using a backup policy. However, for these items, you don't have the benefit of using the backup history to make your selection. Fortunately, you can use the OpsNav Restore wizard to restore individual items on your system, whether they were backed up with a backup policy or not. To access the wizard in OpsNav, right-click Backup, Recovery and Media Services and select Restore.

Scheduling Unattended Backup and Restore Operations

Earlier, you saw how to schedule unattended restricted-state saves using the console monitor and the StrBkuBRM command. Of course, you can also schedule non-restricted-state save and restore operations.

In addition, you can use OpsNav to schedule your backup. To do so, you simply use the OpsNav New Policy wizard to create and schedule a backup. If you need to schedule an existing backup policy, you can do so by right-clicking its entry under Backup Policies in OpsNav and selecting Schedule. If the save operation requires a restricted-state system, you need only follow the console monitor instructions presented by OpsNav when you schedule the backup.

Tip: When you schedule a backup policy to be run, remember that only the items scheduled to be backed up on the day you run the policy will be backed up. For example, say you have a backup policy that includes the library MyLib. In the policy properties, you schedule MyLib for backup every Thursday. If you schedule the policy to run on Thursday, the system backs up MyLib. However, if you schedule the same policy to run on any other day, the system does not back up MyLib.

You can also schedule restore operations in much the same manner as backup operations using OpsNav. Restore operations, however, are scheduled less often than backup operations.

System Recovery Report

BRMS produces a complete system recovery report that guides you through an entire system recovery. The report lets you know exactly which tape volumes are needed to recover your system. When recovering your entire system, you should use the report in conjunction with OS/400 Backup and Recovery (SC41-5304). Keep the recovery report with your tape volumes in a secure and safe off-site location.

BRMS Security Functions

BRMS provides security functions via the Functional Usage Model, which lets you customize access to selected BRMS functions and functional components by user. You must use the OpsNav interface to access the Functional Usage Model feature. You can let certain users use specific functions and components while letting others use and change specific functions and components. You can grant various types of functional usage to all users or to specified users only.

Each BRMS function, functional component, and specific backup and media management item (e.g., policy, control group) has two levels of authority access:

• Access or No Access — At the first level of authority access using the Functional Usage Model, a user either has access to a BRMS function or component or has no access to it. If a user has access, he or she can use and view the function or component. With this basic level of access, a user can process a specific item (e.g., a library, a control group) in a backup operation but can't change the item.
• Specific Change or No Change — The second level of authority access lets a user change a specific function, component, or item. For example, to change a backup list, a user must have access to the specific backup list. Similarly, to change a media policy, a user must have access to the specific media policy.

The Functional Usage Model provides lists of existing items (e.g., control groups, backup lists, media and move policies) for which you can grant specific access. With the Functional Usage Model, you can give a user both types of access (so the user can both use and change a particular function, component, or item) or only one type of access (e.g., access to use but not to change a particular function, component, or item).

Security Options for BRMS Functions, Components, and Items

In the backup area, the following usage levels are available:

• Basic Backup Activities — Users with Basic Backup Activities access can use and view the backup policy, control groups, and backup lists. With use access, these users can also process backups by using backup control groups (i.e., using the StrBkuBRM command) or by saving libraries, objects, or folders (SavLibBRM, SavObjBRM, or SavFlrLBRM). A user without Basic Backup Activities access can't see backup menu options or command parameter options.
• Backup Policy — Users with Backup Policy access can change the backup policy (in addition to using and viewing it). Users without access to the backup policy cannot change it.
• Backup Control Groups — Users with Backup Control Groups access can change specific backup control groups (in addition to using and viewing them). A user can find a list of his or her existing backup control groups under the backup control groups heading in OpsNav. You can grant a user access to any number of specific control groups. Users without access to the backup control groups cannot change them.
• Backup Lists — Users with Backup Lists access can change specific backup lists (in addition to using and viewing them). A user can find a list of his or her existing backup lists under the backup lists heading in OpsNav. You can grant a user access to any number of specific backup lists. Users without access to a backup list cannot change it.

In the recovery area, the following usage levels are available:

• Basic Recovery Activities — Users with Basic Recovery Activities access can use and view the recovery policy. They can also use the WrkMedIBRM (Work with Media Information using BRM) command to process basic recoveries, command RstObjBRM (Restore Object using BRM), and command RstLibBRM (Restore Library using BRM). Users without Basic Recovery Activities access can't see recovery menu options or command parameter options.
• Recovery Policy — Users with Recovery Policy access can change the recovery policy (in addition to using and viewing it). Users without access to the recovery policy can't change it.

In the area of media management, the following usage levels are available:

• Basic Media Activities — Users with Basic Media Activities access can perform basic media-related tasks, such as using and adding media to BRMS. Users with this access can also use and view (but not change) media policies and media classes. Users without Basic Media Activities access can't see related menu options or command parameter options.
• Advanced Media Activities — Users with Advanced Media Activities access can perform media-related tasks such as expiring, removing, and initializing media.
• Media Policies — Users with Media Policies access can change specific media policies (in addition to using and viewing them). A user can find a list of his or her existing media policies under the media policies heading in OpsNav. You can grant a user access to any number of media policies. Users without access to a media policy cannot change it.
• Media Classes — Users with Media Classes access can change specific media classes (in addition to using and viewing them). A user can find a list of his or her existing media classes under the media classes heading in OpsNav. You can grant a user access to any number of media classes. Users without access to a media class cannot change it.
• Media Information — Users with Media Information access can change media information with command WrkMedIBRM (Work with Media Information).
• Basic Movement Activities — Users with Basic Movement Activities access can manually process or display MovMedBRM (Move Media using BRM) commands, but they can't change them.
• Move Verification — Users with Move Verification access can perform move verification tasks.
• Move Policies — Users with Move Policies access can change specific move policies (in addition to using and viewing them). A user can find a list of his or her existing move policies under the move policies heading in OpsNav. You can grant a user access to any number of move policies. Users without access to a move policy cannot change it.

In the system area, the following usage options are available:

• Basic System-related Activities — Users with Basic System-related Activities access can use and view device panels and commands. They can also view and display auxiliary storage pool (ASP) panels and commands. Users with this access level can also use and view the system policy.
• Devices — Users with Devices access can change device-related information. Users without this access can't change device-related information.
• Auxiliary Storage Pools — Users with ASP access can change information about BRMS ASP management.
• Maintenance — Users with Maintenance access can schedule and run maintenance operations.
• System Policy — Users with System Policy access can change system policy parameters.
• Log — Users with Log access can remove log entries. Any user can display log information, but only those with Log access can remove log entries.
• Initialize — Users with Initialize access can use the InzBRM (Initialize BRM) command.

Media Management

BRMS makes media management simple by maintaining an inventory of your tape media. It keeps track of what data is backed up on which tape and which tapes have available space. When you run a backup, BRMS selects the tape to use from the available pool of tapes. BRMS prevents a user from accidentally writing over active files or using the wrong tape.

Before you can use any tape media with BRMS, you need to add it to the BRMS inventory and initialize it. You can do this using OpsNav's Add media wizard (under Media, right-click Tape Volumes and select Add). You can also use the green-screen BRMS command AddMedBRM (Add Media to BRM).

Once you've added tape media to the BRMS inventory, you can view the media based on criteria you specify, such as the volume name, status, media pool, or expiration date. This gives you the capability to manually expire a tape and make it available for use in the BRMS media inventory.

To filter which media you see in the list, under Media, right-click Tape Volumes and select Include. To view information about a particular tape volume or perform an action on that volume, right-click the volume and select the action you want to perform from the menu.

BRMS Housekeeping

You should perform a little BRMS housekeeping on a daily basis. The BRMS maintenance operation automatically performs BRMS cleanup on your system, updates backup information, and runs reports. BRMS maintenance performs these functions:

• expires media
• removes media information
• removes migration information (180 days old)
• removes log entries (from beginning entry to within 90 days of current date)
• runs cleanup
• retrieves volume statistics
• audits system media
• changes journal receivers
• prints expired media report
• prints version report
• prints media information
• prints recovery reports

You can run BRMS maintenance using OpsNav (right-click Backup, Recovery and Media Services and select Run Maintenance) or using BRMS command StrMntBRM (Start Maintenance for BRM).

Check It Out

As you can see, BRMS provides some powerful features for simplifying and managing many aspects of iSeries backup and recovery. Keep in mind that BRMS isn't a replacement for your backup and recovery strategy; rather, it's a tool that can help you implement and carry out such a strategy.

There's a lot more to BRMS than what's been covered here. For the complete details, see Backup, Recovery and Media Services (SC41-5345), as well as the BRMS home page (http://www.as400.ibm.com/service/brms.htm) and IBM's iSeries Information Center (http://publib.boulder.ibm.com/pubs/html/as400/infocenter.htm).

This article is excerpted from the book Starter Kit for the IBM iSeries and AS/400 by Gary Guthrie and Wayne Madden (29th Street Press, 2001). For more information about the book, see http://www.iseriesnetwork.com/str/books/uniquebook2.cfm?NextBook=187.

Debbie Saugen is the technical owner of iSeries 400 and AS/400 Backup and Recovery in IBM's Rochester, Minnesota, Development Lab. She is also a senior recovery specialist with IBM Business Continuity and Recovery Services. Debbie enjoys sharing her knowledge by speaking at COMMON, iSeries 400 and AS/400e Technical Conferences, and Business Continuity and Recovery Services Conferences and writing for various iSeries and AS/400e magazines and Web sites.