Put your company's big iron to work to back up open-systems storage more efficiently.
Most large companies have a mix of multiplatform IT environments: mainframe, Unix, Linux and Windows. Typically, these environments don't share software, staff, and disk and tape resources. But with a few caveats, there are considerable advantages to using a mainframe to back up all of an organization's data to streamline backup and disaster recovery (DR) operations.
Take critical applications, for example, that mostly run on integrated multiplatform systems. An enterprise resource planning (ERP) application such as SAP includes back-end databases running on the mainframe, application processing on Unix servers and Web interfaces running on Windows. There's usually a large amount of data transferred between these environments via FTP, extracts and dumps. This creates a lot of overhead and, at times, impacts the availability and service-level agreements of the business applications. In addition, DR plans for these critical apps are sometimes separate for each storage environment. This makes the data more difficult or impossible to recover because of the following:
- Parts of the data are backed up at different times and aren't synchronized.
- Data is backed up using different tools such as Innovation Data Processing's (IDP) FDR on the mainframe, IBM Corp.'s Tivoli Storage Manager on Unix and Veritas Software Corp.'s Backup Exec for Windows Servers (now owned by Symantec Corp.).
- The data is placed on different tape drives and media such as IBM's 3590 tape drives for the mainframe, Storage Technology Corp.'s (StorageTek, now part of Sun Microsystems) 9940 on Unix and LTO tapes on Windows. There are also different tape handling processes, labeling, vaulting and staff.
A consistent view of data
If the mainframe is used to increase recovery success rates for most mixed environments, there must be a consistent view of the data at a point in time, called consistency groups. The ability to gather data from various platforms at the same time is available with products from most major mainframe/open storage vendors, such as EMC Corp., Hitachi Data Systems (HDS) Inc. and IBM Corp. EMC's TimeFinder and HDS' ShadowImage can coordinate I/O freezing for a database at the host level. IBM's FlashCopy performs this task at the array level. Achieving tight coordination of hosts, applications and data access requires scripting and programming job-scheduling packages to quiesce the application and flush the data.
For example, EMC's solution for Symmetrix storage environments combines its TimeFinder software with IDP's FDRSOS and FDR/Upstream/SOS. The combination provides a point-in-time copy of critical data across multiple platforms.
The diagram "Mainframe backs up all data", shows Unix and Windows systems connected to an EMC Symmetrix array. The volumes are set up with business-continuance volumes (BCVs) using TimeFinder. The BCV data is visible to the mainframe and is backed up using FDRSOS, which is a z/OS- or OS/390-based solution for physical volume, high-speed backup/restore of open systems resident on EMC storage over existing mainframe ESCON or FICON channels. Most users will also use the FDR/Upstream/SOS file-level component for more granular backups and restores.
FDR/Upstream/SOS reads the data off the open-systems disk (which can be a SAN disk, local disk or a LAN logical disk) and writes it to the specially formatted FDRSOS disk on the SAN. The FDR/Upstream OS/390 component then takes the data off the SAN disk and writes it to tape. This process is transparent to the administrator and results in a highly reliable, high-speed solution for LAN and SAN environments. Backups don't go across the network, but travel through the mainframe's ESCON or FICON connection. And open-systems storage administrators aren't held hostage by a mainframe-only process because they can perform their own backups or file-level recovery using a Java-based browser interface.
Organizations can orchestrate all of the dependent steps using mainframe job schedulers such as Allen Systems Group (ASG) Inc.'s ASG-Zeke, Computer Associates (CA) International Inc.'s Unicenter CA-Jobtrac Job Management, IBM's CA7 utility as well as open-systems schedulers such as CRON. With this approach, data is backed up using mainframe resources and staff in a consistent manner. This approach also provides the benefits of LAN- and server-free backups. All the work of backup and recovery is done by the mainframe, so fewer open-systems resources are used.
John Hunter, senior systems programmer at Sigma-Aldrich Corp., St. Louis, MO, uses the mainframe to back up data. "By using FDR/Upstream/SOS, we were able to consolidate our entire Oracle, Windows, Unix, Novell and Domino backups," he says. "Administrators for each platform install a client, and our mainframe manages scheduling and tape management, giving us a backup solution with a single point of control."
|Mainframe backs up all data|
Put big iron to work
Buffalo, NY-based M&T Bank is a major regional bank with branches throughout New York, Pennsylvania, Maryland and West Virginia. The bulk of M&T Bank's core processing takes place on an IBM mainframe. Storage is managed on an EMC Symmetrix array that supports more than 11TB of data and is connected to the enterprise via a SAN. Most of the bank's data originates from more than 275 Novell and Windows 2000/NT servers, a large number of which are configured in four clusters.
Before M&T Bank was able to centralize its backup and storage operations to the mainframe, it faced many of the same issues encountered by companies with rapidly proliferating networks of distributed servers across departments. The bank relies on PC servers to support its Novell Inc. GroupWise enterprise e-mail and messaging infrastructure, as well as key customer service functions. "Our server farms got bigger and more spread out across New York State. Things became unmanageable," says Ronald Strozyk, manager of M&T Bank's Enterprise Storage Management Group.
The institution's network computing group, which oversees PC and Unix system deployments, had some backup and storage management solutions in place, but information from various servers was too scattered. "There were reliability issues," says Strozyk. "Backups often fail, and that doesn't bode too well for being able to successfully restore or recover servers."
In addition, DR procedures were put in the hands of individual departments. "If the user or department wanted the ability to recover data in a reasonable amount of time, they had to do their own backup," explains Strozyk. "Recovering data from the distributed backup system could take days," he adds. "The departments were responsible for pretty much their own recovery of individual files that were inadvertently deleted, or may have been lost or corrupted." In an effort to get its arms around these gaps, M&T Bank delegated these responsibilities to its mainframe data center, which was experienced in automated, unattended backup procedures.
M&T Bank deployed FDR/Upstream/SOS and related tools to consolidate storage management across its departments. The benefits of the mainframe-based storage approach are tangible. "We have absorbed backup tasks into our enterprise storage department," says Strozyk, "and provide a reliable backup and a verifiable recovery process, which is something we didn't have before."