STORE and TurboSTORE/iX Products Manual HP 3000 MPE/iX Computer Systems Edition 2 Manufacturing Part Number: B5151-90003 E0300 U.S.A.
Notice The information contained in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability or fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for direct, indirect, special, incidental or consequential damages in connection with the furnishing or use of this material.
Contents 1. Introduction System Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Product Structure and Feature Comparisons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backup Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Temporarily Suspending Jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62 Sending Final Warning Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63 Aborting Any Remaining Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64 5. Storing Files Specifying Files in a STORE Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Renaming Files (RENAME) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specifying HFS Files (TREE and NOTREE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Storing Database Files Using PARTIALDB or FULLDB . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Disk Directory File (STOREDIRECTORY and NOSTOREDIRECTORY) . . . Storing Files in Interleave Format (INTER) . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Using REPLY and RECALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138 Automatically Assigning Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139 9. When STORE is Complete Checking File Listings for Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142 Verifying That STORE Files Are Error Free Using VSTORE . . . . . . . . . . . . . . . .
Contents Restoring Directory Information (DIRECTORY) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Finding Out What Is on Your Tape (LISTDIR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Progress Messages (PROGRESS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restoring Files with Certain File Codes (FCRANGE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specifying a Maximum Number of Files to Restore (FILES) . . . . . .
Contents B. Command Syntax STORE Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .198 RESTORE Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199 VSTORE Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .200 C.
Figures Figure 2-1.. Sample Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Figure 3-1.. Multiple-Device Planning Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Figure 3-2.. A Correctly Labeled Tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Figure 3-3.. Preparing Tapes for a Single Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Figure 3-4..
Figures 10
Tables Table 1-1.. Product Structure Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Table 1-2.. Feature Comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Table 2-1.. Task Roadmap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Table 6-1.. Maximum Tape Record Sizes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tables 12
Preface This book, the STORE and TurboSTORE/iX Products Manual, describes how to use the Fundamental Operating System (FOS) STORE product and the following TurboSTORE products: Product Number Product Description FOS STORE B5151AA TurboSTORE/iX II B5152AA TurboSTORE/iX 7x24 True-Online Backup NOTE The product structure of the STORE and TurboSTORE/iX products has changed for MPE/iX Release 5.5.
Chapter 4 Preparing the System, provides procedures for notifying the users of the backup process. Chapter 5 Storing Files, provides procedures for using the STORE command to store files and backup media. Chapter6 STORE and TurboSTORE Options, describes each of the STORE and TurboSTORE options. Chapter 7 TurboSTORE/iX 7x24 True-Online Backup , describes the operation and options of the new TurboSTORE/iX 7x24 True-Online Backup product.
1 Introduction This manual presents important information for system managers and operators on all aspects of storing files for backup, archive, or transfer. It describes how to use the STORE command and the TurboSTORE/iX products to save files and restore them back to the system. It also describes important methods for safeguarding the information in your system. More specifically, the manual describes how to do the following: • Maintain your backup media and manage backup devices.
Introduction System Backups System Backups Storing all of the information on your system to backup media is called backing up your system. You back up your system so that you have a copy of the information stored on it should it experience a major failure that causes some or all of your files to be lost. If your system experiences a failure, you can reload that information from your backup media.
Introduction Product Structure and Feature Comparisons Product Structure and Feature Comparisons The following table, Table 1-1. shows how the previous TurboSTORE/iX product structure for MPE/iX Release 5.0 has been incorporated into the current product structure for MPE/iX Release 6.5. Table 1-1. Product Structure Change 5.0 Product Structure 6.
Introduction Hardware Requirements Table 1-2.
Introduction Hardware Requirements When using TurboSTORE/iX 7x24 True-Online Backup, you can back up to and restore from disk files. For the best performance, it is recommended that the store-to-disk file(s) be located on a different device than the files being stored or restored. However, this is not required. Storing to more than one disk file in parallel is supported. Again, for the best performance, each parallel disk file should reside on a different disk or different volume set.
Introduction Backup Media Backup Media Backup media can include reel-to-reel magnetic tapes, DDS tapes, 3480 cartridges, and disk files. Backup media provides an economical way to maintain duplicates of important files on your system. The process of copying a file to backup media is called storing the file. The process of copying a file from backup media is called restoring the file. As a system administrator/operator, you frequently STORE and RESTORE files.
Introduction Disaster Recovery Plans Disaster Recovery Plans Regular system backups protect the information in your system from irretrievable loss by providing a copy of the information. However, natural and man-made problems, such as smoke, noxious fumes, explosion, flood, earthquake, and sabotage, can still threaten both your backup media and your system hardware.
Introduction Disaster Recovery Plans 22 Chapter 1
2 Managing Backups and Backup Media This chapter describes the purpose and process of performing regular backups of your files and systems.
Managing Backups and Backup Media Determining Your Backup Strategy Determining Your Backup Strategy The TurboSTORE programs allow you to store files to a single device or to multiple devices. The best way to use your backup devices depends upon the characteristics of the files that you are storing, your needs for compatibility with other versions of MPE, and your system configuration. The characteristics of the set of files help determine choices (or options) for storing them.
Managing Backups and Backup Media Determining Your Backup Strategy • Do you have user volumesets or mirrored volume sets on your system? If you use volume sets for application and volume management, then you may want to use the ONVS option of STORE. This option allows you to back up all files on a particular volumeset, including the system directory information for the volumeset. Doing backups on a volumeset basis can help reduce downtime by breaking up a large backup into individual volumeset backups.
Managing Backups and Backup Media Using STORE and RESTORE Using STORE and RESTORE The backup (STORE) and recovery (RESTORE) processes have similar steps. Only the specific commands and command options differ. The structure of your organization determines who performs the STORE and RESTORE steps. The basic steps include the following: 1. Determine what you want to store or restore. Refer to "What Should You Backup?" in this chapter. 2. Identify the storage device.
Managing Backups and Backup Media Using STORE and RESTORE Table 2-1. provides a roadmap for system managers and operators of the chapters that pertain to their particular tasks. Table 2-1. Task Roadmap Chapter Description Tasks Define all backup and recovery procedures 1 "Introduction" - Basic backup concepts and hardware requirements. X 2 "Managing Backups and Backup Media" Planning, scheduling, and maintaining backups. X 3 "Preparing Storage Devices" - Procedures for using backup devices.
Managing Backups and Backup Media Using STORE and RESTORE Table 2-1. Task Roadmap Chapter Description Tasks 9 "When STORE is Complete" - Procedures for verifying STORE process is complete. X X X 10 "Backing Up the System Configuration" How to perform a complete system backup with STORE and SYSGEN utility. X X X 11 "Restoring Files" How to use RESTORE and its options. X X X X 12 "Using Backup Media to Recover from a System Failure" - How to restore a system from backup media.
Managing Backups and Backup Media What Should You Backup? What Should You Backup? To completely back up your system, you should copy three types of information: • User and system files. User files are usually the largest part of a system backup. They cannot otherwise be duplicated, except from hardcopy. Since, in total, they can be the product of several months or even years of labor, user files can be considered the most important element within your computer system.
Managing Backups and Backup Media Scheduling Backups Scheduling Backups There are two important considerations when planning a backup schedule: • Plan full and partial backups to efficiently duplicate the most recent system information. • Schedule a regular time for performing backups. Full and Partial Backups There are two ways to perform a system backup. A full backup copies all files stored in your system whether or not any of the information in them has changed since the last backup.
Managing Backups and Backup Media Using Unlabeled vs Labeled Media Selecting a Time for Backups It is best to perform backups at a time when people are not normally using the system. Often, system administrators choose to perform backups at the close of the workday or later in the evening. It is also a good idea to schedule the backup for the same time every day so users know when to expect it and can plan ahead. Be sure to schedule enough time for each backup.
Managing Backups and Backup Media Maintaining a Backup Library Maintaining a Backup Library Establish a library for storing backup media and backup records. Include the following in your library: • A large stock of new or scratch media to use for backups. (Scratch media are used media containing information that is no longer needed.) • A record of each tape's (or other media) contents. It should be easy to find the backup media needed to restore the system in the event of a failure.
Managing Backups and Backup Media Maintaining a Backup Library system's data, and an easy method for locating the data you want to recover. There are two reasons you should always keep older backup data in addition to your current backup data: in case the most recent copies are bad, and for restoring older files that may have been removed from the system some time ago. In such situations, you can restore files from the most recent intact copy.
Managing Backups and Backup Media Maintaining a Backup Library 34 Chapter 2
3 Preparing Storage Devices This chapter describes how to prepare your media and devices for backup. The sections in this chapter are: • Preparation Process • Preparing Tape and DDS Media • Preparing Tape and DDS Devices Preparation Process The following is a brief list of the preparation steps. 1. You must first determine what type of device(s) to use for your backup. Most of this section deals with storing to magnetic tape or DDS devices.
Preparing Storage Devices Preparation Process Parallel Pools Requires more than two backup devices. Files are being stored to more than one device at the same time. This is a combination of Sequential and Parallel. When the media (tape or DDS) fills, additional files are stored on the next device in line. You can set this up to have multiple pairs of toggling devices. 3. Decide on the order that each backup device in the pool is to be used. 4.
Preparing Storage Devices Preparation Process Selecting the Backup Method The best way to use your backup devices depends upon the characteristics of the files that you are storing, your needs for compatibility with other versions of MPE, and your system configuration. The characteristics of the set of files help determine choices (or options) for storing them. Generally speaking, the more files being stored, the more it is to your advantage to use multiple devices.
Preparing Storage Devices Preparation Process Assigning Device File Names When using multiple backup devices, you have the choice of entering multiple FILE commands to assign a different filename to each device or a single FILE command. Assigning each device a different filename makes it easier to keep track of each device's position in the backup media. When you receive media requests, you know exactly to which device the request applies.
Preparing Storage Devices Preparation Process However, you may choose to employ multiple device configurations at times when you have a large set of files to store and you want to speed up the process. If so, you probably want to use the FILE command to give each device a filename that reminds you of its position. Then use the STORESET parameter in a STORE command to reference the multiple devices.
Preparing Storage Devices Preparing Tapes and DDSs In the following example, STORE uses a total of four devices divided into two device pools. :FILE PPA1;DEV=7 :FILE PPA2;DEV=8 :FILE PPB1;DEV=9 :FILE PPB2;DEV=11 :STORE @.OPERATOR.SYS;;STORESET=(*PPA1,*PPA2),(*PPB1,*PPB2) If you gave the backup devices a single filename such as: :FILE T;DEV=TAPE enter the following STORE command to copy files to a set of parallel device pools: :STORE @.@.
Preparing Storage Devices Preparing Tapes and DDSs 3. Label the first unit of backup media. Single or Sequential Label the first unit Volume 1 of n. Replace n with the total number of units of backup media--if you use more or fewer tapes than you planned, you may have to change this number when you finish storing the files. Label the second unit of backup media Volume 2 of n. Label the third unit of backup media Volume 3 of n, and so on.
Preparing Storage Devices Preparing Tapes and DDSs Figure 3-2. shows an example of a correctly labeled backup: Figure 3-2. A Correctly Labeled Tape 5. Stack all your media (tapes or DDSs). Single If you plan to use a single device, stack all of your backups, label side up, in order, with the lowest number on top, near the device, as shown in Figure 3-3.. Figure 3-3.
Preparing Storage Devices Preparing Tapes and DDSs Figure 3-4. Preparing Tapes for Parallel Devices 6. Divide your media among the devices. Sequential Chapter 3 If you plan to use sequential devices, divide your media among the devices in order. For example, if you have two sequential devices and six media, stack media 1, 3 and 5 near device 1, and stack media 2, 4 and 6 near device 2. Stack all media label side up and make sure that the lowest-numbered backup is on the top of each stack. Figure 3-5.
Preparing Storage Devices Preparing Tapes and DDSs Figure 3-5. Preparing Tapes for Sequential Devices Parallel Pool 44 If you are using parallel device pools, divide your media among the devices in each device pool, placing them in order with the label side up. For example, if the first device pool has two sequential devices and four media, stack media Reel1 Set1 and Reel3 Set1 near device A1, and place media Reel2 Set1 and Reel4 Set1 near device A2. Figure 3-6.
Preparing Storage Devices Preparing Tapes and DDSs Figure 3-6.
Preparing Storage Devices Preparing Tape and DDS Devices Preparing Tape and DDS Devices Prepare your backup devices by mounting the first media in the stack near each device onto that device. Follow the instructions in Chapter 3, "Preparing Storage Devices," for mounting backup media. After mounting the media, check the console for a message telling you that the volume has been mounted. For example: 14:47/31/VOL (Unlabeled) mounted on LDEV#8 Note the backup drive's logical device (LDEV) number.
Preparing Storage Devices Preparing Tape and DDS Devices configured to automatically allocate devices (autoreply) or when you are using multiple backup devices. NOTE If auto reply is not enabled on the backup device designated, a reply from the console is necessary to allocate that device for a STORE process. See Chapter 8, "Handling Media Requests," for more information.
Preparing Storage Devices Preparing Tape and DDS Devices Multiple devices can be used as: • Sequential devices. • Parallel devices. • Parallel device pools. Using Tape Devices Sequentially With sequential backup devices, when the first backup on the first backup device is filled, it immediately begins writing files to a second backup on the second backup device and the first backup rewinds. When the first backup is rewound, you can unload it and prepare the drive with a new backup.
Preparing Storage Devices Preparing Tape and DDS Devices Use the FILE command to give each device a filename that reminds you of its position. Then use the STORESET parameter in a STORE command to reference the multiple devices. For example, to store files to three sequential devices, use the following set of commands: :FILE SEQ1;DEV=7 :FILE SEQ2;DEV=8 :FILE SEQ3;DEV=9 :STORE @.@.@;;STORESET=(*SEQ1,*SEQ2,*SEQ3) The above STORE command copies all system and user files to three sequential devices.
Preparing Storage Devices Preparing Tape and DDS Devices Figure 3-9. Parallel Backup Currently, all STORE and TurboSTORE products support a maximum of 16 parallel backup devices. The actual speed of performance depends on the system, disk configuration and the backup devices used. When using a multiple-processor machine, you can see increased backup performance when doing parallel backups. Each parallel device or device pool is controlled by a separate process.
Preparing Storage Devices Preparing Tape and DDS Devices If you gave the backup devices a single filename such as: :FILE T;DEV=TAPE enter the following STORE command to copy files to a set of four parallel backup devices: :STORE @.@.@;;STORESET=(*T),(*T),(*T),(*T) Describe parallel devices in the STORESET parameter by enclosing each backreferenced device filename within parentheses. Use commas to separate devices.
Preparing Storage Devices Preparing Tape and DDS Devices uses a total of four devices divided into two device pools. :FILE PPA1;DEV=7 :FILE PPA2;DEV=8 :FILE PPB1;DEV=9 :FILE PPB2;DEV=11 :STORE @.OPERATOR.SYS;;STORESET=(*PPA1,*PPA2),(*PPB1,*PPB2) If you gave the backup devices a single filename such as: :FILE T;DEV=TAPE enter the following STORE command to copy files to a set of parallel device pools: :STORE @.@.
Preparing Storage Devices Preparing Tape and DDS Devices messages will also be sent to the backup's $STDLIST. NOTE Chapter 3 Remote backup is currently only supported for unlabeled backups. Labeled backups cannot be accessed remotely by either STORE or CMSTORE.
Preparing Storage Devices Storing to Disk Files Storing to Disk Files Using TurboSTORE/iX 7x24 True-Online Backup (product number HPB5152AA), you have the ability to store files to disk files. This feature allows you to quickly back up filesets. It also allows you to create archive files that maintain all MPE file attributes.
Preparing Storage Devices Storing to Disk Files For example, if STORE needed three disk files to store all files, they would be named: /SYS/MYBACKUP/STORDISC /SYS/MYBACKUP/STORDISC.2 /SYS/MYBACKUP/STORDISC.3 When STORE moves on to another file, be sure enough disk space exists before doing the backup. NOTE Chapter 3 The disk files can be restored by the MPE/iX 5.5 Limited Release version of RESTORE or later. RESTORE cannot restore disk files on pre-MPE/iX 5.5 systems.
Preparing Storage Devices Storing to Disk Files 56 Chapter 3
4 Preparing the System This chapter describes the procedures for notifying and preparing all the interactive items of a system for a system level backup. The sections are: • Notifying Users of Pending Backup • Preventing New System Activity • Sending Warning Messages • Replying to Console Requests • Temporarily Suspending Jobs • Sending Final Warning Messages • Aborting Any Remaining Sessions For non-online backups, it is recommended that system backups be done when no one else is using the system.
Preparing the System Notifying Users of Pending Backup Notifying Users of Pending Backup About 15 minutes before you plan to begin the backup, use the TELL command to send a message asking all users to finish their work and to log off the system. Enter the following command substituting the actual time that you plan to begin the backup for hh:mm. :TELL @S; BACKUP BEGINS AT hh:mm.
Preparing the System Preventing New System Activity Preventing New System Activity You control the number of executing jobs and sessions with two commands, LIMIT and JOBFENCE. The LIMIT command controls the number of jobs or sessions that execute concurrently. (The limits you set with the LIMIT command cannot exceed the maximum job/session limit determined by your system configuration.) The JOBFENCE command lets you choose the priority jobfence--a number between 0 and 14 (inclusive).
Preparing the System Sending Warning Messages Sending Warning Messages About 10 minutes before you plan to begin the backup, use the WARN command to send a message to all users asking them to log off the system. Unlike the TELL command, the WARN command interrupts users working in QUIET mode so that you can be sure they know about the impending backup. Enter the command below, substituting the time you intend to begin the backup for hh:mm. :WARN @S; BACKUP WILL BEGIN AT hh:mm.
Preparing the System Replying to Console Requests Replying to Console Requests Before continuing with the backup, check whether there are any console requests pending. Enter: :RECALL If the system responds with NO REPLIES PENDING, skip to the "Temporarily Suspend Jobs" step below. If there are some console requests that you have not yet answered, respond to them now. Refer to Chapter 8, "Handling Media Requests," for information on answering media requests.
Preparing the System Temporarily Suspending Jobs Temporarily Suspending Jobs It is advisable to suspend the execution of all jobs while a STORE is being performed. (If a job step attempts to open a file for write access which is being stored, the open fails, with possible negative consequences for the job.) NOTE Advise users not to schedule jobs during the time schedule for backups. STORE does not copy files opened by suspended jobs. Therefore, a backup undertaken with suspended jobs may be incomplete.
Preparing the System Sending Final Warning Messages Sending Final Warning Messages Check to see whether any users are still logged on to the system by entering: :SHOWJOB JOB=@S If there are any remaining sessions, besides your own, send them one last warning: :WARN @S; LOG OFF NOW! BACKUP ABOUT TO BEGIN NOTE For an online backup, issue this warning to all users who are still logged on. You may want to add that they can log back on once the backup has started.
Preparing the System Aborting Any Remaining Sessions Aborting Any Remaining Sessions Check one more time whether all sessions (except your own) have logged off by entering: :SHOWJOB JOB=@S Either abort any sessions other than your own that are still executing, or check with the users and ask them once more to log off.
5 Storing Files This chapter contains complete information on how to use the STORE command to store files to backup media. STORE can be used to back up a single file, all user, system, and system directory files (that is, a full system backup), or any number of files in between. The information in this chapter describes how to use the STORE command and its options to create backups that can be restored using the RESTORE command. The subjects are: 1. Specifying files in the STORE command 2.
Storing Files Specifying Files in a STORE Command other than LDEV 1. These files reside in the SYS account and can be displayed by entering the SHOW command in the SY configurator of the SYSGEN utility. Also, do not purge or put a lockword on these files. Finally, do not use any command other than SYSGEN to manage the files within a configuration group. These configuration files come as a set and individual files may not be moved between groups or systems.
Storing Files Specifying Files in a STORE Command matches filestostore will be stored, unless the file also matches a filestoexclude. An unlimited number of filestoexclude may be specified. However, if the TRANSPORT option is also being used, only one filestoexclude may be specified. NOTE Since the hyphen (-) is a valid character for HFS syntax filenames, a blank character must separate it from HFS filesets to obtain the special negative fileset meaning.
Storing Files Specifying Files in a STORE Command Using Wildcard Characters Use wildcard characters to select multiple files to store. The wildcard character is expanded to include all files that match. Both MPE and HFS name components use the at sign (@), pound sign (#), and question mark (?) as wildcard characters. These wildcard characters have the following meaning: @ Specifies zero or more alphanumeric characters. # Specifies one numeric character. ? Specifies one alphanumeric character.
Storing Files Specifying Files in a STORE Command MPE and HFS Naming Equivalences When an MPE name component is a single @ wildcard, the @ includes all MPE and MPE-named files at that level and below. To specify only MPE-named files, use ?@ instead. The ? forces the first character of the filename to be an alphanumeric character, which only matches MPE-named files. MPE wildcards are not expanded in exclusion filesets. This means that @.@.@-@.@.@ is NOT an empty fileset. @.@.@ is the same as /. -@.@.
Storing Files Specifying Files in a STORE Command • Storing several files :STORE FILE1.PUB.RESEARCH,FILE2.PUB.MYACCT;*T • Store several files with wildcards — Store all MPE and HFS files in GROUP1.ACCTNAME: :STORE @.GROUP1.ACCTNAME;*T — Store all MPE and HFS files in the dir3 directory: :STORE ./dir3/@;*T — Store all HFS files that start with lower case letters in the CWD: :STORE ./[a-z]@;*T • Exclude some files from a fileset: — Store everything on the system except files in PUB.SYS, MPE format: :STORE @.
Storing Files Specifying Files in a STORE Command and a nonsystem volume set's files and directory. The usual STORE command, as illustrated in the previous section, might be: :STORE @.@.@;*T;DIRECTORY;ONVS=MPEXL_SYSTEM_VOLUME_SET,NV1 Using an indirect file can save time, especially if your STORE command is long or contains information that is difficult to remember. You enter the STORE files and parameters in a text file: @.@.
Storing Files Specifying Files in a STORE Command limit to the number of negative filesets that can be specified. Do not specify any continuation characters, such as ",", ";", "+", or "&", at the end of an indirect file line. If you need to specify more file sets than can fit on a line, just continue specifying them on additional lines. Do not start a line with the "," character. CI variables are not expanded in indirect files, so do not specify filesets using them.
Storing Files Specifying Files in a STORE Command STORE /SYS/PUB/MYFILE;;SHOW For more information regarding symbolic links and device links, see the article "Symbolic Links on MPE/iX" in Chapter 5 of the Communicator 3000 MPE/iX General Release 5.0 (Core Software Release C.50.00). Storing Database Files Storing TurboIMAGE Databases Prior to MPE/iX Release 5.5, the only way to logically back up databases was by using the DBSTORE and DBRESTOR commands.
Storing Files Specifying Files in a STORE Command If an individual ALLBASE/SQL database file is specified without the DBE file, it will not be stored, and the following message will be issued: MYSET01.MYDB.SYS NOT STORED: FILE IS PART OF AN ALLBASE DB ENVIRONMENT AND DBCON IS NOT SPECIFIED. If any of the dataset files are specified in addition to the root file, no warning will be displayed but the individual dataset files will be counted as redundantly specified files.
Storing Files Storing to Labeled Tapes Storing to Labeled Tapes The STORE command syntax for backups to labeled tapes is identical to that for unlabeled tapes. However, you must use a FILE equation to request that the STORE command write to a labeled volume. For example, when preparing for a backup to a volume set labeled VOL25, to be mounted on logical device 7, the following file equation could be entered: :FILE TAPE7=BACKUP.
Storing Files Storing to Labeled Tapes :=REPLY 47,7 The volume mounted is then labeled and the backup continues until a new volume is required. You will receive a message similar to the following: ?23:33/#S5/47/MOUNT REEL 2 OF SET VOL25 ON LDEV 7 This message is followed by a request to provide a volume ID for the volume. ?23:34/#S5/47/REPLY WITH VOL ID FOR VOLSET VOL25 on LDEV 7? Reply to this message with a valid ID for the volume.
Storing Files Monitoring STORE Command Progress Monitoring STORE Command Progress After you enter a STORE command, STORE issues a message similar to the following one on the $STDLIST: TURBO-STORE/RESTORE VERSION A.20.01 TUE, NOV 6, 1989, 2:57 PM (C) 1986 HEWLETT-PACKARD CO. Monitor the console for additional messages.
Storing Files Monitoring STORE Command Progress Handling Media Errors When a media error occurs while writing to a output device, the behavior of STORE depends on the value of the ONERROR option, as explained below. Tape Error Recovery The STORE command's ONERROR parameter lets you specify a backup error recovery procedure. Your options are ONERROR=QUIT and ONERROR=REDO. REDO is the default.
Storing Files Monitoring STORE Command Progress Responding to a NO WRITE RING Message Reel backups require you to insert a write ring into the reel in order to store files onto the backup. You see a NO WRITE RING message when you attempt to store files to a reel-to-reel backup and neglect to insert a write ring into the groove on the back of the backup reel. For example: 15:57/2/LDEV#8 NO WRITE RING The message above tells you there is no write ring on the backup reel mounted on LDEV 8.
Storing Files Monitoring STORE Command Progress Devices." 3. Mount the new piece of media. 4. Continue monitoring the backup process. Mount new media as the system requests them.
6 STORE and TurboSTORE/iX Command Options This chapter describes how to use all of the options available with all STORE and TurboSTORE/iX products, as of MPE/iX Release 5.5. The following options are new as of MPE/iX Release 5.5: STATISTICS PARTIALDB FULLDB STOREDIR[ECTORY] NOSTOREDIR[ECTORY] LOGVOLSET All the STORE and TurboSTORE/iX product options are listed with brief descriptions below. They are in the same order displayed in the STORE command syntax in Appendix B.
STORE and TurboSTORE/iX Command Options ONVS Stores files from volume sets SPLITVS Stores files located on mirrored volume sets RENAME Changes the name of original files on the system or the target files on the backup media TREE, NOTREE Specifies if files should be scanned recursively to include all files in a hierarchical directory INTER Specifies more than one file at a time should be written, or interleave on the backup media. STORESET Allows you to specify multiple backup devices.
STORE and TurboSTORE/iX Command Options STORE Options STORE Options Listing the Files Stored (SHOW) Whenever you store a set of files, the system displays the total number of files stored at your terminal. If there was an error, it also displays the number and names of files not stored and the reason each was not stored. Use the SHOW parameter and its options to display the names and additional information about the files stored and to list them on your system printer as well as at your terminal.
STORE and TurboSTORE/iX Command Options STORE Options Since HFS pathnames can be variable lengths, and can be quite long, they are placed at the end of the line so that they do not affect the spacing of the other columns. If the name does not fit on one line, it wraps to the next line. An asterisk (*) is placed at the last column of the line to indicate that the rest of the filename continues on the next line. NOTE It is likely that a STORE with the fileset @.@.
STORE and TurboSTORE/iX Command Options STORE Options et DISC DISC DISC 500 :C :C :C 16 16 16 1 1 1 /usr/lib/terminfo/e/ex3000 /usr/lib/terminfo/e/exidy /usr/lib/terminfo/e/exidy2* A long file display contains the same information as a short file display plus each file's ending media number, record size, blocking factor, maximum number of extents allowed, end-of-file, and file record limit. Once again, there are two formats for the long listing -- MPE and HFS.
STORE and TurboSTORE/iX Command Options STORE Options Figure 6-5.
STORE and TurboSTORE/iX Command Options STORE Options Figure 6-7.
STORE and TurboSTORE/iX Command Options STORE Options Figure 6-9. Names Only Format MEDIA_NUM 1 - 1 1 - 1 1 - 1 1 - 1 1 - 1 FILENAME /_HFSACCT/_HFSCRP/HFSMAP /usr/lib/terminfo/e/ethernet /usr/lib/terminfo/e/ex3000 /usr/lib/terminfo/e/exidy /usr/lib/terminfo/e/exidy2500 Forcing the HFS Format If SHOW=PATH is specified, the output STORE listing will be in HFS format, even if no HFS syntax files are being stored. You may want to use this so that all of your listings appear in the same format.
STORE and TurboSTORE/iX Command Options STORE Options Selecting an Error Recovery Method (ONERROR) When STORE encounters an error, it either automatically recovers or terminates, depending upon the nature of the error and the error recovery method you choose. Unrecoverable Errors The following unrecoverable errors always cause STORE to terminate: • A command syntax error. • An error in the file system directory. • An error opening a backup device or an indirect file.
STORE and TurboSTORE/iX Command Options STORE Options Optical Disk Errors If an optical disk write error is encountered, STORE displays the same error messages that it would display for tape backup devices. You can determine which piece of media is has been marked bad by using the STATUS command of the MOUTIL program. The status display indicates which piece of media is bad by showing "THE MEDIA IS BAD" in the media name field.
STORE and TurboSTORE/iX Command Options STORE Options Use this form of the DATE parameter when you perform regular backups of a fileset. Store the entire set, for example, once a week and store only those files that were modified or their states were changed since the full backup the remaining six days. NOTE STORE uses the state change date when storing files with the DATE parameter. To see the state change date, use the FINFO(filename,42) and FINFO(filename,41) functions.
STORE and TurboSTORE/iX Command Options STORE Options ;FILE T;DEV=TAPE :STORE @.EMPRECS.PERSONEL;*T;DATE<=02/02/92;PURGE NOTE In order to use the PURGE parameter with a privileged file or files, you must have system manager (SM), system supervisor (OP), or privileged mode (PM) capability. You may want to warn users before you archive files and inform them how to request to have archived files restored.
STORE and TurboSTORE/iX Command Options STORE Options up the system and/or nonsystem volume set directories (account structure). You may then reload the account structure in the event of a system disaster by restoring the directory onto the system from the backup media. You have the added flexibility of backing up the directories of nonsystem volumes attached to the system as a part of or as a separate entity from the system. This allows a nonsystem volume (volume set) to become a separate reliable entity.
STORE and TurboSTORE/iX Command Options STORE Options RENAME NOTIFY LOGVOLSET PART[IAL]DB FULLDB STOREDIR[ECTORY] NOSTOREDIR[ECTORY] STATISTICS Character set specifications, as listed in "Using Wildcard Characters" in chapter 5, "Storing Files," cannot be used with the TRANSPORT parameter.
STORE and TurboSTORE/iX Command Options STORE Options F#######._HFSGRP._HFSACCT Where ####### represents numbered files starting at 0000001. A mapping file is also on the media. This file specifies the mapping between the _HFSACCT name and the actual HFS name. The name of this file is HFSMAP._HFSGRP._HFSACCT. Sample entries in the file would look similar to this: F0000001._HFSGRP._HFSACCT <- /SYS/PUB/dir1/file_a F0000002._HFSGRP._HFSACCT <- /SYS/PUB/dir1/file_b F0000003._HFSGRP.
STORE and TurboSTORE/iX Command Options STORE Options you might enter the following: :FILE T;DEV=TAPE :STORE @.OPERATOR.SYS;*T;TRANSPORT;FILES=6000 Use the MPE/iX RESTORE command to restore files from MPE V/E format backup tapes to an MPE/iX system. MPE/iX RESTORE automatically detects that the tapes are in MPE V/E format, and invokes CM(RE)STORE (Compatibility Mode Restore) to restore the files.
STORE and TurboSTORE/iX Command Options STORE Options Table 6-1. Maximum Tape Record Sizes Tape Drive Record Size HP 7974 16 KB HP 7978A 16 KB HP 7978B 32 KB HP 7979 32 KB HP 7980(XC,S,SX) 32 KB DDS (all) 32 KB 3480 32KB MAXTAPEBUF should be used when storing to magnetic tape, DDS, or 3480 cartridges. Currently, it is not necessary to specify MAXTAPEBUF when storing to MO devices or disk files, since the maximum record size of 32K is already being used.
STORE and TurboSTORE/iX Command Options STORE Options ONLINE option with START or END), the files being stored remain available and can be modified while the backup is occurring. Refer to Chapter 7, "TurboSTORE/iX 7x24 True-Online Backup," for more information.
STORE and TurboSTORE/iX Command Options STORE Options • Number of retries incurred for each piece of media If software compression is enabled with the COMPRESS option, additional data on the amount of compressed data written, and compression ratios and percentages is displayed. If an online or 7x24 true-online backup is performed, then information on the amount of log data written is displayed. All data totals are shown in bytes. To convert these totals to sectors, divide by 256.
STORE and TurboSTORE/iX Command Options STORE Options the total amount of all data written for the backup. The Throughput section follows the data written columns. The throughput for a particular piece of media is computed by dividing the total amount of data written for a piece of media by the time it took to completely write that data. The time required to switch media is NOT accounted for in this computation. Only time spent actually writing the media is used.
STORE and TurboSTORE/iX Command Options STORE Options Following are examples of output from the STATISTICS options. Example 1 The following example is of a normal backup to a single device without software compression or online backup.
STORE and TurboSTORE/iX Command Options STORE Options BACKUP STATISTICS DATA WRITTEN SET 1 FILE DATA MISC DATA COMPRESSED LOG DATA TOTAL ON REEL MEDIA 1 | 63344322 | 418976 | 36349232 | 0 | 36768208 ---------+-------------+-------------+-------------+-------------+-----------SET 1 TOTAL 63344322 418976 36349232 0 36768208 SET 2 FILE DATA MISC DATA COMPRESSED LOG DATA TOTAL ON REEL MEDIA 1 | 66652980 | 307716 | 22195808 | 6144 | 22509668 ---------+-------------+-------------+-------------+-------------+-----
STORE and TurboSTORE/iX Command Options STORE Options Storing Files from Volume Sets (ONVS) To store the files on a particular volume set, use the ONVS parameter of the STORE command. ONVS lets you store files from up to 20 volume sets at once. For example, to store all files from the nonsystem volume sets named VOL_SET_A and VOL_SET_B, enter: :FILE T;DEV=TAPE :STORE @.@.
STORE and TurboSTORE/iX Command Options STORE Options NOTE Although the ONVS and SPLITVS options can be used together, a volume set that is specified for ONVS cannot be specified for SPLITVS and a volume set that is specified for SPLITVS cannot be specified for ONVS. Renaming Files (RENAME) When using the RENAME option, an original file refers to the original disk file, and a target file indicates the final filename on the backup media.
STORE and TurboSTORE/iX Command Options STORE Options The following tables illustrate sample translations for the target filenames: STORE a.b.c=...;TAPE;RENAME;SHOW Original Filename Target Specification Target Filename A.B.C x.y.z X.Y.Z A.B.C @.y.z A.Y.Z A.B.C x.@.z X.B.Z A.B.C x.y.@ X.Y.C STORE /A/B/C=...;TAPE;RENAME;SHOW Original Filename Target Specification Target Filename /A/B/C @.y.z C.Y.Z /A/B/C x.@.z X.B.Z /A/B/C x.y.@ X.Y.A STORE /a/b/c=...
STORE and TurboSTORE/iX Command Options STORE Options Original Filename Target Specification Target Filename /a/ /@/x/@/y/@ NOT STORED: * /a/f1 /@/x/@/y/@ NOT STORED: * /a/b/ /@/x/@/y/@ NOT STORED: * /a/b/f2 /@/x/@/y/@ NOT STORED: * /a/b/c/ /@/x/@/y/@ NOT STORED: * /a/b/c/f3 /@/x/@/y/@ /a/x/c/y/f3 /a/b/c/d/ /@/x/@/y/@ /a/x/c/y/d/ /a/b/c/d/f4 /@/x/@/y/@ /a/x/c/y/f4 /a/b/c/d/e/ /@/x/@/y/@ /a/x/c/y/e/ /a/b/c/d/e/f5 /@/x/@/y/@ /a/x/c/y/f5 /a/b/c/d/e/f/ /@/x/@/y/@ /a/x/c/y/f/
STORE and TurboSTORE/iX Command Options STORE Options The following table illustrates sample translations for a target file directory when the fileset specification was a directory: STORE /a/b/=/w/x/y/z/;*TAPE;RENAME;SHOW Original Filename Target Specification Target Filename /a/b/ /w/x/y/z/ /w/x/y/z/ /a/b/f2 /w/x/y/z/ /w/x/y/z/f2 /a/b/c/ /w/x/y/z/ /w/x/y/z/c/ /a/b/c/f3 /w/x/y/z/ /w/x/y/z/c/f3 /a/b/c/d/ /w/x/y/z/ /w/x/y/z/c/d/ /a/b/c/d/f4 /w/x/y/z/ /w/x/y/z/c/d/f4 /a/b/c/d/e/ /w/x/y/z
STORE and TurboSTORE/iX Command Options STORE Options There is an exception to this rule when the new filename does not have a legal account name in its pathname. A directory off of the root node that has a legal account name will be considered the account for the creator. This is true whether this directory is an account or not. Table 6-1. below illustrates the translations for the creator. All files below in the "sg" group of the "sa" account were created by "CREATOR.CRACCT." Table 6-3.
STORE and TurboSTORE/iX Command Options STORE Options You can specify the same target file information for more than one org file. However, when two or more files have the same name on a backup created using the RENAME option, RESTORE will write the second file over the first file. The files excluded may only be specified on the original side of the fileset. As with normal exclusion, there is no limit to the number of excluded filesets. The example below shows an exclusion file specification: :STORE @.PUB.
STORE and TurboSTORE/iX Command Options STORE Options PARTS22.GROUP.ACCT NOT STORED: FILE IS PART OF AN IMAGE DATABASE AND ROOT IS NOT SPECIFIED If any of the dataset files are specified in addition to the root file, no warning will be displayed but the individual dataset files will be counted as redundantly specified files. If you want to back up a partial database, you can use the PARTIALDB option. STORE will backup only those dataset files specified in the fileset list.
STORE and TurboSTORE/iX Command Options STORE Options NOTE This information in this file is also used to determine if a file being restored has after image log data. A file will have after image log data if it was modified before the sync point during a 7x24 true-online backup. RESTORE must have this information before restoring files, so when creating a 7x24 true-online backup with the sync point at the end of the backup, the STOREDIR option is automatically enabled.
STORE and TurboSTORE/iX Command Options STORE Options If you want to create a 7x24 true-online backup with the sync point at the end of the backup, and do not want a disk directory file to be created, specify the NOSTOREDIRECTORY or NOSTOREDIR option on the STORE command line.
STORE and TurboSTORE/iX Command Options TurboSTORE/iX II Options TurboSTORE/iX II Options The following options are available only if the TurboSTORE/iX II product is purchased. In addition to all of the STORE options, the following additional options are available with TurboSTORE/iX II. For more information on purchasing TurboSTORE/iX II, contact your Hewlett-Packard sales representative.
STORE and TurboSTORE/iX Command Options TurboSTORE/iX 7x24 True-Online Backup Options To compress data when storing files to backup, use the FILE command, then use the COMPRESS parameter in your STORE command. For example: :STORE @.OPERATOR.SYS;*T;COMPRESS=HIGH WARNING If you are using a backup device that performs hardware data compression, COMPRESS=HIGH should NOT be used. Performing compression twice is redundant, and in some cases can lead to slower backup performance.
STORE and TurboSTORE/iX Command Options TurboSTORE/iX 7x24 True-Online Backup Options true-online backup. • The second type of online backup, referred to as a 7x24 true-online backup, lets you backup applications without requiring any files to be closed for write access at any time during the backup. This section describes how to perform the online backups using just the ONLINE option. For information on performing 7x24 true-online backups, refer to Chapter 7.
STORE and TurboSTORE/iX Command Options TurboSTORE/iX 7x24 True-Online Backup Options When online backup begins, the shadow subsystem assigns each file in the store fileset to a log file created on the same volume where the file resides. Actual logging activity does not take place unless the file is modified after the attach phase. TurboSTORE saves the changes made to databases and files being stored in special log files. These files can become quite large when there is a lot of activity on the system.
STORE and TurboSTORE/iX Command Options TurboSTORE/iX 7x24 True-Online Backup Options where the exclamation point ( ! ) is replaced by the actual filename(s). During the RESTORE process, the log file is used to reconstruct the original contents of the files; that is, the way they appeared at the moment they were attached during online backup. NOTE The ONLINE option cannot be specified with the SPLITVS or TRANSPORT options.
STORE and TurboSTORE/iX Command Options TurboSTORE/iX 7x24 True-Online Backup Options 118 Chapter 6
7 TurboSTORE/iX 7x24 True-Online Backup This chapter describes how to use TurboSTORE/iX 7x24 True-Online Backup. It includes a description of all the options provided for performing 7x24 true-online backups, as well as discussions about TurboSTORE's interactions with the system during these backups.
TurboSTORE/iX 7x24 True-Online Backup Using TurboSTORE/iX 7x24 True-Online Backup Using TurboSTORE/iX 7x24 True-Online Backup When using TurboSTORE/iX 7x24 True-Online Backup, you can perform file, application, and system backups without closing files or disrupting users. Some guidelines for performing these backups are discussed below.
TurboSTORE/iX 7x24 True-Online Backup Using TurboSTORE/iX 7x24 True-Online Backup Sync Point at the Beginning of Backup The sync point is always at the beginning of an online backup when only the ONLINE option is used. A 7x24 true-online backup can also have the sync point at the beginning by using the ONLINE=START option.
TurboSTORE/iX 7x24 True-Online Backup Using TurboSTORE/iX 7x24 True-Online Backup backup media. For example, scheduling the sync point at the end of the backup can be useful if you start your backup in the middle of the day (at lunch time, for example). The backup can then run throughout the afternoon shift, and be finished before your disk-intensive batch jobs are run at night. Synchronizing at the end would then allow you to save the state of your system at the end of the working day.
TurboSTORE/iX 7x24 True-Online Backup Consistent Backups Consistent Backups Even though database files generally constitute the largest part of any backup, TurboSTORE/iX 7x24 True-Online Backup also backs up system and non-database files. Since TurboSTORE allows changes to files during a backup, it establishes a close tie to the file system to ensure physical and logical consistency.
TurboSTORE/iX 7x24 True-Online Backup Consistent Backups NOTE Quiescing an ALLBASE/SQL database and storing the ALLBASE/SQL database by TurboSTORE/iX 7x24 True-Online Backup when the DBEnvironment is in normal use, has the same effect as using the STOREONLINE command of SQLUtil. For a 7x24 true-online backup of ALLBASE/SQL to be of use for rollforward recovery, use the same procedures you would use when doing the STOREONLINE commands. If you need to synchronize any other file types (e.g.
TurboSTORE/iX 7x24 True-Online Backup How Shadow Logging Works How Shadow Logging Works TurboSTORE/iX 7x24 True-Online Backup uses shadow logging to intercept any changes made to files while they are being stored. When the Sync Point is at the Beginning When the sync point occurs at the beginning of the backup (ONLINE=START), shadow logging guarantees that TurboSTORE captures the state of the fileset as it is right before the files begin to be written out.
TurboSTORE/iX 7x24 True-Online Backup How Shadow Logging Works When the Sync Point is at the End When the sync point occurs at the end of the backup (ONLINE=END), shadow logging captures the state of the files as they are at the end of the backup. In this case, instead of copying the before images of modifications to log files, shadow logging uses a bitmap to keep track of the modified pages. Once the backup is completed, the bitmap is used to collect the modified "after image" pages from the system.
TurboSTORE/iX 7x24 True-Online Backup Logging File Attribute Modifications Logging File Attribute Modifications In addition to keeping track of changes to a file's data during a 7x24 true-online backup, changes to a file's attributes, such as filename, file limit, and file code, are also captured to ensure a consistent backup. File Creations and Purges When the sync point is at the end of the backup, file creations and file purges that occur during the backup are captured by shadow logging.
TurboSTORE/iX 7x24 True-Online Backup TurboSTORE/iX 7x24 True-Online Backup Options TurboSTORE/iX 7x24 True-Online Backup Options This section discusses the new options available for creating TurboSTORE/iX 7x24 True-Online Backups. Creating a TurboSTORE/iX 7x24 True-Online Backup (ONLINE) A TurboSTORE/iX 7x24 True-Online Backup is performed only when either the START or END parameter is included with the ONLINE option.
TurboSTORE/iX 7x24 True-Online Backup TurboSTORE/iX 7x24 True-Online Backup Options NOTE If you are running the backup unmanned, and you want to synchronize these file types and/or databases, manually quiesce these before beginning the backup.
TurboSTORE/iX 7x24 True-Online Backup TurboSTORE/iX 7x24 True-Online Backup Options If a job fails, ASK would not show a request for that job. You could first do a RECALL to see if all the requests are there. If the job is missing, you could go fix the job, manually rerun it until it gets to ASK, and then complete all the backups by replying to all the ASK operator requests. • Use the START or END parameter with the time parameter.
TurboSTORE/iX 7x24 True-Online Backup TurboSTORE/iX 7x24 True-Online Backup Options For further information on DBRECOV, see the MPE/iX Release 5.5 (C.55.00) Communicator article, "IMAGE/SQL\with TurboIMAGE/XL Enhancements." Storing Part of a Database (PARTIALDB) When doing a 7x24 true-online backup, by default, TurboSTORE does not allow you to specify an incomplete TurboIMAGE or ALLBASE/SQL database to be stored. If you want to override this behavior, specify the PARTIALDB option.
TurboSTORE/iX 7x24 True-Online Backup Restoring TurboSTORE/iX 7x24 True-Online Backups Restoring TurboSTORE/iX 7x24 True-Online Backups This section discusses the options available for restoring backups created by TurboSTORE/iX 7x24 True-Online Backup. When restoring a backup that was created with the sync point at the beginning of the backup, RESTORE performs the following tasks for each file restored: 1. Restores the initial file data. 2. Applies any before image log data that exists on the backup.
TurboSTORE/iX 7x24 True-Online Backup Restoring TurboSTORE/iX 7x24 True-Online Backups Using the STOREDIR option causes RESTORE to read the directory on disk and prompts you to mount the correct media for the restore, shown as follows: 17:30/#S20/40/MOUNT MEDIA 2 OF SET 1 FOR RESTORE ON LDEV 7 For example, to restore the backup created on June 22, 1994 at 1:30pm by Pin 30, issue the following command: :RESTORE *tape;JONNYS.BIG.
TurboSTORE/iX 7x24 True-Online Backup Restoring TurboSTORE/iX 7x24 True-Online Backups 134 Chapter 7
8 Handling Media Requests This chapter describes the processes for handling the backup media. The subjects include: • Preparing the Backup Device • Checking the Console • Replying to a Media Request • Pending Media Requests • Denying a Media Request • Using REPLY and RECALL • Automatically Assigning Devices NOTE Instructions for using backup devices in this chapter are general procedures that apply to most devices. Your devices may operate differently.
Handling Media Requests Preparing the Backup Device Preparing the Backup Device In general, a backup device cannot be shared. Only one person at a time can use it. Often, users cannot access media drives without your assistance because media drives may be in a restricted computer room or you may be required to monitor media drive use. Users only have direct access to media drives when you provide them physical access and configure media drives so that they are automatically assigned to users.
Handling Media Requests Replying to a Media Request Replying to a Media Request Check that the request comes from the user who gave you the media. First, locate the user's job or session number in the media request. There can be different PINs for each request. In the following example, the session number is #S37. $$?16:04/#S37/23/LDEV# FOR "T" ON MEDIA (NUM)? Issue a SHOWJOB command to determine from which user the request came. For example: :SHOWJOB #S37 The system describes the job or session.
Handling Media Requests Pending Media Requests Pending Media Requests If several media requests appear at once, you can choose respond to any or all of them, in any order. When you choose not to respond to a media request, it remains pending until you respond or deny it. You can use the RECALL command at any time to list pending media requests.
Handling Media Requests Automatically Assigning Devices Automatically Assigning Devices You may choose to configure backup devices so that they are automatically assigned to users. This is also referred to as auto reply. When devices are configured for automatic assignment, the system automatically answers media requests for you. Devices configured for automatic assignment must have the following characteristics: • The device mode must be R (autoreply). • The device must not be job or data accepting.
Handling Media Requests Automatically Assigning Devices 140 Chapter 8
9 When STORE is Complete When you see the END OF PROGRAM message, STORE is complete.
When STORE is Complete Checking File Listings for Errors Checking File Listings for Errors As STORE copies files to backup, it will list them on the $STDLIST in the SYSLIST file, provided you use the SHOW parameter. For example, if you enter :STORE T@.SREXP.SYS;*T;SHOW The following might be listed on the console: Figure 9-1. Listing Files Copied to Tape STORE/RESTORE VERSION STORE X.51.00 (C) 1986 HEWLETT-PACKARD CO. a[mn]@.pub.sys;*n;SHOW MON, JUL 10, 1995, FILENAME GROUP AMCAT000.PUB AMMESCAT.
When STORE is Complete Verifying That STORE Files Are Error Free Using VSTORE Verifying That STORE Files Are Error Free Using VSTORE After using the STORE program to back up files, you should check to be sure that no errors occurred during the backup by using VSTORE. VSTORE verifies that the data written to backup is valid. The first place to check is the STORE listing. At the end of the listing, STORE prints a summary of how many files, HFS directories, symbolic links, and MPE directories were stored.
When STORE is Complete Verifying That STORE Files Are Error Free Using VSTORE offline printing option. • The ONERR[OR] parameter informs VSTORE what to do if a media error is encountered while verifying a file. Two options are available. If ONERR=SKIP is specified, then VSTORE will continue to verify files after an error is encountered. It will print an error message for any file that it was unable to verify. This is the default. Specifying ONERR=QUIT causes VSTORE to terminate upon getting a media error.
When STORE is Complete Using NODECOMPRESS Using NODECOMPRESS Normally, when VSTORE verifies a compressed store media, it reads in each record and decompresses it. This results in a thorough verification of the media by checking both the integrity of the data on the media as well as the correctness of the compression algorithm. If the NODECOMPRESS option is specified, VSTORE will only read the records from the media. It will not decompress them.
When STORE is Complete Allowing Users Back on the System Allowing Users Back on the System If you prevented users from accessing the system during your backup, as discussed in Chapter 4, "Preparing the System," you need to allow users to access the system again. To allow users access to the system again, perform the following: 1. Reset the job and sessions limits to their original values. Enter: :LIMIT nn,nn 2.
When STORE is Complete Allowing Users Back on the System should now be listed as executing or EXEC: Figure 9-3. Listing Resumed Jobs JOBNUM #S185 #J17 STATE EXEC EXEC IPRI JIN 20 10S JLIST 20 PP INTRODUCED FRI 1:03P FRI 5:02P JOB NAME OPERATOR.SYS AJOB,MRS.
When STORE is Complete Allowing Users Back on the System 148 Chapter 9
10 Backing Up the System Configuration This chapter describes how to use the SYSGEN utility to perform a system backup.
Backing Up the System Configuration SYSGEN Backup Capabilities SYSGEN Backup Capabilities A complete system backup consists of system files, user files, the file system directory, and system configuration information. STORE copies only system and user files and the file system directory to backup. To back up your system configuration, use the SYSGEN utility. This creates a system load tape (SLT).
Backing Up the System Configuration Running SYSGEN Running SYSGEN To run the SYSGEN utility, enter the following: :SYSGEN basegroup,newgroup,inputfile,outputfile All of the parameters are optional. The basegroup parameter is the group in the account SYS that contains the configuration data you use or alter. The default is CONFIG.SYS (or the group specified at system startup). If you specify a group that does not exist, an error occurs.
Backing Up the System Configuration The System Backup Command NOTE The warnings refer to the network manager configuration file, which configures remote devices and terminals on the system. SYSGEN is concerned with the devices actually interfaced to the system. The System Backup Command The SYSGEN command that you use to make a system load tape is TAPE (TA).
Backing Up the System Configuration Creating a System Load Tape Creating a System Load Tape To create a system load backup that contains a new configuration, follow the sample commands as illustrated: Figure 10-2. Creating a System Load Tape Sample :SYSGEN CONFIG,NEWFIG :SYSGEN version E.00.00 : catalog version E.00.00 FRI, JAN 7, 1994, 5:57 PM Copyright 1987 Hewlett-Packard Co. All Rights Reserved **warning** no NMCONFIG file in this configuration. **warning** NMCONFIG.PUB.
Backing Up the System Configuration Creating a System Load Tape Otherwise, recall the original CONFIG.SYS and store it under a different group name: sysgen>BASEGROUP CONFIG or sysgen>BA CONFIG sysgen>KEEP OLDFIG sysgen> sysgen>EXIT END OF SUBSYSTEM : If the system does not boot under the new CONFIG group, you can use the START GROUP=OLDFIG option under the initial system loader (ISL) to boot the system under the original CONFIG group.
Backing Up the System Configuration Combined SLT and Store Set Combined SLT and Store Set MPE/iX allows you to combine an SLT and any store filesets to make a combined SLT/Store set. This is recommended for DDS devices primarily whose large capacity allows both the SLT and store filesets to fit on a single cassette. In a combined SLT/Store set, the files are stored after the SLT. These files can be retrieved either by a reload or a separate RESTORE command which will skip over the SLT.
Backing Up the System Configuration Combined SLT and Store Set 156 Chapter 10
11 Restoring Files This chapter describes the RESTORE process and options. You RESTORE a file by transferring it from a STORE backup to disk. You might need to RESTORE a single file, for example, when a user accidentally deletes it. You might restore all the files in an account after you have permanently archived the account offline, deleted the files, and a user needs access to the files again. After a major system failure, you might need to RESTORE all of your files from backups.
Restoring Files files may not be moved between groups or systems. Such actions make these system files inaccessible, causing problems either immediately or at a later time. NOTE 158 For simplicity, the term tape is used throughout the procedures in this chapter. Substitute the appropriate media and device where applicable.
Restoring Files Preparing to Restore Files Preparing to Restore Files Since restoring files involves the use of one or more tapes on a tape device, you must complete the following three steps before issuing the RESTORE command: • Locate the necessary backup media. • Check for duplicate filenames. • Prepare the tape and the tape device. Locate the Necessary File or Files Search your tape library for the STORE tape(s) containing the files you want to restore.
Restoring Files Referencing Files in a RESTORE Command Referencing Files in a RESTORE Command You can name a single file to RESTORE, several individual files, or all the files from one or more STORE tapes. The group of files you want to RESTORE is called a fileset. In addition to naming many kinds of filesets, you can name file subsets to exclude from the RESTORE process. As a system supervisor (with OP capability) or a system manager (with SM capability), you can RESTORE any file in the system.
Restoring Files Restoring from Labeled Tapes Restoring from Labeled Tapes Restoring files from labeled tapes requires that the RESTORE command include a RESTORE file reference that was named previously in a file equation. For example: :FILE TAPE7=BACKUP.JAN29;DEV=TAPE;LABEL="VOL25",ANS,02/28/90 To recover all files in the volume set, you would then enter the following RESTORE command. :RESTORE *TAPE7;@.@.@;restoreoptions The system then requests that you mount the first volume of the volume set.
Restoring Files Restoring from Multiple Devices (RESTORESET) Restoring from Multiple Devices (RESTORESET) To RESTORE files from multiple devices, use the RESTORESET parameter in the RESTORE command to reference the multiple devices. Use of the RESTORESET parameter is explained in the following pages. Sequential Devices You can use sequential device configuration when you have a large set of files to RESTORE from a number of tapes and you want to speed up the process.
Restoring Files Restoring from Multiple Devices (RESTORESET) Enter the following RESTORE command to RESTORE files from a set of three sequential tape devices: :RESTORE ;@.@.@;RESTORESET=(*T,*T,*T) You can RESTORE files that were created using parallel devices or parallel device pools in a sequential configuration. For example, to RESTORE a set of reels that have been created using parallel device pools, you must use the following logical order to mount the reels on sequential devices: A1, A2....
Restoring Files Restoring Files from a Disk File NOTE Parallel RESTOREs can be performed only with tape sets that were created with a parallel STORE parameter. A sequential RESTORE can be used with any tape set. Parallel RESTORE allocates every subset of the tape set (for example, STORESET=(*T1),(*T2) creates two subsets) to distinct parallel devices or device pools, and expects a volume belonging to the subset to be mounted on its allocated device or device pool only.
Restoring Files Restoring Files from a Disk File creates disk backup files. Restoring From Multiple Disk Files If the backup to be restored contains more than one disk file, create only one file equation pointing to the first disk file. RESTORE will automatically open the subsequent disk files. Do not create any file equations for the other disk files. Be sure that all of the disk files in a backup are present at the time of the backup.
Restoring Files Restoring Files from a Disk File when storing files, restoring from serial disk files using the RESTORESET command is not supported. You need only to specify a file equation for the first disk file in the backup, or in a parallel set. RESTORE will automatically find and open any additional files in the backup that it needs. All other RESTORE options can be used when restoring from disk files. Verifying Disk Backups Disk files can also be specified for the VSTORE command.
Restoring Files Issuing a RESTORE Command Issuing a RESTORE Command To RESTORE the files from the tape to the system disk, you may optionally first issue a FILE command. The optional FILE command names the tape device and describes its type. If you do not use a FILE command, RESTORE creates a default filename.
Restoring Files Restoring Different Format Tapes Restoring Different Format Tapes RESTORE can restore files from any tape created by STORE. This includes tapes that were made using TurboSTORE only options, such as compression (COMPRESS), online (ONLINE), interleave (INTER), and parallel store sets (STORESET=). Even if you have not purchased a version of TurboSTORE, basic RESTORE can still copy the files off of the tape.
Restoring Files RESTORE Command Options RESTORE Command Options The following sections describe the RESTORE options. The options are: • SHOW • ONERR • CREATE • CREATOR • GID • KEEP, NOKEEP • OLDDATE, NEWDATE • DIRECTORY • LISTDIR • PROGRESS • FCRANGE • FILES • DEV • VOL, VOLCLASS, VOLSET • COPYACD, NOACD • TREE, NOTREE • PARTIALDB • STOREDIRECTORY • RESTORESET For a description of RESTORESET, see the "Restoring from Multiple Devices (RESTORESET)" section earlier in this chapter.
Restoring Files RESTORE Command Options • The filenames displayed in a RESTORE listing are those of the final destination filename, which may not be the same name the file has on the tape. Restore options such as GROUP, ACCOUNT, and LOCAL may affect what filename is printed. • For the LONG listing, RESTORE has an extra field, called OLDSP. This field will contain the old spoolfile name for any spool files that are being restored.
Restoring Files RESTORE Command Options files, are particularly likely to have experienced damage. NOTE This option is provided only for use in the event that a media read error is preventing you from recovering an important file that can not be recovered from any other backup or data source. This option should NOT be used on a regular basis for RESTORE. It should only be used after a normal RESTORE failed to recover a file or files due to a media read error.
Restoring Files RESTORE Command Options Restoring Files to Your Group and Account Regardless of the group, account, or creator from which files were stored, you can RESTORE files into your own group and account if you have read access to the files on the tape, or system manager (SM), system supervisor (OP), or account manager (AM) capability.
Restoring Files RESTORE Command Options NOTE The CREATOR option cannot be used when the LOCAL option is used. Changing a File's GID (GID) If you need to change a file's group ID, or GID, you may specify the GID option. The GID option takes an optional file group name, for example: ;GID=MANAGER If the file group name is specified, all files being restored will have their GID changed to the specified GID. If the file group name is not specified, the GID present on the backup will be preserved.
Restoring Files RESTORE Command Options To change the dates and times to the date you restored the files, use the NEWDATE option. For example: :FILE T;DEV=TAPE :RESTORE *T;@.@.@;NEWDATE You will probably want to use NEWDATE when you RESTORE archived files, so that you do not quickly archive them again. Restoring Directory Information (DIRECTORY) Use the DIRECTORY parameter to restore directory information from backup. To do this, you must have system supervisor (OP) or system manager (SM) capability.
Restoring Files RESTORE Command Options Figure 11-1. Sample RESTORE Command and Output :RESTORE *T;@.PUB.SYS;LISTDIR;SHOW TURBO-STORE/RESTORE VERSION C.55.05 (C) 1986 HEWLETT-PACKARD CO. WED, JUN 26, 1996, 5:07 PM B5152AA MPE/iX MEDIA DIRECTORY MEDIA NAME MEDIA VERSION MEDIA NUMBER : STORE/RESTORE-HP/3000.MPEXL : MPE/iX 08.50 FIXED ASCII : 1 MEDIA CREATION DATE WED, JUN 26, 1996, 4:46 PM STORE w@.pub.
Restoring Files RESTORE Command Options Restoring Files with Certain File Codes (FCRANGE) Use the FCRANGE parameter to restore only files with certain file codes. MPE/iX file codes distinguish different types of files. You can select up to eight file code ranges to restore. For example, files with codes 1100, 1101, and 1102 are HPWORD files. Files with codes 1152 and 1153 are SLATE files. To restore all HPWORD and SLATE files from a backup, enter: :FILE T;DEV=TAPE :RESTORE *T;@.@.
Restoring Files RESTORE Command Options Use the VOLSET parameter to reference a particular volume set. If there is no room in the volume set, RESTORE does not RESTORE the file. For example: :FILE T;DEV=TAPE :RESTORE *T;@.@.@;VOLSET=PRIVATE_VOL_A Use VOLCLASS to reference a particular volume class. If there is no room in the volume class you indicate, RESTORE restores the files to a volume within the volume set. If there is no room in the volume set, RESTORE does not RESTORE the files.
Restoring Files RESTORE Command Options resulting in a horizontal cut in the directory structure. Restoring Part of a Database (PARTIALDB) By default, RESTORE does not allow you to restore only part of a TurboIMAGE or ALLBASE/SQL database. The root file or DBE file and all dataset files must be specified, either by specifying just the root or DBE file, or by specifying a wildcard that includes all files in a database.
Restoring Files RESTORE Command Options files. This information is stored in the disk directory file and in a media directory located near the end of the backup media. It is much faster and more convenient for you to read the after image log information from the disk directory file. Otherwise, RESTORE needs to have you mount the backup media that contains the "final" media directory before it can restore any files.
Restoring Files Monitoring RESTORE Command Progress Monitoring RESTORE Command Progress After entering a RESTORE command, you see the following message at the console telling you that the RESTORE process has begun: TURBO-STORE/RESTORE VERSION (C) 1986 HEWLETT-PACKARD CO. WED, JUN 26, 1996, C.55.05 B5152AA 5:07 PM Responding to Tape Requests If your system is not configured to automatically assign devices, you see a tape request.
Restoring Files Monitoring RESTORE Command Progress Devices." 2. Locate the second tape, prepare it, and mount it. You do not have to issue another RESTORE command to respond to a tape request. The system automatically continues restoring files. If you leave the console while restoring files, other messages can cause mount requests to scroll off of the console screen. 3. Continue monitoring the RESTORE process. Mount new tapes as the system requests them.
Restoring Files When RESTORE is Complete When RESTORE is Complete If you specify the SHOW parameter, as RESTORE proceeds, it lists each file restored at yourterminal. For example: Figure 11-2. Listing Restored Files :RESTORE *T;FILE1.OPERATOR.SYS;SHOW WILL RESTORE 1 FILES; FILENAME GROUP FILE1 .OPERATOR ACCOUNT NUMBER OF FILES ON TAPE = VOLUME R'TIONS .
12 Using Backup Media to Recover from a System Failure This chapter describes how to recover from a major system failure. The sections in this chapter are: • Reloading Your System Configuration • Restoring Files from Partial Backup Tapes • Restoring Files from Full Backup Tapes In the event of a major system failure, you may need to reload your system from backup media.
Using Backup Media to Recover from a System Failure Reloading Your System Configuration Reloading Your System Configuration If your most recent system configuration files are from backups, do the following to retrieve your system configuration: 1. Install your latest system load backup. 2. Start the system. Only the system master volume on LDEV 1 is initialized. Other volumes must be initialized using VOLUTIL.
Using Backup Media to Recover from a System Failure Restoring Files from Partial Backup Tapes Restoring Files from Partial Backup Tapes Use the RESTORE command to copy system files, user files, and the file system directoryfrom your STORE backups to disk. To restore system and user files from your most recent backups, perform the following steps: 1. First gather all the units of backup media from your most recent backup. 2. Mount the backup(s) on the backup drive(s) and bring the drive(s) online. 3.
Using Backup Media to Recover from a System Failure Restoring Files from Full Backup Tapes Restoring Files from Full Backup Tapes If your most recent backups are from a partial backup, you need to reload your remaining files from your most recent full backup. To restore system and user files from your most recent full backups: 1. Gather all the backup media from your most recent full backup. 2. Mount the backup(s) on the backup devices and bring the devices online. 3.
13 Disaster Recovery This chapter discusses methods and planning for disaster recovery. The sections in this chapter are: • Recovery Facilities • Planning for Disaster Recovery • Testing Your Recovery System In this age of highly computerized business, some of your business information may be available only through your computer systems. Very often the information we rely on is only available through our computers.
Disaster Recovery Recovery Facilities Recovery Facilities The best way to prepare for an unpredictable disaster is to have a recovery facility available. A recovery facility contains a backup system onto which you can reload your files from backups. You can use the backup system for all of your information processing needs until your system is repaired or replaced. There are several types of recovery facilities. You should select the type that best meets the needs of your data center.
Disaster Recovery Recovery Facilities Commercial Backup Companies Commercial backup companies offer hot and cold backup sites identical to private hot and cold sites except that the site is owned and operated by a company in the disaster recovery business. A commercial backup site is less costly than a private backup site, but has the disadvantage that the clients of the backup company could potentially compete for backup resources at the same time.
Disaster Recovery Planning for Disaster Recovery Planning for Disaster Recovery Selecting a recovery facility is only part of a comprehensive disaster recovery program. You should prepare and implement a comprehensive disaster recovery plan. Your plan should detail resource requirements and procedures for each step in the recovery process. The Recovery Facility Locate your recovery facility close to the computer system you want to protect, but not in the same building or group of buildings.
Disaster Recovery Planning for Disaster Recovery Storage of Backup Tapes If you keep your regular backups at your Data Center, and the Data Center is destroyed by fire, the backups are also destroyed. Create a duplicate set of backups to keep at a suitable off site storage facility. In this way, you have a set easily accessible for routine problems and a set available in case of a major disaster.
Disaster Recovery Testing Your Recovery System Testing Your Recovery System When you initiate a disaster recovery service contract, use backups to test for system compatibility problems and bugs in your disaster recovery system. As time passes, perform periodic tests (for example, every quarter) to ensure that your systems remain compatible and your disaster recovery procedures work well. Also test your disaster recovery system whenever you change it.
A Error Messages This appendix describes how to interpret and apply STORE, RESTORE, and VSTORE error message information.
Error Messages Determining the Cause of STORE, RESTORE and VSTORE Errors Determining the Cause of STORE, RESTORE and VSTORE Errors Some STORE, RESTORE and VSTORE errors cause the program not to store, restore, or verify a particular file. Others cause the program to stop running. When STORE, RESTORE or VSTORE cannot transfer files that you named in your command, it lists the names of those files on your terminal as part of its standard progress listing.
Error Messages Determining the Cause of STORE, RESTORE and VSTORE Errors Cross-Reference> displays recommended recovery procedures. Table A-1. STOREJCW Values Value Cause Recovery Procedure 0 No errors. None. 1 Syntax error. Correct and reenter command. 2 Error in opening system resource allocation. Purge some files or perform disk space recovery. 3 Error in opening an indirect file.
Error Messages Using the STORE_ERROR Variable Using the STORE_ERROR Variable When STORE, RESTORE, or VSTORE aborts because of an error, the Command Interpreter (CI) variable STORE_ERROR is set to a non-zero value. This value can be used to look up more detailed cause and action error text in the MPE/iX Error Messages Manual Volumes I, II and III. If STORE exits successfully, then STORE_ERROR is set to 0.
B Command Syntax This appendix lists the STORE, RESTORE, and VSTORE command syntax. The parameters, options, and variables are described in Chapter 6, "STORE and TurboSTORE Options" and Chapter 11, "Restoring Files.
Command Syntax STORE Syntax STORE Syntax STORE [filesetlist][;storefile][;option[;...]] where option is [;SHOW[=showparmlist]] [ONERR[OR={REDO QUIT}] [{;DATE[S]<=accdate ;DATE[S]>=moddate}] [;PURGE] [;PROGRESS[=minutes]] [;DIRECTORY] [;FILES=maxfiles] [;TRANSPORT[=MPEXL]] [;COPYACD][;NOACD] [;FCRANGE=filecode/filecode[,...]] [;MAXTAPEBUF] [;NOTIFY] [;STATISTICS] [;ONVS=volumesetname[,volumesetname[,...]]] [;SPLITVS=split_setname[,split_setname]] [;RENAME] [;TREE][;NOTREE] [;INTER] [;STORESET=(device[,...
Command Syntax RESTORE Syntax RESTORE Syntax RESTORE [ restorefile][;filesetlist][;option[;...]] where option is [;SHOW[=showparmlist]] [;OWNER[OR]={QUIT SKIP FULL}] [;{LOCAL GROUP=groupname ACC[OUN]T=accountname}[,...]] [;CREATE[={GROUP ACCT CREATOR PATH}[,...]]] [;CREATOR[=username]] [;GID[=filegroupname]] [;{KEEP NOKEEP}] [;{OLDDATE NEWDATE}] [;DIRECTORY] [;LISTDIR] [;PROGRESS[=minutes]] [;FCRANGE=filecode/filecode[,...
Command Syntax VSTORE Syntax VSTORE Syntax VSTORE[vstorefile][;filesetlist][;option[;...]] where option is [;SHOW[=showparmlist]] [;ONERR[OR]={QUIT SKIP}] [;DIRECTORY] [;PROGRESS[=minutes]] [;COPYACD][;NOACD] [;TREE][;NOTREE] [;NODECOMPRESS] [;STOREDIR[ECTORY[=directoryname] [;PART[IAL]DB [;RESTORESET=(device[,...])] **TurboStore/iX II and TurboSTORE/iX 7x24 True-Online Backup options: [;RESTORESET=(device[,...])[,(device[,...])[,...]]] [;MOSET=(ldev[,...])[,(ldev[,...])[,...
C Transferring Optical STORE Backups onto Standard Tapes STORCOPY is a utility that allows you to transfer optical STORE backups onto standard tape backup, a less expensive backup medium. STORCOPY copies backups on magneto-optical devices to any other STORE backup media except magneto-optical. The STORCOPY program resides in PUB.SYS.
Transferring Optical STORE Backups onto Standard Tapes :STORCOPY Return :STORCOPY:FILE DDSTAPE;DEV=DDS Return :STORCOPY:FILE SYSLIST;DEV=LP Return :STORCOPY:STORCOPY COPYTOSET=(*DDSTAPE);NAME=MOBACK;SHOW=OFFLINE Return In the following example, a backup called MOBACK, which has five sets, is copied to three output devices. Two of the output devices are DDS drives on LDEV 7 and LDEV 8. The other output device is defined by file equation DDSTAPE.
Glossary absolute pathname A pathname that begins with the root directory, such as /SYS/PUB/TDP. See also pathname and relative pathname. access control definition (ACD) Security feature that controls access to files and directories. Consists of a list of access permissions and user specifications. (For example, R,W,X:@.PAYROLL gives all users in the PAYROLL account read, write, and execute access to the file or directory that is assigned this ACD.
concurrent backup devices A set of multiple, concurrently accessible backup devices to which you are able to store information simultaneously. consecutive backup devices A set of multiple backup devices used for a given tapeset to which you are able to store information sequentially. console See system console. current working directory The directory in which you are working and from which relative pathnames are resolved. See also directory and relative pathname. DAT Digital Audio Tape.
error messages Messages describing errors occurring during either an interactive session or a batch job. The messages are reported to the standard list device, which is usually a terminal (for a session) or a line printer (for a job). file An object that can be written to, read from, or both. A file has certain attributes including access permissions and file type. A group of related records that represents ASCII text (text files) or binary data (such as executable code).
indirect file A text file containing the parameters for a STORE or RESTORE command that you execute regularly. input The data to be processed, or the process of transferring data from external storage to the computer. input/output (I/O) The process of, or equipment used in, transmitting information to or from the computer. interleave A method of writing data to a disk device for the purpose of improving data access speed. I/O error A data transmission error between a computer and peripheral.
output Data transferred from internal to secondary (external) storage in a computer. Also, the process of transferring information from the computer to a peripheral device. parallel devices A set of backup devices to which you are able to store information simultaneously. parameter A value in a list of values that is passed to a procedure. The parameter is used on calculations or operations in the procedure. parent directory A directory that contains other directories.
shadow logging A method of saving the "before" images of file blocks when the records in the file block are modified during online backup. The before images are stored on tape and are used by RESTORE to reconstruct the original contents of the file. slash (/) Another name for the root directory. See also root directory. storage device A device (such as a disk pack, a disk cartridge, a flexible disk, magnetic tape, or cartridge tape), onto which data can be stored and subsequently retrieved.
utility program An operating system program that performs specific functions such as file copying, sorting and merging, memory dump analysis, or monitoring available disk space. volume A volume is one disk. Each volume is a member of a volume set and contains a volume label, a label table, and a free space map. volume class Volume classes are used for the allocation and restriction of disk space.
Index Symbols $NULL, 52 $STDIN, 151 $STDLIST, 151 Numerics 7x24 true-online backup, 25, 114, 119 A aborting sessions, 64 ABORTJOB command, 64 account, 171 ACCOUNT parameter,RESTORE command, 172 account structure, 92 ALLBASE/SQL databases,storing, 73 allocating a device, 135 allowing users on system, 146 archiving files, 91 ASK parameter ONLINE option, 128 assigning an LDEV number, 135, 137 attach phase, 25, 115, 116 automatic volume recognition, 75 automatically assigning devices, 46, 47, 135, 139 AVR, 75
Index state change date, 90 STORE command, 90 default group, SYSGEN utility, 150 DEV parameter STORE command, 176, 177 device class, 46 device pool, 39, 48, 49 device, restoring to specific, 176 directory information, restoring, 174 DIRECTORY parameter RESTORE command, 174, 184 STORE command, 92 VSTORE command, 143 disaster recovery, 187, 192 disaster recovery plan, 21 disk read errors, 89 displaying file dates, 86 file security information, 87 progress messages, 92, 175 tape information, 174 duplicate bac
Index restoring files, 161, 170 labeled volumes, 75 last access date, 173 LDEV, 36 LIMIT command, 59, 146 LISTDIR parameter RESTORE command, 174 LISTF command, 159 listing the files restored, 169 listing the files stored, 83, 87 LOCAL parameter RESTORE command, 172, 174 VSTORE command, 143 log files, 117 log handler, 25, 115, 116 logging off users, 57 logical device (LDEV) number, 36, 37, 46, 77, 135, 137, 176, 180 LOGVOLSET option TurboSTORE/iX 7x24 True-Online Backup command, 117 long file display, 83,
Index parallel device pools, 39, 51, 77, 112 preparing backups, 45 restoring devices, 163 parallel devices, 39, 49, 50, 77, 78, 89 maximum number of, 50 restoring files, 163, 164 parallel disk files restoring files, 165 partial system backup, 30, 90, 112, 183 PARTIALDB option, 131 restoring part of a database, 178 STORE command, 109 placeholder, 39, 49, 66 restoring files, 162, 167 preparing backup media, 40 preparing storage devices, 35 LDEV number, 36 multiple-device backup, 35 multiple-device planning c
Index restoring directory information, 174 part of a database, 178 using a disk directory file, 178 restoring files, 20 7x24 true-online backups, 132 account, 171 automatically assigning devices, 167 checking for duplicate filenames, 159 creator, 171 described, 157 error recovery, 170 FILE command, 162 from a disk file, 164 from labeled tapes, 161 from multiple disk files, 165 from parallel device pools, 163 from parallel devices, 163 from parallel disk files, 165 from sequential devices, 162 from single d
Index DEV parameter, 176, 177 DIRECTORY parameter, 92 FCRANGE parameter, 96 FILES= parameter, 96 FULLDB option, 109 INTER parameter, 112 MAXTAPEBUF parameter, 96 monitoring progress, 77 NOSTOREDIRECTORY, 110 NOTIFY parameter, 97 ONERROR option, 78, 89 ONLINE option, 116 ONVS parameter, 92, 103 options, 81 options (parameters), 65 PARTIALDB option, 109 PROGRESS parameter, 79, 92 PURGE parameter, 91 referencing files, 66, 70 RESTORESET parameter, 70 SHOW parameter, 83, 87, 142 SHOW=DATES option, 86 SHOW=LONG
Index T TAPE command, SYSGEN utility, 152 tape error recovery, 170 tape information, displaying, 174 tape label, 40 tape request, 180 tapes labeled, 24 unlabeled, 24 task roadmap, 26 TELL command, 58, 138 testing recovery system, 192 transport mode, 84 TRANSPORT parameter backup, restoring to MPE V/E, 96 RESTORE command, 176 STORE command, 24, 31, 37, 84, 93 true-online backup, 25 TurboIMAGE databases,storing, 73 TurboSTORE/iX 7x24 True-Online Backup described, 119 LOGVOLSET option, 117 ONLINE option, 114,
