Storing Files [ Performing System Operation Tasks ] MPE/iX 5.0 Documentation
Performing System Operation Tasks
Storing Files
The next sections teach you how to store:
* a single file, a group of files, or all files on the system
* all files in a set that you specify, excluding files that you
don't want to store
* a set of files that share the same file codes
* a set of files accessed after a certain date, or files that have
not been accessed since a certain date
* a set of files on a particular volume set
In addition, you will learn how to respond to tape requests, monitor the
progress of the STORE command and display information about the files you
are storing.
To store a single file
1. Select a tape and place the tape drive online.
2. Mount the tape.
3. At the console, enter:
FILE T;DEV=TAPE
STORE filename.groupname.accountname;*T
You may also omit the device parameter (as shown in the example
below). In this case, MPE/iX creates a default file equation with
your username.
STORE filename.groupname.accountname
For example, to store the file MYFILE in the group PERSONAL in the
account SYS, enter:
STORE MYFILE.PERSONAL.SYS;*T
If you are storing a file using HFS syntax, enter:
STORE path/filename;*T
For example, to store my_file in the directory my_dir, enter:
STORE /my_dir/my_file;*T
To monitor STORE command progress
After you enter a STORE command, STORE issues a message similar to the
following on the console:
STORE/RESTORE VERSION A.21.01 (C) 1986 HEWLETT-PACKARD CO.
TUE, JAN 6, 1990, 2:57 PM
Monitor the console for additional messages. STORE sends you messages
when you need to reply to a tape request, to add a write ring to a tape
reel, or to mount a new tape on a backup device.
To respond to tape requests
When your backup devices are not configured to be automatically
allocated, the system answers your STORE command with one or more tape
requests. See chapter 1, "Managing Tapes and Tape Drives" for more
information on tape requests.
If you have previously issued a FILE command that included the backup
device's LDEV number, the tape request asks you to confirm that number.
For example,
?14:57/#S25/43/IS "T" ON LDEV #8 (Y/N)?
To request progress messages
Use the PROGRESS parameter in your STORE command to display progress
messages at regular intervals. To request progress messages every 5
minutes, enter:
STORE fileset;PROGRESS=5
The system displays progress messages every 5 minutes.
STORE OPERATION IS 4% COMPLETE
You see similar messages at regular intervals, for example:
STORE OPERATION IS 7% COMPLETE
STORE OPERATION IS 11% COMPLETE
STORE OPERATION IS 14% COMPLETE
If you use the PROGRESS parameter alone, without specifying an interval,
STORE displays progress messages every minute.
To mount additional tapes
When STORE has filled a tape but there is additional information to
store, it asks you to mount another tape. You see a mount request and an
LDEV NOT READY message like the ones below:
15:28/#S43/59/MOUNT REEL 2 FOR STORE ON LDEV 8
15:29/#S43/59 LDEV 8 NOT READY
To mount another tape:
1. Unload the first tape and stack it, label side down, on top of any
tapes previously written on this drive during the current STORE
operation. Remove the write ring.
2. Select the next tape from the prepared stack near the backup
device. If there are no more tapes prepared, prepare a new tape,
following the instructions in this chapter.
3. Mount the new tape.
4. Continue monitoring the backup process. Mount new tapes as the
system requests them.
When you see the END OF PROGRAM message, the STORE process is complete.
To be absolutely sure that important files have been stored correctly, it
is a good idea to check the file listings and verify that stored files
were copied correctly.
To store several files
To store two or more files at the same time, list all the files but
separate their names with commas. For example:
FILE T;DEV=TAPE
STORE FILE1.PUB.RESEARCH,FILE2.PUB.ACCTING;*T
Or you can use HFS syntax to specify the files. For example:
FILE T;DEV=TAPE
STORE /RESEARCH/PUB/FILE1,ACCTING/PUB/FILE2;*T
To store all files in a single group or account, use a wildcard
specification. For example, to store all files and directories in the
current working directory, enter:
STORE ./@;*T
Or, for example, to store all files and directories in the current
working directory and in directories below it that conform to MPE syntax,
enter:
STORE ?@/;*T
Consult Table 6-1 for a list of wildcard characters and character sets.
For additional examples for specifyig file sets, see Table 6-2.
To rename files stored to tape
Occasionally, you may need to rename files as they are stored to tape.
For example, renaming files is necessary when the accounting structure of
the source machine (the computer where the files are being copied from)
is different from that of the target machine (the computer where the
files are being copied to). To do so, you can use the RENAME parameter
of the STORE command.
To copy and rename a file from a source system to tape, create a file
equation and specify the source file set (those files on the source
system) and the target file set (those on the target system) as shown
below.
FILE T;DEV=TAPE
STORE source = target : creator;*T;RENAME
You may specify the file sets using either MPE or HFS syntax. For more
information on renaming files, refer to Volume II of the MPE/iX Commands
Reference Manual Volumes 1 and 2 (32650-90003 and 32650-90364).
To exclude subset files
At times it may be easier to describe the set of files you want to store
as a large set minus a certain subset. For example, suppose you want to
store all files in all groups of the PERSONEL account except the files in
the FORMS group. Describe the set of files to store as shown in the
following example:
FILE T;DEV=TAPE
STORE @.@.PERSONEL - @.FORMS.PERSONEL;*T
NOTE When you use the minus sign (-) to indicate a set of files to
exclude, you must precede and follow it with a space. Otherwise,
MPE/iX will interpret it as part of the preceding file name, since
the minus sign is a valid character in HFS syntax.
You can describe as many excluded subsets for a set of files as you need
(unless you are creating an MPE V/E store tape, which allows only one
excluded subset). For example, to store all files in the PERSONEL
account except the files in the FORMS and RECORDS groups, enter:
FILE T;DEV=TAPE
STORE @.@.PERSONEL -@.FORMS.PERSONEL -@.RECORDS.PERSONEL;*T
For more information about MPE V/E store tapes, read "To create MPE V/E
compatible STORE tapes" later in this chapter.
Another way you can use excluded subsets is to store all files and
directories that are outside of MPE syntax (that is, create a tape with
only HFS-syntax files and directories on it). To do so, enter:
FILE T;DEV=TAPE
STORE / - @.@.@;*T
To store multiple sets of files
Store multiple sets of files the same way that you store more than one
individual file. Separate the file sets with commas in your STORE
command. For example, to store all files in the PERSONEL account except
the files in the FORMS group and all files in the PAY group of the ACCTG
account, enter:
FILE T;DEV=TAPE
STORE @.@.PERSONEL-@.FORMS.PERSONEL,@.PAY.ACCTG;*T
To store files according to dates
Use the DATE parameter to store only files that have not been accessed
since a certain date. This enables you to do, among other things, a
partial system backup. For example, suppose a full system backup was
performed on May 30, 1994. The following STORE command would copy all
system and user files modified since that date:
FILE T;DEV=TAPE
STORE /;*T;DATE<=05/30/94
You must enter the date in the mm/dd/yy format (as shown above) or as
mm/dd/yyyy (for example, 05/30/1994). The files stored include any that
were modified on the same date as the date entered, and those modified
since the specified date on nonsystem volume sets that are online.
Use this form of the DATE parameter when you perform regular backups of a
file set. For example, store the entire set (a full backup) once a week
and store only those files modified since the full backup on all other
days.
To store files after a certain date
You can also use the DATE parameter to store only files that have not
been accessed since a certain date. For example:
FILE T;DEV=TAPE
STORE /SYS/OPERATOR/@;*T;DATE<=05/30/94
You may enter the year as two digits or four digits (94 or 1994). You
may want to use this form of the DATE parameter with the PURGE parameter
to remove out-of-date files from your system. Refer to the next section
for more information.
To remove stored files from the system: archiving files
If your system contains infrequently used or out-of-date files, you can
store them onto tape and permanently remove them from the system disks at
the same time. This process, called archiving files, increases available
space and provides a backup copy of the files in case you need them in
the future.
To store disk files to tape and then delete the disk files in a single
operation, use the PURGE parameter of the STORE command. For example, to
copy all files in the OLD group of the account ACCTG to tape and delete
the files from disk, enter:
FILE T;DEV=TAPE
STORE @.OLD.ACCTG;*T;PURGE
PURGE deletes the files only after it has successfully stored all of
them. Thus, if STORE terminates in the middle of the process, it does
not purge any files.
You can combine the DATE and PURGE parameters to archive unused files
periodically. For example, the following STORE command stores to tape
all files in the personnel directory that have not been accessed since
September 2, 1994, and then deletes the disk files:
FILE T;DEV=TAPE
STORE /personnel/@;*T;DATE<=09/02/94;PURGE
To use the PURGE parameter with a privileged file or files, you must have
system manager (SM), system supervisor (OP), or privileged mode (PM)
capability. PURGE requires you to have write access to the file in order
to purge it.
You may want to warn users before you archive files and inform them how
to request to have archived files restored. If you need to restore
purged files to the system, you can find them on the tape to which you
stored them and on the tapes from the last full system backup you
performed before you purged the files.
To create MPE V/E compatible STORE tapes
Use the TRANSPORT parameter of STORE to create STORE tapes that are
compatible with MPE V/E. For example, to store all of the files in the
PERSONEL account onto an MPE V/E compatible tape, enter:
FILE T;DEV=TAPE
STORE @.@.PERSONEL;*T;TRANSPORT
You cannot use HFS syntax to specify the file set when you use the
TRANSPORT parameter.
The tape that is produced with the TRANSPORT parameter uses the same
format as MPE V/E STORE tape format. Therefore, files that are not
compatible with MPE V/E (due to file/record size limitations or new file
types), are not stored if TRANSPORT is specified. Also, the TRANSPORT
parameter is not valid if DIRECTORY, ONVS, or FCRANGE is specified.
By default, MPE V/E stores a maximum of 4000 files at a time. If you are
storing more than 4000 files using the TRANSPORT parameter, use the
FILES= parameter to specify the maximum number of files to be stored. If
you do not use the TRANSPORT parameter, the FILES= parameter is not
necessary; if included, it is ignored. For example, to set the maximum
number of files stored to 6000 for a TRANSPORT tape, you might enter the
following:
FILE T;DEV=TAPE
STORE @.OPERATOR.SYS;*T;TRANSPORT;FILES=6000
You cannot use the character set specifications shown in Table 6-1 with
the TRANSPORT parameter.
Use the MPE V/E RESTORE command to restore files from MPE/iX TRANSPORT
tapes to an MPE V/E system. On restore, the backup system automatically
detects a TRANSPORT tape and performs the necessary file format
translation.
To store files from volume sets
To store the files on a particular volume set, use the ONVS parameter of
the STORE command. ONVS lets you store files from as many as 20 volume
sets at once. For example, to store all files from the nonsystem volume
sets named VOL_SET_A and VOL_SET_B, enter:
FILE T;DEV=TAPE
STORE /;*T;ONVS=VOL_SET_A,VOL_SET_B
To store files from system and nonsystem volumes, include the system
volume set name within the ONVS parameter. For example:
FILE T;DEV=TAPE
STORE @.@.@;*T;ONVS=MPEXL_SYSTEM_VOLUME_SET,&
VOL_SET_A,VOL_SET_B
MPE/iX 5.0 Documentation