Basic Backup Procedures; Backup Guidelines And Examples - HP BACKCOPY Reference Manual

Table 9 BACKUP Completion Codes (continued)
Code Description
2 An abnormal, voluntary termination with errors. BACKUP could not copy one or more files because of
errors on the tape or disk. The tape is left in a consistent state minus the files in error. For example, if
BACKUP encounters a corrupt file, it skips the file and continues with the next file.
3 A premature, voluntary termination with fatal errors. BACKUP terminated because of a fatal error or an
invalid user command. The tape generated might be incomplete.
4 The BACKUP process never got started. This completion code is generated by the TACL process executing
BACKUP. TACL returns the process creation error in the terminationinfo field.
5 The BACKUP process calls ABEND on itself. This code is the default completion code for the ABEND
procedure.

BACKUP Guidelines and Examples

Table 10 BACKUP Guidelines and Examples
Topic

Basic Backup Procedures

Backing Up Format 1 and Format 2 Files
Using Qualified File-Set Lists
Backing Up SQL Files
Backing Up or Converting DP1 and DP2 Files
Backing Up With Labeled Tapes
Backing Up in Volume Mode
Basic Backup Procedures
When you back up files, you use a qualified file set (QFS) to specify the set of files to back up. All
files in the QFS must originate from the same node; you cannot specify two nodes in the BACKUP
command. BACKUP records the names of the files in the QFS in local internal format, without a
node identifier (volume.subvol.file-id).
Although the files in the QFS all originate from one node, they might have implicit relationships
with files on other nodes. For example, a file might be partitioned over several nodes, or a base
table might reside on one node while its indexes reside on another. Unless you specify otherwise,
BACKUP backs up these related files along with the files in the QFS. BACKUP stores the names of
files from other nodes in remote internal format (node-number.volume.subvol.file-id) to
prevent accidental overwriting of files that have the same names.
NOTE: The terms local and remote have a different meaning for QFS. Local implies the node
specified in the QFS. Remote implies other nodes on the same network as the QFS.
The change in definition of "local" eliminates ambiguous file names that were caused by implicitly
named files; for example, an SQL table that is remote in relation to where BACKUP is run and that
has an index that is local in relation to the BACKUP utility. For example, if you perform this BACKUP
command from one system (\A):
BACKUP $Tape, \B.$Vol.Subvol.Table1
where the file (Table1) is an SQL table on a remote node (\B) that has an index (TInd1) local to
system \A. The index (TInd1) is being backed up implicitly with the Table1 file.
Prior to the D30.00 RVU, the NonStop files were backed up using:
$Vol.Subvol.Table1
\A.$Vol.Subvol.TInd1
After the D30.00 RVU, files are backed up using:
72 BACKUP
Page
(page 72)
(page 73)
(page 74)
(page 74)
(page 76)
(page 77)
(page 80)