Guardian Disk and Tape Utilities Reference Manual Abstract This publication describes the disk and tape utilities BACKCOPY, BACKUP, DCOM, DSAP, PAK/UNPAK, and RESTORE for the HP NonStop operating system.
© Copyright 2013, 2014 Hewlett-Packard Development Company, L.P. Legal Notices Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents What’s New in This Manual.........................................................................16 Manual Information................................................................................................................16 New and Changed Information................................................................................................16 About This Manual......................................................................................
BACKUP Options....................................................................................................................47 ALTFILE.............................................................................................................................47 Guidelines...................................................................................................................48 Example.............................................................................................................
Example......................................................................................................................62 PART................................................................................................................................62 Guidelines...................................................................................................................63 Example..................................................................................................................
Exiting DCOM.......................................................................................................................85 Stopping DCOM....................................................................................................................85 Completion Information...........................................................................................................85 Guidelines........................................................................................................
ALTFILE...........................................................................................................................127 Guidelines.................................................................................................................127 Example....................................................................................................................127 AUDITED.....................................................................................................................
OPEN............................................................................................................................144 PAGELENGTH.................................................................................................................144 Guidelines.................................................................................................................144 Example....................................................................................................................
Restoring Existing Disk Files...............................................................................................171 Restoring Using Name Mapping........................................................................................171 Restoring Files From Multiple Systems.............................................................................172 Restoring Files to a Different Network.............................................................................172 Qualified File Sets........
7031...................................................................................................................................190 7032..................................................................................................................................190 7033..................................................................................................................................190 7034.............................................................................................
7123...................................................................................................................................201 7124...................................................................................................................................201 7125...................................................................................................................................201 7126...........................................................................................
7519...................................................................................................................................215 7520..................................................................................................................................215 7523..................................................................................................................................215 7524.............................................................................................
7791..................................................................................................................................227 7792..................................................................................................................................227 7793..................................................................................................................................227 7794..............................................................................................
8030..................................................................................................................................239 8031..................................................................................................................................239 8032..................................................................................................................................240 8033..............................................................................................
8150...................................................................................................................................260 8151...................................................................................................................................260 8152...................................................................................................................................260 8153...........................................................................................
What’s New in This Manual Manual Information Abstract This publication describes the disk and tape utilities BACKCOPY, BACKUP, DCOM, DSAP, PAK/UNPAK, and RESTORE for the HP NonStop™ operating system. Product Version Utilities G06 Supported Release Version Updates (RVUs) This publication supports J06.03 and all subsequent J-series RVUs, H06.03 and all subsequent H-series RVUs, and G06.27 and all subsequent G-series RVUs, until otherwise indicated by its replacement publications.
• Added a new RESTORE option, EMULATEFSF (page 133). • Updated the Guidelines, in section PARTONLY (page 148). Changes to the 523325–015 Manual • Using the BACKUP process on open files can result in ERROR-3012. Added information about avoiding this error to OPEN (page 61). • Updated the recovery procedure for ERROR-3012 (page 273). • Added a new procedure and example TACL script for ???. Changes to the 523325–014 Manual Removed the procedure for restoring EKS files to classic key-sequenced files.
About This Manual This manual describes how to use these disk and tape utilities for the NonStop operating system: BACKCOPY Disk Space Analysis Program (DSAP) BACKUP (T9074) PAK/UNPAK Disk Compression (DCOM) RESTORE The G06 product version of the utilities cannot be executed on G-series preceding the G06.00 RVU. The D46 product version of the utilities cannot be executed on D-series preceding the D46.00 RVU. SPR Requirements for Increased Enscribe Limits for the H06.28/J06.17 Release As of H06.
Audience This manual is written for system operators, system managers, and all other users of the disk and tape utilities.
• SQL/MP Programming Manual for C • SQL/MP Programming Manual for COBOL • SQL/MX Installation and Management Guide • SQL/MX Programming Manual for C and COBOL • TACL Reference Manual Notation Conventions Hypertext Links Blue underline is used to indicate a hypertext link within text. By clicking a passage of text with a blue underline, you are taken to the location described.
… Ellipsis. An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times. For example: M address [ , new-value ]... [ - ] {0|1|2|3|4|5|6|7|8|9}... An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times. For example "s-char..." Punctuation. Parentheses, commas, semicolons, and other symbols not previously described must be entered as shown.
Nonitalic text. Nonitalic letters, numbers, and punctuation indicate text that is displayed or returned exactly as shown. For example: Backup Up. lowercase italic letters. Lowercase italic letters indicate variable items whose values are displayed or returned. For example: p-register process-name [ ] Brackets. Brackets enclose items that are sometimes, but not always, displayed.
Change Bar Notation Change bars are used to indicate substantive differences between this manual and its preceding edition. Change bars are vertical rules placed in the right margin of changed portions of text, figures, tables, examples, and so on. Change bars highlight new or revised information. For example: The message types specified in the REPORT clause are different in the COBOL environment and the Common Run-Time Environment (CRE).
1 Disk and Tape Utilities Overview This section briefly describes the disk and tape utilities of the NonStop operating system. The usage scenarios of most of these utilities are defined clearly by their basic functions.
Figure 1 BACKCOPY Utility BACKUP The BACKUP utility copies files from disk to magnetic tape. Using BACKUP minimizes the risk of losing valuable data by disk failure or human error. Information stored using BACKUP can be copied back onto your system using the RESTORE utility. BRCOM (T2721), the interface to Backup and Restore 2.0, coexists with the Backup and Restore utilities (T9074). CAUTION: The syntax for Backup and Restore 2.0 is different from the syntax for the Backup and Restore utilities (T9074).
DCOM The Disk Compression (DCOM) utility compresses the space used by disk files. DCOM moves allocated file extents (areas reserved for the growth of designated files) and free-space extents (unallocated areas) to different locations on a disk volume. DCOM consolidates the free-space extents, making larger extents available. After using DCOM to compress disk space, you can allocate new files with larger extent sizes. DCOM is for use by programmers, system operators, and system managers.
Figure 4 DSAP Utility PAK/UNPAK The PAK utility compresses NonStop files. PAK compresses Guardian files into a single unstructured archive file on any Expand-connected NonStop system. You can create a self-extracting archive file or use UNPAK to decompress the archive file when needed. PAK efficiently and compactly collects data, which is useful in situations such as transferring large numbers of files to the Global Customer Support Center (GCSC) for analysis.
Figure 5 RESTORE Utility Using BACKCOPY, BACKUP, and RESTORE The BACKCOPY, BACKUP, and RESTORE utilities are related programs that share common procedures: • Commands used by BACKUP and RESTORE are entered the same way, and both use qualified file-set lists. • All three utilities share a common procedure for mounting tapes on the tape drive. • The utilities can use the CLASS TAPE DEFINE to trigger $ZSVR to process a labeled-tape request.
Entering BACKUP and RESTORE Commands To enter commands in BACKUP and RESTORE, either: • Type a complete command at the command interpreter prompt: 1> BACKUP /HIGHPIN OFF/ $TAPE, \CSYS.$MYVOL.MYSUBVOL.*,& 1>& LISTALL This example shows how to use the HIGHPIN OFF option to back up files on D-series or G-series by using the TACL RUN command. By default, HIGHPIN OFF runs at a low PIN and is needed only if BACKUP was manually set to run at a high PIN.
Mount correct tape #n? Mount next tape #n? Mount previous tape #n? 7. 8. For each subsequent prompt, go to Step 5. When no more tape prompts appear, go to Step 9. If you used the NOPROMPT option, this noninteractive message appears: $tape: device not ready -- beginning to poll -- 9. Mount the first (or the next) tape. For each reel, the program continues when it detects that the drive is ready. When there are no more tape prompts, the process is complete.
A format 2 file is either a large format file, or a file that can contain larger partitions than a file created on RVUs preceding G06.00 or D46.00. A format 2 file has the potential of exceeding the 2 GB - 1 MB size limit of a format 1 file. For more information about handling format 1 and format 2 files, see the File Utility Program (FUP) Reference Manual. Tape Formats A tape used with the BACKCOPY, BACKUP, or RESTORE utilities can have one of the different tape formats listed in Table 3.
6 If the input files include DP2 files or the DP2FORMAT option is specified, tape format 2 is used. 7 Record size (BLOCKSIZE) for DP2 tapes can be an even value in the range 2 through 30, but BACKUP rounds the given BLOCKSIZE down to a multiple of 4 (unless BLOCKSIZE is 2). For details, see BLOCKSIZE (page 50). The default tape format for each version of the NonStop operating system is displayed in Table 5. Starting with the B00 software release, the default tape version is conditional.
2 BACKCOPY The BACKCOPY utility duplicates tapes that are made from a file-mode operation in BACKUP. It cannot to duplicate tapes that are made from a volume-mode BACKUP operation. For more information about BACKUP, see Chapter 3: BACKUP. BACKCOPY can create one or two duplicate tapes for archive storage, distribution, or disaster recovery. It can also create one or two labeled (or unlabeled) tape sets from a labeled or unlabeled tape set.
IN filename OUT listfile The IN option specifies input files, and the OUT option specifies the output files. These files usually override the home terminal as the input or output device. An IN file is a text file containing the remainder of the command line, including parameters and options. For a complete list of run-options and a description of the command interpreter RUN command, see the TACL Reference Manual. source-tape is the name of the tape drive that reads the backup tape.
ARCHIVEFORMAT specifies tape format 3 for dest-tape. If you specify two tape drives for dest-tape (to make two copies of the backup tape), ARCHIVEFORMAT is automatically selected. If you specify one tape drive and do not specify ARCHIVEFORMAT, the tape format is the same as the format on the original backup tape. CATALOGFILES specifies catalog information about disk files. For more information and examples, see the DSM/Tape Catalog User's Guide.
STARTSTOP | STREAM specifies the tape mode of the destination drive. It applies only to tape units that support streaming. STARTSTOP Tape speed is 50 ips (inches per second). Tape density is 12000 bpi (bits per inch). This mode writes one record to the tape at a time. STREAM Tape speed is 75 ips. Tape density is 12000 bpi. This mode writes one block to tape at a time. NOTE: You cannot use the DENSITY and TAPEMODE in the same BACKCOPY command.
Examples: Different Ways to Use BACKCOPY • To read an unlabeled backup tape on the device $TAPE1 and duplicate it on \REMOTE.$TAPE2: 1> BACKCOPY $TAPE1, \REMOTE.$TAPE2, *.*.*, LISTALL • To read a labeled BACKUP tape and create an unlabeled duplicate of it on $TAPE2: 2> ADD DEFINE =Input, CLASS TAPE, LABELS BACKUP, & 2> &VOLUME (FOX082,FOX004) 3> BACKCOPY =Input, $TAPE2, *.*.
Table 6 Completion Codes Returned by BACKCOPY and the Operating System (continued) 38 Code Description 3 A premature, voluntary termination with fatal errors. BACKCOPY terminated because of a fatal error or an invalid user command, and the copy generated might not be complete. 4 BACKCOPY never started. This completion code is generated by the TACL process executing BACKCOPY. The terminationinfo field holds the error code returned by the process creation procedure.
3 BACKUP The BACKUP utility copies files from disk to magnetic tape. The RESTORE utility, described in Chapter 7: RESTORE performs the complementary function of copying files from magnetic tape back to disk. CAUTION: The syntax for Backup and Restore 2.0 is different from the syntax for the Backup and Restore utilities (T9074).
NOTE: DSM/SCM automatically licenses the BACKUP program file. If you do not use DSM/SCM to install BACKUP, the BACKUP program file is not licensed. The super ID can use the FUP LICENSE command to license the BACKUP program file at any time. • Give super-group users (255, n) EXECUTE access to a PROGID copy of the BACKUP utility, and set PROGID to the super ID (255, 255). • Create a special user ID that is used only for running BACKUP.
[ / run-option [, run-option ] ... / ] { tape-device-name } { ( tape-device-name1, tape-device-name2, ... ) } , VOLUMEMODE, { $volume | $ldev } [ -P | -M ] [ , volume-mode-backup-option ] ... node.volume.subvolume indicates the node, volume, and subvolume where BACKUP runs. It defaults to the current node, volume, and subvolume if these parameters are omitted. NOTE: The current node during a backup is the node where BACKUP is running.
file-mode-backup-option specifies one or more conditions for the file-mode BACKUP operation (see File-Mode BACKUP Options (page 46)). VOLUMEMODE instructs BACKUP to run in volume mode. $volume | $ldev specifies the disk volume name or logical device number for a volume-mode backup. -P-M specifies the primary or mirror half of a volume pair to be backed up. If neither one is specified, the primary and mirror halves must be valid and matching, and the logical pair is backed up.
NOTE: You can specify only one node name with the BACKUP syntax. You can only back up files from one node during a single BACKUP operation. Run BACKUP once for each node that you want to back up. fileset-list is one or more filesets in the form: ( fileset [ , fileset ] ... ) For example, this fileset-list specifies all files on the subvolume PAYROLL (that are on the volume $DATA), and all the files on the volume $ACCOUNT that begin with B: ($DATA.PAYROLL.*, $ACCOUNT.*.
START filename specifies a filename within the fileset or fileset-list at which to start the BACKUP. This is useful for restarting a backup operation that was interrupted. The only wild-card character allowed in a fileset qualified by the START qualifier is an asterisk (*) in place of the entire subvolume (or file ID) of a Guardian file name. The START qualifier works the same as the BACKUP START option. WHERE expression specifies criteria for further qualifying the backup-files.
time is specified as: hh:mm[:ss ] where hh (hour) is an integer in the range 0 through 23; mm (minute) and ss (second) are 2-digit integers in the range 00 through 59. Valid time-value examples are: 1 JAN 2001 06:30 JAN 1 2001 06:30 02 JUL 2001 08:25:30 The default time-value is 00:00:00 (midnight) of today's date. FILECODE conditional number selects a file based on its file code. The conditional qualifier is any of: < > <= = >= <> (not equal to) number is a file code such as 101.
Table 7 File Attributes for the WHERE Expression (continued) Attribute Specifies... ENTRYSEQUENCED Entry-sequenced files. FILECODE A file based on its file code. FORMAT 1 Files created using an RVU prior to G06 or D46; or non-large-format files created using G06, D46, or later RVUs. FORMAT 2 Large-format files (created using RVU G06, RVU D46, or subsequent RVUs). INDEX SQL indexes. KEYSEQUENCED Key-sequenced files.
• • • IGNORE NOPROMPT PARTONLY LISTALL NOREWIND REMOTEIOSIZE File conversion BACKUP options for converting files from one tape format to another: DP1FORMAT DSLACK ISLACK DP2FORMAT EXT SCRATCHVOL Enscribe file BACKUP options for backing up Enscribe files: ALTFILE PART NOSAFEGUARD PARTIAL SQL file BACKUP options for backing up SQL files: INDEXES • VOL NOSQLDATA SQLCATALOGS DSM/TC BACKUP option, used to catalog information about disk files: CATALOGFILES NOTE: File mode BACKUP filters o
key-file-number is an integer in the range 0 through 255, inclusive, that identifies the alternate-key file you are naming. volume.subvolume.file-id is the new name of the alternate-key file. Guidelines • Because the ALTFILE option affects all backup files that have alternate keys, use the ALTFILE option only when you are backing up a single primary-key file. • You cannot use wild-card characters with this option.
• • TMF has its own recovery mechanisms for audited files, but you might want to use BACKUP and RESTORE to: ◦ Transport audited files to another system ◦ Archive files and retrieve files that are used infrequently ◦ Keep old versions of files No entries are made in the TMF catalog for audited files that are backed up.
• BACKUP and RESTORE can be used with the TMFCOM DUMP command for disks containing a combination of audited and nonaudited files or for disks that contain only audited files: 1. Ensure the safe and complete recovery of files when media recovery is needed. At a SCF prompt, type: 1> 2> 2> 3> CONTROL DISK $DATA, REFRESH BACKUP $TAPE, $DATA.*.*,OPEN,AUDITED, & &PARTONLY ON ,LISTALL TMFCOM DUMP FILES $DATA.*.
BLOCKSIZE * 1024. The longest structured file block length is 4096. BLOCKSIZE must be a multiple of 4 so that the long reads will contain an integral number of whole-structured blocks. • The default data-record-size on NonStop operating systems is 8 (8192 bytes); the default on NonStop 1+ systems is 2 (2048 bytes). • You can back up files on a NonStop 1+ system and restore those files on a NonStop operating system with no special command options.
density is the tape recording density: Density Specified Recording Density in Bits per Inch GCR or 6250 6250 PE or 1600 1600 NRZI or 800 800 Tape drives supported on D-series and G-series do not include an 800-bpi density. Guidelines • You cannot use the DENSITY and TAPEMODE options in the same BACKUP command. • Generally, the higher the density specified, the shorter the backup time and the less tape used to complete the backup.
DP2FORMAT The DP2FORMAT option directs BACKUP to write all files to tape in DP2 format (tape format 2). DP2FORMAT Guidelines • Any DP1 files encountered are converted on disk into temporary DP2 files and then written to tape. • Because SQL objects can be backed up only with tape format 3, any SQL files named in the backup-files are skipped. • For DP2 key-sequenced files, index blocks must be the same size as data blocks; this is not true for DP1 files.
0:33,554,432 [ PAGE[S] ] specifies the extent size in pages (2048-byte units). The minimum extent size is one page, so specifying 0 pages allocates one page (2048 bytes). The PAGE is the default unit of measurement for the EXT option. 0:68,719,476,735 BYTE[S] specifies the extent size in bytes. BACKUP rounds up to the next full page (2048-byte units). For example, if you specify 2047 bytes, BACKUP allocates one page; for 2049, BACKUP allocates two pages, and so on.
a block-by-block basis. For structured files, the length of this block is the data-block length. For unstructured files, this block is the buffer length. INDEXES The INDEXES option specifies whether the indexes defined for SQL tables are automatically backed up when the tables are backed up. INDEXES [ IMPLICIT | EXPLICIT ] IMPLICIT specifies that indexes defined for a table are backed up automatically when the table is backed up.
Figure 6 Listing Format Figure 7 Listing Format Sample Output The BACKUP listing generated when LISTALL is used will include whatever of this information is relevant to the specific backup operation: 56 Tape: [\node.]$tape Name of the tape drive used. Operating System: vsn Version of the NonStop host. Tape Version: v Tape format in use with this operating system. Backup options: params Command options that might affect the restoration of these files.
RWEP rwep Security of the listed file for read, write, execute, and purge access. Four asterisks (****) indicate that the listed file is protected by Safeguard. Type type File type of the listed file.
MULTIDRIVE The MULTIDRIVE option lets you have up to four tape drives queued for unlabeled-tape BACKUP operations. The sequence of tape-device-names specified in the BACKUP command determines the order in which BACKUP writes to the tapes.
If the NOMYID option is specified, backup tapes are marked so that the MYID option cannot be used during a RESTORE procedure. CAUTION: Although the NOMYID option provides greater security, it is not a substitute for a careful security plan with restricted physical access to confidential disk and tape information. NOPROMPT The NOPROMPT option instructs BACKUP not to prompt the user before beginning to write on each tape, but to begin when it detects the tape drive is ready.
NOSQLDATA The NOSQLDATA option makes BACKUP record only the SQL file label for all SQL files in the qualified file set. It does not skip the SQL files entirely, it just skips the data transfer portion of the BACKUP process. NOSQLDATA sets the EOF in the file labels for all SQL files on the tape to 0, so the resulting BACKUP tape contains the DDL information necessary to re-create an empty version of the SQL object, without any of the system's SQL data.
NOUNLOAD The NOUNLOAD option directs BACKUP to rewind the final tape and leave it online when the BACKUP process is completed. NOUNLOAD CAUTION: Using BACKUP with the NOUNLOAD option leaves the tape online and write-enabled. Subsequent BACKUP commands (either from you or another user) could write over the data that was just backed up. If you are backing up critical data, do not use the NOUNLOAD option unless there is no possibility that the tape can be inadvertently overwritten.
Example To back up all files on the current volume, excluding audited files and including open files: 6> BACKUP $TAPE, *.*.* WHERE NOT AUDITED, OPEN, LISTALL PAGELENGTH The PAGELENGTH option specifies the number of lines per page of output from the BACKUP procedure. PAGELENGTH number number is an integer in the range 20 through 100 that specifies the number of lines per page of output from the BACKUP procedure.
0:33554432 [ PAGE[S] ] specifies the extent size in pages (2048-byte units). The minimum extent size is one page, so specifying 0 pages allocates one page (2048 bytes). The PAGE is the default unit of measurement. 0:68719476735 BYTE[S] specifies the extent size in bytes. BACKUP rounds up to the next full page. For example, if you specify 2047 bytes, BACKUP allocates one page; for 2049, it allocates two pages, and so on.
day is a one- or two-digit day of the month, such as 1, 02, 15, or 31. month is the first three letters of the month name, such as JAN, FEB, JUN, JUL, DEC. year is a four-digit year, such as 1986, 1991. hour is a one-digit or two-digit number, such as 0 for midnight, 1 for 1 a.m., 22 for 10 p.m. minute is a two-digit number, such as 00 for the hour, 20 for twenty minutes after the hour, and 55 for fifty-five minutes after the hour.
1> VOLUME $STORE1 2> BACKUP $TAPE, *.*, PARTIAL 24 AUG 2001, 3:00, & 2> &LISTALL PARTONLY The PARTONLY option specifies whether all partitions of a partitioned file are backed up. This option applies to both Enscribe and SQL files. PARTONLY [ ON | OFF ] ON specifies that only the partitions of a file explicitly named in backup-files are backed up. ON is the default if you specify PARTONLY in the BACKUP command.
• Do not use this option if you plan to use the RESTORE PARTOF option when you recover the files. If you use the PARTONLY ON option during BACKUP and then use the PARTOF option during RESTORE, RESTORE fails. • When you later use RESTORE, you can specify PARTONLY with MAP NAMES or CATALOG[S] if you also specify KEEP. Examples • To back up all files on the volume $BOOKS (including primary and secondary partitions on $BOOKS, but not partitions on other volumes): 1> BACKUP $TAPE1, $BOOKS.*.
and automatically limited remote I/O size cannot be identified. If the REMOTEIOSIZE exceeds current hardware or software limitations, RESTORE returns this error: TABLENAME *ERROR* Guardian error: 21 (BulkWrite) You must repeat the operation using a smaller REMOTEIOSIZE. • The default ENSCRIBE I/O transfer size is equal to BLOCKSIZE, but you can use REMOTEIOSIZE to reduce it if you need to because of Expand limitations.
Example To back up all files on the current volume (excluding key-sequenced files) and allow shared-read access to the backup files: 1> BACKUP $TAPE, *.*.* WHERE NOT KEYSEQUENCED, SHAREOPEN, & 1> &LISTALL SQLCATALOGS The SQLCATALOGS option lets you specify whether SQL catalog tables are to be backed up. SQLCATALOGS [ ON | OFF ] ON lets you back up a table that is part of a catalog. ON is the default if you specify the SQLCATALOGS option in the BACKUP command.
$volume.subvolume.AA* • The START option works the same as the START qualifier in a qualified file set. Example If $DATA.AAA.AA through $DATA.CCC.PZZZZZZ are already backed up, and you do not want to back them up again, to start another BACKUP procedure where the previous one ended: 1> BACKUP $TAPE2, $DATA.*.*, START CCC.QA, LISTALL TAPEMODE The TAPEMODE option specifies the tape recording mode for tape units that support streaming.
Guidelines • While creating a tape in format 2, BACKUP with the VERIFYTAPE option examines each file after it is written to tape. • After creating a tape set in format 3 (archive format), using the VERIFYTAPE option rewinds the tape when it reaches the end, then reads and examines the tape. • In both cases, verification involves checking tape-record sequence numbers, and reading the volume labels, file labels, data records, and checksums.
Guidelines • Use -P or -M when you only know the primary or mirror half of the volume pair is valid. • The disk volume you specify to be backed up must be on the current node (system); that is, you cannot do a remote volume-mode backup.
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.
\B.$Vol.Subvol.Table1 $Vol.Subvol.TInd1 This removes the need for a mapping clause to restore files to their original locations. Examples: Basic Backup Commands • To copy all files on the volume $MYVOL, and subvolume MYSUBVOL to the tape mounted on the device $TAPE, and to list (on the current output device) the files backed up and files that caused errors: 1> BACKUP $TAPE, $MYVOL.MYSUBVOL.*, LISTALL • To back up the file $DATA.RECRDS.
If your FILE MODE backup tape contains both format 1 and format 2 files, you will need the fallback SPR to restore files to a system that does not support format 2 files. The fallback SPR will restore the format 1 files, skip the format 2 files, and issue an error message. Do not use an older version of RESTORE to process a tape containing format 2 files. When a format 2 file is encountered, the results are unpredictable. BACKUP might abort or create an unusable file.
For SQL backup strategies and options, including guidelines for performing daily and periodic backups, and using the FROM CATALOG, PARTONLY, and INDEXES options, see the SQL/MP Installation and Management Guide. CAUTION: BACKUP is normally used as a secondary recovery method for SQL objects; TMF recovery operations are used as the primary method. An SQL object recovered with RESTORE might be inconsistent with the current catalog description of the object.
Examples These examples display common BACKUP procedures for SQL files. Each example is followed by the command syntax for the procedure: • To back up only SQL shorthand views on volume $A, subvolume A: 1> BACKUP $TAPE, $A.A.* WHERE VIEW, AUDITED, LISTALL • To back up only SQL programs from volume $A and catalog $C.C: 2> BACKUP $TAPE, $A.*.* WHERE SQLPROGRAM 2> &FROM CATALOG $C.C, AUDITED, LISTALL • To explicitly back up index table $B.B.INDX: 3> BACKUP $TAPE, $B.B.
entry-sequenced file can remain in the same partition, then the file is converted; otherwise, it is skipped. • To convert a DP1 disk file in which the records of a relative or entry-sequenced file are split into different partitions: 1. Back up the entire partitioned file using the DP2FORMAT option and omitting the PARTONLY option. 2. Restore the file to a DP1FORMAT disk. 3. Back up the file again by using DP2FORMAT and omitting PARTONLY.
Labeled Backup Tape Volume Labels For labeled backup tapes, BACKUP writes either an IBM volume label or a customized ANSI volume label (the BACKUP label) at the beginning of the tape.
Table 11 Permissible DEFINE Attributes for Labeled-Tape Backup (continued) Attribute Use Description GEN Optional Indicates that this file is part of a generation group. LABELS Required Specifies the tape label type (BACKUP or IBMBACKUP). MOUNTMSG Optional Specifies a message to be displayed to the operator. OWNER Optional As many as 14 characters identifying the tape owner. RETENTION Optional Specifies the number of days to retain the tape file.
more information on creating DEFINEs, see Appendix E: CLASS TAPE DEFINEs. For more information on CLASS TAPE CATALOG, see the DSM/Tape Catalog User's Guide.
1. 2. Close or make inactive any partitioned files. Check the current state of the disk to be backed up. 1> SCF STATUS DISK $DATA If the output from the STATUS DISK command shows that the disk to be backed up is not in a normal UP state, perform whatever steps are necessary to return this disk to a normal UP state. 3.
1> SCF INFO DISK $DATA, DETAIL If a backup error occurred, some paths could have been left in the special (S*) state. If this happens, use the SCF STOP DISK command to bring down the paths before proceeding. 10.
4 Disk Compression (DCOM) The Disk Compression (DCOM) utility moves disk file extents to yield more usable space on a disk.
NOTE: To ensure compatibility with low-level system interfaces, the version of DCOM must match the version of the NonStop operating system. The D42 version of DCOM does not run on any earlier versions of the operating system. All older D-series versions of DCOM run only on versions of the operating system prior to D42. The DCOM command syntax is: [ run ] [ \node.
Although this parameter provides an upper limit for the number of extent moves, it does not indicate the number of moves DCOM actually performs. If DCOM exhausts its possibilities for extent moves, it concludes before reaching the specified limit. VERIFY specifies that every write operation DCOM performs to the disk must be verified. This option causes DCOM to run much longer but with more integrity checking. WORKFILE volume overrides the default work file volume.
The completion information returned by DCOM includes these fields: Field Description completioncode An integer that describes how DCOM terminated (see Table 12) terminationinfo An integer that describes the nature of errors or warnings (see Table 12) subsystem Contains the DCOM subsystem ID, TANDEM.32.
DCOM can move open files for all releases above D45, otherwise, it does not move open files. ◦ DCOM burdens disk I/O channels and can degrade the performance of important disk I/O applications. Running DCOM at a low priority reduces (but does not eliminate) performance degradation. ◦ DCOM rearranges file extents. Any file that was specially allocated in contiguous extents to reduce disk seek time might end up in a noncontiguous state after it is compressed.
• DCOM supports a 512 byte sector disk and a 514 byte internal disk. • DCOM does not permit multiple volumes in the command line. Examples of Compression Output In its preliminary stage, DCOM produces the same summary report and space-distribution reports produced by DSAP. For examples of these reports, see Report Formats (page 101). You can have Enscribe and SQL files on the volume you specify for the DCOM procedures.
Figure 11 Format of DCOM Operator Messages (Concluded) The time required for a single compression run varies according to the disk size and its degree of fragmentation. Subsequent compressions take less time than the first. Changing the Default Work File Volume You cannot change the default workfile because DCOM/DSAP has become a native object since G06.16. In the object files of DSAP and DCOM, the default work file volume name is located at the beginning of the procedure SELECT^WORK^VOLUME.
5 Disk Space Analysis Program (DSAP) The Disk Space Analysis Program (DSAP) analyzes how disk space is used on a specified volume. DSAP copies the disk directory and free-space table to the current work file. By specifying options, you can manipulate this data to produce several different reports about the use of the disk space for that volume. The free-space table is limited only by the primary (main) and secondary (contiguous disk space) memory requirements.
DSAP measures disk space and has no effect on the system, so restricting its use is often unnecessary. However, it might not be preferable in some environments to permit general access to some of the reports generated by DSAP. To set the appropriate level of access to DSAP and all other system utilities, see the security policy standards established by your organization. For a complete discussion about securing information on a NonStop system, see the Security Management Guide.
If volume-specification matches more than one volume name, DSAP displays a list of all the volumes it finds before producing the first report. If you omit volume-specification, a brief description of DSAP and its options is displayed (identical to the display shown if you specify HELP. Each volume name can contain wild-card characters (*) or alias characters (?). The asterisk (*) matches 0 to 7 characters, and the question mark (?) matches any single character.
TEMPORARY UNEXPIRED UNUSED number USER [ group-name.user-name ] [ group-number , user-number ] [ -1 ] [ group-name.* ] [ group-number , * ] Each detail-selection-option limits the scope of the DETAIL report. If you specify the DETAIL report option and one or more detail-selection-options, only the files that meet the requirements of at least one detail-selection-option are analyzed and included in the DETAIL report. Reporting SMF Files DSAP creates reports about the contents of disk volumes.
AGE { [ OVER ] number | UNDER number } OVER number causes the DETAIL report to include all of the files in the file set whose most recent modification occurred number days (or more) ago. UNDER number causes the DETAIL report to include all of the files in the file set modified in the last number days. number is an integer in the range 0 through 32,767. ANALYSIS generates all of the analysis reports (except the DETAIL report).
EXTENTCHECK requests DSAP to make a repeated effort to perform an extent consistency check. Whenever all files are being analyzed (that is, when you do not specify the USER detail selection option), DSAP normally checks the consistency of the allocated and free-space disk extents and displays the results in the space allocation consistency-analysis portion of the summary report. To perform this check, DSAP must be able to copy the disk directory when it is not changing.
PARTITIONED causes the DETAIL report to include all of the partitioned files in the file set. DSAP does not support the PARTITIONED option for SQL/MX format objects. PROGID causes the DETAIL report to include all of the files in the file set that have the PROGID option set. The PROGID option is set by the FUP SECURE command. ROLLFORWARD[NEEDED] causes the DETAIL report to include all of the TMF-audited files in the file set that are marked needing a ROLLFORWARD because a crash-recovery process failed.
SQL causes the DETAIL report to include in the file set all of the SQL/MX format objects that are SQL files and SQL object program files. SUMMARY generates the summary report. The DSAP utility automatically generates the summary report unless you specify the SHORT option. This option also supports SMF virtual volumes. If you only want to see the summary report, specify SUMMARY (or omit all report options).
filename specifies a file name for the allocation of a permanent work file (used by the Enform product to generate additional reports). The filename is of the form $volume.subvolume.file-id, or simply file-id, if you want to put the work file into the current subvolume. DSAP $(volume-set), including $*, with a permanent workfile option will display reports for the selected volumes as long as the collective workfile size is less than or equal to (500MB SQL Buffer size). SQL Buffer size = 32 pages.
Table 13 DSAP Completion Codes Code Explanation 0 A normal, voluntary termination of DSAP with no errors or warnings. 1 A normal, voluntary termination of DSAP with warnings. The disk report was created normally, but DSAP reported disk structure diagnostics, space allocation problems, or a nonfatal internal program error. DSAP includes this termination information with the completion code.
• When DSAP needs to allocate 500 MB of workspace, it displays "WARNING: 500MB SPACE WILL BE REQUIRED" before proceeding. If the required space is not available, DSAP abends and displays "DIRECTORY WORKFILE CREATION/OPEN/MAPPING ERROR: 43. TRY AGAIN WITH 500MB WORKSPACE". • Extent overlaps (double allocated pages) indicate a hardware or software error.
Report Formats Table 14 Summary of DSAP Report Types Report Options Report Name Report Contents SUMMARY Summary Physical disk description, space use summary, exceptional condition report USER User Summary Summary of space use for a specific user FREESPACE Free Space Distribution Space distribution analysis of free space extents FILESPACE File Extent Size Distribution Space distribution analysis of allocated file extents SPACE Combines Free Space and File Extent Space distribution analysis of
Summary of Space Use For the specified disk, the summary of space use lists the total number of: • Free pages (available for file allocation) • Allocated pages (assigned to a file) • Unused pages (assigned to a file but beyond the current end of file) • Deallocatable pages (unused pages in assigned but empty extents) To reclaim deallocatable space, use the FUP DEALLOCATE command to return unused extents.
Figure 13 Sample Summary Report for an Entire Disk In the parentheses of the summary of space use are percentages of the total disk pages on the volume. The allocated pages percentage plus the free pages percentage might not equal 100 percent. The system tables (containing the disk directory, free-space table, spare tracks table, volume label, and others) use the remaining space.
Figure 14 Sample Free-Space Distribution Report To produce a file extent-size distribution report: 1> DSAP $volume FILESPACE This report displays information in the same manner as the free-space distribution report. Figure 15 Sample File Extent-Size Distribution Report (FILESPACE) To produce a file-size distribution report: 1> DSAP $volume FILESIZE This report displays information in the same manner as the free-space distribution report.
Figure 16 Sample File-Size Distribution Report (FILESIZE) Report by Subvolume To produce a subvolume summary report: 1> DSAP $volume BYSUBVOL Figure 17 Sample Subvolume Summary Report The first two entries of the subvolume summary report portion always list the number of free-space pages available, followed by the number of pages devoted to the disk directory. The next entry is for any temporary files that exist.
• Age (in days) of the most recently modified file, including the number of days since a file was modified (MOD) and opened (OPN). 1K+ indicates that the age is greater than 999. If a file has never been opened, three dashes (---) appear under OPN. • Number of expired files Report by User To produce a user summary report: 1> DSAP $volume BYUSER Figure 18 Sample User Summary Report The user IDs 8,49 and 8,131 displayed in Figure 18 have files allocated on the volume.
Figure 19 Sample User Detail Report The user detail report displays a detailed list of all the files (or a selected subset of the files) on a disk. To control the contents of this report, use the DSAP command options. For each selected file, the DETAIL report displays: • Type: A maximum of five characters can be displayed in this field: 1: R Redoneeded (or undoneeded) is necessary for the file or label (base and index tables) or for the label (views). ? The file is crashed.
• SQL Type: A maximum of three characters can be displayed in this field.
Newformat Report You must use the NEWFORMAT option for disks 36 GB or larger. While running with discs 36 GB and larger, parameters like FILES and PAGES (TOTAL, UNUSED and DEALLOC) have larger values to display. These parameters do not fit in existing DSAP report file formats, so column widths are increased to avoid the overlapping problem. The NEWFORMAT option can also be used if the user wants the report in new format irrespective of the disk size for disks of size less than 36 GB.
System Manager or System Operator Examples • To create a hard copy of all analysis reports from DSAP for the volume $DATA, including the list of all user files that the DETAIL report provides: 1> DSAP /OUT $S.
The order of the records in a permanent work file depends on the order DSAP reports your request. Initially, the records are ordered in the standard collating sequence by their names. The by-user and DETAIL reports sort the records by owner ID and then by file name. The format for the records in the permanent file is provided in a DDL description released with the program.
The format of the DSAPDDL template used by Enform to produce written reports is displayed in Figure 21. NOTE: An SQL sensitive object file (program) is not considered an SQL file. The file-kind field in the Workfile Report displays SQL sensitive object files (programs) as "ENS" for Enscribe.
Format of the Permanent Work File 113
Disk Space Analysis Program (DSAP)
Work File Guidelines If the entire disk is analyzed, the first two file records are named ****FREE.SPACE and ****DISC.DIRECTRY. These records indicate, respectively, the amount of free space and overhead space (directory, free-space table, and so forth) on the disk. Because the first two file records are not completely filled in, they should not be treated as user file records. If a group or user is analyzed, only the files of the group or user appear in the work file.
• The DSAP optioins specified in the DSAPCSTM file are taken as default. That is, the options specified in the DSAPCSTM file are appended to the DSAP command you specify at the TACL prompt. • The DSAPCSTM file exists in the DEFAULT VOL-SUBVOL of the user running DSAP. • DSAP creates the DSAPCSTM file in your DEFAULT VOL-SUBVOL the first time you run DSAP or when the file has been purged. • If the DSAPCSTM is already in your DEFAULT VOL-SUBVOL, DSAP reads information from this file.
6 PAK/UNPAK This section describes the PAK and UNPAK utilities, which are used to compress and decompress files on a NonStop system. PAK compresses Guardian files into a single unstructured archive file on any Expand-connected NonStop system. You can create a self-extracting archive file or use UNPAK to decompress the archive file when needed. PAK efficiently and compactly collects data, which is useful in situations such as transferring large numbers of files to the GCSC for analysis.
There are two alternatives: • The IN file contains one file name per line and nothing else. For example: $vol1.subvol1.filename1 • The IN file contains the complete syntax that would otherwise come after the archive name (that is, fileset-list,backup-options). This can be multiple lines long, so the length is effectively unlimited. The syntax is similar to BACKUP IN files except that the tape drive name is not included. For example: $vol1.subvol1.
-s creates a self-extracting archive (object file with file code 700). The self-extracting archive can be extracted by running the archive with any options. For example: run archive, *.*.*, vol $vol.subvol, listall The self-extracting file should not be manipulated with NLD or NOFT or in any other way. Otherwise the self-extracting structure is corrupted, and the archive can no longer be used. -c 'params' creates a self-extracting archive that automatically executes the specified UNPAK command when run.
-password password Encrypts the archive contents with 56-bit DES encryption. The password is case-sensitive, and cannot contain any blank spaces. -split { nnn | nnnK | nnnM } Creates a multifile archive. Each file is at most nnn bytes, where nnn is any integer up to 2,147,483,647 bytes. You can also use nnnK to specify the value in kilobytes, or nnnM to specify it in megabytes. When the first file fills up, a second one is created.
UNPAK [-i] archive,@fileset [,restore-options...] RUN archive [-i] @fileset [,restore-options...] UNPAK and self-extracting archives also accept these run options: -restore restore-program specifies the RESTORE object file to be used. The default is $SYSTEM.SYSnn.RESTORE. -password password specifies the password for an encrypted archive. Considerations • PAK compresses files to a single unstructured archive file (code 1729).
terminates displaying an error message Error: Output file exceeded its limit, cannot write in Output file further. In this case PAK or UNPAK does not create any archive file or unpax all files. To PAK or UNPAK files that required more than 99,999 lines for logging records, run the PAK or UNPAK operation without the /OUT option.
7 RESTORE The RESTORE utility copies files from magnetic tape to disk. The BACKUP utility (discussed in Chapter 3: BACKUP TPSEC03.fm BACKUP) performs the complementary function of copying files from disk to magnetic tape. RESTORE lets you: • Copy files from magnetic tape to disk (The tape must be created with BACKUP.
NOTE: DSM/SCM automatically licenses the RESTORE program file. If you do not use DSM/SCM to install RESTORE, the RESTORE program is not licensed. The super ID can use the FUP LICENSE command to license the RESTORE program file at any time. • Give the super group Execute access to a PROGID copy of RESTORE with PROGID set to the super group user (255,n). You must update this copy of RESTORE when you install a new version of it.
{ tape-device-name } { ( tape-device-name1, tape-device-name2, ... ) } , VOLUMEMODE, { $volume | * } [ , volume-mode-restore-option ] ... run-option is any option for the TACL RUN command. The two most common run options are: IN filename OUT listfile The IN option specifies the input files, and the OUT option specifies the output files. These files usually override the home terminal as the input or output device.
* specifies that any disk volume on the tape is to be restored. The asterisk matches any disk volume name on the tape. volume-mode-restore-option specifies one or more conditions for the RESTORE process (see RESTORE Options (page 127)). File-Mode RESTORE Options The RESTORE options fall into five categories in file mode. For descriptions, see RESTORE Options (page 127).
Volume-Mode RESTORE Options These RESTORE options are available in volume mode: LISTONLY NOREWIND TARGET MULTIDRIVE NOUNLOAD VERIFYTAPE NOPROMPT RENAME VOLUMEMODE RESTORE Options This subsection describes each of the file-mode and volume-mode RESTORE options. ALTFILE The ALTFILE option changes the name of an alternate-key file in the file label of the primary-key file. (Enscribe files only.) ALTFILE (key-file-number,[$volume.][ subvolume.
• If a file was audited by TMF when it was backed up, you must include the AUDITED option in the RESTORE command when restoring the file. If you do not include the AUDITED option, RESTORE skips the audited file and sends the message * WARNING* Audited File Skipped to the output file. • After restoring audited files, use TMF to perform an online dump of the restored audited files before you update them. Purging an audited file erases its online dump information in the TMF catalog.
*WARNING*: COULDN'T MAKE FILE AUDITED • You can use BACKUP and RESTORE with the TMFCOM DUMP command for disks containing a combination of audited and nonaudited files, or containing only audited files: 1. Ensure the safe, complete recovery of files when media recovery is needed. At an SCF prompt, type: 1> 2> 2> 3> CONTROL DISK $DATA, REFRESH BACKUP $TAPE, $DATA.*.*,OPEN,AUDITED, & &PARTONLY ON ,LISTALL TMFCOM DUMP FILES $DATA.*.
Table 16 Interaction Between RESTORE and TMF (continued) RESTORE Command Used Conditions What RESTORE Does AUDITED and TURNOFFAUDIT File exists but is not audited File is restored nonaudited. AUDITED and TURNOFFAUDIT File exists and is audited If TMF is running, the file is restored nonaudited. Otherwise, RESTORE issues Purge Error 82 and does not restore the file. CAUTION: Restoring any audited file backed up in a WRITE OPEN state can make TMF bring down the whole volume.
Guidelines • To register SQL objects in a different catalog than they were originally registered in, use CATALOGS. If the objects are being restored on a different system, use a fileset that describes the destination fileset, not the original. • If you use the MAP NAMES option to move SQL objects, make sure to define the MAP NAMES and CATALOGS parameters correctly for the dependent tables, indexes, views, and programs.
Guidelines • You can use the COLLATIONS option with MAP NAMES, CATALOG, or both. • You can specify up to 10 file-set names or 80 collation names in a collation specification. • The order of mapping rules is important. The first collation specified whose simple name matches the simple name of a collation referenced in the object being restored is mapped to the restored object. If the restored object is referenced in more than one specified file set, the first file set specified is used.
System: \TCSDRP1 Operating System: H06 Tape Version: 3 Backup options: NO AUDITED, BLOCKSIZE 8, NO IGNORE, NO OPEN, PARTONLY OFF, INDEXES IMPLICIT Restore time: 1Jul2005 14:55 Backup time: 1Jul2005 14:55 Page: 1 Tape: 1 $DATA4.SGHOSH.TEST ENSCRIBE TYPE U FORMAT 1 CODE 100 EXT ( 6 PAGES, 6 PAGES ) MAXEXTENTS 900 OWNER -1 SECURITY (RWEP): NUNU, PROGID, TRUST ME MODIF: 14Jul2004 8:10 CREATION DATE: 1 Jul 2005, 14:55 LAST OPEN: 30 Jun 2005, 17:21 EOF 2076 (0.0% USED) EXTENTS ALLOCATED: 1 $DATA4.SGHOSH.
Guidelines • The file-mode options that are meaningful with the EMULATEFSF option is LISTONLY. • This is to fasten the LISTONLY and PARTIAL in some specific types of physical tape drives such as M8501 and M8502 models of LTO-3 tape drives. • You cannot use the EMULATEFSF option with the VOLUMEMODE restore option. • The usage of EMULATEFSF is meant for M8501 and M8502 Tape drives.
Examples • To set primary and secondary extent sizes to 2 pages and 3 pages, respectively, for the files in $DP1.CONV: 1> RESTORE $TAPE, $DP1.CONV.*, EXT (2,3) • To set the data slack and index slack values and set file extents to 3: 2> RESTORE $TAPE1, *.*.*, DSLACK 20, ISLACK 10, EXT 3 IGNORE The IGNORE option directs RESTORE to ignore certain data errors on tape. The RESTORE utility copies the invalid data to disk (if possible). Otherwise, RESTORE writes zeros in place of invalid data.
index on an existing table, if you know that the table has not changed since the index was backed up, use RESTORE with the INDEXES EXPLICIT option. • If a base table and its indexes are backed up with the INDEXES IMPLICIT option, you can restore the base table only by specifying the INDEXES EXPLICIT option and the base table name in the RESTORE command. Examples • To restore all SQL indexes whose tables were on the volume $FIN: 1> RESTORE $TAPE, $FIN.*.
Example This example is a listing created from the RESTORE command: 1> RESTORE $GCC, *.*.*, LISTALL, DETAIL The listing shows some of the BACKUP options used to create the tape. This information helps to verify the contents of the tape.
FILEMODE, the LISTONLY option for VOLUMEMODE BACKUP does not list the files that were on the disk when the backup was performed. • For examples, see Viewing the Contents of a Tape (page 159).
Ensure that the volume name of the remote system should not be more than seven characters (including $). • To change file names, use the MAP NAMES option, not the VOL option. The VOL option has limitations handling secondary partitions, alternate-key files, and SQL objects. • Wild-card characters can be used in the volume, subvolume, and file-id fields of the old-fileset-list: * (asterisk) matches from 0 through 8 characters in the position where it appears.
Examples • To restore all files on the volume $DATA to the volume $PAYROLL: 1> RESTORE $TAPE1, *.*.*, & 1> &MAP NAMES $DATA.*.* TO $PAYROLL.*.* The files were backed up from and restored to the same node. • To move the shorthand view $A.SH.VIEW, which refers to the base table $B.VIEW.TAB, to volume $C: 1> RESTORE $TAPE, $A.SH.VIEW, & 1> &MAP NAMES ($A.SH.VIEW TO $C.SH.VIEW, $B.VIEW.TAB TO $C.VIEW.
Guidelines • The RESTORE utility verifies the sequence of each tape reel before it begins restoring the tape. If a tape is mounted out of sequence, RESTORE issues an error message and waits for the correct tape.
NOPURGEUNTIL The NOPURGEUNTIL option instructs RESTORE to preserve the NOPURGEUNTIL date of the Enscribe files if you set the option before the Enscribe files are backed up. This option only applies to the Enscribe files. NOPURGEUNTIL Guideline For the SQL files, the NOPURGEUNTIL date is restored by default. Therefore, if the NOPURGEUNTIL option is specified for the SQL files, it is ignored.
Guidelines • This option does not affect ENSCRIBE files. Any ENSCRIBE files on the backup tape and included in the qualified file set are recovered with all included data. Only SQL data is omitted. • An SQL object can effectively be copied using a standard BACKUP tape and the RESTORE MAP NAMES and CATALOG[S] options with NOSQLDATA. This provides a CREATE LIKE function for multiple partition objects.
OPEN The OPEN option restores files that were open during the BACKUP process. If you omit the OPEN option, files of this type are not restored. OPEN • For more information on backing up open and audited files, see AUDITED (page 127). • For more information on restoring open files, see OPEN (page 61). CAUTION: If audited files are backed up in the WRITE OPEN state, they could be corrupt. Restoring such files and using them in audited mode can cause TMF to bring down the whole volume.
volume is the name of the volume where the secondary partition is to reside. If you omit the volume name, RESTORE uses the original volume name of the secondary partition. pri-extent-sizesec-extent-size defines the primary and secondary extent sizes, respectively. The default value is 1 page (2048 bytes). You can specify these values for pri-extent-size and sec-extent-size: 0:512000000 [ PAGE[S] ] specifies the extent size in pages (2048-byte units).
Examples • To restore the secondary partition of the file $PUBS.BOOKS.SECT1 to the volume $SAVE: 1> RESTORE $TAPE, $PUBS.BOOKS.SECT1, PART (2, $SAVE) • To restore the secondary partition of the file $DATA.GOOD.ONE to the volume $SAFE and sets the primary and secondary file extents to 2 and 3, respectively: 1> RESTORE $TAPE1, $DATA.GOOD.
Examples • To restore file partitions on the backup tape whose primary partitions reside on the volume $GEN: 1> RESTORE $TAPE, *.*.*, PARTOF $GEN • To restore all file partitions on the volume $DATA: 1> RESTORE $TAPE2, $DATA.*.*, PARTOF * PARTONLY The PARTONLY option specifies if all of the partitions of a partitioned file (or table) are to be restored. This option applies to Enscribe and SQL files.
qualified file set operates in a separate catalog. The final PARTONLY ON operation cannot be performed in parallel. After a PARTONLY PARTIAL operation, NonStop SQL/MP objects might be in an unaudited state, owned by the RESTORE user ID, and secured OOOO. The final PARTONLY ON operation corrects these temporary states by putting all partitions online and linking all indexes.
In this example, the partition 1 of TABLE1 is backed up and restored to the target partition 1 of TABLE2. CAUTION: It is critical that the CATALOGS and MAP NAMES mapping lists are complete even when recovering an individual partition: • If the CATALOGS option is specified, every associated catalog must be mapped. • If the MAP NAMES option is specified, every partition must be mapped. If the maps are incomplete or incorrect, severe catalog inconsistencies for the object will result.
Guidelines • The ALTFILE, PART, and MAP NAME[S] RESTORE options are used to rename files, and the VOL RESTORE option can be used to change the node, volume, and subvolume of Enscribe files. Renaming a file can affect device residence, and each of these RESTORE options lets the volume name be changed. To restore all files on the BACKUP tape $TURBO to the SMF virtual disk $BRVC4: RESTORE $TURBO, *.*.
REGISTERONLY The REGISTERONLY option directs RESTORE to restore a program without recompiling it. This option is valid only when the SQLCOMPILE option is ON. REGISTERONLY [ ON | OFF ] ON directs the SQL compiler to register a program that was previously compiled with SQL in the specific catalog without compiling any SQL statements in the program. The SQL compiler marks the program file label as sensitive to SQL and valid to SQL. The program retains its existing execution plans.
• The 52 KB limit is due to current tape BLOCKSIZE limitations. Expand can handle data transfers larger than 52 KB. • Older Expand environments might not handle 52 KB transfer sizes. Different qualified file sets might involve systems with different Expand limitations, and the systems at RESTORE time might be different than those that created the BACKUP tape. For these reasons, individual limitations and automatically limited remote I/O size cannot be identified.
Guideline You can use the SCRATCHVOL option if disk space is inadequate when converting key-sequenced files. If you omit the SCRATCHVOL option and file conversion is performed, RESTORE places the temporary files (with prefix ZZRA) on the current default volume and subvolume. If disk space is inadequate, RESTORE returns error 43 (unable to obtain disk space for file extent) for the file that was to be converted. SQLCATALOGS The SQLCATALOGS option specifies whether SQL catalogs are to be restored.
on compiling SQL program files, see the SQL/MP Programming Manual for C and the SQL/MP Programming Manual for COBOL. • If you use the SQLCOMPILE ON option during a RESTORE process of a program file that is not sensitive to SQL, the file is restored but not as a program that is sensitive to SQL. SQLTAPEPARTARRAY The SQLRAPEPARTARRAY option makes RESTORE update all partitions of the target object with the partition array from the tape, and makes RESTORE recover data for the target partition.
TAPEDATE The TAPEDATE option determines the date used for the last modification and last open timestamps of the files that are being restored. TAPEDATE [ ON | OFF ] ON sets the last modification and last open timestamps of the restored files to the values they had when the files were backed up. ON is the default for this option. OFF changes the last modification and last open timestamps of the restored files to the time of the RESTORE process.
Guidelines • If the TARGET option is not specified, the disk image is restored to the disk volume that is named on the backup tape. • SQL objects can be dependent on files in multiple volumes. Before restoring files to a different volume, consider the dependencies of SQL objects that might be affected. For more information, see the SQL/MP Installation and Management Guide.
new-vol is the new volume name. new-subvol is the new subvolume name. Guidelines • If you specify the VOL option, you cannot specify the MAP NAMES option. • The VOL option has limitations in handling secondary partitions and alternate-key files. For more information, see MAP NAMES (page 138). • Specify the name of the remote node for node to restore files to a remote node.
(:_COMPLETION), where you can examine it using TACL functions. TACL also displays the completion codes at the home terminal, unless the RESTORE process completes normally without any warnings or errors. For more information about completion codes and batch processing, see the TACL Programming Guide. In addition to a completion code, RESTORE also returns a subsystem identifier (TANDEM.75.version), where version is the release number (for example, C30).
Viewing the Contents of a Tape To display the contents of a tape without physically restoring files to disk: • To verify the tape on drive $TAPE1 and list the files without writing the tape to disk: 1> RESTORE $TAPE1,*.*.
255). The object file being restored is licensed if the program is running under the super ID (255, 255). • If an object file being restored is a licensed file, the file loses its license if a user other than the super ID restores the file. • The report listings from RESTORE and BACKUP display the significant options that were used when the utility was run. For example, use of the DETAIL option is not reported because that option has no significant impact on a BACKUP or RESTORE process.
If the RESTORE process does not complete normally, the file is marked corrupt and should be purged. The file system rejects normal OPENs of corrupt files. • If the state of FLTrustFlags for an object file being restored is ME or SHARED, FLTrustFlags for the file is set to OFF if a user other than the super ID restores the file. NOTE: The FLTrustFlags attribute is supported only on systems running H-series RVUs or J-series RVUs.
releases that only support key-sequenced files with fewer partitions: 1. Restore each partition from the enhanced key-sequenced file one at a time in the system. 2. Attach the partition to a temporary classic key-sequenced file to gain access to the data records in the partition. 3.
== To invoke the macro, load it and run without any command line options ======================================================================== #frame #push AF AN cmd parts pext sext partfile fvar fname #push work_vol1 work_vol2 tfile tloc tgt_file done1 inp yy mm dd hh ss mi #push temp done #exit count #inlineprefix #informat stime etime isDef #def myarr STRUCT begin subvol vol_part(0:127); end; #set #inlineprefix + #set #informat tacl #output #output #output #output #output #output #output +-----------
#set cmd RESTORE #set done1 0 [#loop |while| (done1<>1) |do| #set isDef [#input Is the tape info included in a define?(y/n): ] [#case [isDef] | y Y | #set isDef 1 #set done1 1 | n N | #set isDef 0 #set done1 1 | otherwise | ] ] #set AN & [#input Give the name of the tape or define (e.g. $tape or =def): ] [#if ((isDef) OR ((isDef<>1) AND [#processexists [AN] ])) |then| #set done 1 |else| [#if (isDef<>1) |then| #output Non-existent Tape Process.
] #set done 0 #output [#loop |while| (done = 0) |do| #output Provide a work location ($vol) for a temp copy. This is for a #output partition 0 of the temp file. There should be no subvol & file #set work_vol1 [#input in this location similar to source file name: ] [#if ( ([#charfind work_vol1 1 $] = 1) AND ([#charfind work_vol1 1 .] <= 0)) |then| #set done 1 |else| #output !!!! Bad input !!!! ] ] #set done 0 #output [#loop |while| (done = 0) |do| #output Provide a work location ($vol) for a temp copy.
] =========================================== == Start the restoration work =========================================== #set count [#compute ([#charfind partfile 1 .] + 1)] #set tfile [#charget partfile [count] & for [#compute ([#charcount partfile] - [count] + 1) ] ] #set count 1 == no need for part 0 #set inp 0 #set done1 0 fup purge [work_vol2].
For more information about restoring SQL objects, including guidelines for restoring and moving individual objects and entire databases, and renaming objects, see the SQL/MP Installation and Management Guide. • When you use PARTONLY OFF and INDEXES IMPLICIT: ◦ When a base table is restored to disk, any SQL protection views defined on the table are restored automatically. Any SQL shorthand views that depend on the table are not restored unless they are explicitly named in the restore-files.
used, RESTORE purges the restored SQL components. If the INDEXES EXPLICIT or PARTONLY ON options were used, RESTORE purges the restored partition or index and leaves the base table invalid. If an error occurs when RESTORE attempts to validate objects towards the end of the operation, the restored objects are left invalid. In these situations, you might have to fix inconsistencies in SQL tables: 168 RESTORE ◦ All of the components were not restored. ◦ The security or owner ID is mismatched.
• ◦ Constraints are mismatched with the underlying table. ◦ Physical attributes of partitions are mismatched. The state of restored SQL files depends on the particular RESTORE options that were used during the BACKUP and RESTORE processes. The default options of BACKUP and RESTORE are: PARTONLY OFF, INDEXES IMPLICIT If only the default options are used, these statements are true: • ◦ Sets of logically related objects such as partitions and indexes are backed up and restored together.
• To restore a shorthand view, the view must have been backed up explicitly. In this example, the shorthand view is restored to a different volume from the one on which it was backed up; its underlying table and index were previously moved to a different volume from the one on which they were backed up. The MAP NAMES option moves the files and resets the pointers to maintain consistency in the SQL object. 1> 1> 1> 1> • RESTORE $TAPE, $A.A.SVIEW, AUDITED, LISTALL & &MAP NAMES ($A.A.* TO $D.D.*, & &$B.B.
• To include the MAP NAMES option in the previous example and restore the files to another volume: 1> 1> 1> 1> RESTORE $TAPE, ($A.*.*, $B.*.*),& &MAP NAMES ($A.*.* TO $C.*.*, $B.*.* TO $D.*.*),& &CATALOGS ($C.CAT FOR $C.*, $D.CAT for $D.*),& &LISTALL, AUDITED This command produces these results: • ◦ The tape files are copied to disk if they have the volume name $A or $B. All partitions, protection views, and indexes associated with files that have the volume name $A or $B are restored.
destinations. RESTORE restores each file to its original location. However, if you must restore files to a different network, or if you must restore SQL objects to a new location, you might need to perform name mapping. The CATALOG[S] option is necessary with the MAP NAMES option if a different catalog is to be used during RESTORE. A complete mapping scheme eliminates errors if AUTOCREATECATALOG is OFF, and unexpected registration locations if it is ON.
\??.$VOL.SUBVOL Table1 2. After running RESTORE with the LISTONLY option once, run it again, but use the appropriate QFS in RESTORE command along with a MAP NAMES option to specify the destination node names. For example, you can restore the files from Step 1 with the command: RESTORE $TAPE, ( \B.$VOL.SUBVOL.TABLE1 ),& MAP NAMES ( \B.$VOL.SUBVOL.* TO $NEW.SUB.* ) You cannot restore the files of a remote file set if the system node is offline.
1> RESTORE $TAPE, $A.*.*, & 1> &MAP NAMES ($A.*.* TO $C.*.*) & 1> &CATALOGS ($C.CAT FOR C.*.*) The CATALOGS option does not use the original file names; instead, it uses the new file names specified by the MAP NAMES option because the MAP NAMES option is processed before the CATALOGS option. The MAP NAMES option also applies to the names and definitions of restored SQL views.
You do not specify disk conversion during the RESTORE process; RESTORE automatically converts the files if needed: • When RESTORE converts files, it creates temporary disk files on the current subvolume which, in the destination-file format, have names that begin with ZZRA. If you terminate the RESTORE process early, the current subvolume might contain some of these files. To regain disk space, purge any remaining ZZRA files. If disk space is inadequate, use the SCRATCHVOL option.
NOTE: Though the VOLUME attribute is required for CLASS TAPEDEFINEs and optional for CLASS TAPECATALOGDEFINEs, you cannot specify it for LABELS BYPASS DEFINEs. For more information on CLASS TAPECATALOGDEFINEs, see the DSM/Tape Catalog User's Guide. In your DEFINE for a labeled-tape RESTORE process, specify one of: LABELS BACKUP Identifies the format of the tapes to be read for the RESTORE process as NonStop BACKUP labeled tapes.
Examples To create a DEFINE and use it in a RESTORE command: • To use the DEFINE =MYBACKUP to specify that the labeled backup tapes NY082 and NY004 be used for the RESTORE process (if you use the VOLUME attribute, you must specify tape volume IDs in the order the tapes were written): 1> 2> 2> 3> SET DEFMODE ON ADD DEFINE =MYBACKUP, CLASS TAPE, LABELS BACKUP, & &VOLUME (NY082,NY004) RESTORE =MYBACKUP, *.*.
This example shows how to find out information on backup sessions and how to use ADD DEFINE and RESTORE commands: • To find out which backup sessions have the file you want to restore, use the MEDIACOM INFO DISKFILE command. This example lists two backups on the same physical tape: 1> info diskfile \CAUNI3.$FOX082.AUG1999.
• To restore the file from the first backup session, use the ADD DEFINE. You must specify the GENERATION and VERSION. Otherwise, their default values would be for the latest backup performed. 2> add define =DEF1, class tapecatalog, pool WEEKLY_APPENDABLE, volcat \CAUNI3.SILO1_VOLCAT, gen 1, version 0, device $tape0,filecat \CAUNI3.
• If you want to restore a volume-mode BACKUP to an upgraded disk, you must first issue an SCF START command to the new target disk to update its internal tables. For example: ◦ A volume-mode backup was performed on a device with subtype XX. ◦ You need to issue an SCF START command on the new target volume, then an SCF STOP command. ◦ Now you can perform a volume-mode RESTORE to the new target volume (on a device with subtype YY).
1> SCF STATUS DISK $DATA 2. Verify that there are no new bad sectors on the specified disk drive. This is a normal procedure to perform before you bring down the disk for the RESTORE process. INFO DISK $DATA, BAD If you find any unspared defective sectors: a. Use the SCF CONTROL DISK, SPARE command to correct the situation. b. Recheck the status of both halves of the mirrored volume using the INFO DISK command. You must find no new defects before continuing. 3.
A BACKCOPY, BACKUP, and RESTORE Messages These messages are produced by the BACKCOPY, BACKUP, or RESTORE utilities. When a message is displayed at your terminal, it is preceded by either *ERROR* or *WARNING*. 49 access violation Cause. The version of BACKUP or RESTORE in use is not licensed. Effect. SQL files cannot be backed up. Recovery. Use a licensed version of BACKUP or RESTORE. 1070 The process's program file is not licensed. Cause. The version of BACKUP or RESTORE in use is not licensed. Effect.
Recovery. For corrective action for the error indicated in the message, see the Guardian Procedure Errors and Messages Manual. 2013 File not dumped : nnn Cause. BACKUP encountered a disk with no files that met the backup criteria. Effect. The utility terminates. Recovery. For corrective action for the error number indicated by nnn, see "File-System Errors" in the Guardian Procedure Errors and Messages Manual. 3nnn File aborted filename : [read | write | open] error Cause.
Cause. BACKUP or RESTORE tried to adjust the extent sizes of individual partitions when converting them from one disk-process type to another. The extent sizes could not be adjusted so that the records of relative and entry-sequenced files could remain in the same partition. Effect. The file is skipped, and BACKUP or RESTORE proceeds to the next file. Recovery. The entire partitioned file must be converted in one process. Back up the source file again without specifying the BACKUP PARTONLY ON option.
7005 Audited file skipped. Cause. The utility tried to back up a file audited by TMF, but the AUDITED option was not included in the command. Effect. BACKUP or RESTORE skips the audited file and continues processing the file set. Recovery. To back up or restore audited files, include the AUDITED option in the command. Rerun the utility, specifying the audited files that were skipped. To restore audited files, see AUDITED (page 48) for BACKUP, or (page 127) for RESTORE. 7006 Audit turned off. Cause.
Cause. An attempt to restore a file that was previously audited by TMF was successful, but the file is not currently audited. This can occur when the file is restored, TMF has not been started, or TMF has not been configured. Effect. The file is restored, and RESTORE continues execution. Recovery. Audit the file using TMF. 7011 File is audited. Cause. The file that was backed up was audited by TMF. Effect. None. Recovery. Informational message only; no corrective action is needed.
Effect. Because the IGNORE option was specified, BACKUP writes the bad data to tape. Recovery.
7019 File was open for write during backup. Cause. The file that was restored was open for write when it was backed up. Effect. RESTORE continues. Recovery. Informational message only; no corrective action is needed. 7020 File skipped. Lock encountered in file and user specified skip. Cause. BACKUP was run with the MSGONLOCK option specified, and a locked file or record was encountered. User instructed BACKUP to skip the file. Effect. BACKUP skips the locked file and proceeds with the next file.
Cause. Although the EXT option was used, the extent-size specification was ignored because extent sizes for unstructured files must remain the same. Effect. BACKUP or RESTORE converts the file with the old extent sizes. Recovery. Informational message only; no corrective action is needed. 7025 File skipped. File does not have alternate key file specified with ALTFILE. Cause. The ALTFILE option was used to specify an alternate-key file that does not exist for the file. Effect.
7030 Secondary partition not found on tape. Cause. RESTORE could not find the requested secondary partition of the partitioned file on tape. The tape has an invalid format. There are three possible reasons: • BACKUP was stopped in the middle of a BACKUP process, resulting in an incomplete BACKUP tape. The "Bad Tape Format" was detected when unwanted or meaningless information was encountered at the interruption point on the tape. • The BACKUP tape was corrupted in some way.
7034 The alternate key files of this entry sequenced file will have to be reloaded using FUP LOADALTFILE. Cause. The file conversion caused the record addresses to change, making the record addresses stored in the alternate keys invalid. Effect. BACKUP or RESTORE converts the file. Recovery. Reload the alternate-key files by using the FUP LOADALTFILE command. 7035 Old format tape -- no checksums. Cause.
7039 File aborted. Too much alternate key and/or partition information for DP1. Cause. The DP2 file has too many alternate keys and files or too many partitions for conversion to a DP1 file. Effect. BACKUP or RESTORE skips the file and proceeds to the next file. Recovery. Eliminate alternate keys, files, or partitions in the DP2 file. Otherwise, the file cannot be converted. 7040 File aborted.
Cause. An entire partitioned file was terminated. This message is preceded by an error message indicating that a file was terminated. Effect. BACKUP or RESTORE skips the entire partitioned file and proceeds to the next file. Recovery. Correct the error that caused the partition to be terminated, and retry the operation on the file. 7044 File not dumped (Error nnn). Cause. A file-system error occurred when BACKUP was trying to copy the file. Effect.
7049 Tape parity error encountered on data block(Bad data byte offset in file: b,Expected length: e, Actual length: a). Cause. The IGNORE option was specified in the RESTORE command, and a parity error was encountered on a data block. Effect. RESTORE continues to process the file. Recovery. The data at the specified location is probably corrupted and requires repair. 7050 File aborted. Tape parity error encountered on data block. Cause. A parity error was encountered on a data block. Effect.
7055 File skipped. Duplicate secondary partition name. Cause. Two or more secondary partitions of a partitioned file have the same name. Effect. BACKUP or RESTORE skips the partitioned file and continues processing. Recovery. Use the PART parameter to specify a different volume name for the secondary partition. 7057 At least one secondary partition file name references a volume that does not exist. Cause.
7062 Unable to back up all the files for the System Image tape. Cause. One of the files to be recorded on the system image tape (SIT) for SYSGEN was terminated. Effect. BACKUP terminates. Recovery. Correct the problem that caused the file to terminate and rerun SYSGEN. 7063 This System Image tape is for a different volume type (DP1/DP2) System Disk. The OSIMAGE will not boot from the current volume. Cause. The operating system contained in the OSIMAGE file could not be booted from the current volume.
7073 File is corrupt and will not be dumped. Cause. The specified file was marked corrupt, and the IGNORE option was not specified to BACKUP. Effect. BACKUP skips the file and proceeds to the next file. Recovery. A corrupted file generally is not recoverable. 7075 Secondary partition partition-name is corrupt and will not be dumped. Cause. The specified secondary partition was marked corrupt, and the IGNORE option was not specified to BACKUP. Effect.
Recovery. None. 7081 Original source file was corrupt. Will not restore. Cause. The specified file was marked corrupt on tape, and the IGNORE option was not specified. Effect. RESTORE skips the file without restoring it. Recovery. A corrupt file generally is not recoverable. 7083 Secondary partition partition-name is corrupt. Cause. The specified secondary partition was marked corrupt on the tape. Effect. The corrupt file is restored, but the corrupt flag remains set. Recovery.
7091 Safeguard information for this file cannot be backed up because it is too long when combined with the file label. Cause. BACKUP could not accommodate both the file label and the Safeguard information. Effect. BACKUP continues, but Safeguard information is not included. Recovery. None. 7092 Safeguard protection has been turned off for this file. Cause. Either the NOSAFEGUARD option was specified, or Safeguard is not running on the system. Effect. Safeguard information is not backed up or restored.
Cause. RESTORE of SQL objects using the PARTOF option. Effect. RESTORE of the object fails. Recovery. Use the PARTONLY option to restore the specific partitions. 7105 Attempt to purge an SQL object while restoring an Enscribe file. Cause. The Enscribe file has the same name as an existing SQL object. Effect. File is not restored. Recovery. Purge the SQL object before performing the RESTORE operation. 7109 Too many files specified for the system disk directory. Cause.
7122 Unable to copy all files Cause. File errors caused some files to be skipped in the BACKCOPY operation. Effect. Files are missing on the destination tape. Recovery. Reissue the command to see if the file errors are transitory. 7123 File exists on disk and is not being replaced Cause. The RESTORE KEEP option is in use. Effect. Tape files with names identical to files on the destination disk are not restored. Recovery. Informational message only; no corrective action is needed.
Effect. BACKUP or RESTORE terminates. Recovery. Reissue the command without the incompatible options. In a BACKUP command, PARTONLY ON cannot be used with the INDEXES IMPLICIT option or with the PART option if extent sizes are specified. In a RESTORE command, PARTONLY ON cannot be used with the EXT or INDEXES IMPLICIT options. 7128 Unable to determine file attributes for qualification Cause. The file-set qualifier contains invalid file attributes. Effect. BACKUP or RESTORE terminates. Recovery.
7138 OUT file cannot be created due to security violation error. Cause. Attempt to create a file with an unauthorized user ID. Effect. The file is not created. Recovery. Create the file using an authorized user ID or assign write permission to the user ID. 7139 The backup files may be opened for write because the SHAREOPEN option was used for Backup. This may result in inconsistent file data on the backup tape. Cause.
Cause. A D30 version of this product (or later) is required because the BLOCKSIZE is larger than 28 KB. Effect. BACKUP or BACKCOPY continues. Recovery. Informational message only no corrective action is needed. 7145 This tape was backed up using BLOCKSIZE larger than 28 but the following tape drive does not support large transfers: nnnn. Cause. The tape drive does not support large blocks. Effect. RESTORE or BACKCOPY terminates. Recovery. Use a tape drive that supports a larger BLOCKSIZE.
Recovery. Informational message only; no corrective action is needed. 7159 The NOSQLDATA option is active. No SQL data is being recovered from this tape. Cause. A RESTORE command was entered using the NOSQLDATA option. Effect. All data contained in SQL files is skipped during the RESTORE. An empty version of each SQL object on tape is created at the target location. Recovery. Informational message only; no corrective action is needed. 7251 Disk volume diskname is in the diskstate.
7255 Name of the volume on tape does not match the volume name specified. Cause. An attempt was made to RESTORE a tape, but the name of the volume on the tape did not match the specified volume name. Effect. RESTORE terminates. Recovery. Retry the operation with the correct volume name or specify the "*" wild card to match any volume. 7257 The disk does not have mirror (-M). Cause. BACKUP or RESTORE encountered a disk that did not have a mirror. Effect. BACKUP or RESTORE terminates. Recovery.
7264 The subtype of the disk on tape (subtype number) is not known by (this version of) this program. Cause. An attempt was made to RESTORE a tape, but the disk subtype on the tape was unknown to the version of RESTORE being used. Effect. RESTORE terminates. Recovery. None. 7266 One or more boot strap sections have not been restored to the target volume (Use PUP REPLACEBOOT). Cause. A RESTORE was performed, but one or more bootstrap sections were not restored. Effect. RESTORE continues. Recovery.
7270 Volume mode backup and restore can only be performed under the SUPER.SUPER user ID. Cause. An attempt was made to perform a volume-mode BACKUP or RESTORE with a user ID other than the super ID (255,255). Effect. BACKUP or RESTORE terminates. Recovery. Log on as the super ID and retry the operation. 7271 The audit record cannot be sent to the Audit Collector due to file-system-name. Cause.
7502 Bad tape format (Bad length for a DP1 tape file label). Cause. An attempt was made to restore a tape, but a BACKUP tape in the proper format could not be found. There are three possible reasons: • BACKUP was stopped in the middle of a backup operation, resulting in an incomplete BACKUP tape. The "Bad Tape Format" was detected when unwanted or meaningless information was encountered at the interruption point on the tape. • The BACKUP tape was corrupted in some way.
7504 Bad tape format (Bad length for a DP2 tape file label). Cause. An attempt was made to restore a tape, but a BACKUP tape in the proper format could not be found. There are three possible reasons: • BACKUP was stopped in the middle of a backup operation, resulting in an incomplete BACKUP tape. The "Bad Tape Format" was detected when unwanted or meaningless information was encountered at the interruption point on the tape. • The BACKUP tape was corrupted in some way.
7508 Bad tape format (Record found that is not a file label or ending volume label). Cause. An attempt was made to restore a tape, but a BACKUP tape in the proper format could not be found. There are three possible reasons: • BACKUP was stopped in the middle of a backup operation, resulting in an incomplete BACKUP tape. The "Bad Tape Format" was detected when unwanted or meaningless information was encountered at the interruption point on the tape. • The BACKUP tape was corrupted in some way.
7510 Bad tape format (No files on tape) Cause. An attempt was made to restore a tape, but a BACKUP tape in the proper format could not be found. There are three possible reasons: • BACKUP was stopped in the middle of a backup operation, resulting in an incomplete BACKUP tape. The "Bad Tape Format" was detected when unwanted or meaningless information was encountered at the interruption point on the tape. • The BACKUP tape was corrupted in some way.
7512 Bad tape format (Bad continuation indicator for beginning volume label). Cause. An attempt was made to restore a tape, but a BACKUP tape in the proper format could not be found. There are three possible reasons: • BACKUP was stopped in the middle of a backup operation, resulting in an incomplete BACKUP tape. The "Bad Tape Format" was detected when unwanted or meaningless information was encountered at the interruption point on the tape. • The BACKUP tape was corrupted in some way.
7514 Tape drive does not support density selection. Cause. The BACKUP DENSITY option was specified, but the tape drive does not implement density selection. Effect. BACKUP proceeds. Tape drive uses physical density setting. Recovery. Informational message only; no corrective action is needed. 7515 Bad tape format (End-of-file encountered where beginning volume label expected). Cause. An attempt was made to restore a tape, but a BACKUP tape in the proper format could not be found.
7518 End of tape encountered near the beginning of the tape. Cause. BACKUP encountered the end-of-tape near the beginning of the tape. Either the tape is too short, or there is a hardware problem in the tape drive, causing it to report the end-of-tape prematurely. Effect. BACKUP terminates. Recovery. Use a longer tape. If this is not the cause of the problem, have the tape drive checked. 7519 Tape verify encountered end-of-file where beginning/ending volume label expected. Cause.
Effect. BACKUP or RESTORE terminates. Recovery. Contact your service provider and provide all relevant information: • The information in this message • Description of the problem and accompanying symptoms • Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable If your local operation procedures require contacting the GCSC, supply your system number and the numbers and versions of all related products as well.
Effect. BACKUP terminates. Recovery. The SIT must fit on one reel. Mount a longer tape reel, and reissue the command. 7528 Not a BACKUP tape (bad label identifier). Cause. An attempt was made to restore a tape, but the label could not be read. Effect. RESTORE terminates. Recovery. Check that you are using the correct tape or create a new BACKUP tape. Then retry the RESTORE operation. 7529 Not a BACKUP tape. Cause. BACKUP requested a previous reel, and the reel mounted was not a BACKUP tape. Effect.
Recovery. If the invalid sequence number is a result of one of the first two causes, the files cannot be restored.
Cause. An attempt was made to restore a tape, but a BACKUP tape in the proper format could not be found. Three possible reasons are: • BACKUP was stopped in the middle of a backup operation, resulting in an incomplete BACKUP tape. The "Bad Tape Format" was detected when unwanted or meaningless information was encountered at the interruption point on the tape. • The BACKUP tape was corrupted in some way.
Cause. An attempt was made to restore a tape, but a BACKUP tape in the proper format could not be found. Three possible reasons are: • BACKUP was stopped in the middle of a backup operation, resulting in an incomplete BACKUP tape. The "Bad Tape Format" was detected when unwanted or meaningless information was encountered at the interruption point on the tape. • The BACKUP tape was corrupted in some way.
7752 Invalid system disk directory size. Cause. While attempting to create a system image tape, the directory size specified to SYSGEN in the SYSTEM_VOLUME_DIRECTORY_SIZE option included too many files for the disk. Effect. BACKUP terminates. Recovery. Specify a smaller directory size to SYSGEN and rerun SYSGEN. 7753 Keyword too long. Cause. The specified keyword was too long. Effect. BACKUP, BACKCOPY, or RESTORE terminates. Recovery. Check and reenter the command with the right keyword.
7759 Invalid slack value. Must be in the range 0 . . .99. Cause. An invalid slack value was specified. Effect. BACKUP or RESTORE terminates. Recovery. Make sure the slack value is in the range 0 through 99. 7760 Must be local to the system that BACKUP/RESTORE is running on. Cause. An attempt was made to restore a remote file. Effect. RESTORE terminates. Recovery. You can only restore files that are local to the system on which RESTORE resides. 7761 Invalid START file set.
Cause. The date was entered with a year prior to 1975. Effect. BACKUP or RESTORE terminates. Recovery. Correct the date or time and reissue the command. 7765 Bad date/time. Cause. The date was entered in an incorrect format. Effect. BACKUP or RESTORE terminates. Recovery. Correct the date or time in the format ddmmmyyyy,hh:mm and reissue the command. 7766 Colon between hour and minute expected. Cause. The time was entered without a colon between the hour and minute. Effect. BACKUP or RESTORE terminates.
7770 Bad density number. Expecting 800, 1600, or 6250. Cause. An invalid density number was specified. Effect. BACKUP or RESTORE terminates. Recovery. Reenter the command with a valid density number. 7771 Only a single volume can be backed up when VOL is specified. Cause. An attempt was made to dump more than one volume by using the VOL parameter. Effect. BACKUP terminates. Recovery. Restrict the backup to one volume.
Cause. An attempt was made to use both the VERIFYTAPE and VERIFYREEL options. Effect. BACKUP terminates. Recovery. Reenter the command, specifying only one of the options. 7777 More than one tape format option specified. Cause. An attempt was made to specify more than one tape format option (DP1FORMAT, DP2FORMAT, OLDFORMAT). Effect. BACKUP terminates. Recovery. Correct the tape option, and reenter the command. 7778 VERIFYTAPE is only allowed when LISTONLY is specified. Cause.
7782 Bad partition file number. Cause. An invalid partition file number was specified. Effect. BACKUP or RESTORE terminates. Recovery. Reenter the command with a partition file number in the range 1 through 15. 7783 Bad extent size. Cause. An invalid extent size was requested. Effect. BACKUP or RESTORE terminates. Recovery. Reenter the command with an extent size in the range 1 through 65535. 7784 PART parameter specified more than once for this secondary partition. Cause.
Cause. An attempt was made to issue a file name using the ALTFILE parameter, but the file name was already specified. Effect. BACKUP or RESTORE terminates. Recovery. Reissue the command, specifying a different file name in the ALTFILE parameter. 7789 Not allowed to specify new extent sizes with EXT or PART when PARTONLY or PARTOF specified. Cause. An attempt was made to change the extent size of an individual partition that was being converted. Effect. BACKUP or RESTORE terminates. Recovery.
Recovery. Reissue the command without wild-card characters in the START option. 7794 Not allowed to specify PARTOF and PART together. Cause. An attempt was made to use PARTOF with the PART option. Effect. RESTORE terminates. Recovery. Reenter the command, specifying either PARTOF or PART. 7795 3 character alphabetic month name expected. Cause. The month name in the BACKUP PARTIAL option is not in the required three-character alphabetic format. Effect. BACKUP fails and terminates. Recovery.
7801 The MYID option is not allowed in this copy of RESTORE. Cause. This older version of RESTORE does not support the MYID option. Effect. RESTORE fails and terminates. Recovery. Reissue the command without the MYID option or use a later version of RESTORE. 7802 Bad tape mode name. Expecting STARTSTOP or STREAM. Cause. An invalid TAPEMODE specification was used in the BACKUP command. Effect. BACKUP fails and terminates. Recovery.
Effect. RESTORE fails and terminates. Recovery. Specify either VOL or MAP NAMES, but not both, and reissue the command. 7810 Only one file renaming option can be specified. Cause. The RENAME and MAP NAMES options cannot be used in a single RESTORE command Effect. RESTORE fails and terminates. Recovery. Specify either RENAME or MAP NAMES, but not both, and reissue the command. 7811 PART/ALTFILE and MAP NAMES options are mutually exclusive. Must use only one of these. Cause.
7815 Expecting a complete fileset, *.*.*. Cause. BACKCOPY expects a complete file set, *.*.*, to be specified. Effect. BACKCOPY fails and terminates. Recovery. Specify *.*.* in the BACKCOPY command and reissue the command. 7816 PARTONLY and MAP NAMES cannot be used together without KEEP. Cause. The PARTONLY and MAP NAMES options cannot be used in a single RESTORE command unless you also use the KEEP option. Effect. RESTORE fails and terminates. Recovery.
Effect. RESTORE fails and terminates. Recovery. Reissue the command without these two options together or with the KEEP option added. 7831 Invalid REMOTEIOSIZE. Must be in the range 2 .. 52 and even. Cause. An invalid number was entered for REMOTEIOSIZE in a BACKUP command. Effect. BACKUP fails and terminates. Recovery. Reissue the command specifying an even number from 2 to 52. 7832 PARTONLY must be set when setting SQLTAPEPARTARRAY. Cause.
Effect. RESTORE fails and terminates. Recovery. Specify either ON, OFF, PARTIAL, or no parameter for the PARTONLY parameter, then reissue the RESTORE command. Specifying no parameter is the same as specifying ON. 7836 Invalid CATALOGFILES NUMBER. Must be in the range 1...20000 Cause. A RESTORE command was issued including both the NOSQLDATA and SQLCATALOGS option, which cannot be used in the same command. An invalid CATALOGFILES NUMBER (value of every-n-files ) was specified. Effect. BACKUP terminates.
8002 Tape DEFINE define is not LABELS BACKUP or LABELS BYPASS. Cause. A DEFINE was specified that was not LABELS BACKUP or LABELS BYPASS. Effect. RESTORE terminates. Recovery. Specify a LABELS BACKUP or LABELS BYPASS DEFINE. 8003 File names for the two parallel tape copies are not different. Cause. The same file name was specified for both copies of a parallel backup. Effect. BACKUP terminates. Recovery. Specify different file names when making a parallel backup.
8007 The SYSTEM attribute of the tape DEFINE define specifies a system, node, that is on a pre-C00 operating system. Cause. A node was specified with a DEFINE that is not running a C00.00 or later RVU. Effect. BACKUP or RESTORE terminates. Recovery. Specify a node running on a C00.00 or later RVU. 8008 The DEVICE attribute of the tape DEFINE define specifies a drive, drive, whose system is on a pre-C00 operating system. Cause. A node was specified with a DEFINE that is not running a C00.
8012 Duplicate volume ID found in the VOLUME attribute of the tape DEFINE define. Cause. A labeled tape volume ID was specified more than once in the VOLUME attribute's list of volume IDs. Effect. BACKUP or RESTORE terminates. Recovery. Specify a unique list of labeled tape volume IDs. 8013 Tape volume IDs for the two parallel copies are not unique. Cause. A labeled tape volume ID was specified in both VOLUME attribute lists of a parallel backup. Effect. BACKUP terminates. Recovery.
8025 Tape record is too short. Length: rec-len. Cause. This error could be caused by: • Corruption of the tape media • Dirty tape drive heads • Faulty tape drives • A BACKUP being stopped in the middle, resulting in an incomplete tape. • A software problem in BACKUP or RESTORE Effect. BACKUP or RESTORE terminates. Recovery. Investigate whether a corrupt tape or the tape drive is causing the problem.
Cause. This error could be caused by: • Corruption of the tape media • Dirty tape drive heads • Faulty tape drives • A BACKUP being stopped in the middle, resulting in an incomplete tape • A software problem in BACKUP or RESTORE Effect. BACKUP or RESTORE terminates. Recovery. Investigate whether a corrupt tape or the tape drive is causing the problem.
• Faulty tape drives • A BACKUP being stopped in the middle, resulting in an incomplete tape • A software problem in BACKUP or RESTORE Effect. BACKUP or RESTORE terminates. Recovery. Investigate whether a corrupt tape or the tape drive is causing the problem.
Effect. BACKUP or RESTORE terminates. Recovery. Investigate whether a corrupt tape or the tape drive is causing the problem.
Recovery. Investigate whether a corrupt tape or the tape drive is causing the problem. If not, identify the problem file. If the problem exists on another tape containing the identical file, it is probably a software problem.
Recovery. Investigate whether a corrupt tape or the tape drive is causing the problem. If not, identify the problem file. If the problem exists on another tape containing the identical file, it is probably a software problem.
Effect. BACKUP or RESTORE terminates. Recovery. Investigate whether a corrupt tape or the tape drive is causing the problem. If not, identify the problem file. If the problem exists on another tape containing the identical file, it is probably a software problem.
• Faulty tape drives • A BACKUP being stopped in the middle, resulting in an incomplete tape Effect. BACKUP or RESTORE terminates. Recovery. Investigate whether a corrupt tape or the tape drive is causing the problem. If not, identify the problem file. If the problem exists on another tape containing the identical file, it is probably a software problem.
Cause. This error could be caused by: • Corruption of the tape media • Dirty tape drive heads • Faulty tape drives • A BACKUP being stopped in the middle, resulting in an incomplete tape • A software problem in BACKUP or RESTORE Effect. BACKUP or RESTORE terminates. Recovery. Investigate whether a corrupt tape or the tape drive is causing the problem.
Cause. This error could be caused by: • Corruption of the tape media • Dirty tape drive heads • Faulty tape drives • A BACKUP being stopped in the middle, resulting in an incomplete tape • A software problem in BACKUP or RESTORE Effect. BACKUP or RESTORE terminates. Recovery. Investigate whether a corrupt tape or the tape drive is causing the problem.
• Faulty tape drives • A BACKUP being stopped in the middle, resulting in an incomplete tape • A software problem in BACKUP or RESTORE Effect. BACKUP or RESTORE terminates. Recovery. Investigate whether a corrupt tape or the tape drive is causing the problem.
Effect. BACKUP or RESTORE terminates. Recovery. Investigate whether a corrupt tape or the tape drive is causing the problem.
Recovery. Investigate whether a corrupt tape or the tape drive is causing the problem.
Recovery. Investigate whether a corrupt tape or the tape drive is causing the problem.
Recovery. Investigate whether a corrupt tape or the tape drive is causing the problem.
Recovery. Investigate whether a corrupt tape or the tape drive is causing the problem.
Recovery. Investigate whether a corrupt tape or the tape drive is causing the problem.
Recovery. Investigate whether a corrupt tape or the tape drive is causing the problem.
Recovery. Investigate whether a corrupt tape or the tape drive is causing the problem.
Recovery. Investigate whether a corrupt tape or the tape drive is causing the problem.
Cause. The tape could not be recognized. This could have been caused by mounting a tape not produced by BACKUP or by parity or checksum errors or a corrupted tape. Effect. RESTORE rewinds and unloads the tape and prompts for a tape. Recovery. If the drive used has a manual density switch, make sure that it is set to the correct density and try again. If the problem persists, see the cause and recovery for error 8025 (page 237). 8107 Found a regular labeled tape. Cause.
8113 Wrong tape mounted (Found tape #tape-num, expected tape #expected-tape-num). Cause. The wrong tape from a multitape tape set was mounted. Effect. RESTORE rewinds and unloads the tape and prompts for the correct tape. Recovery. Mount the correct tape. 8115 An EOF mark was not found after the Archive volume label set. Cause. An invalid tape format was discovered. Effect. RESTORE rewinds and unloads the tape and prompts for the correct tape. Recovery. Check the tape and remount it.
Cause. The first I/O operation attempted on a tape encountered a file-system error. Effect. BACKUP rewinds and unloads the tape and prompts for a tape. Recovery. For corrective action for the error number n, see the Guardian Procedure Errors and Messages Manual. 8120 Labeled tape mounted for input is a scratch tape. Cause. A tape that has been labeled or relabeled and has no data was mounted for reading. Effect. RESTORE rewinds and unloads the tape and prompts for another tape. Recovery.
Cause. A tape mount error was discovered during a labeled tape operation. Effect. BACKCOPY, BACKUP, or RESTORE tries to recover from the error until the operation succeeds or until a file-system error occurs. The error number is one of: • 120, the data parity error, which often indicates that the tape drive needs cleaning or that the tape is unusable • 190, undefined device error Recovery. If the error number is 120, clean the tape drive or try mounting a different tape.
Effect. BACKUP continues. Recovery. To make use of the parameter, use a drive capable of streaming. 8154 During repositioning an EOF mark was not found where it was expected. Cause. While repositioning the tape, to overwrite a terminated file, an EOF mark was not found where it was expected. Effect. BACKUP terminates. Recovery. See the cause and recovery sections of error 8025 (page 237). 8155 During repositioning an EOF mark was found where a record was expected. Cause.
Effect. BACKUP terminates. Recovery. Mount unique labeled tapes for the whole operation. 8159 The labeled tape has already been used in this tape set for the other copy. Cause. A labeled tape already written for the other copy was mounted again. Effect. BACKUP terminates. Recovery. Mount unique labeled tapes for the whole parallel backup operation. 8160 The file being aborted began on one of the earlier tapes. That tape will have to be remounted. Cause.
8166 Unable to turn on tape buffering due to insufficient I/O buffer space (file-system error n). Cause. The tape process reported that it was unable to allocate space for buffered mode. Effect. BACKUP and RESTORE proceed in unbuffered mode. The rate at which the tape is read or written might be lower than expected. Recovery. If this occurs frequently, memory utilization in the tape process processor should be examined.
B DCOM/DSAP Messages These error messages can appear on your terminal in response to a Disk Space Analysis Program (DSAP) or Disk Compression Program (DCOM) command. COMMAND ERROR: command Cause. A syntax error was encountered in a DSAP or DCOM command. Effect. DSAP or DCOM stops. Recovery. Rerun the command with the corrected syntax. COMPRESSION IS BEING TERMINATED Cause. DCOM encountered an invalid sector on the disk during the DCOM operation. Effect.
Recovery. For corrective action for the error number indicated by nnn, see the Guardian Procedure Errors and Messages Manual. DIRECTORY FILE NAMES NOT IN ASCENDING ORDER -- filename-1 FOLLOWS filename-2 Cause. The file names in the disk directory were not in ascending order. The directory is bad. Effect. DSAP or DCOM stops. Recovery. The procedure for fixing the directory is complex.
Effect. DCOM cancels the extent exchange but continues to run, working around the unmoved extents. Recovery. For corrective action for the error number indicated by nnn, see the Guardian Procedure Errors and Messages Manual. EXTENT MOVE LOGIC ERROR Cause. DCOM detected an error in the internal logic of the program. Effect. DCOM cancels the most recent extent move but continues to run, working around the unmoved extents. Recovery. None. FATAL DISK ERROR: nnn Cause. DCOM detected a fatal disk error.
Recovery. The procedure for fixing the directory is complex. Contact your service provider and provide all relevant information as follows: • The information in this message • Description of the problem and accompanying symptoms • Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable If your local operation procedures require contacting the GCSC, supply your system number and the numbers and versions of all related products as well.
Cause. DSAP or DCOM failed while trying to perform a physical I/O operation to the mirror (or primary) disk. Effect. DSAP or DCOM stops. Recovery. For corrective action for the error number indicated by nnn, see the Guardian Procedure Errors and Messages Manual. PLEASE ELIMINATE BAD SECTORS USING THE PUP SPARE COMMAND Cause. DSAP or DCOM detected that the disk contained unspared bad sectors. Effect. If this message appears during a DCOM run, DCOM terminates without performing any compression.
Effect. The utility (DSAP or DCOM) specified in the run command is not started. Recovery. You cannot use this version of DSAP or DCOM to analyze disk space use or compress files with the current operating system. If you need to compress files, see the discussion of consolidating disk free space in the system operator's guide for your system. Or upgrade your system to meet the requirements of DSAP and DCOM. UNABLE TO { OPEN } SYSDCOM.RECOVERY FILE, { CREATE } { SECURE } ERROR: nnn Cause.
Effect. DSAP or DCOM stops. Recovery. Reenter the command correctly. filename WRITE ERROR: nnn Cause. DCOM tried to perform a WRITE on the filename but encountered an error. Effect. DCOM continues its compression activities. It ignores this file, working around it, until it reaches the maximum number of extent moves specified. Recovery. For corrective action for the error number indicated by nnn, see the Guardian Procedure Errors and Messages Manual.
C PAK/UNPAK Messages This section describes the error messages that can arise when you use PAK or UNPAK. In addition to their own messages, PAK and UNPAK can display any BACKUP or RESTORE messages during their processing. num files created Cause. The -split option was used, and PAK created num files. Effect. None. Recovery. Informational message; no corrective action is necessary. 'after' command too long Cause. The length of the parameter to the -after option is larger than 255. Effect.
Cause. The string specified in the -comment option is too long. The maximum length is 255 characters not including the surrounding quotes. Effect. The program stops with completion code 2. No archive is created. Recovery. Correct the syntax and try again. Compressed bytes: num-bytes Cause. PAK has created an archive. num-bytes is the number of compressed data written to the archive file. Effect. None. Recovery. Informational message; no corrective action is necessary.
Cause. The file-system error error was encountered when writing to archive file filename. Effect. The program stops with completion code 2. The created archive file is purged. Recovery. For an explanation and possible recovery, use the ERROR command or see the Guardian Procedure Errors and Messages Manual. Error – 2013,Fileset not dumped (error 11) Cause. There was an attempt to compress an empty file set, or the file set is not available.
Effect. The program stops with completion code 2. If the -split option was used, any archive files already created are purged. Recovery. For an explanation and possible recovery, use the ERROR command or see the Guardian Procedure Errors and Messages Manual. File creation failed: Error 10 (File already exists), Filename filename Cause. File-system error 10 occurred when trying to create the archive file filename. An archive file with the name specified in the PAK command already exists. Effect.
Cause. The call to FILE_OPEN_ failed while the process was opening its program file. error is the return value of FILE_OPEN_. Effect. The program stops with completion code 2. The archive is created but is invalid. Recovery. This is an internal error. Report it to your service provider. FILE_OPEN_ of $RECEIVE failed: error Cause. The $RECEIVE file could not be opened. error is the error code returned by FILE_OPEN_. Effect. The program ABENDs. Possibly a saveabend file is created.
Effect. The program abends. Possibly a saveabend file is created. No archive is created, and no files are extracted. Recovery. This is an internal error. Report it to your service provider. INITDES failed Cause. The call to INITDES failed. This call initializes the encryption data structures. Effect. The program stops with completion code 2. The archive is not created. No files are extracted. Recovery. This is an internal error. Report it to your service provider. Invalid archive Cause.
Recovery. Re-create the archive. Invalid split size Cause. The file size given in the -split option is larger than 2147483647. Effect. The program stops with completion code 2. No archive is created. Recovery. Use a smaller file size and try again. Memory allocation failure: 1 Cause. The disk is full, so PAK cannot allocate memory for file buffers. Effect. The program stops with completion code 2. The created archive files are purged. Some files might have been extracted. Recovery.
Cause. The RESTORE process issued an unexpected WRITE operation. RESTORE should only read data from the UNPAK process. Effect. The program abends. Possibly a saveabend file is created. The archive extraction is interrupted. Recovery. This is an internal error. Report it to your service provider. TACL creation failed: error pc-err,detail-err Cause. The -after option was specified, but the needed TACL process could not start because of a PROCESS_CREATE_ error pc-err. detail-err is the detailed error code.
Effect. The program abends. Possibly a saveabend file is created. No archive is created, and no files are extracted. Recovery. If the default volume is not accessible, issue a VOLUME command to an accessible volume and resubmit the command after changing the appropriate volume references. For an explanation of the error code and possible recovery, use the ERROR command or see the Guardian Procedure Errors and Messages Manual.
Cause. The -password option was given in the UNPAK command, but the encryption version used in the archive file is not supported. The only supported version is 1. Effect. The program stops with completion code 2. No files are extracted. Recovery. Use a correct file name, remove -password, or re-create the archive. Warning: file might be corrupt Cause.
D Syntax Summaries BACKCOPY Syntax [[[\node.]$volume.]subvolume.]BACKCOPY [ / run-option [ , run-option ] ... / ] source-tape, dest-tape, *.*.* [ [ [ [ [ [ [ [ , , , , , , , , ARCHIVEFORMAT CATALOGFILES every-n-files { DENSITY density | TAPEMODE tapemode } LISTALL { NOREWINDIN | NOUNLOADIN } { NOREWINDOUT | NOUNLOADOUT } PAGELENGTH number VERIFYREEL ] ] ] ] ] ] ] ] BACKUP File-Mode Syntax [[[\node.]$volume.]subvolume.
[ [ [ [ [ [ [ [ , , , , , , , , SCRATCHVOL $volume ] SHAREOPEN ] SQLCATALOGS [ ON | OFF ] ] START [ $volume.] [ subvolume.] file-id ] TAPEMODE [ STARTSTOP | STREAM ] ] VERIFYREEL ] VERIFYTAPE ] VOL [ $new-vol.] new-subvol ] backup-files is: { fileset } { fileset-list } { qualified-fileset-list } fileset is: [[[ \node.]$volume.] subvolume.]file-id fileset-list is: ( fileset [ , fileset ] ... ) Qualified File-Set Lists qualified-fileset-list is: { list-element } { ( list-element [ , list-element ] ...
conditional is: < > BEFORE AFTER time-value is: day [ time ] | [ day ] time day is specified as: dd mmm yyyy | mmm dd yyyy where dd (day) is an integer from 1 through 31; mmm (month) is one of: JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, DEC, and yyyy (year) is a 4-digit integer from 1900 through 2999. The default for day is today's date. time is specified as: hh:mm[:ss ] where hh (hour) is an integer from 0 through 23; mm (minute) and ss (second) are 2-digit integers from 00 through 59.
UNSTRUCTURED [ SHORTHAND | PROTECTION ] VIEW NOTE: TRUSTED, TRUSTME, and TRUSTSHARED attributes are supported only on systems running H-series RVUs or J-series RVUs. BACKUP Volume-Mode Syntax [[[\ node.]$volume.]subvolume.]BACKUP [ / run-options / ] { tape-device-name } { ( tape-device-name1, tape-device-name2, ...
FREESPACE SHORT SPACE SUMMARY detail-selection-options AGE { [ OVER ] number | UNDER number } AUDITED BROKEN CRASHOPENED DEALLOC number ENSCRIBE EXPIRED LICENSED OPENED { [ OVER ] number | UNDER number } PARTITIONED PROGID ROLLFORWARD[NEEDED] SEPARATE SHOWNAMEMAP SHOWPATH SIZE { [ OVER ] number | UNDER number } SQL TEMPORARY UNEXPIRED UNUSED number USER [ group-name.user-name ] [ group-number , user-number ] [ -1 ] [ group-name.
[ , file-mode-restore-option ]... [ , ALTFILE ( key-file-number , [$volume.]subvolume. file-id ) ] [ , AUDITED [ , TURNOFFAUDIT ] ] [ , AUTOCREATECATALOG [ ON | OFF ] ] [ , CATALOG[S] ( catalog-name FOR fileset-list [ , catalog-name FOR fileset-list ] ...) ] [ , COLLATION[S] ( mapping-rule [, mapping-rule ...
RESTORE Volume-Mode Syntax RESTORE [ / run-option [, run-option ]... / ] { tape-device-name } { ( tape-device-name1, tape-device-name2, ...
E CLASS TAPE DEFINEs This appendix lists the attributes that can be used in a DEFINE of CLASS TAPE for labeled-tape processing. For more information about creating DEFINEs, see the TACL Reference Manual and the Guardian User's Guide. NOTE: You can also use CLASS TAPECATALOG DEFINEs to request scratch tapes for new tape files and cataloging of new tape files, and to access cataloged tape files. For more information, see the DSM/Tape Catalog User's Guide.
This definition applies only to BACKUP. Other applications, such as FUP, default to RETENTION=0, and the tape is considered "scratch" as soon as it is written. FILEID tape-file-name specifies the name of the tape file. The tape-file-namecan be as many as 17 characters long. If names are over 17 characters, only the right-most 17 characters are used. FILESECT volume-order specifies the position of this tape volume in a multivolume file, which is being created at the same time.
For IBM or IBMBACKUP labeled tapes, the owner ID can be from 1 through 10 characters long. PHYSICAL { number } identifies a backup volume set created by BACKCOPY that contains a file to which you want to read or write data. BACKCOPY is a standard Backup Restore utility. number is the physical copy number of the volume set you want and is specified in the range 1 through 99. The default is 1.
TAPEMODE { STARTSTOP | STREAM } specifies the operating mode for a cartridge tape drive such as the 5120. STARTSTOP is the default. For other than cartridge drives, this attribute is ignored. TAPEMODE is valid but ignored by Backup and Restore 2.0. The internally used value of TAPEMODE will always be STREAM. USE { IN | OUT | EXTEND | OPENFLAG } specifies how the tape file is to be used. IN—the file is to be read from tape. OUT—the file is to be written to tape.
Table 20 TAPE DEFINE Consistency Rules (continued) Check Number Description 7 If you specify LABELS BYPASS or LABELS OMITTED, then DEVICE is required, and these attributes might not be specified: BLOCKLEN, EBCDIC, EXPIRATION, FILEID, FILESECT, FILESEQ, GEN, OWNER, RECFORM, RECLEN, REELS, RETENTION, SYSTEM, USE, VERSION, and VOLUME. 8 If you specify VOLUME SCRATCH, then USE IN or USE EXTEND is not allowed. 9 If you specify LABELS IBM or LABELS IBM BACKUP, you must also specify FILEID and RECFORM.
F Tape Label Formats This appendix lists the standards for the two tape label formats (ANSI version-3 and IBM-MVS) that HP supports. In these tables, all fields of the standards are documented. However, HP does not support all fields within these standards. For example, IBM-specific fields such as VTOC Pointer are not supported. NOTE: "Spaces" and "Space" in the Content column of these tables indicate fields that HP does not support.
Character Position in the Field Name Label Record Length (in Bytes) Content 55 - 60 Block Count 6 Number of blocks written in this file section 61 - 73 Implementation Identifier 13 Spaces 74 - 80 Reserved for Future Standardization 7 Spaces ANSI HDR2/EOF2/EOV2 Label Format Character Position in the Label Record Field Name Length (in Bytes) Content 1-3 Label Identifier 3 "HDR" or "EOF" or "EOV" 4 Label Number 1 "2" 5 Record Format 1 "F": Fixed length "U": Undefined length 6 - 10
IBM HDR1/EOF1/EOV1 Label Format Character Position in the Label Record Field Name Length (in Bytes) Content 1-3 Label Identifier 3 "HDR" or "EOF" or "EOV" 4 Label Number 1 "1" 5 - 21 Data Set Identifier 17 Tape-file name 22 - 27 Data Set Serial Number 6 File-set name to which this volume belongs 28 - 31 Volume Sequence Number 4 Ordinal number of this volume within a multivolume data set 32 - 35 Data Set Sequence Number 4 Ordinal number of this data set within a multi-dataset file-se
Character Position in the Field Name Label Record Length (in Bytes) Content Space: Records are not blocked 40 - 42 Reserved for Future Standardization 8 Spaces 43 - 46 Serial Number (5180 Tape Drive only) 4 "NNNN": Unit's serial number in hexadecimal Spaces: device other than 5180 47 Device Address (5180 Tape Drive only) 1 "0": 5180 device Space: device other than 5180 48 Checkpoint Data Set Identifier 1 Space 49 - 80 Reserved for Future Standardization Spaces 296 Tape Label Formats 32
Index Symbols $SYSTEM.SYSTEM.
Commands, entering, 29 Compatibility of DCOM and the NonStop operating system, 83, 87 of DSAP and the NonStop operating system, 99 Completion codes DCOM, 85 DSAP, 98, 99 RESTORE, 157, 158 Converting files, 65 CRASHOPENED option (DSAP), 94 D Data Definition Language (DDL) for permanent workfile, 110 Data errors, ignoring, 54, 135 Data integrity, verifying on disk, 156 on tape, 69, 156 DCOM command entry exiting, 85 stopping, 85 syntax, 84, 85, 284 examples, 88, 89 guidelines for using changing the workfile
ALTFILE option, 47 AUDITED option, 48 BLOCKSIZE option, 50, 53 DP1FORMAT option, 52 DSLACK option, 53 EXT option, 53 ISLACK option, 55 including, in DSAP reports, 94 restoring guidelines, 159 options for, 126 Enscribe option (DSAP), 94 Ensure, 139 Entry-sequenced files, converting, during restore, 175 Error 45, avoiding, 175 Error messages see Messages Exceptional condition report (DSAP), 102 EXCLUDE qualifier, 43 Exiting BACKCOPY, 30 BACKUP, 30 DCOM, 85 DSAP, 93 RESTORE, 30 EXPIRATION attribute, 288 EXPIRE
Increase disk space see DCOM INDEXES option BACKUP, 55 RESTORE, 135 Install program, 40 ISLACK option BACKUP, 55 RESTORE, 136 MSGONLOCK option (BACKUP), 57 MULTIDRIVE option BACKUP, 58 RESTORE, 140 Multireel operations backup, 58 restore, 140 MYID option (RESTORE), 141 K N KEEP option (RESTORE), 136, 161 Key-sequenced files, converting, during restore, 175 Name mapping, 138, 140, 171, 172 NEEDBOTH, 58 Newformat option (DSAP), 95 NOMYID option (BACKUP), 58 NonStop operating system, compatibility with DC
command entry syntax, 285 introduction, 27 PART option BACKUP, 62, 63 RESTORE, 144, 146 Partial backup attributes, 43, 46 NOSAFEGUARD option, 59 NOT option, 60 PARTIAL option, 63, 64, 160 PARTONLY option, 65, 66 START option, 68, 69 PARTIAL option (BACKUP), 63, 64, 160 Partial restore NOSAFEGUARD option, 142 NOT option, 142, 143 PARTONLY option, 147, 149 START option, 154 Partitioned files backing up, 65, 66, 76 converting (DP1-DP2), 65 renaming secondary, 62, 63, 144, 146 restoring, 140, 146, 147, 149, 169
summarized, 126, 127 output, 132, 159 security of program file, 123, 124, 167 of SQL catalogs, 130 Restoring audited files, 127, 129, 144, 156 corrupt files, 135 entire volume, 157 existing files, 171 open files, 144 partitioned files, 140, 144, 146, 147, 149, 169 SQL catalogs, 153 SQL files, 170 name mapping, 138, 139, 171, 172 SQL indexes, 135 RETENTION attribute, 290 Rewinding tape reels, 61, 143 ROLLFORWARD option (DSAP), 96 S SAFEGUARD excluding files from backup, 59 excluding files from restore, 142
rewinding, 61 scratch, 176 verifying data, 69, 156 viewing contents, 159 TAPE DEFINEs see DEFINE (CLASS TAPE) Tape drives, using multiple, 58, 140 Tape formats defaults and options (table), 31, 32 used by BACKUP format 1, 52 format 2, 53 TAPEDATE option, RESTORE, 155 TAPEMODE attribute, 291 TAPEMODE option BACKCOPY, 35 BACKUP, 69 TARGET option (RESTORE), 155 Temporary files, 52, 66, 67, 97, 152 TEMPORARY option (DSAP), 97 Timestamp, controlling (RESTORE), 155 TMF and BACKUP, 48 and DCOM, 83 and DSAP, 96 and
