HP 3000 Manuals HP 3000 Manuals
Storing Files in Compatible Formats (TRANSPORT)
The TRANSPORT option stores files on media that is compatible with:
* MPE V/E systems
* Pre-POSIX systems
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 NMSTORE options:
STORESET
INTER
DIRECTORY
ONVS
FCRANGE
SPLITVS
ONLINE
MAXTAPEBUF
MOSET
NAME
COMPRESS
TREE
NOTREE
RENAME
NOTIFY
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 sytem and restored on a pre-POSIX system (4.0 or earlier).
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 file set 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 file names, 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.