HP 3000 Manuals HP 3000 Manuals
STORE Options (contd.)
Renaming Files (RENAME)
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 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:
1. Each component of the file or pathname must either be equal to @
or have no wildcards.
2. 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: (1) |
| |
| /a/f1 /@/x/@/y/@ NOT STORED: (1) |
| |
| /a/b/ /@/x/@/y/@ NOT STORED: (1) |
| |
| /a/b/f2 /@/x/@/y/@ NOT STORED: (1) |
| |
| /a/b/c/ /@/x/@/y/@ NOT STORED: (1) |
| |
| /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 |
| |
-------------------------------------------------------------------------------------------
(1) Source name does not have component for substitution
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 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 Target Specification Target Creator |
| Filename |
| |
------------------------------------------------------------------------------------------
| |
| 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:
* PURGE
* TRANSPORT
* SPLITVS
Specifying HFS Files (TREE and NOTREE)
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.
Storing Database Files Using PARTIALDB or FULLDB
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 PARTIALDB not 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.
Creating a Disk Directory File (STOREDIRECTORY and NOSTOREDIRECTORY)
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.
The following naming convention is used:
store_yyyymmdd_hhmmsstt_pin##_day
For example:
/SYS/HPSTORE/store_dirs/store_19940622_13300314_pin30_wed
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.
Storing Files in Interleave Format (INTER)
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:
1. Partitions the set of files to your backup device or devices.
2. Opens the files. It may (depending upon file characteristics),
access several files at the same time.
3. 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:
:STORE @.@.@;;SHOW=OFFLINE;&
STORESET=(*T,*T),(*T,*T);INTER