Whenever you store a set of files, the system displays the total number of
files stored at your terminal. If there was an error, it also displays the
number and names of files not stored and the reason each was not stored. Use
the SHOW parameter and its options to display the names
and additional information about the files stored and to list them
on your system printer as well as at your terminal.
Internally, the STORE program writes information about the files it
stores to a file with the formal file designator SYSLIST. It prints
file information at your terminal by equating SYSLIST with the
standard listing device for your session (your terminal). You can redirect the
file information to another file or device by issuing a FILE command
that assigns SYSLIST to that device or file. For example, you might
want to redirect the file information to a disk file so that you can keep it
online for your records.
To write STORE information to the disk file, SHOWFILE, enter:
:FILE SYSLIST=SHOWFILE;DEV=DISC
To print information on the files you stored at the system printer as well as
at your terminal, use the SHOW=OFFLINE option:
To redirect the OFFLINE listing to another file or device, issue the following
FILE command, it will send a copy of the STORE listing to the
disk file SHOWOFFL:
:FILE OFFLINE=SHOWOFFL;DEV=DISC
To generate a store listing to the terminal as well as to a disk file, 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 files stored. Using the SHOW parameter, you can
choose to display file information in either long or short form.
A short file display prints the file's full name, volume restrictions, number
of sectors, file code, and media number for each file you store.
In addition to there being a long and a short SHOW listing, there are
also two different versions of each - MPE and HFS. The type of listing printed
depends on the input fileset list. You will get a HFS style listing if:
At least one file in the fileset list is specified in HFS
syntax.
A fileset wildcard is expanded to include a HFS syntax
file.
The HFS style listing contains the same information as the MPE style listing.
The only difference is that the filename is printed as an absolute pathname at
the end of the line.
Since HFS pathnames can be variable lengths, and can be quite
long, they are placed at the end of the line so that they do not
affect the spacing of the other columns. If the name does not fit
on one line, it wraps to the next line. An asterisk (*) is placed
at the last column of the line to indicate that the rest of the
filename continues on the next line.
NOTE: It is likely that a STORE with the fileset @.@.@
will result in a HFS format listing, since MPE/iX,
by default, contains some HFS-named files.
To display the list of files stored using the short form in MPE format, use the
SHOW=SHORT option in your STORE command. For example:
A long file display contains the same information as a short
file display plus each file's ending media number, record size,
blocking factor, maximum number of extents allowed, end-of-file,
and file record limit.
Once again, there are two formats for the long listing --
MPE and HFS. The HFS format contains the same information as the
MPE format, except that the variable-length HFS filename is at the
end of the line. It will be wrapped in the same was as the short
listing if the filename length exceeds the line length.
To display the list of files stored using the long form in
MPE format, use the SHOW=LONG option. For example:
If you use the SHOW parameter, but do not specify either LONG
or SHORT, the system displays files in short form when the record size
of the output device or file (SYSLIST) contains fewer than 132
characters in native mode and 114 characters in transport mode. The system
displays files in long form when the record size is equal to or greater than
132 characters in native mode and equal to or greater than 114 characters in
transport mode.
You can combine either LONG or SHORT with any of the other
SHOW options, except NAMESONLY, but you cannot specify both
LONG and SHORT at the same time within a STORE
command.
Displaying File Dates
To display each file's creation date, last access date, and last modification
date for the files stored, use the SHOW=DATES option. For example:
When the output listing is in HFS format, an additional field is added to the
dates display. The STATE_CHANGE field indicates the last date that a file
attribute was changed. An example listing is:
Figure 6-7 "File Date Information (HFS
Format)" illustrates a file listing created from the above example in HFS
format.
Figure 6-7 File Date Information (HFS Format)
To display file security information for the files stored, use the
SHOW=SECURITY option. The listing includes the file creator's user and
account name, the security matrix, and a flag indicating the presence or
absence of an ACD. The HFS format displays the same security information. For
example:
Figure 6-8 "File Security Information"
illustrates a file listing with security information from the above example.
Figure 6-8 File Security Information
The SHOW=NAMESONLY allows an abbreviated listing to be displayed.
The only fields shown are the starting and ending media number,
and the name of the file. This option is most useful when displaying
HFS syntax files. Since they can be longer than MPE syntax names,
it is sometimes useful to allow more room on the line to display
the full pathname. NAMESONLY cannot be used with the SHORT or
LONG options to SHOW. It has a slightly different format for
MPE and HFS. The HFS style has the filename as the last field, while the
MPE style has the filename as the first field.
Figure 6-9 "Names Only Format" is an example
for HFS format.
Figure 6-9 Names Only Format
If SHOW=PATH is specified, the output STORE listing will be
in HFS format, even if no HFS syntax files are being stored. You
may want to use this so that all of your listings appear in the
same format.
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.
This additional information is a single character, immediately following the
volume restrictions field. The values and meanings for this character
are as follows:
&
After image file label data exists for this file, since the file label
was modified before the sync point occurred. Only backups created with
ONLINE=END will have files with after image file label
data.
#
After image data exists for this file, since the file was modified
before the sync point occurred. Only backups created with
ONLINE=END will have after image file data.
+
This file was created during the backup, before the sync point
occurred. Only backups created with ONLINE=END will have newly
created files flagged this way.
-
This file was deleted or renamed out of this backup before the sync
point occurred. These files will not be restored by RESTORE. Backups
created with ONLINE=START and ONLINE=END can have files
flagged this way.
An example of these flags follows. Note that FOO5 was modified during the
backup, FOO6's file label information was updated, FOO9 was removed from the
backup, and FOO1 was added to the backup.
When STORE encounters an error, it either automatically recovers
or terminates, depending upon the nature of the error and the error
recovery method you choose.
Unrecoverable Errors
The following unrecoverable errors always cause STORE to terminate:
A command syntax error.
An error in the file system directory.
An error opening a backup device or an indirect file. An indirect
file is a text file containing STORE commands and options.
Refer to "Using Indirect Files", in Chapter 5, "Storing
Files".
Disk Read Errors
If STORE encounters a disk read error while storing a file,
it skips the remainder of that file and sends an error message to
the standard listing device describing the offset from the start
of the file and the number of bytes that have been lost. STORE
then continues to copy the remainder of the files.
The STORE operation does not terminate. Since the files
that contain disk errors are not stored, you will not be able to
restore them.
Media Errors
When a media error occurs while writing to a output device, the behavior of
STORE depends on the value of the ONERROR option, as
explained below.
Tape Error Recovery
The STORE command's ONERROR parameter lets you specify a
backup error recovery procedure. Your options are ONERROR=QUIT and
ONERROR=REDO. REDO is the default. QUIT instructs
STORE to abort upon encountering a backup I/O error while
REDO instructs STORE to continue after encountering an I/O
error.
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 file or device to which you have assigned the file 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. After you mount
the new reel, STORE automatically stores all the files from the point
where the bad reel began.
The message is similar to the following:
The user sees:
STORE ENCOUNTERED MEDIA WRITE ERROR ON LDEV #
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 #
Optical Disk Errors
If an optical disk write error is encountered, STORE displays the same error
messages that it would display for tape backup devices.
You can determine which piece of media is has been marked bad by using the
STATUS command of the MOUTIL program. The status display
indicates which piece of media is bad by showing "THE MEDIA IS BAD" in
the media name field. If a disk write error occurs while storing to a disk
file, STORE aborts, irrespective of what ONERROR option was specified.
Bad Media
Once a piece of media has been marked bad, it should not be used for future
STORE operations. If a media that has been marked bad is mounted for
use in a STORE operation, STORE will issue the following
message to the console:
MEDIA ON LDEV # IS BAD. CONTINUE ANYWAY?(Y/N)
If you reply YES, then STORE will write over this media. If you reply
NO, the media will be unloaded, and you should mount another piece of media.
NOTE:STORE will not check to see if a piece of media has been
marked bad if it is the very first reel mounted. Therefore, it is important
that once a reel has been marked bad by store, some note is made on the
physical label of the media to indicate that it encountered a write error while
storing to it.
The DATE option specifies which files are stored based on two
possibilities:
STORE files that have been modified since a specified date
STORE files that have not been accessed since a specified
date
Storing Files Modified Since a Specified Date
You can use the DATE parameter to store only files that were modified
or their states were changed since a specified date. (The state change date and
time are updated any time the file is renamed or an ACD is changed. However,
this information is not automatically shown. The state change date and time can
be different from the last modified date displayed with the LISTFILE
filename,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 files modified
since that date:
:FILE T;DEV=TAPE
:STORE @.@.@;*T;DATE>=09/30/93
The date must be entered in either the above format (mm/dd/yy)
or as mm/dd/yyyy (for example, 09/30/1993). The files
stored include any modified on the same date as the date entered. The files
stored also include 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 fileset. Store the entire set, for example, once a week and store
only those files that were modified or their states were changed
since the full backup the remaining six days.
NOTE: STORE uses the state change date when storing files with the
DATE parameter. To see the state change date, use the
FINFO(filename,42) and FINFO(filename,41)
functions.
The following command file displays the state change date and time for a
specific file, such as TSETUTIL in this example:
The year can be entered as two digits or four digits (93 or
1993). The above command stores any files in the OPERATOR
group of the 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 files from your system. Refer to
the next section.
If your system contains infrequently used or out-of-date files,
you can store them onto backup 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 and then
delete the disk files in a single operation, use the PURGE
parameter of the STORE command. For example:
:FILE T;DEV=TAPE
:STORE @.OLD.ACCTG;*T;PURGE
The command above stores all files in the OLD group of the account
ACCTG and deletes the files from disk. 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 periodically
archive unused files. For example, the following STORE command stores
to backup all files in the EMPRECS group of the PERSONEL
account that have not been accessed since February 2, 1992 and then deletes the
disk files:
NOTE: In order to use the PURGE parameter with a privileged
file or files, you must have system manager (SM), system supervisor (OP), or
privileged mode (PM) capability.
You may want to warn users before you archive files and inform
them how to request to have archived files restored. If you need
to restore purged files to the system, you can find them on the
piece of media to which you stored them and on the media from the
last full system backup you performed before you purged the files.
Use the PROGRESS parameter to display STORE command progress
messages at regular intervals. For example, to display progress messages every
five minutes, use the following command:
:FILE T;DEV=TAPE
:STORE @.@.@;*T;PROGRESS=5
If you use the PROGRESS parameter alone, without specifying an
interval, STORE displays status messages every minute.
If STORE is being run from a MPE session, the progress messages will
be send to the standard list ($STDLIST). Otherwise, the messages will go to the
system console.
The system directory keeps track of the accounts, groups,
users, and files 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. All HFS directories
on the system are also stored.
The following example will store all files on the system,
plus the system volume set accounting information.
:FILE T;DEV=TAPE
:STORE @.@.@;*T;DIRECTORY
To store nonsystem volume set directory information, use DIRECTORY and
ONVS in the same command. For example:
In the above example, the ONVS parameter will limit @.@.@
to only files that reside on the specified volume sets. Only the
directory information for groups and accounts on the specified volume
sets will be stored. The system directory information will NOT be
stored. See "Storing Files From Volume Sets" in this chapter for
more information.
As illustrated above, the DIRECTORY parameter of the STORE
command allows you to back up the system and/or
nonsystem volume set directories (account structure). You may then reload
the account structure in the event of a system disaster by restoring
the directory onto the system from the backup media. You have the
added flexibility of backing up the directories of nonsystem volumes
attached to the system as a part of or as a separate entity from
the system. This allows a nonsystem volume (volume set) to become
a separate reliable entity. System supervisor (OP) or system manager
(SM) capability is required to use the DIRECTORY parameter.
NOTE: When using the DIRECTORY parameter, the default fileset
list is empty. This allows a backup to be created that contains only directory
accounting information for the system volume set, or for the specified
volume sets.
Here is an example of how to back up the system directory and all other files
along with a nonsystem volume set directory and its files:
The TRANSPORT option stores files 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
files in the PERSONEL account onto an MPE V/E compatible backup, enter:
:FILE T;DEV=TAPE
:STORE @.@.PERSONEL;*T;TRANSPORT
The backup that is produced with the TRANSPORT parameter uses the same
format as MPE V/E STORE backup 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. The TRANSPORT
option cannot be used with the following STORE and TurboSTORE options:
STORESET
INTER
DIRECTORY
ONVS
FCRANGE
SPLITVS
ONLINE
MAXTAPEBUF
COMPRESS
TREE
NOTREE
RENAME
NOTIFY
LOGVOLSET
PART[IAL]DB
FULLDB
STOREDIR[ECTORY]
NOSTOREDIR[ECTORY]
STATISTICS
Character set specifications, as listed in "Using Wildcard Characters" in
chapter 5, "Storing Files," cannot be used with the TRANSPORT
parameter.
Creating Pre-POSIX Compatible Tapes
With the addition of HFS syntax files and other new POSIX-related features,
mechanisms exist in STORE to allow backups to be created on a POSIX
system and restored on a pre-POSIX system (4.0 or 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 files would need to be
transferred to a pre-POSIX system:
Planned Transport
The user stores off a set of files from one system, to be restored on
another system right away.
Unplanned Transport
The data stored off from a system (usually a system backup) is
suddenly required to be restored on the same or a different system.
This kind of transport is usually done to recover lost data and may
require a POSIX system's backup to be restored on a pre-POSIX
system.
With these two cases in mind, STORE has the following objectives with
respect to data transport:
The media created on a POSIX system should be restorable on a
pre-POSIX as well as a post-POSIX release.
The planned transport operation should be as simple
and easy as possible.
A default name conflict should not exist. This means that the
naming of non-MPE syntax files on a transport to a pre-POSIX system
should occur such that the user does not inadvertently overwrite
previously transported files.
For each of the transport situations, the security should be at
least equal to or more restrictive than require on the target
system.
The following sections list the features in STORE which address these
objectives.
HFS Name Mapping
Every POSIX STORE media is created such that any HFS syntax file can be
restored to a pre-POSIX system with a unique MPE syntax name. When restoring a
backup to a pre-POSIX system, the fileset of @.@.@HFSACCT will contain
all HFS syntax files on that media. These files are named with the MPE syntax
of:
F#######._HFSGRP._HFSACCT
Where ####### represents numbered files starting at 0000001.
A mapping file is also on the media. This file specifies the mapping between
the _HFSACCT name and the actual HFS name. The name of this file is
HFSMAP._HFSGRP._HFSACCT. Sample entries in the file would look similar
to this:
Since _HFSGRP and _HFSACCT are illegal MPE filenames, special
steps must be taken when attempting to restore these files on a pre-POSIX
system. The LOCAL option can be used to restore the HFS files into
your logon group. For example, on a pre-POSIX system, issue:
This will restore all of the HFS syntax files to the group
NEWGRP.MYACCT. The HFSMAP file will allow to you identify the real
names of the F####### files.
If you want to only restore MPE syntax files from the backup, that can be
accomplished by the following command:
NOTE: There are certain types of files that exist on a POSIX
system that have no equivalent on a pre-POSIX system, such as symbolic
links and device links. It is not recommended that you attempt to
restore these files on a pre-POSIX system. They will contain no
useful information for that system, and may be difficult to use or purge.
Preserving File Security
An argument of the TRANSPORT option allows POSIX style ACD's to be
translated to pre-POSIX systems, while maintaining the correct security. Using
TRANSPORT=MPEXL will cause STORE to write out the pre-POSIX
format ACD's. If a POSIX media is created without TRANSPORT=MPEXL, and
then restored to a pre-POSIX system, the ACD's will not be understood and the
system will enforce a "creator only" security. This provides a more restrictive
security. Also, all POSIX-related fields of the file labels being stored are
cleared on the backup media.
The FILES parameter works with the TRANSPORT parameter. By
default, MPE/iX 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 ignored. For example, to set the maximum number of files stored to
6000 for a TRANSPORT backup, you might enter the following:
Use the MPE/iX RESTORE command to restore files from MPE V/E format
backup tapes to an MPE/iX system. MPE/iX RESTORE automatically detects
that the tapes are in MPE V/E format, and invokes CM(RE)STORE
(Compatibility Mode Restore) to restore the files.
An additional way to manage the security of files being stored is to use the
COPYACD and NOACD options. The default is COPYACD.
This means that in addition to the MPE security matrix, a file's ACD (if one
exists) is written to backup. This allows you to store the extra security
information associated with an ACD.
If for some reason you want to store files without their ACD, the
NOACD option can be specified. This would remove the
extra security associated with ACD's, which may be desired if you
are moving files to a system where the current ACD's would be inapplicable or
undesired. When using these options, keep in mind that RESTORE also
has COPYACD and NOACD options. So, even if you create a
STORE media with ACD's, you have the choice at RESTORE time
to restore or not restore the ACD information.
Use the FCRANGE parameter to store files with certain file codes.
MPE XL file codes distinguish different types of files. You can
select up to eight file code ranges to store. For example, files
with codes 1100, 1101, and 1102 are HPWORD files. Files with codes
1152 and 1153 are SLATE files. To store all HPWORD and SLATE files
in the LETTERS group of the PERSONEL account enter:
Files are stored with greater efficiency by using the maximum
backup record (buffer) size allocated to a given backup device.
Performance increases because data transmission is more efficient
and because the amount of media used for interrecord gaps decreases.
The maximum backup record size of MPE/iX supported backup devices differs from
device to device and is shown in Table 6-1
"Maximum Tape Record Sizes"Table 6-1 Maximum Tape Record Sizes
Tape Drive
Record Size
HP 7974
16 KB
HP 7978A
16 KB
HP 7978B
32 KB
HP 7979
32 KB
HP 7980(XC,S,SX)
32 KB
DDS (all)
32 KB
3480
32KB
MAXTAPEBUF should be used when storing to magnetic tape, DDS, or 3480
cartridges. Currently, it is not necessary to specify MAXTAPEBUF when
storing to MO devices or disk files, since the maximum record size of 32K is
already being used.
Normally when a STORE command is issued, a default record size of 16
kilobytes is used. However, by using the MAXTAPEBUF parameter of the
STORE command, the maximum record size of the specified device is
automatically used. If multiple backup devices are specified, using the
STORESET parameter, in conjunction with MAXTAPEBUF,
STORE uses the maximum record size, which is the lowest common
denominator of the different devices. This is necessary to ensure that the
record sizes are the same on all volumes of the backup set.
NOTE: Do not use the MAXTAPEBUF parameter with a backup device
of 32 KB record size if you anticipate that you will later restore the backup
created to a backup device whose maximum record size is 16 KB. Restoring
a backup to a larger maximum record size device, on the other hand,
does not cause any problem.
To increase record size when storing files, use the MAXTAPEBUF
parameter in your STORE command. For example:
During the STORE process, the fileset that you are storing is usually
unavailable for modification. Files can be modified again after STORE
is completed. If you are doing an on-line backup using:
TurboSTORE/iX 7x24 True-Online Backup online
backup (using the ONLINE option only), the files
being stored are unavailable for a short time at the beginning of the
store. However, once they have been attached to STORE's
logging mechanism, they are available for modification.
TurboSTORE/iX 7x24 True-Online Backup with true-online
backup, (using the ONLINE option with
START or END), the files being stored remain
available and can be modified while the backup is occurring. Refer to
Chapter 7, "TurboSTORE/iX 7x24 True-Online Backup," for more
information.
The NOTIFY option can be used to help automate the process
of performing some action at the time where the files being stored
are available for modification, either at the end of the STORE,
at the end of the attach phase, or at the end of the sync point.
NOTIFY allows STORE to stream a user-specified job file
(using the MPE/iX STREAM command) either at the end of the attach
phase (while using ONLINE), at the end of a successful STORE
operation (normal backup), or at the end of the sync point
(ONLINE=START or ONLINE=END). The job file is specified by
the user by setting up a formal file designator named NOTIFY, prior to
running the store job. This job can contain various actions that notify users
that the files are free, start other jobs that modify the files, or allow users
back on to the system, for example.
If the specified job does not contain passwords, STORE will prompt the
user for the passwords if STORE is being run from a session. If
STORE is being run from a job and passwords are not present, the job
stream will fail.
When the job fails to stream, due to lack of passwords, or
other reasons, all error messages will be sent to the standard list
($STDLIST). All other output as the result of streaming the job
will also be sent to $STDLIST.
The following is an example of using the NOTIFY command in conjunction
with a user specified job file.
First, set up the file equation, using the FILE command:
:FILE NOTIFY=MYJOB.PUB.SYS
Where the job stream could contain, for example:
!JOB NOTIFY,MANAGER.SYS
!TELL @ Your files are now available!
!EOJ
Since this is an online store, the job stream will be executed
once the files have been attached, and a message would then be sent
to all users telling them that their files are now free to be accessed.
In addition to the counts of files stored and not stored that are normally
reported at the end of a backup, the STATISTICS option provides extra
data about the backup. This extra information includes:
Amount of data written to each piece of media for each parallel
set
Amount of time required to write each piece of media
Throughput for each piece of media
Number of retries incurred for each piece of media
If software compression is enabled with the COMPRESS option,
additional data on the amount of compressed data written, and compression
ratios and percentages is displayed.
If an online or 7x24 true-online backup is performed, then information on the
amount of log data written is displayed.
All data totals are shown in bytes. To convert these totals to sectors, divide
by 256.
When displaying the amount of backup data written, up to five columns of data
can be displayed, depending on what options were specified for the backup.
These columns display the following backup data information:
File Data
This is the amount of the backup that comes from the actual data in
files. Most of the data in your backup will be accounted for in this
column. If you are using software compression (COMPRESS=LOW or
COMPRESS=HIGH), then this is the total number of
uncompressed bytes of file data written. The actual,
compressed amount of data written is displayed in the "Compressed"
column.
Misc Data
This is data that STORE needs to write to the backup to manage what
files are on the backup, such as the STORE backup label and a media
directory. The amount of miscellaneous data on a backup is proportional
to the number, but not size, of files being stored.
Compressed
This column is only displayed if software compression was used to
create the backup (with COMPRESS=LOW or COMPRESS=HIGH).
It displays the total number of compressed bytes of file data written to
the backup. The ratio between this column and the file data column is
used to display the Compression ratios and percentages later in the
statistics listing.
Log Data
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 definition of
before and after image log data, refer to Chapter 7).
This total depends on how much activity occurred on the files being
backed up during the backup. This is a good total to check if your online
backup is taking longer or consuming more media than you think it should.
Such a slowdown could be attributed to too much activity on files being
stored, which slows down both the users and the online backup.
Total on Reel
This column is a sum of all the other columns displayed for this
particular piece of media. It represents the entire amount of data stored
for that media. Note that if software compression was used, then the
Compressed column, and NOT the File Data column, is used to compute the
media total. If no software compression is used, then the File Data
column is used.
These data columns are displayed for each piece of media written to during the
backup. If a parallel backup is performed (using the STORESET option),
then the media will be grouped by parallel
set. After all parallel sets are displayed, totals for each parallel
set, and then for the entire backup are displayed. Look for the
"Backup Total" line to determine the total amount of all data written
for the backup.
The Throughput section follows the data written columns. The
throughput for a particular piece of media is computed by dividing
the total amount of data written for a piece of media by the time
it took to completely write that data. The time required to switch
media is NOT accounted for in this computation. Only time spent
actually writing the media is used. Also, note that if software
compression is being used, then the amount of compressed data written
is used to compute the throughput. Your virtual
throughput may actually be higher, if software compression is used.
The number of hardware retries encountered when writing the
data is also displayed here. This only applied to magnetic tape,
DDS, and 3480 media. It has no meaning when writing to disk files
or magneto-optical devices, and will always be zero. Monitoring
the number of retries for a piece of media is important in determining
if that media is starting to go bad. An increased number of retries
could indicate that the media should no longer be used, or that
your devices should be cleaned and/or serviced.
After the Throughput section, the total elapsed time for the
backup is displayed. This time does include media switches.
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 file data written is displayed with
the amount of data actually written when that file 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. Similarly, the higher the percentage, the better the
data compressed. A negative percentage is possible, and indicates
that the data you were storing did not compress at all. If you see
this in your statistics display, or see very low compression ratios,
it indicates that you are storing data that does not compress well,
and that it might be better not to use software compression, or
try a different software compression (LOW instead of HIGH, for example).
NOTE: These compression ratios are highly dependent on the
type of data being stored, and may vary from the Hewlett-Packard
supplied compression ratios. In general, data files will compress
better than application and system files. You should carefully pick
the type of data compression used to match the type of data being stored.
Following are examples of output from the STATISTICS options.
Example 1
The following example is of a normal backup to a single device
without software compression or online backup.
BACKUP STATISTICS
DATA WRITTEN
FILE DATA MISC DATA TOTAL ON REEL
MEDIA 1 | 189826798 | 1389164 | 191215962
---------+-------------+-------------+-------------
BACKUP
TOTAL 189826798 1389164 191215962
THROUGHPUT
MEDIA START TIME MEDIA END TIME THROUGHPUT (K/S) RETRIES
MEDIA 1 11:45 AM 12:02 PM 177 K/S 0
TOTAL ELAPSED TIME: 0 hours, 17 minutes, 31 seconds
Example 2
The following example is of a backup to two pieces of media.
BACKUP STATISTICS
DATA WRITTEN
FILE DATA MISC DATA TOTAL ON REEL
MEDIA 1 | 13538720 | 166480 | 13705200
MEDIA 2 | 176288078 | 747888 | 177035966
---------+-------------+-------------+-------------
BACKUP
TOTAL 189826798 914368 190741166
THROUGHPUT
MEDIA START TIME MEDIA END TIME THROUGHPUT (K/S) RETRIES
MEDIA 1 11:41 AM 11:41 AM 669 K/S 0
MEDIA 2 11:41 AM 11:45 AM 835 K/S 0
TOTAL ELAPSED TIME: 0 hours, 3 minutes, 49 seconds
Example 3
The following example is of a backup to parallel devices with software
compression and online backup.
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 6144 22509668
SET 3 FILE DATA MISC DATA COMPRESSED LOG DATA TOTAL ON REEL
MEDIA 1 | 59869176 | 164384 | 8199956 | 0 | 8364340
---------+-----------+----------+-----------+----------+------------
SET 3
TOTAL 59869176 164384 8199956 0 8364340
SET TOTALS
SET 1 | 63344322 | 418976 | 36349232 | 0 | 36768208
SET 2 | 66652980 | 307716 | 22195808 | 6144 | 22509668
SET 3 | 59869176 | 164384 | 8199956 | 0 | 8364340
---------+-----------+----------+-----------+----------+------------
BACKUP
TOTAL 189866478 891076 66744996 6144 67642216
THROUGHPUT
MEDIA START TIME MEDIA END TIME THROUGHPUT (K/S) RETRIES
SET 1
MEDIA 1 12:15 PM 12:19 PM 147 K/S 0
SET 2
MEDIA 1 12:15 PM 12:18 PM 100 K/S 0
SET 3
MEDIA 1 12:15 PM 12:17 PM 50 K/S 0
TOTAL ELAPSED TIME: 0 hours, 4 minutes, 3 seconds
COMPRESSION
FILE DATA COMPRESSED RATIO PERCENTAGE
SET 1
MEDIA 1 63344322 36349232 1.7:1 43%
SET 2
MEDIA 1 66652980 22195808 3.0:1 67%
SET 3
MEDIA 1 59869176 8199956 7.3:1 86%
BACKUP TOTAL 189866478 66744996 2.8:1 65%
To store the files on a particular volume set, use the ONVS parameter
of the STORE command. ONVS lets you store files from up to 20
volume sets at once. For example, to store all files from the nonsystem volume
sets named VOL_SET_A and VOL_SET_B, enter:
NOTE: Although the ONVS and SPLITVS options can be
used together, a volume set that is specified for ONVS cannot be
specified for SPLITVS and a volume set that is specified for
SPLITVS cannot be specified for ONVS.
Use the SPLITVS option to store files that are located on the
specified split volume sets. These volumes are also known as mirrored
disks.
This provides a form of concurrent, or online backup, because
you can:
Split a volume set.
Allow users to access their files
Perform a backup on the mirrored volume
The SPLITVS option requires:
The Mirrored Disk/iX product be installed on the system.
The specified volume sets must be configured as mirrored
volumes.
The basic procedure to use split volumes and STORE together is:
Request users to close the files on the volume sets that are to be
backed up for a short duration.
VSCLOSE the mirrored volume set with the SPLIT
option.
VSOPEN the volume set. This will open the user and backup
sets.
Allow users to begin accessing the files again.
Issue the store command, using the SPLITVS option. For
example:
:STORE @.@.@;*T;SHOW;SPLITVS=my_split_set
After the backup has completed, join the split set back together
using the JOINMIRRSET command in VOLUTIL.
For more information on using mirrored disks, see the Mirrored Disk/iX
User's Guide.
NOTE: Although the ONVS and SPLITVS options can be
used together, a volume set that is specified for ONVS cannot be
specified for SPLITVS and a volume set that is specified for
SPLITVS cannot be specified for ONVS.
When using the RENAME option, an original file refers to the original
disk file, and a target file indicates the final filename on the backup media.
Renaming a file requires the capabilities necessary to manipulate files across
groups and accounts. Table 6-2 "Required
Capabilities for RENAME" assigns capabilities to the different levels of
file renaming.
Table 6-2 Required Capabilities for RENAME
Capabilities Required
File
Group
Acct
Creator
File Creator
Yes
Yes
No
No
Account Manager (AM)
Yes
Yes
No
Yes
System Manager (SM)
Yes
Yes
Yes
Yes
System Supervisor (OP)
Yes
Yes
Yes
Yes
The RENAME option has the following syntax:
STORE file set [=targetname [:creatorname [.creatoraccount] ]]
[,file set[=targetname [:creatorname [.creatoraccount] ] ]]
;*TAPE;RENAME;SHOW
The fileset consists of the inclusion fileset and all exclusion
filesets. All legal filesets are allowed. The targetname can be
any legal MPE or HFS filename with the following restrictions on wildcards:
Each component of the file or pathname must either be equal to
@ or have no wildcards.
An HFS pathname which ends in a / can have no wildcards.
The trailing slash is used to designate a directory to place all
files.
Each component of the creator name must either be equal to @ or have
no wildcards. The account part of the creator name may be omitted.
The @ is used to specify that the component in the original
filename should be used for that component of the target filename.
When specifying HFS pathnames, components will be replaced from
the root on down. However, if the last component of the target pathname
is an @ the last component of the original pathname will
be used. If there is not a corresponding component for an @ in the
original pathname the file will not be stored.
The following tables illustrate sample translations for the target filenames:
STORE a.b.c=...;TAPE;RENAME;SHOW
Original Filename
Target Specification
Target Filename
A.B.C
x.y.z
X.Y.Z
A.B.C
@.y.z
A.Y.Z
A.B.C
x.@.z
X.B.Z
A.B.C
x.y.@
X.Y.C
STORE /A/B/C=...;TAPE;RENAME;SHOW
Original Filename
Target Specification
Target Filename
/A/B/C
@.y.z
C.Y.Z
/A/B/C
x.@.z
X.B.Z
/A/B/C
x.y.@
X.Y.A
STORE /a/b/c=...;TAPE;RENAME;SHOW
Original Filename
Target Specification
Target Filename
/a/b/c
@.y.z
/z/y/c
/a/b/c
x.@.z
/z/b/x
/a/b/c
x.y.@
/a/y/x
STORE /a=/@/x/@/y/@;*TAPE;RENAME;TREE;SHOW
Original Filename
Target Specification
Target Filename
/a/
/@/x/@/y/@
NOT STORED: *
/a/f1
/@/x/@/y/@
NOT STORED: *
/a/b/
/@/x/@/y/@
NOT STORED: *
/a/b/f2
/@/x/@/y/@
NOT STORED: *
/a/b/c/
/@/x/@/y/@
NOT STORED: *
/a/b/c/f3
/@/x/@/y/@
/a/x/c/y/f3
/a/b/c/d/
/@/x/@/y/@
/a/x/c/y/d/
/a/b/c/d/f4
/@/x/@/y/@
/a/x/c/y/f4
/a/b/c/d/e/
/@/x/@/y/@
/a/x/c/y/e/
/a/b/c/d/e/f5
/@/x/@/y/@
/a/x/c/y/f5
/a/b/c/d/e/f/
/@/x/@/y/@
/a/x/c/y/f/
/a/b/c/d/e/f/f6
/@/x/@/y/@
/a/x/c/y/f6
/a/b/c/d/e/f/g/
/@/x/@/y/@
/a/x/c/y/g/
/a/b/c/d/e/f/g/f7
/@/x/@/y/@
/a/x/c/y/f7
*Source name does not have component for subsitition
The following table illustrates sample translations for a target file directory
when the fileset specification was not a directory:
STORE /a/b=/w/x/y/z/;*TAPE;RENAME;TREE;SHOW
Original Filename
Target Specification
Target Filename
/a/b/
/w/x/y/z/
/w/x/y/z/b/
/a/b/f2
/w/x/y/z/
/w/x/y/z/b/f2
/a/b/c/
/w/x/y/z/
/w/x/y/z/c/
/a/b/c/f3
/w/x/y/z/
/w/x/y/z/c/f3
/a/b/c/d/
/w/x/y/z/
/w/x/y/z/d/
/a/b/c/d/f4
/w/x/y/z/
/w/x/y/z/d/f4
/a/b/c/d/e/
/w/x/y/z/
/w/x/y/z/e/
/a/b/c/d/e/f5
/w/x/y/z/
/w/x/y/z/e/f5
/a/b/c/d/e/f/
/w/x/y/z/
/w/x/y/z/f/
/a/b/c/d/e/f/f6
/w/x/y/z/
/w/x/y/z/f/f6
/a/b/c/d/e/f/g/
/w/x/y/z/
/w/x/y/z/g/
/a/b/c/d/e/f/g/f7
/w/x/y/z/
/w/x/y/z/g/f7
The following table illustrates sample translations for a
target file directory when the fileset specification was a directory:
STORE /a/b/=/w/x/y/z/;*TAPE;RENAME;SHOW
Original Filename
Target Specification
Target Filename
/a/b/
/w/x/y/z/
/w/x/y/z/
/a/b/f2
/w/x/y/z/
/w/x/y/z/f2
/a/b/c/
/w/x/y/z/
/w/x/y/z/c/
/a/b/c/f3
/w/x/y/z/
/w/x/y/z/c/f3
/a/b/c/d/
/w/x/y/z/
/w/x/y/z/c/d/
/a/b/c/d/f4
/w/x/y/z/
/w/x/y/z/c/d/f4
/a/b/c/d/e/
/w/x/y/z/
/w/x/y/z/c/d/e/
/a/b/c/d/e/f5
/w/x/y/z/
/w/x/y/z/c/d/e/f5
/a/b/c/d/e/f/
/w/x/y/z/
/w/x/y/z/c/d/e/f/
/a/b/c/d/e/f/f6
/w/x/y/z/
/w/x/y/z/c/d/e/f/f6
/a/b/c/d/e/f/g/
/w/x/y/z/
/w/x/y/z/c/d/e/f/g/
/a/b/c/d/e/f/g/f7
/w/x/y/z/
/w/x/y/z/c/d/e/f/g/f7
In a similar manner, the wildcard @ is used to specify the use of the
original creator name component in the new creator name. If no creator is
specified, the original creator is kept. This is equivalent to specifying
@.@ in the creator field. If the creator name is specified without an
account part, the account part of the creator name will be made equal to the
account of the new file.
There is an exception to this rule when the new filename does
not have a legal account name in its pathname. A directory off of
the root node that has a legal account name will be considered the
account for the creator. This is true whether this directory is
an account or not.
Table 6-3 "Creator File Translations" below
illustrates the translations for the creator. All files below in the "sg" group
of the "sa" account were created by "CREATOR.CRACCT."
Table 6-3 Creator File Translations
Original Filename
Target Specification
Target Creator
s1.sg.sa
d1.dg.da
CREATOR.DA
s2.sg.sa
d2.dg.da:@.@
CREATOR.CRACCT
s3.sg.sa
d3.dg.da:user.acct
USER.ACCT
s4.sg.sa
d4.dg.da:user
USER.DA
s5.sg.sa
d5.dg.da:user.@
USER.CRACCT
s6.sg.sa
d6.dg.da:@.acct
CREATOR.ACCT
s7.sg.sa
d7.dg.da:@
CREATOR.DA
s8.sg.sa
/d8
CREATOR.CRACCT
s9.sg.sa
/d9:@.@
CREATOR.CRACCT
s10.sg.sa
/d10:user.acct
USER.ACCT
s11.sg.sa
/d11:user
USER.CRACCT
s12.sg.sa
/d12:user.@
USER.CRACCT
s13.sg.sa
/d13:@.acct
CREATOR.ACCT
s14.sg.sa
/d14:@
CREATOR.CRACCT
s15.sg.sa
/ACCOUNT/GROUP/D15
CREATOR.CRACCT
s16.sg.sa
/ACCOUNT/GROUP/D16:@.@
CREATOR.CRACCT
s17.sg.sa
/ACCOUNT/GROUP/D17:user.acct
USER.ACCT
s18.sg.sa
/ACCOUNT/GROUP/D18:user
USER.CRACCT
s19.sg.sa
/ACCOUNT/GROUP/D19:user.@
USER.CRACCT
s20.sg.sa
/ACCOUNT/GROUP/D20:@.acct
CREATOR.ACCT
s21.sg.sa
/ACCOUNT/GROUP/D2:@1
CREATOR.CRACCT
If the SHOW option is specified, only the target names are listed. The
security option of the SHOW option displays the target creator name if
one is specified.
The ACD associated with a file is not changed when the file is renamed. As with
other STORE operations, the ACD is copied unless the NOACD
option is specified. If you need to change the ACD, use the ALTSEC command.
You can specify the same target file information for more than one org file.
However, when two or more files have the same name on a backup created using
the RENAME option, RESTORE will write the second file over
the first file.
The files excluded may only be specified on the original side
of the fileset. As with normal exclusion, there is no limit to the
number of excluded filesets. The example below shows an exclusion
file specification:
:STORE @.PUB.SYS -a -b -c -d=@.backup.sys:creator;*t;rename
Lockwords are not allowed on target files, and if specified
cause STORE to abort. The options that are not supported with
the RENAME option and will cause STORE to abort are:
By default, STORE uses the last character of a HFS filename to
determine if the specified file or fileset should be scanned recursively to
include all files below the specified wildcards or directories. If a filename
ends in a /, then it will be scanned recursively to include all files
below it in the hierarchical directory. Otherwise, the file or fileset is not
scanned recursively, resulting in a horizontal cut at its level in the
hierarchical directory. Using TREE and NOTREE can override
that default behavior.
If TREE is specified, ALL files and filesets are scanned recursively,
regardless of their ending character. If NOTREE is specified, then NO
files or filesets are recursively scanned, resulting in a horizontal cut in the
directory structure.
By using the new options PARTIALDB or FULLDB, you can back up
either a partial or an entire TurboIMAGE database and/or ALLBASE/SQL
DBEnvironment. The type of backup you are performing determines the type of
option you would use:
PARTIALDB can be used with a 7x24 true-online backup
(using ONLINE=START or ONLINE=END)
FULLDB can be used with a non-7x24 true-online backup
(all other backups)
Storing Database Files Using 7x24 True-Online Backup
When performing a 7x24 true-online backup using the ONLINE=START or
ONLINE=END options, by default, STORE backs up the entire database.
To back up a TurboIMAGE database, specify the name of the root
file only in the fileset list.
To back up an ALLBASE/SQL DBEnvironment, specify the name of the
DBE file.
Specification of the TurboIMAGE root file or the ALLBASE/SQL DBE file causes
STORE to store the entire database. If a dataset file is specified without the
root file, then STORE prints the following warning:
PARTS22.GROUP.ACCT NOT STORED: FILE IS PART OF AN IMAGE
DATABASE AND ROOT IS NOT SPECIFIED
If any of the dataset files are specified in addition to the
root file, no warning will be displayed but the individual dataset
files will be counted as redundantly specified files.
If you want to back up a partial database, you can use the PARTIALDB
option. STORE will backup only those dataset files specified in the fileset
list.
CAUTION: When using the PARTIALDB option, if the root file is
missing from the fileset list, the quiesce may not succeed (refer to Chapter 7,
"TurboSTORE/iX 7x24 True-Online Backup," for more information on quiescing).
STORE will still back up the dataset files listed in the fileset list.
Since quiescing a partial database cannot be guaranteed, we recommend that
PARTIALDBnot be used with a 7x24 true-online backup.
NOTE: Quiescing an ALLBASE/SQL database and storing the ALLBASE/SQL
database by TurboSTORE/iX 7x24 True-Online Backup when the DBEnvironment is in
normal use, has the same effect as using the STOREONLINE command of
SQLUtil. For a 7x24 true-online backup of ALLBASE/SQL to be of use for
rollforward recovery, use the same procedures you would use when doing the
STOREONLINE commands.
Storing Database Files Using Non-7x24 True-Online Backup
When performing a non-7x24 true-online backup (where you do not specify the
7x24 true-online backup options, ONLINE=START or ONLINE=END),
by default, STORE allows a partial database backup of only those database files
included in the fileset list. For example:
STORE parts01,parts02;...
Stores only database files parts01 and
parts02.
STORE parts@;...
Stores entire database parts as well as any files starting
with parts including positive and negative filecodes.
STORE parts;...
Stores only the TurboIMAGE root file parts or the ALLBASE/SQL
DBE file partsdbe.
If you want to store an entire database, use the new option, FULLDB.
To increase the ease and speed of file 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 file. This directory information allows RESTORE to more
quickly determine where files 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.
NOTE: This information in this file is also used to determine
if a file being restored has after image log data. A file will have
after image log data if it was modified before the sync point during
a 7x24 true-online backup. RESTORE must have this information before
restoring files, so when creating a 7x24 true-online backup with
the sync point at the end of the backup, the STOREDIR option
is automatically enabled. See Chapters 7 and 11 for more information on
creating and restoring 7x24 true-online backups.
The filename used by STORE uniquely identifies the file and associates
it with a specific backup. The file is placed in the store_dirs HFS
directory in the HPSTORE.SYS group.
WARNING! The HPSTORE group and store_dirs directory do NOT exist on the
system by default. You must create them, and set up the appropriate security
before using the STOREDIR option. STORE will NOT print a warning if it
cannot create the file because the path does not exist. See the following
paragraphs for information on creating and maintaining the HPSTORE group and
store_dirs directory.
This name contains the date and time of the backup and the pin of the STORE
process. This naming convention allows a LISTFILE,2 to show a
chronological list of STORE directory files.
You should not rename or purge STORE directory files that
you plan on using, since RESTORE looks for a specifically named
file. However, if the file does not exist, all files can still be
restored from the backup. The size of the directory file is directly
proportional to the number of files stored in the backup. You can
control how much disk space is used for these directory files by
putting a disk file limit on HPSTORE.SYS.
The following example limits the space used by the HPSTORE group to 4000
sectors:
:ALTGROUP HPSTORE.SYS;FILES=4000
You can have STORE associate a shorter, more meaningful name to the
disk directory files by specifying an optional filename argument to
STOREDIR. You can specify an MPE or HFS filename. STORE then
creates a symbolic link with the specified name, which points to the original
disk file.
For example, to create a full backup on Friday and give it the name
FRIFULL, issue the command:
:STORE /;*tape;STOREDIRECTORY=FRIFULL.HPSTORE.SYS
To create a partial backup of all files that were modified
since May 4, 1994, and create a disk directory filename, WedPartial,
in the current working directory, issue the command:
:STORE /;*tape;STOREDIR=./WedPartial;DATE>=5/4/94
If you want to create a 7x24 true-online backup with the sync point at the end
of the backup, and do not want a disk directory file to be created,
specify the NOSTOREDIRECTORY or NOSTOREDIR option on the
STORE command line.
With STORE, TurboSTORE/iX II, and TurboSTORE/iX 7x24 True-Online
Backup, you have the capability of simultaneously reading information
from different files on multiple disk drives and storing the accessed
information on the backup device in a single operation.
This process called interleaving allows you to match slow
input devices (such as disk drives), with fast output devices (such
as streaming tape devices). This effectively increases the input
rate.
By varying the number of concurrent input operations, the
effective input rate can be matched with the output rate. This allows
the backup to execute closer to the speed of the output device.
When you STORE files in interleave format, STORE:
Partitions the set of files to your backup device or
devices.
Opens the files. It may (depending upon file characteristics),
access several files at the same time.
Interleaves files on the same backup to make sure that your backup
device or devices operate at the highest speed possible.
Interleave format significantly reduces the time necessary
to store a large set of files, such as when performing a full system
backup. It merges the stream of data from multiple files on separate
disks into a single stream of data sent to the backup device or devices. If
necessary, STORE processes files out of sequence to keep backup
devices operating efficiently.
Interleave format is most efficient when your fileset is evenly
spread across two or more system disks. Use sequential devices or
parallel devices alone when the set of files to store is smaller
and less evenly distributed, such as when doing a partial backup,
or if the files are only coming from one disk.
To STORE files in interleave format, use the INTER parameter.
For example:
:FILE T;DEV=TAPE
:STORE @.OPERATOR.SYS;*T;INTER
When these files are restored, RESTORE will automatically recognize
the interleave format and restore the files properly.
Using the STORESET and INTER parameters together improves
backup time on large systems. For example, the following STORE command
uses both parallel device pools and interleaving to minimize backup time: