900 Series HP 3000 Computer Systems STORE and TurboSTORE/iX Products Manual ABCDE HP Part No. B5151-90001 Printed in U.S.A.
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 tness 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.
Printing History The following table lists the printings of this document, together with the respective release dates for each edition. The software version indicates the version of the software product at the time this document was issued. Many product releases do not require changes to the document. Therefore, do not expect a one-to-one correspondence between product releases and document editions. Edition Date Software Version First Edition July 1996 C.55.
iv
This book, the STORE and TurboSTORE/iX Products Manual (B5151-90001), describes how to use the Fundamental Operating System (FOS) STORE product and the following TurboSTORE products: Product Description Product Number FOS STORE B5151AA TurboSTORE/iX II B5152AA TurboSTORE/iX 7x24 True-Online Backup Preface Note The product structure of the STORE and TurboSTORE/iX products has changed for MPE/iX Release 5.5.
This book is divided into 13 chapters and 3 appendices as follows: Chapter 1 Introduction, provides basic backup concepts and lists hardware requirements. Chapter 2 Managing Backups and Backup Media, describes planning, scheduling, and maintaining backups. Chapter 3 Preparing Storage Devices, provides procedures for using backup devices. Chapter 4 Preparing the System, provides procedures for notifying the users of the backup process.
product structure including information on the new TurboSTORE/iX 7x24 True-Online Backup product, and to show the changes made to the existing functionality. The manual changes include the following: Chapter 1, \Introduction," was rewritten to include the restructuring of the TurboSTORE products in the \Feature Comparisons" section, and to modify the \Hardware Requirements" section.
\Responding to a NO WRITE RING Message" \Mounting Additional Tapes" The following section was added: \Handling Media Errors" The following section was deleted: \REDO Tape Errors" In Chapter 6, \STORE and TurboSTORE Command Options," the introductory information and the following sections were modi ed: \Listing the Files Stored (SHOW)" - the symbol information in the \Displaying TurboSTORE/iX 7x24 True-Online Backup Information" section was modi ed.
\RESTORE Command Options" - the options, ONERROR, PROGRESS, STOREDIR and PARTIALDB were added to the list. \Selecting a RESTORE Error Recovery Method (ONERROR)" most of the information after the bullets has been modi ed.
Conventions UPPERCASE In a syntax statement, commands and keywords are shown in uppercase characters. The characters must be entered in the order shown; however, you can enter the characters in either uppercase or lowercase.
Conventions (continued) [ ... ] In a syntax statement, horizontal ellipses enclosed in brackets indicate that you can repeatedly select the element(s) that appear within the immediately preceding pair of brackets or braces. In the example below, you can select parameter zero or more times. Each instance of parameter must be preceded by a comma: [,parameter][...
Contents 1. Introduction System Backups . . . . . . . . . . . . Product Structure and Feature Comparisons Hardware Requirements . . . . . . . . . Backup Media . . . . . . . . . . . . . Backup Devices . . . . . . . . . . . . Disaster Recovery Plans . . . . . . . . . Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 1-2 1-4 1-6 1-6 1-7 1-7 2. Managing Backups and Backup Media Why Perform Backups? . . . . . . . . . . Determining Your Backup Strategy . . .
Determining the Number of Disks Needed . Specifying the Magneto-Optical Device . . Naming the Backup . . . . . . . . . . . Storing to a Single Magneto-Optical Device Storing to Multiple Magneto-Optical Devices Storing to Disk Files . . . . . . . . . . . 4. Preparing the System 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 . . .
6. STORE and TurboSTORE/iX Command Options STORE Options . . . . . . . . . . . . . . . . Listing the Files Stored (SHOW) . . . . . . . . Using a Long or Short File Display . . . . . . Displaying File Dates . . . . . . . . . . . . Displaying File Security Information . . . . . Displaying Names Only . . . . . . . . . . . Forcing the HFS Format . . . . . . . . . . Displaying TurboSTORE/iX 7x24 True-Online Backup Information . . . . . . . . . . .
Creating a Disk Directory File (STOREDIRECTORY and NOSTOREDIRECTORY) . . . . . . . . . Storing Files in Interleave Format (INTER) . . . TurboSTORE/iX II Options . . . . . . . . . . . Compressing Data (COMPRESS) . . . . . . . Storing to Magneto-Optical Devices (MOSET and NAME) . . . . . . . . . . . . . . . . . TurboSTORE/iX 7x24 True-Online Backup Options Storing Files Online (ONLINE) . . . . . . . . Performing an Online Backup . . . . . . . . Specifying Where to Place Log Files (LOGVOLSET) 7.
8. Handling Media Requests 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9. When STORE is Complete Checking File Listings for Errors . . . . . . . . Verifying That STORE Files Are Error Free Using VSTORE . . . . . . . . . . . .
Contents-6 Selecting a RESTORE Error Recovery Method (ONERROR) . . . . . . . . . . . . . . . Restoring Files to the Correct Group, Account, and Creator (CREATE) . . . . . . . . . . . . Creating Groups, Accounts, and Creators . . . Restoring Files to Your Group and Account . . Restoring a File to a Di erent Group, Account, or Creator . . . . . . . . . . . . . . . . Changing a File's GID (GID) . . . . . . . . . Overwriting or Retaining Disk Files (KEEP, NOKEEP) . . . . . . . . . . . . . . . .
System Compatibility . . . . . . . . . Disaster Noti cation and Response Time Storage of Backup Tapes . . . . . . . Testing Your Recovery System . . . . . . . . . . . . . . . . . . . . . . 13-3 13-4 13-4 13-4 A. Error Messages Determining the Cause of STORE, RESTORE and VSTORE Errors . . . . . . . . . . . . . Viewing the Value of STOREJCW . . . . . . Determining the Cause of an Error . . . . . . Using the STORE ERROR Variable . . . . . . . . . . A-1 A-2 A-2 A-4 B. Command Syntax STORE Syntax . . .
Figures 2-1. 3-1. 3-2. 3-3. 3-4. 3-5. 3-6. 3-7. 3-8. 3-9. 3-10. 3-11. 4-1. 6-1. 6-2. 6-3. 6-4. 6-5. 6-6. 6-7. 6-8. 6-9. 7-1. 7-2. 8-1. 9-1. 9-2. 9-3. 10-1. 10-2. 11-1. 11-2. Contents-8 Sample Backup . . . . . . . . . . . . . . . Multiple-Device Planning Chart . . . . . . . . A Correctly Labeled Tape . . . . . . . . . . . Preparing Tapes for a Single Device . . . . . . . Preparing Tapes for Parallel Devices . . . . . . Preparing Tapes for Sequential Devices . . . . .
Tables 1-1. 1-2. 2-1. 6-1. 6-2. 6-3. A-1. Product Structure Change . . . . . Feature Comparison . . . . . . . Task Roadmap . . . . . . . . . . Maximum Tape Record Sizes . . . Required Capabilities for RENAME Creator File Translations . . . . . STOREJCW Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 Introduction This manual presents important information for system managers and operators on all aspects of storing les for backup, archive, or transfer. It describes how to use the STORE command and the TurboSTORE/iX products to save les and restore them back to the system. It also describes important methods for safeguarding the information in your system. More speci cally, the manual describes how to do the following: Maintain your backup media and manage backup devices. Plan and manage 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 les to be lost. If your system experiences a failure, you can reload that information from your backup media.
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 5.5. Table 1-1. Product Structure Change 5.0 Product Structure 5.
Table 1-2.
systems, therefore, will see an even greater increase in performance when using parallel backups. A general rule is to use one less parallel device than there are processors. For a four-way MP system, this would mean three parallel devices. When using the TurboSTORE/iX II or TurboSTORE/iX 7x24 True-Online Backup products, the following Hewlett-Packard magneto-optical (MO) devices are supported as backup devices: C1700T C1708T C1100B Note After MPE/iX Release 5.
Backup Media Backup media can include reel-to-reel magnetic tapes, DDS tapes, 3480 cartridges, magneto-optical disks, and disk les. Backup media provides an economical way to maintain duplicates of important les on your system. The process of copying a le to backup media is called storing the le. The process of copying a le from backup media is called restoring the le. As a system administrator/operator, you frequently STORE and RESTORE les.
Disaster Recovery Plans Related Documentation 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, ood, earthquake, and sabotage, can still threaten both your backup media and your system hardware.
2 Managing Backups and Backup Media This chapter describes the purpose and process of performing regular backups of your les and systems. The sections in this chapter are: Why Perform Backups? TurboSTORE Backup Features STORE and RESTORE Process What Should You Backup? Scheduling Backups Preparing to STORE Files Using Unlabeled vs Labeled Media Maintaining a Backup Library Why Perform Backups? Selecting backup methods and scheduling regular backups are important aspects of a system administrator's job.
Determining Your Backup Strategy The TurboSTORE programs allow you to store les to a single device or to multiple devices. The best way to use your backup devices depends upon the characteristics of the les that you are storing, your needs for compatibility with other versions of MPE, and your system con guration. The characteristics of the set of les help determine choices (or options) for storing them.
Labeled tapes can be used with a single device and parallel devices, but not with sequential devices. Unlabeled tapes can be used with single, parallel, and sequential devices. Magneto-optical devices cannot be used to perform labeled backups. 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.
the state of all les being backed up is synchronized. When the backup is restored, all les are restored to the state they were in at the time of the sync point. TurboSTORE also synchronizes any TurboIMAGE or ALLBASE/SQL databases being stored, ensuring that consistent copies of the databases are written to the backup. See Chapter 7 for more information on using the new TurboSTORE/iX 7x24 True-Online Backup feature.
1. The user gives you empty backup media onto which to store disk les, or the user gives you the STORE media from which to restore les to disk. 2. You mount the media and prepare the device. 3. The user enters the FILE and STORE or RESTORE commands. 4. You check the console for a media request. 5. If the system does not automatically answer the media request, you must reply to it. 6. When the process is complete, remove the media and return it to the user. 7.
Table 2-1. Task Roadmap (continued) Chapter Description Tasks De ne all backup and recovery procedures Create one Translate requirements or more job streams into TurboSTORE commands X 5 \Storing Files" - Procedures for using STORE to store les and backup media. 6 \STORE and TurboSTORE Command Options" - STORE and TurboSTORE option descriptions. 7 \TurboSTORE/iX 7x24 True-Online Backup" Describes the new 7x24 true-online backup product.
What Should You Backup? To completely back up your system, you should copy three types of information: User and system les. User les 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 les can be considered the most important element within your computer system.
Scheduling Backups Full and Partial Backups There are two important considerations when planning a backup schedule: Plan full and partial backups to e ciently duplicate the most recent system information. Schedule a regular time for performing backups. There are two ways to perform a system backup. A full backup copies all les stored in your system whether or not any of the information in them has changed since the last backup.
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. Full backups take more time and more media than partial backups.
Maintaining a Backup Library Maintaining a Large Stock Of Backup Media 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 nd the backup media needed to restore the system in the event of a failure. Your actual backup media.
Storage of Backup Media Backup media may be the only copy of current or previous information stored from your system. When you need to restore information from backup media, you should be able to easily nd the item you need. Your library enables you to maintain complete copies of your system's data, and an easy method for locating the data you want to recover.
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 Preparing Magneto-Optical Media and Devices Preparation Process The following is a brief list of the preparation steps. 1. You must rst determine what type of device(s) to use for your backup. Most of this section deals with storing to magnetic tape or DDS devices.
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) lls, additional les 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. Assign each device a position in the backup, identifying each device by its logical device (LDEV) number.
Figure 3-1. Multiple-Device Planning Chart Selecting the Backup Method The best way to use your backup devices depends upon the characteristics of the les that you are storing, your needs for compatibility with other versions of MPE, and your system con guration. The characteristics of the set of les help determine choices (or options) for storing them. Generally speaking, the more les being stored, the more it is to your advantage to use multiple devices.
multiple-device backup method to use. Use the following guidelines to select a method: Which and How Many Backup Devices Do You Have? Which devices you may use for a multiple-device backup are described in this chapter. Obviously, to use sequential or parallel devices, you must have at least two backup devices. If you have two or three devices, you may use either parallel or sequential devices. If you have three or more devices, you may use two or more parallel device pools.
Assign unique lenames based on each device's position in the backup. For example, if you plan to use four parallel devices, you might issue the following set of FILE commands: :FILE :FILE :FILE :FILE BACKA;DEV=7 BACKB;DEV=8 BACKC;DEV=9 BACKD;DEV=11 Label sequential devices in order.
:FILE SEQ3;DEV=9 :STORE @.@.@;;STORESET=(*SEQ1,*SEQ2,*SEQ3) The above STORE command copies all system and user les to three sequential devices. The parentheses surrounding backreferenced le names group the devices into a device pool. Note You do not backreference the lename of a backup device immediately after the name(s) of the le(s) you are storing when you use the STORESET parameter. Rather, you must use a placeholder for the missing parameter normally supplied when using a single backup device.
:FILE PPB2;DEV=11 :STORE @.OPERATOR.SYS;;STORESET=(*PPA1,*PPA2),(*PPB1,*PPB2) If you gave the backup devices a single lename such as: :FILE T;DEV=TAPE enter the following STORE command to copy les to a set of parallel device pools: :STORE @.@.@;;STORESET=(*T,*T),(*T,*T) Note Up to 16 parallel devices may be speci ed for one backup. With a serial device pool, up to 8 devices may be speci ed.
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. Label each piece of media with both the reel Parallel or Parallel Pools number and the set number. Label the rst media of each parallel device or device pool as Volume 1 of "x", Set 1 of "y" where \x" is the total number of media allocated to the particular parallel set, and \y" is the total number of parallel sets.
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.
Parallel If you are using parallel devices, stack all of your backups, label side up, in order with the lowest number on top, near the corresponding device. For example, place all the backups with numbers ending with Set1 near your rst parallel device. Put media Reel1 Set1 on top of the stack. Figure 3-4 shows how to prepare backup medias for parallel devices. Figure 3-4.
6. Divide your media among the devices. Sequential 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 shows an example. Figure 3-5.
Parallel Pool 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 rst 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 shows media prepared for storing les to parallel device pools. Figure 3-6.
Preparing Tape and DDS Devices Prepare your backup devices by mounting the rst 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. (The LDEV number is 8 in the example above.
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. If you are using labeled tapes for your backup, you may or may not have to respond to console requests, depending on how your system is con gured. Refer to the \Storing to Labeled Tapes" section in Chapter 5 for more information on using labeled tapes.
Parallel devices. Parallel device pools. Using Tape Devices Sequentially With sequential backup devices, when the rst backup on the rst backup device is lled, it immediately begins writing les to a second backup on the second backup device and the rst backup rewinds. When the rst backup is rewound, you can unload it and prepare the drive with a new backup. You do not lose time while the rst backup is rewinding nor while you are loading a new backup.
: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 les to three sequential devices. The parentheses surrounding backreferenced lenames group the devices into a device pool. Note You do not backreference the lename of a backup device immediately after the name(s) of the le(s) you are storing when you use the STORESET parameter.
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 con guration 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.
:FILE T;DEV=TAPE enter the following STORE command to copy les 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 lename within parentheses. Use commas to separate devices. Using Parallel Device Pools Parallel device pools are multiple sets of sequential devices used in parallel.
: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 lename such as: :FILE T;DEV=TAPE enter the following STORE command to copy les to a set of parallel device pools: :STORE @.@.@;;STORESET=(*T,*T),(*T,*T) Using $NULL as a STORE Device The devices speci ed for a backup can also refer to $NULL. This essentially does the backup to the \bit bucket"|no data is stored to any backup media.
Although the initial console device request will appear on the console of the remote system, all further STORE console messages will be sent to the local system's console. These messages will also be sent to the backup's $STDLIST. Note Remote backup is currently only supported for unlabeled backups. Labeled backups cannot be accessed remotely by either STORE or CMSTORE. Also, magneto-optical devices cannot be used remotely. Any backups to MO devices must be done to a local device.
Determining the Number of Disks Needed You should compute the number of disks needed for a backup by dividing the total number of sectors to be stored by the capacity of one MO disk surface. For example, each single density optical disk surface can hold approximately 290 MBytes of uncompressed data (depending on the type of data and assuming there are no bad sectors on the disk). By comparison, 2400 feet of 1/2 inch backup holds approximately 140 MBytes of data.
Specifying the Magneto-Optical Device When storing to a magneto-optical device, you do not use le equations as you do when using backup drives. Nor do you use the STORESET parameter to backreference the device. Instead, you specify the devices to be used for a MO backup through the MOSET parameter of the STORE command. Specify the LDEV number of the magneto-optical device as a parameter to MOSET.
Storing to Multiple Magneto-Optical Devices Multiple magneto-optical devices can be used in parallel (sequential use is not supported) for backup by specifying each magneto-optical device drive with the MOSET parameter. For example, to use LDEV 102 and 103 in parallel, the MOSET entry would be: ;MOSET=(102),(103) For example, to use the rst available media in parallel, the MOSET entry is: ;MOSET=(MO),(MO) Do not mix alphanumeric with numeric allocation requests.
d :LISTFILE MYBACKUP,2 FILENAME CODE c a MYBACKUP STORE ------------LOGICAL RECORD----------- ----SPACE---SIZE TYP EOF LIMIT R/B SECTORS #X MX 128W FB 8736 16776959 1 10272 8 * b Although it is not recommended, you can create the target disk les before starting the backup. Only normal, xed, or unde ned length record les can be speci ed. STORE opens the le for user-mapped write access, so any restrictions that apply for user-mapped access apply for store disk les.
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.
begin. It is also a good idea to announce backups in the WELCOME message. To prepare for a backup, follow the steps below. 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 nish their work and to log o 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.
users from gaining access to the system during a system backup. Enter: :LIMIT 0,0 :JOBFENCE 14 To check the new job/sessions limits and the system jobfence, enter: :SHOWJOB STATUS The last line of the message on your console should now exactly match the example shown below: JOBFENCE= 14; JLIMIT= 0; SLIMIT= 0 If you see anything else, you made a mistake entering the LIMIT and JOBFENCE commands. Follow the instructions again.
Note For an online backup, send these messages to users. However, you could change the text of the message to let users know that they can log on after a certain amount of time has passed. The amount of time users have to remain logged o the system depends on how much data is being stored. It can range anywhere from 1 to 30 minutes. For a 7x24 true-online backup, you can send a warning message to users notifying them that the true-online backup is about to begin.
If you see a message stating NO SUCH JOBS, or if the list contains no executing jobs (check the STATE column for EXEC), skip to the \Send Another Warning" step below. If any jobs are in the EXEC state, you should temporarily stop them. To do so, use the job numbers that appear in the rst column on your screen with the BREAKJOB command, as follows: :BREAKJOB #Jnnn Repeat the BREAKJOB command for each executing job in the list.
Aborting Any Remaining Sessions Check one more time whether all sessions (except your own) have logged o 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 o .
5 Storing Files This chapter contains complete information on how to use the STORE command to store les to backup media. STORE can be used to back up a single le, all user, system, and system directory les (that is, a full system backup), or any number of les 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 les in the STORE command 2. Using indirect les 3.
increase performance when you have a large set of les to store, for example, when you are performing a full system backup. See Chapter 3 for information on preparing backup devices. Caution Do not use the STORE or RESTORE programs to transfer any of the les that originally came from your system load tape (SLT) from LDEV 1 to a disk other than LDEV 1. These les reside in the SYS account and can be displayed by entering the SHOW command in the SY con gurator of the SYSGEN utility.
Filesets A leset speci es a group of les to be stored. It can also include an exclusion set, which is a group of les to be excluded from the STORE operation. The syntax for a leset is: 2 2 filestostore - filestoexclude -. . . . 33 Where filestore represents a leset and filestoexclude represents an exclusion leset. The filestostore and filestoexclude are speci ed using the same syntax. Any le that matches lestostore will be stored, unless the le also matches a lestoexclude.
Each of the components dir lev i and ledesig can have a maximum of 255 characters with the full pathname being restricted to 1023 characters. Each of the components dir lev i and ledesig can use the following characters: Letters a to z Letters A to Z Digits 0 to 9 Special characters - . For HFS syntax, the lowercase letters are distinct from the uppercase letters (no upshifting). Names in MPE syntax are upshifted. Using Wildcard Characters Use wildcard characters to select multiple les to store.
Examples of using character sets are: [A-C]@ All les that begin with the letters A, B, or C. myset[e-g1] All les that begin with the name myset and end in E, F, or G, or 1. myset[d-e1-6] All les that begin with the name myset and end in D or E, or 1, 2, 3, 4, 5, or 6. You specify up to a maximum of sixteen characters for each character set, and you cannot nest brackets. Do not use character sets with the TRANSPORT option. A character set speci es a range for only one ASCII character.
file.group.acct file.group file ./file One particular le in one particular group in one particular account. One particular le in one particular group in the logon account. One particular le in the CWD. All les (MPE and HFS) in one particular group in one particular account. ?@.group.acct All MPE-named les in one particular group in one particular account. @.group All the les (MPE and HFS) in one particular /LOGONACCT/GROUP/ group in the logon account. ?@.
:STORE ./dir3/@;*T Store all HFS les that start with lower case letters in the CWD: :STORE ./[a-z]@;*T Exclude some les from a leset: Store everything on the system except les in PUB.SYS, MPE format: :STORE @.@.@-@.PUB.SYS;*T HFS format: :STORE / - /SYS/PUB/@;*T Store everything on the system except the 3000devs account: :STORE @.@.@ - /3000devs;*T Store only the HFS-named les on the system: :STORE / - @.@.@;*T Store only the MPE-named les on the system: :STORE ?@.@.
Using an indirect le can save time, especially if your STORE command is long or contains information that is di cult to remember. You enter the STORE les and parameters in a text le: @.@.@;DIRECTORY;ONVS=MPEXL_SYSTEM_VOLUME_SET,NV1 Give the text le a name that is easy to remember, and reference the text le name in a STORE command. The following STORE command references the le BACKUP as an indirect le: :STORE ^BACKUP;*T The caret (^) is used prior to the lename to tell STORE that it is an indirect le.
should be speci ed between the leset and its associated negative lesets. As when specifying negative lesets on the command line, there is no limit to the number of negative lesets that can be speci ed. Do not specify any continuation characters, such as \,", \;", \+", or \&", at the end of an indirect le line. If you need to specify more le sets than can t on a line, just continue specifying them on additional lines. Do not start a line with the \," character.
Storing Symbolic Links and Device Links As of Release 5.0 and later, MPE/iX supports symbolic links and device links. When storing symbolic links, TurboSTORE only follows the link if it is not the last component of an HFS lename. If the symbolic link is the last component of an HFS lename, the only the link, or \container" will be stored. When storing device links, only the link is stored.
If any of the dataset les are speci ed in addition to the root le, no warning will be displayed but the individual dataset les will be counted as redundantly speci ed les. If you are using the TurboSTORE/iX 7x24 true-online backup ONLINE option, then all TurboIMAGE databases fully speci ed, either by wildcards or by specifying the root le, are quiesced at the online backup sync point. If you want to back up part of an IMAGE database, you can specify the PARTIALDB option.
Storing Non-HP Databases When storing databases other than than TurboIMAGE/SQL and ALLBASE/SQL databases, STORE does not enforce any root le/data set rules. You should continue to store other databases using the same procedures used prior to MPE/iX Release 5.5. 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.
Using Unlabeled Volumes If you plan to create labeled volumes using backups that are not labeled, the preceding procedure di ers slightly. Use the FILE equation and STORE command as you would with a labeled volume. For example: :FILE TAPE7=BACKUP.JAN29;DEV=TAPE;LABEL="VOL25",ANS,02/28/90 :STORE @.@.
Responding to Tape Requests When your backup devices are not con gured to be automatically allocated, the system answers your STORE command with one or more backup requests. Refer to Chapter 8, \Handling Media Requests," for more information. If you have previously issued a FILE command that included the backup device's LDEV number, the backup request asks you to con rm that number.
If you specify REDO and the STORE command encounters a backup I/O error on any device, STORE sends a message to your terminal (or the le or device to which you have assigned the le SYSLIST). This message indicates where the error occurred. For example, STORESET=(*T1,*T2,*T3) is requested and a backup error occurs on the device referenced by *T2 while it is creating reel 2. STORE rewinds the reel to the load point, marks the reel as bad, and asks you to mount another reel.
physical label of the media to indicate that it encountered a write error while storing to it. Responding to a NO WRITE RING Message Reel backups require you to insert a write ring into the reel in order to store les onto the backup. You see a NO WRITE RING message when you attempt to store les to a reel-to-reel backup and neglect to insert a write ring into the groove on the back of the backup reel.
1. Unload the rst piece of media and stack it, label side down, on top of any media previously written on this drive during the current STORE operation. Remove the write ring. 2. Select the next piece of media from the prepared stack near the piece of media device. If there are no more media prepared, prepare a new piece of media following the instructions in \Preparing Your Backup Media", in Chapter 3, \Preparing Storage Devices." 3. Mount the new piece of media. 4. Continue monitoring the backup process.
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.
Stores les located on mirrored volume sets RENAME Changes the name of original les on the system or the target les on the backup media TREE, NOTREE Speci es if les should be scanned recursively to include all les in a hierarchical directory INTER Speci es more than one le at a time should be written, or interleave on the backup media. STORESET Allows you to specify multiple backup devices. PARTIALDB In a 7x24 true-online backup environment, allows you to back up part of a database leset.
TurboSTORE/iX 7x24 True-Online Backup Options ONLINE LOGVOLSET Option that stores les while they are open. Option that speci es which volume set to use for log les. Note that all options available in FOS are also available in TurboSTORE/iX II and TurboSTORE/iX 7x24 True-Online Backup. All options available in TurboSTORE/iX II are also available in TurboSTORE/iX 7x24 True-Online Backup. TurboSTORE/iX II provides you with certain special features not available with the standard STORE program.
To redirect the OFFLINE listing to another le or device, issue the following FILE command, it will send a copy of the STORE listing to the disk le SHOWOFFL: :FILE OFFLINE=SHOWOFFL;DEV=DISC To generate a store listing to the terminal as well as to a disk le, enter the previous FILE command followed by the STORE command: :STORE @.OPERATOR.SYS;*t;SHOW=OFFLINE Using a Long or Short File Display The STORE command gives you two options for displaying additional information about the les stored.
d c Figure 6-1 illustrates a short le display in MPE format using the above example. FILENAME GROUP ACCOUNT VOLUME RESTRICTIONS SECTORS CODE MEDIA FILE1 FILE2 FILE3 DISC DISC DISC .PUB .TEST .PUB .TEST .PUB .TEST :C :C :C 1104 0 32 a 1 1 1 b Figure 6-1. Short File Display (MPE Format) This example uses the same leset as the rst example, except that it is speci ed in HFS syntax.
A long le display contains the same information as a short le display plus each le's ending media number, record size, blocking factor, maximum number of extents allowed, end-of- le, and le record limit. Once again, there are two formats for the long listing|MPE and HFS. The HFS format contains the same information as the MPE format, except that the variable-length HFS lename is at the end of the line. It will be wrapped in the same was as the short listing if the lename length exceeds the line length.
Displaying File Dates To display each le's creation date, last access date, and last modi cation date for the les stored, use the SHOW=DATES option. For example: :FILE T;DEV=TAPE :STORE @.PUB.DOC;*T;SHOW=DATES d Figure 6-6 illustrates a le listing created from the above example. a FILENAME GROUP ACCOUNT VOLUME RESTRICTIONS SECTORS CODE MEDIA CREATED ACCESSED MODIFIED FILE1 .PUB .TEST DISC 1/12/1994 1/12/1994 1/12/1994 :C 1104 1 FILE2 .PUB .
Displaying File Security Information To display le security information for the les stored, use the SHOW=SECURITY option. The listing includes the le creator's user and account name, the security matrix, and a ag indicating the presence or absence of an ACD. The HFS format displays the same security information. For example: :FILE T;DEV=TAPE :STORE @.PUB.TEST;*T;SHOW=SECURITY d Figure 6-8 illustrates a le listing with security information from the above example.
Forcing the HFS Format If SHOW=PATH is speci ed, the output STORE listing will be in HFS format, even if no HFS syntax les are being stored. You may want to use this so that all of your listings appear in the same format. Displaying TurboSTORE/iX 7x24 True-Online Backup Information When creating backups using the ONLINE=START or ONLINE=END options of the TurboSTORE/iX 7x24 True-Online Backup product, additional information is shown in the STORE listing.
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 le system directory. An error opening a backup device or an indirect le. An indirect le is a text le containing STORE commands and options.
where LDEV # is the device referenced by *T2. This means that the store error recovery occurs on the same device where the error occurred. The operator sees the following messages on the console: STORE IS MARKING REEL BAD ON LDEV # MOUNT MEDIA # OF SET # FOR STORE ON LDEV # If an optical disk write error is encountered, STORE displays the same error messages that it would display for tape backup devices. Optical Disk Errors.
date displayed with the LISTFILE lename ,3 command. See the note below for information on displaying the state changes.) The DATE parameter enables you to do, among other things, a partial system backup. For example, suppose a full system backup was performed on September 30, 1993. The following STORE command would copy all system and user les modi ed since that date: :FILE T;DEV=TAPE :STORE @.@.
SYS account that have not been accessed since June 10, 1993. You may want to use this form of the DATE parameter with the PURGE parameter to remove out-of-date les from your system. Refer to the next section. Removing Stored Files from the System: Archiving Files (PURGE) If your system contains infrequently used or out-of-date les, you can store them onto backup and permanently remove them from the system disks at the same time.
System Directory Backup (DIRECTORY) The system directory keeps track of the accounts, groups, users, and les in your system. Nonsystem volume set directories keep track of the contents of nonsystem volumes. Directory information can be stored when you back up system or nonsystem volumes. Storing directory information helps you rebuild your system from backups should it unexpectedly lose information. To store system directory information, use the DIRECTORY parameter.
Storing Files in Compatible Formats (TRANSPORT) The TRANSPORT option stores les on media that is compatible with: MPE V/E systems (TRANSPORT) Pre-POSIX systems (TRANSPORT=MPEXL) Creating MPE V/E Compatible STORE Tapes Use the TRANSPORT parameter of STORE to create STORE backups that are compatible with MPE V/E. For example, to store all of the les in the PERSONEL account onto an MPE V/E compatible backup, enter: :FILE T;DEV=TAPE :STORE @.@.
earlier). Pre-POSIX backups are created using the TRANSPORT=MPEXL option. For example: :STORE @.MYGR.SOMEACCT;*T;SHOW;TRANSPORT=MPEXL There are two general scenarios when les would need to be transferred to a pre-POSIX system: Planned Transport The user stores o a set of les from one system, to be restored on another system right away. Unplanned Transport The data stored o from a system (usually a system backup) is suddenly required to be restored on the same or a di erent system.
F0000001._HFSGRP._HFSACCT <- /SYS/PUB/dir1/file_a F0000002._HFSGRP._HFSACCT <- /SYS/PUB/dir1/file_b F0000003._HFSGRP._HFSACCT <- /SYS/PUB/dir1/file_c Since _HFSGRP and _HFSACCT are illegal MPE lenames, special steps must be taken when attempting to restore these les on a pre-POSIX system. The LOCAL option can be used to restore the HFS les into your logon group. For example, on a pre-POSIX system, issue: :FILE T;DEV=TAPE :RESTORE *T;@.@.
:FILE T;DEV=TAPE :STORE @.OPERATOR.SYS;*T;TRANSPORT;FILES=6000 Use the MPE/iX RESTORE command to restore les 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 les. Managing File Security (COPYACD and NOACD) An additional way to manage the security of les being stored is to use the COPYACD and NOACD options. The default is COPYACD.
Table 6-1. Maximum Tape Record Sizes Tape Drive HP 7974 HP 7978A HP 7978B HP 7979 HP 7980(XC,S,SX) DDS (all) 3480 MO Record Size 16 KB 16 KB 32 KB 32 KB 32 KB 32 KB 32KB 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 les, since the maximum record size of 32K is already being used. Normally when a STORE command is issued, a default record size of 16 kilobytes is used.
TurboSTORE/iX 7x24 True-Online Backup with true-online backup , (using the ONLINE option with START or END), the les being stored remain available and can be modi ed while the backup is occurring. Refer to Chapter 7, \TurboSTORE/iX 7x24 True-Online Backup," for more information.
Additional Backup Information (STATISTICS) In addition to the counts of les stored and not stored that are normally reported at the end of a backup, the STATISTICS option provides extra data about the backup.
Log Data Total on Reel If an online backup (ONLINE) or 7x24 true-online backup (ONLINE=START or ONLINE=END) backup is performed, this column displays how much log data was written to the backup. This includes both before image and after image log data. (For a de nition of before and after image log data, refer to Chapter 7). This total depends on how much activity occurred on the les being backed up during the backup.
If software compression is used for the backup (with COMPRESS=LOW or COMPRESS=HIGH), then a section on compression ratios will follow the Throughput section. For each media, or each media in each parallel set, the amount of uncompressed le data written is displayed with the amount of data actually written when that le data is compressed. The ratio between these two numbers and a compression percentage is also displayed. The higher the ratio is, the better the data compressed.
Example 2 d The following example is of a backup to two pieces of media.
d a 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 ---------+-------------+-------------+-------------+-------------+-----------SET 2 TOTAL 66652980 307716 22195808 614
Storing Files from Volume Sets (ONVS) To store the les on a particular volume set, use the ONVS parameter of the STORE command. ONVS lets you store les from up to 20 volume sets at once. For example, to store all les from the nonsystem volume sets named VOL_SET_A and VOL_SET_B, enter: :FILE T;DEV=TAPE :STORE @.@.@;*T;ONVS=VOL_SET_A,VOL_SET_B To store les from system and nonsystem volumes, include the system volume set name within the ONVS parameter. For example: :FILE T;DEV=TAPE :STORE @.@.
Although the ONVS and SPLITVS options can be used together, a volume set that is speci ed for ONVS cannot be speci ed for SPLITVS and a volume set that is speci ed for SPLITVS cannot be speci ed for ONVS. Note Renaming Files (RENAME) When using the RENAME option, an original le refers to the original disk le, and a target le indicates the nal lename on the backup media. Renaming a le requires the capabilities necessary to manipulate les across groups and accounts.
The following tables illustrate sample translations for the target lenames: STORE a.b.c=...;TAPE;RENAME;SHOW Original Filename Target Speci cation Target Filename A.B.C A.B.C A.B.C A.B.C x.y.z @.y.z x.@.z x.y.@ X.Y.Z A.Y.Z X.B.Z X.Y.C STORE /A/B/C=...;TAPE;RENAME;SHOW Original Filename Target Speci cation Target Filename /A/B/C /A/B/C /A/B/C @.y.z x.@.z x.y.@ C.Y.Z X.B.Z X.Y.A STORE /a/b/c=...;TAPE;RENAME;SHOW Original Filename Target Speci cation Target Filename /a/b/c /a/b/c /a/b/c @.y.
Original Filename /a/ /a/f1 /a/b/ /a/b/f2 /a/b/c/ /a/b/c/f3 /a/b/c/d/ /a/b/c/d/f4 /a/b/c/d/e/ /a/b/c/d/e/f5 /a/b/c/d/e/f/ /a/b/c/d/e/f/f6 /a/b/c/d/e/f/g/ /a/b/c/d/e/f/g/f7 Target Speci cation /@/x/@/y/@ /@/x/@/y/@ /@/x/@/y/@ /@/x/@/y/@ /@/x/@/y/@ /@/x/@/y/@ /@/x/@/y/@ /@/x/@/y/@ /@/x/@/y/@ /@/x/@/y/@ /@/x/@/y/@ /@/x/@/y/@ /@/x/@/y/@ /@/x/@/y/@ Target Filename NOT STORED:1 NOT STORED:1 NOT STORED:1 NOT STORED:1 NOT STORED:1 /a/x/c/y/f3 /a/x/c/y/d/ /a/x/c/y/f4 /a/x/c/y/e/ /a/x/c/y/f5 /a/x/c/y/f/ /a/x/c/y
Original Filename /a/b/ /a/b/f2 /a/b/c/ /a/b/c/f3 /a/b/c/d/ /a/b/c/d/f4 /a/b/c/d/e/ /a/b/c/d/e/f5 /a/b/c/d/e/f/ /a/b/c/d/e/f/f6 /a/b/c/d/e/f/g/ /a/b/c/d/e/f/g/f7 Target Speci cation /w/x/y/z/ /w/x/y/z/ /w/x/y/z/ /w/x/y/z/ /w/x/y/z/ /w/x/y/z/ /w/x/y/z/ /w/x/y/z/ /w/x/y/z/ /w/x/y/z/ /w/x/y/z/ /w/x/y/z/ Target Filename /w/x/y/z/ /w/x/y/z/f2 /w/x/y/z/c/ /w/x/y/z/c/f3 /w/x/y/z/c/d/ /w/x/y/z/c/d/f4 /w/x/y/z/c/d/e/ /w/x/y/z/c/d/e/f5 /w/x/y/z/c/d/e/f/ /w/x/y/z/c/d/e/f/f6 /w/x/y/z/c/d/e/f/g/ /w/x/y/z/c/d/e/f/g/
Table 6-3. Creator File Translations Original Filename Target Speci cation Target Creator s1.sg.sa s2.sg.sa s3.sg.sa s4.sg.sa s5.sg.sa s6.sg.sa s7.sg.sa s8.sg.sa s9.sg.sa s10.sg.sa s11.sg.sa s12.sg.sa s13.sg.sa s14.sg.sa s15.sg.sa s16.sg.sa s17.sg.sa s18.sg.sa s19.sg.sa s20.sg.sa s21.sg.sa d1.dg.da d2.dg.da:@.@ d3.dg.da:user.acct d4.dg.da:user d5.dg.da:user.@ d6.dg.da:@.acct d7.dg.da:@ /d8 /d9:@.@ /d10:user.acct /d11:user /d12:user.@ /d13:@.acct /d14:@ /ACCOUNT/GROUP/D15 /ACCOUNT/GROUP/D16:@.
:STORE @.PUB.SYS -a -b -c -d=@.backup.sys:creator;*t;rename Lockwords are not allowed on target les, and if speci ed cause STORE to abort. The options that are not supported with the RENAME option and will cause STORE to abort are: PURGE TRANSPORT SPLITVS Specifying HFS Files (TREE and NOTREE) By default, STORE uses the last character of a HFS lename to determine if the speci ed le or leset should be scanned recursively to include all les below the speci ed wildcards or directories.
If any of the dataset les are speci ed in addition to the root le, no warning will be displayed but the individual dataset les will be counted as redundantly speci ed les. If you want to back up a partial database, you can use the PARTIALDB option. STORE will backup only those dataset les speci ed in the leset list.
Creating a Disk Directory File (STOREDIRECTORY and NOSTOREDIRECTORY) Note To increase the ease and speed of le recovery, all STORE and TurboSTORE products have the ability to put a copy of a backup's STORE label and STORE directory into a disk le. This directory information allows RESTORE to more quickly determine where les are located on the backup, and to prompt users to mount the necessary media. If you want to enable this feature, specify the STOREDIR[ECTORY] option.
You can have STORE associate a shorter, more meaningful name to the disk directory les by specifying an optional lename argument to STOREDIR. You can specify an MPE or HFS lename. STORE then creates a symbolic link with the speci ed name, which points to the original disk le. For example, to create a full backup on Friday and give it the name FRIFULL, issue the command: :STORE /;*tape;STOREDIRECTORY=FRIFULL.HPSTORE.
distributed, such as when doing a partial backup, or if the les are only coming from one disk. To STORE les in interleave format, use the INTER parameter. For example: :FILE T;DEV=TAPE :STORE @.OPERATOR.SYS;*T;INTER When these les are restored, RESTORE will automatically recognize the interleave format and restore the les properly. Using the STORESET and INTER parameters together improves backup time on large systems.
Note No matter whether you specify HIGH or LOW, the actual level of data compression is dependent upon the type of data being compressed. For example, program les will not compress as much as data les. You must determine which of the compression algorithms best suits your needs. In some cases the low-compression algorithm may perform almost as well as, or better than, the high-compression algorithm.
Storing to Magneto-Optical Devices (MOSET and NAME) TurboSTORE/iX II allows you to store backup data to magneto-optical (MO) devices. This is done by using the MOSET option to specify which MO devices should be used for the backup. The NAME option is used to associate a logical name with the backup. This name is used during the restore process to identify which backup should be used. These options are discussed in detail in Chapter 3, \Preparing Storage Devices".
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. Performing an Online Backup At the time the online backup is started, all les must be closed for a brief period while they are attached to the shadow logging system. Shadow logging saves the \before images" of le blocks when the records in the le block are modi ed during online backup.
When online backup begins, the shadow subsystem assigns each le in the store leset to a log le created on the same volume where the le resides. Actual logging activity does not take place unless the le is modi ed after the attach phase. TurboSTORE saves the changes made to databases and les being stored in special log les. These les can become quite large when there is a lot of activity on the system. The LOGVOLSET option allows you to specify which volume set to use for the log les.
This message is also written to $STDLIST if STORE is being run from a session. After you receive the above message, the users are allowed read, write and purge access to the attached les. Send your users a message telling them they may resume their applications. For example: WARN @S;ONLINE BACKUP HAS BEGUN. YOU MAY NOW RESUME YOUR APPLICATIONS. The NOTIFY option (described earlier in this chapter) can be used to automate this task.
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.
The Sync Point When performing a backup, you want to know at what point in time the backup occurred. This is helpful when performing a recovery so you know that all les were restored to a state at the same time. This is the point called the sync point , where all les are synchronized. It can occur at di erent times, depending on the type of backup performed. You can schedule when the sync point occurs (either at the start or the end) by scheduling when the backup job is launched.
It allows for migration of les to earlier releases of TurboSTORE/iX, whereas sync at end does not. For example, scheduling the sync point at the beginning of the backup is useful when your system is heavily used during the day, making performing backups then impractical. The backup can be started at the end of the busy day shift, and run during the night. Since no application shutdown is required, users, perhaps from other time zones, can continue to access their les and applications uninterrupted.
Consistent Backups Physical Consistency Even though database les generally constitute the largest part of any backup, TurboSTORE/iX 7x24 True-Online Backup also backs up system and non-database les. Since TurboSTORE allows changes to les during a backup, it establishes a close tie to the le system to ensure physical and logical consistency. Physical consistency is ensured by providing a snapshot of the leset at a speci c point in time, speci cally, at the sync point.
Logical Consistency In addition to physical consistency, TurboSTORE/iX 7x24 True-Online Backup also guarantees logical consistency for databases. This is done by setting the sync point to occur when all open transactions against the databases have completed. No new transactions can start until the open transactions are complete, which is called quiescing the database.
TurboSTORE/iX 7x24 True-Online Backup uses shadow logging to intercept any changes made to les while they are being stored. How Shadow Logging Works 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 leset as it is right before the les begin to be written out. When a le is opened for write access, any changes made to the le are monitored by shadow logging.
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 les as they are at the end of the backup. In this case, instead of copying the before images of modi cations to log les, shadow logging uses a bitmap to keep track of the modi ed pages. Once the backup is completed, the bitmap is used to collect the modi ed \after image" pages from the system. This data is then written out to the end of the media.
Logging File Attribute Modifications File Creations and Purges Other File Attributes TurboSTORE/iX 7x24 True-Online In addition to keeping track of changes to a le's data during a 7x24 true-online backup, changes to a le's attributes, such as lename, le limit, and le code, are also captured to ensure a consistent backup. When the sync point is at the end of the backup, le creations and le purges that occur during the backup are captured by shadow logging.
Specifying Time In addition to the START or END parameter, you can specify a time for the sync point to occur. The time is speci ed in 24-hour format (hh:mm[:ss]). If a time is speci ed with END, the sync point occurs at the time speci ed or once all les have been stored, which ever event occurs last. If a time is speci ed with START, the sync point occurs at the time speci ed, or once all les are prepared for the backup, which ever event occurs last.
When TurboSTORE receives a reply of YES to this question, it quiesces all TurboIMAGE and ALLBASE/SQL databases, turns on before image logging, unquiesces the databases, tells you to unquiesce all your applications, and completes the backup. You are noti ed on the console: 17:35/#S21/59/ALL OF YOUR APPLICATIONS CAN BE UNQUIESCED NOW. You can then perform any actions needed to unquiesce your applications. Synchronizing Multiple Applications You can synchronize multiple applications in several ways.
Use the END, ASK, and time parameters. If you think there might be a job failure, this is the best method to use. Set the time far enough in the future to be sure all backups are complete. This method puts all the ASK requests on the console at the speci ed time, instead of displaying each job request as it completes.
Storing Part of a Database (PARTIALDB) Note 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. Any databases that are partially stored are NOT quiesced at the sync point. Database corruption may result if not all database les are stored during a 7x24 true-online backup.
If RESTORE is unable to read the media directory information from a media directory disk le, it asks you to mount the last piece of media from the backup. Once it has read the media directory, it prompts you to mount the necessary piece(s) of media for the recovery process. Since the after image log data is stored at the end of the backup, les that need to have after image log data applied is unavailable for read OR write access, until the after image log data is applied at the end of the backup.
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 di erently.
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 con gure media drives so that they are automatically assigned to users. See \Automatically Assigning Devices," later in this chapter.
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 di erent 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 d The system describes the job or session. For example: JOBNUM STATE INPRI #S37 EXEC WANDA.
Pending Media Requests Denying a Media Request 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. If the backup device is unavailable, or for another appropriate reason, you choose not to let a user or users access a backup device, you should deny media requests when they appear.
The device speci cation must be unique. You must use the device speci cation (logical device number or unique device class) in a FILE command describing the device. The user must request an unlabeled media. Refer to System Startup, Con guration, and Shutdown Reference Manual (32650-90042) for instructions for con guring devices.
9 When STORE is Complete When you see the END OF PROGRAM message, STORE is complete.
d The following might be listed on the console: STORE/RESTORE VERSION a X.51.00 (C) 1986 HEWLETT-PACKARD CO. STORE a[mn]@.pub.sys;*n;SHOW MON, JUL 10, 1995, 5:50 PM FILENAME GROUP AMCAT000.PUB AMMESCAT.PUB AMSYSDIC.PUB AMTCX .PUB AMTRX .PUB ANSTART .PUB ANSTAT .PUB ANSTOP .PUB ANUTIL .PUB c ACCOUNT .SYS .SYS .SYS .SYS .SYS .SYS .SYS .SYS .
occurred while actually storing the le to the backup media. The STORE listing should be examined to determine which les failed to store, and why. The user interface for the VSTORE command is similar to that for the RESTORE command which is described in Chapter 11, \Restoring Files." Command syntax for VSTORE is shown in Appendix B, \Command Syntax." To verify one or more les on a STORE backup, mount the backup on your backup device. The write ring should be removed as a precaution.
:VSTORE *T;@.@.@;SHOW :VSTORE *T;FILE1.MANAGER.SYS;SHOW;ONERR=SKIP :VSTORE *T;@.@.@;DIRECTORY Note The VSTORE command is not valid for a STORE backup created with the TRANSPORT parameter. For a full discussion of all VSTORE command options, refer to the MPE/iX Commands Reference Manual Volumes 1 and 2 (32650-60238) or refer to Chapter 11, \Restoring Files." Implementation of the VSTORE options is the same as implementation of the RESTORE options, except for the ones described above.
The NODECOMPRESS option can only be used with VSTORE, for example: :FILE T;DEV=TAPE :VSTORE *T;@.@.@;SHOW;NODECOMPRESS Retaining the STORE Tapes Allowing Users Back on the System Unload each backup and check for correct labeling. If you used the SHOW=OFFLINE option of the STORE command, the system has printed a list of the les you stored. Retrieve the report from your printer and either le it with your records or attach it directly to one or more backup reels. Place each backup in your backup library.
d a JOBNUM STATE IPRI JIN #S185 EXEC 20 #J17 SUSP 10S 2 JOBS: 0 INTRO; 0 SCHEDULED 0 WAIT; INCL 0 DEFERRED 1 EXEC; INCL 1 SESSIONS 1 SUSP c JLIST 20 PP INTRODUCED FRI 1:03P FRI 5:02P JOB NAME OPERATOR.SYS AJOB,MRS.T JOBFENCE= nn; JLIMIT= nn; SLIMIT= nn b Figure 9-2. Listing Suspended Jobs The example shows one suspended job (#J17). To restart that job, enter: :RESUMEJOB #J17 Repeat the RESUMEJOB command for each job listed as SUSP.
10 Backing Up the System Configuration This chapter describes how to use the SYSGEN utility to perform a system backup. The subjects in this chapter are: SYSGEN Backup Capabilities Running SYSGEN The System Backup Command Creating a System Load Tape Combined SLT and Store set SYSGEN Backup Capabilities A complete system backup consists of system les, user les, the le system directory, and system con guration information. STORE copies only system and user les and the le system directory to backup.
CONFIG.SYS is a permanent leSet containing information on device classes, assigned I/O paths, assigned LDEV numbers, volume names, and various data in system les. When changes are made to the system con guration from one or more of the con gurators, the les remain unchanged until you formally keep the new information through the SYSGEN KEEP command. You can always back out of changes until you actually keep them. You may KEEP the base group or to a group you specify.
:FILE SYSGIN=NEWIN :FILE NEWOUT;DEV=LP :SYSGEN,MYGROUP,*NEWIN,*NEWOUT When you run SYSGEN, you receive a list of SYSGEN rst-level commands: d a 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.
If an error occurs during the tape creation, a ashing TAPE ERROR message is issued to the console, describing the error. To create a system load backup that contains a new con guration, follow the sample commands as illustrated: Creating a System Load Tape d a :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.
base group and you issue the TAPE command, NEWFIG is written to the backup as CONFIG.SYS, overwriting the default con guration les. Recall the new con guration and generate a system load backup: sysgen>BA NEWFIG sysgen>TA If you are completely con dent that you have a working con guration, exit SYSGEN. Otherwise, recall the original CONFIG.
When the STORE option is used, les will be stored after the SLT as speci ed through the lesetlist string. The lesetlist string parameter is the same as the lesetlist parameter that is speci ed when using the STORE command. The only di erence is that it speci es a set of les to be stored after an SLT as opposed to just a normal backup. An example of how to use the STORE option is as follows: sysgen> TA STORE = "@.pub.
11 Restoring Files This chapter describes the RESTORE process and options. You RESTORE a le by transferring it from a STORE backup to disk. You might need to RESTORE a single le, for example, when a user accidentally deletes it. You might restore all the les in an account after you have permanently archived the account o ine, deleted the les, and a user needs access to the les again. After a major system failure, you might need to RESTORE all of your les from backups.
Caution Note Preparing to Restore Files Locate the Necessary File or Files Checking for Duplicate Filenames Caution Do not use RESTORE to transfer any of the les originally on your system load tape from LDEV 1 to a system disk other than LDEV 1. These les are contained in the SYS account and can be displayed by entering the SY con gurator of the SYSGEN utility and using the SHOW command. Do not purge or put a lockword on these les.
Use wildcard characters to represent a set of les. Refer to \Using Wildcard Characters", in Chapter 5, \Storing Files," for details. For example, the following LISTF command lists all les in the PUB group of the RESEARCH account: :LISTF @.PUB.RESEARCH If at least one le exists, the system prints the lename at your terminal.
Restoring from Labeled Tapes Restoring les from labeled tapes requires that the RESTORE command include a RESTORE le reference that was named previously in a le equation. For example: :FILE TAPE7=BACKUP.JAN29;DEV=TAPE;LABEL="VOL25",ANS,02/28/90 To recover all les in the volume set, you would then enter the following RESTORE command. :RESTORE *TAPE7;@.@.@;restoreoptions The system then requests that you mount the rst volume of the volume set.
Restoring from Multiple Devices (RESTORESET) Sequential Devices To RESTORE les 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. You can use sequential device con guration when you have a large set of les to RESTORE from a number of tapes and you want to speed up the process.
Enter the following RESTORE command to RESTORE les from a set of three sequential tape devices: :RESTORE ;@.@.@;RESTORESET=(*T,*T,*T) You can RESTORE les that were created using parallel devices or parallel device pools in a sequential con guration. 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....B1, B2 and so on.
Enter the following RESTORE command to copy les from a set of parallel device pools: :RESTORE ;@.@.@;RESTORESET=(*T,*T),(*T,*T) Notes 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.
Restoring From Multiple Disk Files If the backup to be restored contains more than one disk le, create only one le equation pointing to the rst disk le. RESTORE will automatically open the subsequent disk les. Do not create any le equations for the other disk les. Be sure that all of the disk les in a backup are present at the time of the backup. RESTORE will abort with an error if it is unable to open a disk le that is part of the backup.
Note Just as storing to serial disk les with the STORESET command is not allowed when storing les, restoring from serial disk les using the RESTORESET command is not supported. You need only to specify a le equation for the rst disk le in the backup, or in a parallel set. RESTORE will automatically nd and open any additional les in the backup that it needs. All other RESTORE options (other than MOSET and NAME) can be used when restoring from disk les.
Specifying the Backup Name The media name you speci ed with the STORE command is required when restoring from a magneto-optical device. Use the NAME option to indicate the logical tape name from which the RESTORE is to be done. For example: ;NAME=BK1130PM.D23OCT90.KING If the media is not loaded in the magneto-optical device at the time the RESTORE is started, you are prompted to mount the media. For example: 23:24/#S1/51/MOUNT THE MEDIA LABELLED BK1130PM.D23OCT90.
Issuing a RESTORE Command To RESTORE the les from the tape to the system disk, you may optionally rst 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 lename. You must issue a RESTORE command describing: The les you want to RESTORE The options you want to use, if any Back references to the lename of the tape device, unless you use the default lename. For example: :FILE T;DEV=TAPE :RESTORE *T;FILE1.
devices than were used to create the tape. Mount the media from the rst store set initially. When RESTORE has nished reading les from that set, it will prompt you to mount media from the next set. It will continue to request media until all les have been restored. RESTORE can restore les from a tape which is in MPE/VE STORE format. MPE/VE STORE format tapes are made when the TRANSPORT option is speci ed on an MPE/iX STORE command.
MOSET NAME For descriptions of MOSET and NAME, see the \Restoring Files from Magneto-Optical Disk (MOSET and NAME)" section earlier in this chapter. For a description of RESTORESET, see the \Restoring from Multiple Devices (RESTORESET)" section earlier in this chapter. Listing Restored Files (SHOW) Whenever you RESTORE a set of les, the system displays the total number of les restored at your terminal.
No continuation reel. You did not nd a continuation reel for a multi-reel tape set. A device reference error. Either the speci cation for the device parameter is illegal, or the device is not available. The ONERROR option of the RESTORE command lets you choose an error recovery procedure. Your options are ONERROR=QUIT , ONERROR=SKIP , or ONERROR=FULL . QUIT is the default. You do not have to specify the ONERROR option if you want the default behavior.
RESTORE the le from tape using the CREATE option. RESTORE sets account, group, and user capabilities to their default values when it creates them. You must have the necessary capabilities to create a new group or account. That is, you must have system manager (SM) or system supervisor (OP) capability to create a new account. You must have system manger (SM), system supervisor (OP), or account manager (AM) capability to create a new group.
or ACCOUNT with LOCAL. You must have system manager (SM) or system supervisor (OP) capability to switch a le's account. You must have system manager (SM), system supervisor (OP), or account manager (AM) capability to switch a le's group. Note A user without the capabilities described above can RESTORE a le to a di erent account or group if the following conditions are met: The group, account, and le level access are available to the user. The le has no lockword, or if it does, the user knows the lockword.
Overwriting or Retaining Disk Files (KEEP, NOKEEP) By default, RESTORE replaces disk les with the same fully quali ed lename as the le you are restoring from backup. Therefore, especially if you are restoring a large number of les, to be sure that you do not overwrite an important le or les, use the KEEP parameter of RESTORE. For example, your STORE tape might contain several les, some of which have names that are the same as les on disk.
To change the dates and times to the date you restored the les, use the NEWDATE option. For example: :FILE T;DEV=TAPE :RESTORE *T;@.@.@;NEWDATE You will probably want to use NEWDATE when you RESTORE archived les, 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.
The following example shows a sample RESTORE command and output display format using the LISTDIR parameter: d a :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.
Displaying Progress Messages (PROGRESS) Use the PROGRESS parameter to display RESTORE command progress messages at regular intervals. For example, to display progress messages every ve minutes, use the following command: :FILE T;DEV=TAPE :RESTORE *T;@.@.@;*T;PROGRESS=5 If you use the PROGRESS option alone, without specifying an interval, RESTORE displays status messages every minute. If RESTORE is being run from a MPE session, the progress messages will be send to the standard list ($STDLIST).
If you do not specify a device with the DEV parameter, RESTORE tries to RESTORE a le to the logical device compatible with the device type and subtype speci ed in the le's label and the device type and subtype of the mounted home volume set. If it cannot nd such a device, RESTORE tries to RESTORE the le to a device with the device class speci ed in the le's label and the home volume set.
Note The VOL, VOLCLASS, and VOLSET parameters are not valid for restoring from TRANSPORT tapes. Modifying ACDs (COPYACD, NOACD) When restoring les, the NOACD option can be used to prevent the ACDs on the backup from being restored. This will cause the les being restored to have less security than when they previously existed on the system. Using NOACD can be useful when the ACDs that exist on the backup refer to users or accounts that do not exist on the current system.
Note Restoring using a disk directory file (STOREDIRECTORY) 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 e ect 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.
For example, to tell RESTORE to use the le MYDIR as the disk directory le, issue the command: :RESTORE *T;@.@.@;SHOW;STOREDIR=MYDIR or :RESTORE *T;@.@.@;SHOW;STOREDIR=/SYS/HPSTORE/MYDIR If RESTORE cannot open the speci ed disk directory le, or it cannot open the disk directory le in the default location, it will use the STORE directory from the backup media. No warning message will be displayed if RESTORE cannot locate a disk directory le.
Responding to Tape Requests If your system is not con gured to automatically assign devices, you see a tape request. For example: ?9:08/#S25/43/LDEV# FOR "T" ON TAPE (NUM)? If you have previously issued a FILE command that included the tape device's LDEV number, the tape request asks you to con rm that number. For example: ?14:57/#S25/43/IS "T" ON LDEV #8 (Y/N)? See Chapter 7, \Handling Media Requests," for information on how to respond to tape requests.
Using the PROGRESS Option When RESTORE is Complete d If you specify the SHOW parameter, as RESTORE proceeds, it lists each le restored at your terminal. For example: a :RESTORE *T;FILE1.OPERATOR.SYS;SHOW WILL RESTORE FILENAME GROUP FILE1 c If you speci ed the PROGRESS option of RESTORE, you can monitor the progress of your recovery by looking at the progress messages issued by RESTORE. If RESTORE is being run from a session, then the progress messages will be issued on $STDLIST.
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 Con guration 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.
Reloading Your System Configuration If your most recent system con guration les are from backups, do the following to retrieve your system con guration: 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. This can be done with the following set of commands: :VOLUTIL volutil: NEWVOL volumesetname:membername LDEV=nn The volumesetname for the system volume set is MPEXL_SYSTEM_VOLUME_SET.
4. Issue the following FILE and RESTORE commands to copy the les from the backup media. :FILE T;DEV=TAPE :RESTORE *T;@.@.@;KEEP;OLDDATE;DIRECTORY 5. Monitor the console for tape requests. 6. Mount additional backup media when necessary until you have copied all les from all backups. Restoring Files from Full Backup Tapes If your most recent backups are from a partial backup, you need to reload your remaining les from your most recent full backup.
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.
Private Recovery Facilities: Cold Sites and Hot Sites A private recovery facility is owned and maintained by your company. It is usually located at a facility close to, but separate from, your data center. There are two types of private backup sites, cold sites and hot sites. Cold Sites A cold site is a facility with su cient electrical power, air conditioning, and telecommunications equipment to support a computer system, but it does not contain an actual computer system.
Commercial Backup Companies Commercial backup companies o er 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.
capability, and that upgrades in the Data Center computer system are quickly re ected in the disaster recovery computer system. Disaster Notification and Response Time A disaster can occur any time without warning. Your recovery center should be available 24 hours a day. The time from when you notify the recovery center to the time that your backup system is up and running is called response time. Response time requirements vary depending upon the business situation.
A Error Messages This appendix describes how to interpret and apply STORE, RESTORE, and VSTORE error message information. The sections in this appendix are: Determining the Cause of STORE, RESTORE and VSTORE Errors Using the STORE ERROR Variable 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 le. Others cause the program to stop running.
Viewing the Value of STOREJCW To view the value assigned to STOREJCW, use the following SHOWVAR command: :SHOWVAR STOREJCW The system reports the current value. For example: STOREJCW=4 Determining the Cause of an Error A-2 Error Messages The value of STOREJCW after you issue a STORE, RESTORE, or VSTORE command tells you the cause of any errors in storing, restoring, or verifying the les you named. To determine the cause of an error: 1. Use the SHOWVAR command to view the value of STOREJCW. 2.
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 les or perform disk space recovery. 3 Error in opening an indirect le. Does the indirect le you named exist? Do you have adequate access to it? Is it in use? Is the redirect le an EDIT le? 4 Error in opening the le.
A complete listing of all possible STORE and RESTORE errors, along with the probable cause and recommended action can be found in the MPE/iX Error Messages Manual Volumes I, II and III (32650-60016). 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.
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.
STORE Syntax 2 STORE filesetlist 32 ;storefile 32 2 ;option ; . . . 33 where option is 2 2 ;SHOW =showparmlist 2 REDO ;ONERR OR = QUIT 2 3 2 33 3 ;DATE2 S 3<=accdate ;DATE S >=moddate 3 ;PURGE 33 2 2 ;PROGRESS =minutes 2 3 ;DIRECTORY 3 2 ;FILES=max les 2 2 33 ;TRANSPORT =MPEXL 2 32 3 ;COPYACD ;NOACD 2 2 ;FCRANGE= lecode/ lecode , . . . 2 3 ;MAXTAPEBUF 2 3 ;NOTIFY 2 ;STATISTICS 33 3 333 2 2 2 ;ONVS=volumesetname ,2volumesetname 3,3 . . .
RESTORE Syntax 2 RESTORE restorefile 32 ;filesetlist 32 2 ;option ; . . . 33 where option is 2 2 ;SHOW =showparmlist 2 4 ;ONERR 2 33 93 8 QUIT = 3 < OR = SKIP 5 ; : FULL 9 =2 2 8 < LOCAL 4 ; GROUP=groupname 2 3 : ACC OUN T=accountname 9 2 8 GROUP > > > > =2 6 6 < 6 ;CREATE6 = ACCT , 4 4 > CREATOR > > > ; : ; PATH 2 ; . .. 5 33 2 2 3 3 ...
VSTORE Syntax 2 VSTORE vstorefile 32 ;filesetlist 32 2 ;option ; . . . 33 where option is 2 2 2 2 2 ;SHOW =showparmlist QUIT ;ONERR OR = SKIP 2 3 ;DIRECTORY 2 3 2 ;PROGRESS =minutes 32 3 2 3 ;COPYACD ;NOACD 2 32 3 ;TREE ;NOTREE 2 3 ;NODECOMPRESS 2 33 33 ;STOREDIR ECTORY =directoryname 2 3 3 3 ;PART IAL DB 2 2 ;RESTORESET=(device , . . . 3 3 ) ** TurboStore/iX II and TurboSTORE/iX 7x24 True-Online Backup options: 2 2 2 B-4 Command Syntax 2 ;RESTORESET=(device , .
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.
:STORCOPY 4Return5 :STORCOPY:FILE DDSTAPE;DEV=DDS 4Return5 :STORCOPY:FILE SYSLIST;DEV=LP 4Return5 :STORCOPY:STORCOPY COPYTOSET=(*DDSTAPE);NAME=MOBACK;SHOW=OFFLINE 4Return5 In the following example, a backup called MOBACK, which has ve 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 de ned by le 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 de nition (ACD) Security feature that controls access to les and directories. Consists of a list of access permissions and user speci cations. (For example, R,W,X:@.PAYROLL gives all users in the PAYROLL account read, write, and execute access to the le or directory that is assigned this ACD.
case sensitivity HFS lenames can be saved in uppercase or lowercase letters. The le named ./FILE1 does not refer to the same le as ./file1 or ./File1. character A letter, number , or symbol represented by one byte of data. character set A series of characters to substitute for a single character to name a group of les. command A system-reserved word that directs the operating system, a subsystem, or a utility program to perform a speci c operation.
DDS Digital Data Storage. A format for storing computer data on DAT cassettes. device See peripheral. device class A collection of devices that have some user-de ned relation. The MPE/iX le system supports a means of maintaining collections of devices but is cognizant of the relation only for certain MPE device class names. device pool A series of identical backup devices. device type Device types are de ned by a number.
binary data (such as executable code). Every le must have a lename so that the user can access the le's contents. le equation A method of equating a lename to a device or another le. The MPE/iX FILE command is used to establish the relationship of the le to the device. Generally used to direct the input to or output from a program, job, or session to a particular device by referencing the device class, such as TAPE or LP. lename A name of a le that can be in MPE syntax (FILE.GRP.
hierarchical le system (HFS) A le system that is tree structured and can contain les at many di erent levels. This le organization is obtained through the use of directories, which can contain les and other directories. indirect le A text le 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.
manages all system resources and coordinates the execution of all programs running on the system. MPE syntax Rules that determine the lename length, special characters, and conditions for les, groups, and accounts. Account, group, and lenames can be up to 8 characters. Characters are always converted up uppercase. Characters must be alphanumeric. This is the syntax current MPE/iX users are used to using (for example, LEDGER.PUB.SYS). native mode (NM) The native run-time environment of MPE/iX.
POSIX Portable Operating System Interface. A set of standards that address various areas of operating system technology. The POSIX standards describe functions of an operating system interface that applications use to become \POSIX- compliant." The main point of POSIX is to facilitate software portability and minimize porting costs. purge To delete a permanent le from the system with the PURGE command.
slash (/) Another name for the root directory. See also root directory . storage device A device (such as a disk pack, a disk cartridge, a exible disk, magnetic tape, or cartridge tape), onto which data can be stored and subsequently retrieved. subdirectory A directory that is contained within another directory is sometimes referred to as a subdirectory. system A group of one or more CPUs that communicate through buses without the use of data communications software.
transport backup Transport refers to the movement of les between MPE V/E and MPE/iX systems using backup media. MPE/iX backup and recovery provides a compatibility option with which an MPE V/E-compatible tape may be created or read. true online backup A tool that allows users to perform application and system backups without closing les or disrupting users. user Anyone logged on to a session, using a local or remote terminal to interact with the computer.
Index 7 7x24 true-online backup, 2-4, 6-38, 7-1 A aborting sessions, 4-6 ABORTJOB command, 4-6 aborts, A-1 account, 11-14 ACCOUNT parameter,RESTORE command, 11-15 account structure, 6-14 ALLBASE/SQL databases,storing, 5-11 allocating a device, 8-1 allowing users on system, 9-5 archiving les, 6-13 ASK parameter ONLINE option, 7-9 assigning an LDEV number, 8-1, 8-3 attach phase, 2-4, 6-39, 6-40 automatically assigning devices, 3-13, 3-14, 8-1, 8-4 automatic volume recognition, 5-12 Auto Reply.
supported by MPE/iX, 1-6 backup error recovery, 5-14 backup media de ned, 1-6 duplicate, 13-4 preparing, 3-7{12 verifying, 9-2 backups labeled, 3-4 unlabeled, 3-4 basegroup parameter, SYSGEN utility, 10-2 base group, SYSGEN utility, 10-1 BREAKJOB command, 4-4 bu er size, 6-18 Index-2 C caret, 5-8 character sets, 5-2 cold site, 13-2 commercial backup companies, 13-3 compatibility of MPE V/E & XL backups, 6-15 with MPE V/E, 2-2, 3-3 compressing data, 6-36 compression algorithms, 6-36 COMPRESS parameter HIG
device pool, 3-6, 3-15, 3-16 device, restoring to speci c, 11-20 devices.
full system backup, 2-8, 6-12, 6-35, 12-1 Index-4 G group, 11-14 GROUP parameter,RESTORE command, 11-15, 11-18 H hardware requirements, 1-4 HELLO command, 4-3 HIGH option COMPRESS parameter, 6-36 HIPRI parameter HELLO command, 4-3 JOB command, 4-3 hot site, 13-2 I improving storage e ciency, 6-18, 6-36 increasing record size, 6-18 indirect le, 5-7, 6-10 restoring les, 11-13 initializing volumes, 12-2 input le parameter, SYSGEN utility, 10-2 interleave format, 6-35 INTER parameter STORE command, 6-35,
log handler, 2-4, 6-39, 6-40 logical device (LDEV) number, 3-2, 3-4, 3-13, 5-14, 8-1, 8-3, 11-20, 11-25 LOGVOLSET option TurboSTORE/iX 7x24 True-Online Backup command, 6-41 long le display, 6-4, 6-6 LOW option COMPRESS parameter, 6-36 M magneto-optical, 2-2, 3-20 restoring les, 11-9 maintaining a backup library, 2-10{11 maximum number of les, restoring, 11-20 maximum number of les, specifying, 6-17 MAXTAPEBUF parameter STORE command, 6-18 media.
Index-6 N NAME option RESTORE command, 11-9 STORE command, 3-22 TurboSTORE/iX II command, 6-38 naming les in RESTORE command, 11-3 in STORE command, 5-2, 5-7 native mode, 6-4 NEWDATE option RESTORE command, 11-18 newgroup parameter, SYSGEN utility, 10-2 NEWVOL command VOLUTIL utility, 12-2 NOKEEP option RESTORE command, 11-17 nonsystem volume set directory, 6-14 NOSTOREDIRECTORY option STORE command, 6-34 notifying users of a backup, 4-2 NOTIFY parameter STORE command, 6-19 NO WRITE RING message, 5-16 $NU
P parallel device backup, 3-16 preparing backups, 3-12 parallel device pools, 3-6, 3-18, 5-14, 6-36 preparing backups, 3-12 restoring devices, 11-6 parallel devices, 3-6, 3-16, 3-17, 5-14, 6-10 maximum number of, 3-17 restoring les, 11-6, 11-7 parallel disk les restoring les, 11-8 PARTIALDB option, 7-12 restoring part of a database, 11-22 STORE command, 6-32 partial system backup, 2-8, 6-11, 6-35, 12-1 PIN.
ONERROR option, 5-14, 6-10 reel-to-reel media MPE/iX backup media, 1-6 reel-to-reel tapes end-of- le marker, 2-9 header label, 2-9 labeled, 2-9 unlabeled, 2-9 reload of system con guration, 12-1, 12-2 removing les from disk, 6-13 REPLY command, 8-3, 8-4 CTRL/A keys, 8-4 replying to console requests, 4-4 RESTORE monitoring progress, 11-24 using MOSET, 11-9 using NAME, 11-9 using PARTIALDB, 11-22 using RESTORESET, 11-5 using STOREDIRECTORY, 11-23 using VSTORE, 11-9 RESTORE command, 2-4, 6-18, 6-36, 11-1, 12-1
directory information, 11-18 part of a database, 11-22 using a disk directory le, 11-23 restoring les, 1-6 7x24 true-online backups, 7-12 account, 11-14 automatically assigning devices, 11-11 checking for duplicate lenames, 11-2 creator, 11-14 described, 11-1 error recovery, 11-13 FILE command, 11-5 from a disk le, 11-7 from labeled tapes, 11-4 from magneto-optical devices, 11-9 from multiple devices, 11-10 from multiple disk les, 11-8 from optical disk, 11-9 from parallel device pools, 11-6 from parallel d
S Index-10 scheduling system backup, 2-8{9 scratch tapes, 2-10 sequential backup, 3-15 sequential device backup preparing backups, 3-7, 3-11 sequential devices, 3-5, 3-15, 5-14, 6-10 maximum number of, 3-15 restoring les, 11-5, 11-6 service bureaus, computer, 13-3 sessions, 4-2 shadow logging, 7-6 shadow subsystem, 2-4, 6-39, 6-40 short le display, 6-4, 6-6 SHOW=DATES option STORE command, 6-7 SHOWJOB command, 4-3, 4-4, 8-3, 9-5 SHOW=LONG option STORE command, 6-6 SHOW=OFFLINE option RESTORE command, 11-2
DIRECTORY parameter, 6-14 FCRANGE parameter, 6-18 FILES= parameter, 6-17 FULLDB option, 6-32 INTER parameter, 6-35, 6-36 MAXTAPEBUF parameter, 6-18 monitoring progress, 5-13 MOSET option, 3-22 NAME option, 3-22 NOSTOREDIRECTORY, 6-34 NOTIFY parameter, 6-19 ONERROR option, 5-14, 6-10 ONLINE option, 6-40 ONVS parameter, 6-14, 6-26 options, 6-1 options (parameters), 5-1 PARTIALDB option, 6-32 PROGRESS parameter, 5-16, 6-13 PURGE parameter, 6-13 referencing les, 5-2, 5-7 RESTORESET parameter, 5-7 SHOW=DATES opt
magneto-optical devices, 3-20 multiple devices, 3-14 optical media, 3-20 parallel device pools, 3-18 parallel devices, 3-16 sequential devices, 3-15 streaming backup drive, 6-35 suspended job, restarting, 9-5 suspending jobs, 4-4 sync point, 7-2 beginning of backup, 7-2 end of backup, 7-3 SYS account, 2-7, 10-2 SYSGEN utility, 10-1, 10-5 base group, 10-1 basegroup parameter, 10-2 default group, 10-1 described, 2-7 KEEP command, 10-2 SYSGIN, 10-2 SYSGOUT, 10-2 SYSLIST, 5-14, 6-3, 6-6, 6-10 system backup, 1-2
T TAPE command, SYSGEN utility, 10-3 tape error recovery, 11-14 tape information, displaying, 11-18 tape label, 3-7 tape request, 11-25 tapes.
Index-14 V verifying backup media, 9-2 VOLCLASS parameter STORE command, 11-21 VOL parameter STORE command, 11-21 VOLSET parameter STORE command, 11-21 volumes, 11-21 volume set, 6-26 VOLUTIL utility, 12-2 NEWVOL command, 12-2 VSTORE command, 5-1, 9-2, 9-4 ONERROR=QUIT option, 9-3 ONERROR=SKIP option, 9-3 restoring les, 11-9 syntax, B-4 W WAIT state, 4-2 WARN command, 4-3 WELCOME message, 4-1 wildcard characters, 5-2, 5-7 restoring les, 11-2 write ring, 5-16 restoring les, 11-3
