HP 3000 Manuals HP 3000 Manuals
STORE Options (contd)
Storing Files in Compatible Formats (TRANSPORT)
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
MOSET
NAME
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:
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 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:
:FILE T;DEV=TAPE
:RESTORE *T;@.@.@HFSACCT;SHOW;LOCAL
Alternately, you can specify a specific group and account to place the
HFS files, using the CREATE, GROUP, and ACCOUNT options:
:FILE T;DEV=TAPE
:RESTORE *T;@.@.@HFSACCT;SHOW;CREATE;GROUP=NEWGRP;ACCT=MYACCT
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:
:FILE T;DEV=TAPE
:RESTORE *T;@.@.@ - @.@.@HFSACCT;SHOW;CREATE
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.
Specifying the Number of Files to Store (FILES)
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:
:FILE T;DEV=TAPE
:STORE @.OPERATOR.SYS;*T;TRANSPORT;FILES=6000
Use the MPE/iX RESTORE command to restore files from MPE V/E format
backup tapes to an MPE/iX system. MPE/iX RESTORE automatically detects
that the tapes are in MPE V/E format, and invokes CM(RE)STORE
(Compatibility Mode Restore) to restore the files.
Managing File Security (COPYACD and NOACD)
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.
Storing Files with Certain File Codes (FCRANGE)
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:
:FILE T;DEV=TAPE
:STORE @.LETTERS.PERSONEL;*T;FCRANGE=1100/1102,1152/1153
Improving Storing Efficiency by Increasing Record Size (MAXTAPEBUF)
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 .
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 |
| |
| MO 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:
FILE T;DEV=TAPE
STORE @.OPERATOR.SYS;*T;MAXTAPEBUF
Notification of File Availability (NOTIFY)
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 online 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
Then, run STORE with the NOTIFY option:
:FILE T;DEV=TAPE
:STORE @.PUB.SYS;*T;SHOW;ONLINE;NOTIFY
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.
Additional Backup Information (STATISTICS)
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
or MOSET options), 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% |
| |
_________________________________________________________________________________________
Storing Files from Volume Sets (ONVS)
To store the files on a particular volume set, use the ONVS parameter of
the STORE command. ONVS lets you store files from up to 20 volume sets
at once. For example, to store all files from the nonsystem volume sets
named VOL_SET_A and VOL_SET_B, enter:
:FILE T;DEV=TAPE
:STORE @.@.@;*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
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.
Storing Files from Split Volumes (SPLITVS)
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:
1. Request users to close the files on the volume sets that are to be
backed up for a short duration.
2. VSCLOSE the mirrored volume set with the SPLIT option.
3. VSOPEN the volume set. This will open the user and backup sets.
4. Allow users to begin accessing the files again.
5. Issue the store command, using the SPLITVS option. For example:
:STORE @.@.@;*T;SHOW;SPLITVS=my_split_set
6. 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 (30349-90003).
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.