|
|
Performing System Operation Tasks: 900 Series HP 3000 Computer Systems > Chapter 6 Copying Files to TapeAn Overview of the Store Process |
|
Typically, when someone needs to store files, the following things happen:
There may be times, however, when you are both the user and the system operator. In this case, you issue the FILE and STORE commands to store a set of your own files or a set of system files and you also handle the media and monitor the console for STORE messages. This chapter describes the store process with this in mind. The next section explains how and when to issue a FILE command to name a backup device. Following that is a brief explanation of the hierarchical file system (HFS) that was introduced with Release 4.5 of MPE/iX, along with the general rules for specifying file sets using MPE syntax and HFS syntax. The remainder of the chapter describes the how to use the STORE command and all of its options. Use the FILE command to assign a file name to a backup device according to its logical device number (LDEV), or its device class. Using the backup device's logical device number is a more exact way to assign a file name to a particular device. There is only one device with LDEV number 8 in your system. However, several devices may be assigned the device class TAPE. For example, to assign the file name T to LDEV 8, enter:
Or, for example, to assign the file name BACKUP to all devices with the device class name TAPE, enter:
When you are choosing how to reference a backup device in the FILE command, keep in mind that you must reply to device requests at the console under two circumstances:
Some backup devices have an Auto Reply feature. To set up such a device so that it automatically replies to a request, enable Auto Reply on the device and assign it a unique name with the FILE command. The simplest way to assign it a unique name is to reference the device by its LDEV number. You may, however, reference it by device class name so long as the device class name is associated with one, and only one, device. You use the filesetlist parameter of the STORE command to specify exactly which files you want stored: one file, several files, or all the files on the system. In addition to naming many kinds of file sets, you can name file subsets to be excluded from the STORE process. With Release 4.5 of MPE/iX, the file system is no longer limited to three levels (account, group, and user) but instead is hierarchical, or tree structured. To facilitate this new organization, MPE/iX uses a new type of file, called a directory, which contain lists of files and pointers to those files. Users can now keep MPE files in directories as well as in groups, and a single directory (or a group) can have multiple levels of subdirectories within it. Moreover, all files in the system are stored in a root directory, represented by the slash character (/). The introduction of the hierarchical file system (HFS) has resulted in changes to the process of storing files which you, as the system operator, need to understand. The next few sections outline the changes you can anticipate. Throughout this chapter, you will see examples of the STORE command that include MPE syntax and HFS syntax. For the complete syntax of the STORE command and the text of the error messages, refer to the MPE/iX Commands Reference Manual, Vol. II (32650-90374).
Valid file names that use MPE syntax are also valid in HFS syntax; however, the converse is not necessarily true. For example, the MPE file name STORE.PUB.SYS is equivalent to /SYS/PUB/STORE in the HFS syntax; but the file name /tmp/store is not a valid MPE file designation because HFS syntax is case sensitive whereas MPE syntax is not. As a result, the way you specify the file set to store or restore has changed. Here are the rules for specifying MPE/iX file sets in the STORE command:
You can use wildcard characters in the file set specification. This allows you to store, for example:
You may use the following wildcard characters and character sets to refer to a set of files: @, #, ?, [xy], [x-z], [ax-z]. Table 6-1 “Wildcard Characters and Character Sets” shows the meanings of the wildcard characters and provides examples. Table 6-1 Wildcard Characters and Character Sets
Every path component specified in the file set expands to include all directories, accounts, or groups at the level that match the wildcard. So, for example, to store all files and directories at the third level below the root directory, the file set would be /@/@/@. If you include a trailing slash (/) in the file set, then all of the directory matches at the last component of the specified set are scanned recursively. For example, to store all files and directories at the third level below the root directory and any files and directories below that level, the file set would be /@/@/@/. You can use two options, TREE and NOTREE, to override the trailing slash on the file set. The TREE option forces every file set to be scanned recursively from the specified level, including any levels beneath it; the NOTREE option forces every file set to be scanned at the specified level. The following table shows examples of valid MPE/iX file sets for STORE and RESTORE. Table 6-2 Example File Sets for STORE/RESTORE
If you omit a list of files in the STORE command (except in conjunction with the DIRECTORY parameter), the default fileset is all files in your current logon group. You can also use character sets to name groups of files. A character set is a series of characters to substitute for a single character. For example, to store all files beginning with the character a, b, c, d, e, or f in the current working directory, enter:
Or, for example, to store all files ending with e, f, g, or 1 in the current working directory, enter:
You may specify a maximum of 16 characters for each fully qualified file designator part; you may not nest brackets. |
|