Abstract:
A storage media management system operating in a heterogeneous computing environment having different servers, different operating systems, and different backup applications. The management system extracts backup information from each backup application and consolidates the information in a tracking database. A centralized interface to the tracking database permits centralized management of backup storage media, such as movement, retention, vaulting, reporting, utilization, and duplication.

Description:
BACKGROUND OF THE INVENTION  
       [0001]     1. Field of the Invention  
         [0002]     The present invention relates to a system for tracking and managing backup storage media and, more particularly, to a centralized media management system for use in a computing environment having multiple, disparate hardware and software systems and backup applications.  
         [0003]     2. Description of the Relevant Art  
         [0004]     In order to ensure that original data is not lost, a copy of that data is typically stored in another medium. Should the original data be lost or damaged, the copied data is then available to restore the original data. This process is generally known as disaster recovery or backup and restore. However, the amounts of data stored and backed up has grown at almost exponential rates. This dramatic rise in the amount of data required to be backed up is attributed to many factors, such as the decreasing costs of disk space, the increasing processing power, demands of the users, etc. Further, most corporate computing environments have disparate hardware operating systems and backup applications further complicating backup and restore.  
         [0005]     In the simplified network shown in  FIG. 1 , a plurality of clients  12  are connected via a network, such as LAN  14 , to a server  10 .  FIG. 2  shows a slightly more complex system wherein a large number of clients might be attached to a network  14  in communication with a large number of servers  10 . Conventionally, each server  10  is backed up using some type of removal storage media, such as tape cartridges; a tape backup recording device is shown as reference numeral  16  in  FIG. 2 . In the network of  FIG. 2 , the backup tape cartridges can be recorded using spreadsheets and handwritten notes to track the tapes&#39; location and contents. In typical computing environments, such backup tapes are “vaulted” or moved to an offsite location so that in the event of a physical disaster to the computing environment, the backup tapes are not destroyed.  
         [0006]     Computing environments, however, have become quite complex over the network depicted in  FIG. 2 . For example, a computer network might have a storage area network (SAN), network attached storage (NAS), or direct attached storage (DAS) environments for data storage. Such computing environments can be seen in U.S. Pat. Nos. 6,564,252; 6,564,228; and 6,557,123(incorporated herein by reference). Such complex computing environments often include a tape library for onsite tape consolidation equipped with a mixture of tape drives, varying connectivity interfaces, tape cartridge robotics, and thousands of tape cartridge slots.  
         [0007]     A prime difficulty in such modem, complex computing environments is that the network is typically complex and sourced from a variety of different vendors running a variety of different operating systems and backup applications. That is, it is common to see servers from IBM, Hewlett-Packard, Dell Computer, or Sun Microsystems all running different operating systems, such as Unix, Windows NT, or Lennox having a different databases, such as Oracle, SQL, DB2, with a variety of backup applications. Such backup applications might be from Legato, Veritas, Tivoli, LXI, Computer Associates, or Hewlett-Packard. Further, mainframe computing might also be a portion of the computing environment. A number of attempts at backing up disparate applications have been made, such as U.S. Pat. No. 6,038,379 (incorporated herein by reference).  
         [0008]     With such a disparate platforms, systems, and applications in a typical complex computing environment, it is difficult to track and manage the backup storage media both onsite in the computing environment and offsite at a secure storage facility (i.e., vault). Therefore, there exists a need to provide a system which will manage backup storage media in such a complex, heterogeneous, disparate computing network environment both on and offsite.  
       SUMMARY OF THE INVENTION  
       [0009]     The present invention provides a media management system for a computing environment having multiple disparate hardware, operating systems, and backup applications so that the storage media can be managed during their entire life cycle. That is, the storage media is managed during its entire life cycle, from backup procedures, transportation to the vault, in the vault, during the return or restore operations to the computing environment, and reuse or “scratch.” 
         [0010]     Broadly, the media management system includes a consolidated tracking database and a plurality of import agents specific for each unique backup application in the computing environment. The import agents operate to extract backup information from each of the backup applications and store the backup information in the consolidated database. A rules-based policy vault manager interfaces with the consolidated tracking database to accept user-defined rules or policies concerning the backup storage media, and outputs instructions for removing or maintaining the backup storage media.  
         [0011]     In one form, the method of storage management in accordance with the present invention contemplates a heterogeneous computing environment connecting a plurality of servers to a network wherein at least some of the servers have different backup applications to backup data to storage media. Storage media information is stored in a native form usable by the proprietary backup application, and the method of the present invention extracts storage media information from such native form and normalizes the storage media before storing such storage media information in a consolidated tracking database. The consolidated tracking database is used to manage the movement and location of the storage media.  
         [0012]     There are many types of storage media management concepts that can be utilized in the present invention, such as inputting company specific policies to the consolidated tracking database concerning the movement of the storage media from onsite to the vault, and designated times for movement and maintenance criteria at the vault. Additionally, the storage media itself can be tracked, such as tape usage. In a preferred form, the consolidated tracking database includes export agents for taking a relevant storage media information and exporting it to the native backup application. This system and method of storage media management is particularly useful in complex computing environments having disparate hardware, operating systems, and backup applications. 
     
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0013]     Other objects and advantages of the invention will become apparent upon reading the following detailed description and upon reference to the accompanying drawings in which:  
         [0014]      FIG. 1  is a prior art schematic depicting a simplified, client server, computing network.  
         [0015]      FIG. 2  is a prior art schematic depicting a multiple server network having different backup applications and tape backup systems.  
         [0016]      FIG. 3  is a schematic depicting a computing network having multiple servers connected to a LAN and a tape library.  
         [0017]      FIG. 4  is a schematic depicting a computing environment wherein the storage media (i.e., tapes) are transported offsite (i.e., vault).  
         [0018]      FIG. 5  is a diagram showing the functional interface to a consolidated tracking database with disparate backup applications, reporting functions, and a tape library.  
         [0019]      FIG. 6  is a diagram showing the operation of the consolidated tracking database with backup applications.  
     
    
     DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS  
       [0020]     Corporate computing has increased in complexity in recent years due to a variety of factors. First, mergers and acquisitions have forced an integration problem on many corporate computing centers, where multiple platforms and multiple backup applications have been mixed into a disparate, heterogeneous, computing environment. Second, many government regulations require certain types of backups and protection, for example, securities and health regulatory requirements have specific requirements depending on the data. Third, data growth has grown at an exponential rate while the need for control with fewer human resources has increased. Further, backup media must be controlled and tracked not only in the computing center, but also offsite at the vault location.  
         [heading-0021]     1. General Overview  
         [0022]     Broadly speaking,  FIG. 3  depicts a computing environment in accordance with the present invention, wherein a plurality of servers  10  are connected to a network LAN  14 . Of course, the depiction is for simplicity and the network may be much more complex, including different network topologies and data storage solutions such as a SAN, NAS, or DAS. Regardless of the particular network topology, the servers  10  represent data storage units and may include iseries or mainframe computing systems. In the embodiment illustrated in  FIG. 3  the network servers  10  are connected to a tape library device  22 . The tape library device  22  may be equipped with a mixture of tape drives, varying conductivity interfaces, tape handling robotics, and expansion capabilities for additional tape cartridge slots. Assuming the servers  10  are backup servers running different backup applications from a number of different vendors, sharing the tape library  22  can be difficult.  
         [0023]     In the computing topology of  FIG. 3 , a consolidated database  20  is also shown connected to the network  14 . A interface console  26  provides access to the consolidated database  20  providing centralized capabilities wherein all the disparate backup applications running on servers  10  may be accessed. That is, the consolidated database  20  and interface  26  may communicate with the disparate backup applications residing on servers  10 . While  FIG. 3  shows consolidated database  20  connected to the network  14 , direct alternative interface to tape library  22  may be made.  
         [0024]      FIG. 4  shows the physical layout between the corporate computing environment  24  and the offsite storage or vault  28 .  FIG. 4  depicts the physical layout and the necessity for the automated scheduling for movement of the tapes between the corporate computing environment  24  and the offsite storage location  28 .  
         [0025]     While  FIG. 3  represents a the physical layout of a media management system  40  in accordance with a preferred embodiment of the present invention,  FIG. 5  is the functional depiction. As can be seen in  FIG. 5 , tape management policies may be entered into the interface  26  for control of the operation of tape movement. Such policy management provides a single point of control for implementing, e.g., move schedules of the backup media between the corporate computing environment  24  and offsite storage  28 . As seen in  FIG. 5 , the consolidated database  20  accepts tape information from the multiple and disparate backup applications and keeps track of the tape information in the single consolidated database  20 . This provides an enterprise view of the backup media and the ability to control and report on the tape media, such as pick lists, scratch lists, reports, and label generation.  
         [0026]     In more detail,  FIG. 6  shows how import agents  30  interface to backup applications  32 . As can be appreciated, the proprietary backup applications  32  each store tape information in a proprietary format. Broadly speaking, the import agents  30  map the format of the proprietary backup applications to a “generic” format for use by the consolidated database  20 . This allows the tape information from each backup application  32  to be consolidated in the single point of control database  20 .  
         [0027]     The normal processing cycle for the system shown in  FIGS. 5 and 6  is the following: 
        1. Tape backup application data is extracted from the backup applications  32 ;     2. The extracted tape information is input to the consolidated database  20 ;     3. The consolidated database  20  is updated using the latest tape information from the backup application  32 ;     4. Information from the tape library  22  is used to update the consolidated database  20 ;     5. Scratchlists and other reports such as picklists reports and labels are generated from the consolidated database  20 ;     6. A vault management process is run ( FIG. 4 ) which dictates the move and/or return of the offsite tapes in accordance with the policies;     7. The changes from the consolidated database  20  are periodically used to update the backup applications  32  using export agents  34  ( FIG. 6 ). 
 
 2. Detailed Description 
       
 
         [0036]     a. Agents  
         [0037]     The media management system  40  hereof consolidates corporate backup information from multiple servers, hosts, platforms and network backup applications  10 , as shown in  FIGS. 3,6 , into a consolidated database  20 . An “agent”  30 , 34  is created within the media management system  40  for each network backup application  32 . The “agent” is a set of programs and routines that control the importing as at  30  (pulling information from the network backup application  32 ) and exporting as at  34  (sending vault and movement information back to the network backup application  32 ).  
         [0038]     An import agent  32  can be run in two modes. First, in a simple network on a single server where the media management system and the network backup application are both installed as in  FIGS. 1 and 2 . Second, in a multiple servers/hosts environment as in  FIG. 3  where the media management system is installed on one server/host and the network backup applications are installed on any number of servers/hosts  10 .  
         [0039]     Currently agents exist for the following backup applications within the media management system: 
        Veritas NetBackup     Legato NetWorker     HP OmniBack     IBM/Tivoli Storage Manager     BakBone NetVault     LXI MMS     a generic agent that can be configured for any application or product, including mainframe.        
 
         [0047]     Defined update agents are agents that have been created for specific backup applications. The generic agent programs are provided for users wishing to automate the input of tape database changes from a source application. The media management system can also send processed record information back to the source application as at  34  in  FIG. 6 . Once defined, the agent  30 ,  34  runs under the control of the Gateway/Multi-Host System  24 .  
         [0048]     All activity processed by the generic and defined agents is written to a log file called tms_log located in the {$TMS_HOME} directory. For activity processed via the Gateway feature (described later in this section), information is also written to the gtwy_log and gwy_Jog files located in the {$TMS_HOME} directory.  
         [0049]     The steps involved in importing the data are similar for all the agents. The following example shows the processing of the Legato NetWorker import agent:  
         [0050]     To execute an import agent initiated by the user or a job scheduling product, 
        1. The media management system requests that the backup application report command returns the required tape volume fields in a specific order and restrict the length of each field to the required field length. The output is redirected to a file by using UNIX standard output redirection.     2. Each line in the produced file is read and copied to a memory structure in the program, which corresponds to the requested format (field list order and lengths).     3. The tape volume data is validated for appropriate data types for certain fields, upper/lower case checking and converted as needed.     4. The tape volume data is added to the database. 
 
 To process an import agent vaulting occurs as defined by the user. As part of the vaulting process, the tape volumes are changed to reflect their new locations based on the corporate vaulting policies which are predefined by the user as in  FIG. 6 . 
       
 
         [0056]     To execute an export agent ( FIG. 6 ) upon completion of the vaulting process, the media management system, through a backup application command, requests that the backup application change the value of the tape volume location field in NetWorker&#39;s database for the volume involved. This occurs for all tape volumes vaulted by the media management system.  
         [0057]     The NetWorker Defined Agent interacts with standard NetWorker interfaces to both extract and update volume data between the media management system and NetWorker. Volume data created by NetWorker may be updated in the media management system as frequently as desired. The media management system can then update NetWorker when volumes are moved offsite by the Vault Management System. All media management system functions are available for processing, reporting, and querying NetWorker volumes. Multiple NetWorker zones are supported.  
         [0058]     With the exceptions of Tape Duplication and Vault management, tape volume information flows one way: from NetWorker to the media management system. The Tape Duplication feature can be used to create a duplicate tape before Vault management moves the original volume offsite. Vault management updates the NetWorker volume location field with the media Manager vault name, or clears it.  
         [0059]     The ttk_nw program queries NetWorker and adds/updates the volume information in media management system. The ttk_nw_vlt program updates the NetWorker volume location field.  
         [heading-0060]     Corresponding Data Fields  
         [0061]     The following chart depicts the Networker data fields and the corresponding media management system database fields updated by the NetWorker Defined Agent.  
                                   NetWorker Data Fields   Media Manager Data Fields       Field Name   Field Name                   Volid*   VOLSER           IVOLSER       Barcode (if present)*   VOLSER       Volume/Label Name   FILE NAME       Volume flags   READONLY flag       Volume Expiration   EXPIRATION       Pool   POOL           FILE NAME (If the -f argument is specified           on the import process.)       Number of Mounts   UCOUNT       Access Date   CREATE DATE           REF DATE       Labeled Date   CREATE DATE           REF DATE           LIB DATE       Tape Type   TYPE       Volume Location &amp; Access   LOCATION ID (if Access=OFFSITE)       Volume flags   SCRATCH flag is set if Recyclable flag is           set                 *If no barcode is present:            VOLSER=Volid            IVOLSER=Volid            *If a barcode is present:            VOLSER=Barcode            IVOLSER=Volid            NOTE:            VOLSER and IVOLSER fields support up to 12 characters.            The following fields are set to default values:            OWNER=networker            PRG=networker (create program)            OS=UNIX            CRHOST=**            RFHOST=**            LBHOST=**            **If the ttk_nw program is processed using the -h argument, fields are populated with that value. If the -h argument is not used, fields are populated with the local host name.             
 
 Vault management is most efficient using filename patterns. To facilitate volume movement, specify the -f argument on the NetWorker Import Agent command (ttk_nw). The -f argument instructs the media management system  40  to populate the filename field with the contents of the NetWorker pool field. If the pool field value contains any spaces, they are replaced with an underscore (_) character in the Media Manager filename field. 
 
         [0063]     If there is a conflict between the importing data and the management system database  20  for the create date field, and the management system database  20  shows that volume to be at an offsite location; the media management system will automatically return the volume back to the onsite location, then update the management system database  20  fields with values contained in the importing record. If the volume is part of a multi-volume set, the entire set is processed in the same manner.  
         [0064]     To configure, the media management system uses NetWorker commands to retrieve volume information from NetWorker (mminfo), send vault information back to NetWorker (mmlocate), for the Tape Duplication feature (nsrclone), and for the Automatic Tape Ejection feature (nsrjb). Tape Duplication and Automatic Tape Ejection features are useful with the tape library  22  of  FIG. 3 .  
         [0065]     Configuration involves creating symbolic links to the NetWorker commands, writing simple scripts to interface with NetWorker, and setting up remote access commands if needed. If the media management system is installed on the same host as the tape application, then remote shell/remote copy or secure shell/secure copy commands are not required.  
         [0066]     On the NetWorker server and/or storage node, create symbolic links to the NetWorker mminfo and mmlocate commands by running the following commands: 
        In -s/&lt;NetWorker path&gt;/mminfo/usr/local/bin/mminfo     In -s/&lt;NetWorker path&gt;/mmlocate/usr/local/bin/mmlocate 
 
 If planning to use the Tape Duplication feature: A copy of the nsrclone command must be created in the /usr/local/bin directory on the NetWorker server and/or storage node, then the permissions to the copied command changed. Run the following commands signed on as root: 
    cp/&lt;NetWorkerpath&gt;/nsrclone/usr/local/bin     chmod 6711 /usr/local/bin/nsrclone 
 
 If planning to use the Automatic Tape Ejection feature: A copy of the nsrjb command must be created on the Networker server and/or storage node, and the permissions to the copied command changed. Run the following commands, signed on as root: 
    cp/&lt;NetWorkerpath&gt;/nsrjb/usr/local/bin     chimod 6711 /usr/local/bin/nsrjb     NOTE: If the commands are changed by a release level upgrade to the tape application, the commands must be re-copied. 
 
 The ttk_nw and ttk_nw_vlt programs can use either the UNIX remote shell (rsh) and remote copy (rcp) commands or the secure shell (ssh) and secure copy (scp) commands. 
       
 
         [0077]     To import data using the NetWorker agent from a NetWorker server running on a Windows NT system, follow these additional steps:  
                                     NETWORKER MUST BE INSTALLED ON A UNIX SYSTEM       ACCESSIBLE TO THE UNIX SYSTEM WITH MEDIA       MANAGEMENT SYSTEM.                                Add an entry in the /etc/hosts file for the Windows NT NetWorker server.       Run the NetWorker agent with the following command to import the data       into media management system:               ttk_nw -h Unix system -s Windows NT server -f             To export the data, run the following command:               ttk_nw_vlt -h unix system -s Windows NT server                  
 
 In use, adding and updating NetWorker tape volumes is done entirely by NetWorker with the exceptions of Tape Duplication and Vault Management. The ttk_nw program should be run on a frequent basis to ensure that media management system accurately reflects the volume status. 
 
         [0079]     How to use the ttk_nw program:  
                                             ttk_nw                                -h   &lt;networker_host&gt;   Specifies the UNIX based machine to               establish communications with first in the               network. It must be a machine that is a               NetWorker client which can issue the               mminfo command. If omitted the local host               is used. Optional.       -s   &lt;networker_server&gt;   Specifies the the NetWorker server name               from which data is to be imported. This               argument is typically used if the NetWorker               server is not a UNIX based machine.               Optional.       -r   &lt;networker_release&gt;   Specifies the release of Legato NetWorker               from which data is to be imported. Valid               released are 553, 601, 602, 610 and 611.               Periods in the release level are not               permitted. The default is 602. Optional.       -f   filename   Specifies that the media management system               filename field is to be populated with the               contents of the NetWorker pool field. This               argument is required to reference the               filename field in move job definitions, and               for using the Tape Duplication feature.               Otherwise, it is optional.       -u   media usage based   Specifies whether to set the media           vaulting   management system flag “NO               VAULT” if the NetWorker volume full flag               is checked. When STRVMS runs and the               “NO VAULT” flag is set then media               management system will ignore those               volumes when move records are generated.               Optional.       -e   expiration argument   Specifies the volume will be set to expired if               no save sets are found. Optional.       -t   test mode   Runs the agent in test mode which causes all               normal processing to occur yet the media               management system database is not updated.               Optional.                  
 
 Example: 
        ttk_nw -h systema -f 
 
 This will retrieve NetWorker 6.0.2 tape volume information from remote host systema, and update the media management system database on the local host. The filename field will be populated with the NetWorker pool field. 
 
 Multiple NetWorker server example script: 
    ttk_nw -h systema -f     ttk_nw -h systemb -f     ttk_nw -h systemc -f     ttk_nw -h systemd -f 
 
 How to use the ttk_nw_vlt program: 
       
 
         [0089]     The ttk_nw_vlt program requires a userid that has NetWorker administrator privilege.  
                                             ttk_nw_vlt                                -f   &lt;agent_vault_list&gt;   Specifies a file read as input that controls               which volumes are updated in NetWorker.               The agent vault list is generated when the               strvms -a command is processed. This is a               required parameter.       -h   &lt;networker_host&gt;   Specifies the UNIX based machine to               establish communications with first in the               network. It must be a machine that is a               NetWorker client which can issue the               mmlocate command. If omitted the local               host is used. Optional.       -s   &lt;networker_server&gt;   Specifies the NetWorker server name to               which data is to be exported. This argument               is typically used if the NetWorker server is               not a UNIX based machine (Windows NT,               etc.). Optional.       -t   test mode   Runs the agent in test mode which causes all               normal processing to occur yet the media               management system database is not updated.               Optional.                  
 
         [0090]     The ttk_nw_vlt program should be run after every execution of the strvms/runpend programs. It should be run for each NetWorker host. These programs are part of the Vault Management System.  
         [heading-0091]     Example:  
         [none]    
       
         
           
              strvms—a moved_vols -p  
              ttk_nw_vlt -f moved_vols -h systema 
 
 Multiple NetWorker server script: 
 
              strvms -a moved_vols -p  
              ttk_nw_vlt -f moved_vols -h systema  
              ttk_nw_vlt -f moved_vols -h systemb  
              ttk_nw_vlt -f moved_vols -h systemc  
              ttk_nw_vlt -f moved_vols -h systemd  
           
         
       
     
         [0100]     Example List, long display option  
                                                                       CREATION/REFERENCE DATA                                VOLSER=1758039041   IVOLSER=1758039041   EXDATE/CODE=20030119       FILE_NAME=UA0002       LAVEL=NONE   OWNER=networker   USERID=       JOBID=   PRG=networker   GROUP=       SEQUENCE=0/0   UNCR=   UNREF=       FIRST_VOL=1758039041   PREV_VOL=   NEXT_VOL=            ENTRY_DATE=20010219/16:01CREATE_DATE=20010121/20:00   REF_DATE=20010121/20:00            RFUSERID=   LBUSERID=tms   LIB_DATE=20010219/16:05       CRHOST=p2ibm   RFHOST=p2ibm   LBHOST=dogbert       TYPE=   DENSITY=   FORMAT=       MEDIA_CAPACITY=   0 MB   MEDIA_USAGE=  0 MB   FILESIZE=   0 MB       FLAGS=[RDONLY]       BKLEVEL=0   BKDIR=       LOCATION_ID=DOGNWVLT       VSLOT= 2       LOCATION_TXT=DOGNWVLT       LIBRARY=       DVN=   OS=UNIX   POOL=AIXFULL       VENDOR=       UCOUNT=0   CLCOUNT=0   CLUSE=0       CLDATE=   RD_ERRORS=0   WR_ERRORS=0       OUT_DATE=20010219   RTN_DATE=20050510       COMMENTS=       &gt;            Continue to the next record? &lt;Y/N&gt; &gt;                  
 
 Scratch Reporting 
 
         [0102]     When a Legato NetWorker tape volume becomes “recyclable”, the volume can be flagged as a scratch tape in the media management system database and included on a scratch list. This is done via the media management system scratch program.  
         [0103]     b. Management Reports  
         [0104]     Standard management reports are included with The media management system. These reports are described in more detail in the following sections, and a sample of typical report output is also included. Each report can be executed from the UNIX command line, the character menu programs, or the GUI menu programs.  
         [0105]     The GUI [Media Management System Management Reports] selection screen is launched from the [Librarian] menu. tms_rpt launches the character based menu described below. The user is allowed to choose any of the standard reports, and is prompted for format (landscape or portrait), lines per page, and destination (screen, file, or printer). Any user is allowed to run the media management system reports, but the typical report requester will be the site Librarian.  
         [0106]     Each report has two versions—a compact 80 column version which will print on a line printer or in portrait mode on a standard laser printer, and an expanded 132 column version which will print on a line printer or in landscape mode on a laser printer. Examples of each are included later in this document. The user is allowed to select the number of lines per page if the default of 55 prints too many or too few lines for the desired printer.  
         [0107]     If the user chooses a file for the destination, a prompt for the filename will be issued. All media management system reports will be written to the {$TMS_HOME}/reports directory—if the directory does not exist, tms_rpt will create it. Once created, the report files can be pulled into mail documents or distributed in other ways.  
         [0108]     If a printer is selected as the destination, tms_rpt will prompt for a printer destination. If the UNIX user has initialized a printer in the LPDEST environment variable, tms_rpt will use this as an assumed default printer. If LPDEST is empty, tms_rpt will use as the default printer the value of PTR (set automatically by the tms_env environment script that should be included in every user&#39;s login profile). The program will ask if the default is okay, and if not, will give the user the opportunity to select a different printer.  
         [0109]     Upon completion of a report (usually in 2 to 10 seconds), the original menu screen is displayed.  
         [0110]     The following is an example of a user selecting the audit report and sending it to a printer.  
                                             /home/tms &gt; tms_rpt &lt;CR&gt;                                SCREEN 1:                   Reports               System: p2ibm        Select one of the following:        1.  Audit File        2.  Expiration        3.  File        4.  Recovery        5.  Media Error        6.  Media Usage        7.  Owner        8.  Volume        9.  Vault        Selection [ ]        SCREEN 2:           Reports               System: p2ibm        Select one of the following:        1.  Audit File        2.  Expiration        3.  File        4.  Recovery        5.  Media Error        6.  Media Usage        7.  Owner        8.  Volume        9.  Vault        Selection [1]        1. Do you want portrait or landscape format?           (Default = land) &lt;port, land&gt;[L]        2. How many lines per page? (55 = default) [ ]        3. Do you want output to the screen, file, or printer? (S, F, P) [P]        4. Is printer cntlasr correct? (Y/N) [ Y ]                 Note:            Prompts 1, 2, 3, and 4 display sequentially after response to the preceding prompt.             
 
         [0111]     c. Scratch Reporting  
         [0112]     The media management system scratch process can be used to provide listings of the volumes in the media management system database currently available for use (referred to in media management system as ‘scratched’ tapes or volumes). The scratch program is usually scheduled to process after updated data has been imported into The media management system via the Defined and/or the Generic Update Agent programs.  
         [0113]     It should also be processed only after any librarian changes that are needed have been entered via the tmsx program. Usually, librarian changes are only necessary when managing all volume information via the media management system database utilities.  
         [0114]     Once all database updates have completed, the scratch program is to be processed to review the tape expiration status updates. The expiration date and/or code information is compared to the current system date, and determines if the volume is now available for use. The scratch program sets the scratch flag in the media management system database to on, and includes the volume as a new scratch and the report is generated. The volume will continue to appear on the scratch report each time the scratch is executed (unless the -n argument is used, which indicates that The media management system is to include only new scratch volumes).  
         [0115]     An important note regarding scratch processing: Since The media management system does not perform I/O functions on the tapes themselves, the scratch program is not used to provide any sort of data overwrite protection once they are mounted onto a device. The tape generating application from which the data originated is usually what provided this protection from accidental data loss.  
         [0116]     d. Vault Management System  
         [0117]     The purpose of a vault (or container) management system is to minimize the risk of losing data by spreading it out over multiple locations. This way, if one location, such as the on-site data center is destroyed, data from another location can be retrieved and business can continue. With government regulations requiring that data be maintained for longer periods, multiple locations minimize the space required to keep tapes onsite. If for no other reason, keeping tapes at multiple locations reduces the security issues that could exist if all tapes were kept at a central location. media management system&#39;s Vault Management System (VMS) supports virtually limitless locations.  
         [0118]     This section will review the following: 
        tape movement strategies (location, container, vaulting)     how to set up the VMS configuration files (vmsx utility)     commands used to process the volume movement cycle     move/return reports     the tape duplication feature     the automatic tape eject feature     tape movement     how to set up     commands 
 
 Tape Movement Strategies 
       
 
         [0129]     The media management system provides a variety of tape movement options. From simple location moves, (using no containers or slots), to a complex schedule of container or vaulting patterns, The media management system provides the functions necessary to create and manage them with ease. Setting up The media management system is simple once you understand the concepts.  
         [heading-0130]     Location Management  
         [0131]     Locations are defined through a location definition. The definition includes the location name, address, contacts, telephone and fax numbers. When volumes move, The media management system verifies that the location exists and then moves the volume(s) to that location. Additional options include the ability to work with volumes, containers and slots at a location. When a volume returns, it returns to the location defined as the default location in the media management system database.  
         [heading-0132]     Container Management Concepts  
         [0133]     A container is a physical box that contains tapes. The number of tapes that the box holds depends on the size of the box and the size of the tapes. The container starts out at the data center where it is packed with tapes going to an offsite location for a user-defined period of time. The container is packed and locked by the user. Once complete, the container is retrieved by an offsite storage vendor and transferred to their location for safekeeping. When the user specified time has elapsed, the container returns to the user where it is unpacked and the tapes returned to the tape rack. Once the container has been unpacked, it is available for reuse. If an offsite tape is required for recovery, the container must be recalled from the offsite vendor.  
         [heading-0134]     Vault Management Concepts  
         [0135]     Vaulting (slot) management is accomplished by storing tapes individually at an offsite company&#39;s tape rack. This type of management requires that the user allocate a specific number of slots from an offsite storage vendor. The number of slots allocated usually equals the number of tapes at the location at any point in time. When tapes move offsite, the offsite storage vendor retrieves the tapes from the user and transfers them to available slots. If slot management is controlled by the user, the user must tell the vendor which slot to use. When the tape returns from offsite, it is placed in the user&#39;s tape rack. Since vaulting deals with each tape individually, packing and unpacking do not apply. If an offsite tape is required for recovery, it must be recalled from the offsite vendor.  
         [heading-0136]     Move/Return Concepts  
         [0137]     The move schedule definition defines the volume or range of volumes to move offsite, the location that the volumes are moving to, the move date if other than today, an optional container class and a return date. The media management system uses this definition to move the volume to an offsite location on the specified date and return it when the return date is equal to or less than the current date. If a container class is specified, the volumes are packed into the container based on the container class rules for packing. When the volume returns, the move/return record is deleted. If the volume returns in a container, it remains there until unpacked by the user.  
         [0138]     Move jobs must be defined within The media management system. A move job defines the container class, move schedule, and calendar to use for volumes using this move job. If the name of the move job matches a saved file name, movement for volumes containing the file name will automatically occur provided the strvms and runpend commands have been scheduled.  
         [0139]     Move schedules are used to logically group move schedule entries. A move schedule entry will specify the location where the volumes will move and how long they will stay at the specified location. If the volumes are moving to multiple locations, a move schedule entry should be added to the move schedule for each location. Container Class and Slots Concepts.  
         [0140]     The use of containers or slots (vaulting) is optional. If used, they can be associated to a container class definition. The container class defines the size and rules for packing. Rules for packing determine if multiple systems or multiple return dates can