Page 1 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. HP Part Number: 523325-017 Published: February 2013...
Page 2 The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
Page 3: Table Of Contents
Tape Format History......................31 Using BACKUP and RESTORE With DSM/Tape Catalog..............32 2 BACKCOPY.....................33 Security..........................33 BACKCOPY Syntax.........................33 Guidelines........................36 Examples: Different Ways to Use BACKCOPY................37 Completion Information......................37 3 BACKUP....................39 Security..........................39 BACKUP and RESTORE Interaction....................40 BACKUP Syntax........................40 File Sets, File-Set Lists, and Qualified File-Set Lists..............42 Wild-Card Characters in a File Set..................42...
Page 4 ALTFILE..........................47 Guidelines........................48 Example........................48 ARCHIVEFORMAT......................48 Guidelines........................48 Example........................48 AUDITED..........................48 Guidelines........................48 BLOCKSIZE........................50 Guidelines........................50 CATALOGFILES........................51 Guideline........................51 DENSITY..........................51 Guidelines........................52 DP1FORMAT........................52 Guidelines........................52 DP2FORMAT........................53 Guidelines........................53 DSLACK...........................53 EXT..........................53 Guidelines........................54 Examples........................54 IGNORE...........................54 Guidelines........................54 INDEXES..........................55 Examples........................55 ISLACK..........................55 LISTALL..........................55 Guidelines........................55 MSGONLOCK........................57 Guidelines........................57 MULTIDRIVE........................58 Guideline........................58 Example........................58 NEEDBOTH........................58 Guideline........................58 Example........................58 NOMYID..........................58 NOPROMPT........................59 Example: Mounting a Tape for a BACKUP using NOPROMPT..........59 NOREWIND........................59 NOSAFEGUARD.......................59 Guidelines........................59...
Page 5 PART..........................62 Guidelines........................63 Example........................63 PARTIAL..........................63 Guidelines........................64 Example........................64 PARTONLY........................65 Guidelines........................65 Examples........................66 REMOTEIOSIZE.........................66 Guidelines........................66 SCRATCHVOL........................67 Guidelines........................67 SHAREOPEN........................67 Guidelines........................67 Example........................68 SQLCATALOGS.........................68 Guidelines........................68 START..........................68 Guidelines........................68 Example........................69 TAPEMODE........................69 Guidelines........................69 VERIFYREEL........................69 Guidelines........................69 VERIFYTAPE........................69 Guidelines........................70 VOL..........................70 Guidelines........................70 VOLUMEMODE.........................70 Guidelines........................71 WHOLEDISC........................71 Guidelines........................71 Completion Information......................71 BACKUP Guidelines and Examples...................72 Basic Backup Procedures....................72 Examples: Basic Backup Commands................73 Backing Up Format 1 and Format 2 Files................73 Using Qualified File-Set Lists....................74...
Page 6 Stopping DCOM........................85 Completion Information......................85 Guidelines..........................86 Examples of Compression Output.....................88 Before DCOM Moves File Extents..................88 While DCOM Moves File Extents..................88 After DCOM Moves File Extents...................88 Changing the Default Work File Volume..................89 5 Disk Space Analysis Program (DSAP)............90 Security..........................90 DSAP Syntax..........................91 Reporting SMF Files........................93 Exiting DSAP..........................93 Stopping DSAP........................93 DSAP Options........................93...
Page 7 Guidelines.........................127 Example........................127 AUDITED........................127 Guidelines.........................127 AUTOCREATECATALOG....................130 Guidelines.........................130 CATALOGS........................130 Guidelines.........................131 Example........................131 COLLATIONS........................131 Guidelines.........................132 Examples........................132 DETAIL..........................132 Guidelines.........................132 Example........................132 DSLACK.........................133 EMULATEFSF........................133 EXT..........................134 Guidelines.........................134 Examples........................135 IGNORE.........................135 Guidelines.........................135 INDEXES........................135 Guidelines.........................135 Examples........................136 ISLACK...........................136 KEEP..........................136 Guidelines.........................136 LISTALL...........................136 Guideline........................136 Example........................137 LISTONLY........................137 Guidelines.........................137 MAP NAMES........................138 Guidelines.........................138 Examples........................140 MULTIDRIVE........................140 Guidelines.........................141 Example........................141 MYID..........................141 Guideline........................141 NOPROMPT........................141...
Page 8 PAGELENGTH.........................144 Guidelines.........................144 Example........................144 PART..........................144 Guidelines.........................145 Examples........................146 PARTOF..........................146 Guidelines.........................146 Examples........................147 PARTONLY........................147 Guidelines.........................148 Examples........................149 PHYSVOL........................149 Guidelines.........................150 Example........................150 REBUILD.........................150 Guidelines.........................150 REGISTERONLY.......................151 REMOTEIOSIZE.......................151 Guidelines.........................151 RENAME........................152 Guidelines.........................152 SCRATCHVOL.........................152 Guideline........................153 SQLCATALOGS.......................153 Guidelines.........................153 SQLCOMPILE........................153 Guidelines.........................153 SQLTAPEPARTARRAY......................154 Guidelines.........................154 START..........................154 Guidelines.........................154 Example........................154 TAPEDATE........................155 Examples........................155 TARGET..........................155 Guidelines.........................156 TURNOFFAUDIT......................156 VERIFY...........................156 Guideline........................156 VERIFYTAPE........................156 Guideline........................156 VOL..........................156...
Page 9 Moving SQL Objects....................173 Restoring or Converting DP1 and DP2 Files.................174 Restoring From Labeled-Tapes....................175 Using Scratch Tapes....................176 Using the LABELS BYPASS DEFINE Attribute..............176 Examples........................177 Restoring in Volume Mode....................179 Example........................180 A BACKCOPY, BACKUP, and RESTORE Messages..........182 49............................182 1070...........................182 1500..........................182 2003..........................182 2012...........................182 2013...........................183 3nnn...........................183 6000..........................183...
Page 10: Contents
7031...........................190 7032..........................190 7033..........................190 7034..........................191 7035..........................191 7036..........................191 7037..........................191 7038..........................191 7039..........................192 7040..........................192 7041..........................192 7042..........................192 7043..........................192 7044..........................193 7045..........................193 7046..........................193 7047..........................193 7048..........................193 7049..........................194 7050..........................194 7052..........................194 7053..........................194 7054..........................194 7055..........................195 7057..........................195 7058..........................195 7060..........................195 7061..........................195 7062..........................196 7063..........................196 7064..........................196 7066..........................196 7069..........................196 7073..........................197 7075..........................197 7077..........................197 7078..........................197 7079..........................197 7080..........................197 7081..........................198 7083..........................198 7088..........................198 7089..........................198...
Page 11 7123...........................201 7124...........................201 7125...........................201 7126...........................201 7127...........................201 7128...........................202 7129...........................202 7130...........................202 7131...........................202 7132...........................202 7138...........................203 7139...........................203 7141...........................203 7142...........................203 7143...........................203 7144...........................203 7145...........................204 7146...........................204 7147...........................204 7157...........................204 7158...........................204 7159...........................205 7251...........................205 7252..........................205 7253..........................205 7254..........................205 7255..........................206 7257..........................206 7258..........................206 7259..........................206 7260..........................206 7264..........................207 7266..........................207 7267..........................207 7268..........................207 7269..........................207 7270..........................208 7271...........................208 7274...........................208 7500..........................208 7501..........................208 7502..........................209 7503..........................209...
Page 12: Contents
7519...........................215 7520..........................215 7523..........................215 7524..........................216 7525..........................216 7526..........................216 7527..........................216 7528..........................217 7529..........................217 7530..........................217 7532..........................217 7533..........................218 7534..........................218 7535..........................218 7536..........................219 7537..........................219 7542..........................220 7750..........................220 7751...........................220 7752..........................221 7753..........................221 7754..........................221 7755..........................221 7757..........................221 7758..........................221 7759..........................222 7760..........................222 7761...........................222 7762..........................222 7763..........................222 7764..........................222 7765..........................223 7766..........................223 7767..........................223 7768..........................223 7769..........................223 7770..........................224 7771..........................224 7772..........................224 7774..........................224 7775..........................224 7776..........................224 7777..........................225...
Page 13: Contents
7791..........................227 7792..........................227 7793..........................227 7794..........................228 7795..........................228 7796..........................228 7797..........................228 7799..........................228 7801..........................229 7802..........................229 7803..........................229 7807..........................229 7808..........................229 7809..........................229 7810...........................230 781 1...........................230 7812...........................230 7813...........................230 7814...........................230 7815...........................231 7816...........................231 7818...........................231 7819...........................231 7820..........................231 7824..........................231 7831...........................232 7832..........................232 7833..........................232 7834..........................232 7835..........................232 7836..........................233 7837..........................233 7900..........................233 8000..........................233 8001..........................233 8002..........................234 8003..........................234 8004..........................234 8005..........................234 8006..........................234 8007..........................235 8008..........................235...
Page 14: Contents
8030..........................239 8031..........................239 8032..........................240 8033..........................240 8034..........................241 8035..........................241 8036..........................242 8037..........................242 8038..........................243 8039..........................243 8040..........................244 8050..........................244 8051..........................245 8052..........................245 8053..........................246 8054..........................246 8055..........................247 8056..........................247 8057..........................248 8058..........................248 8059..........................249 8060..........................249 8061..........................250 8062..........................250 8063..........................251 8064..........................251 8065..........................252 8066..........................252 8067..........................253 8068..........................253 8069..........................254 8070..........................254 8071..........................255 8072..........................255 8100...........................256 8101...........................256 8102...........................256 8103...........................256 8106...........................256 8107...........................257 8108...........................257 81 10...........................257 81 1 1............................257...
Page 15 8165...........................262 8166...........................263 8167...........................263 8168...........................263 8169...........................263 8170...........................263 B DCOM/DSAP Messages.................264 C PAK/UNPAK Messages................271 D Syntax Summaries..................281 BACKCOPY Syntax.......................281 BACKUP File-Mode Syntax.....................281 Qualified File-Set Lists.......................282 BACKUP Volume-Mode Syntax....................284 DCOM Syntax........................284 DSAP Syntax........................284 PAK/UNPAK Syntax......................285 RESTORE File-Mode Syntax....................285 RESTORE Volume-Mode Syntax....................287 E CLASS TAPE DEFINEs................288 TAPE DEFINE Attributes......................288...
Page 16 Tape Formats........................31 History and Attributes of Tape Formats................31 Default Tape Formats and Tape Format Options..............32 Completion Codes Returned by BACKCOPY and the Operating System........37 File Attributes for the WHERE Expression................45 BACKUP and TMF Interaction While Backing Up Audited Files..........49 BACKUP Completion Codes....................71 BACKUP Guidelines and Examples..................72...
Page 17: What's New In This Manual
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.00 and all subsequent G-series RVUs, until otherwise indicated by its...
Page 18 Changes to the 523325-014 Manual Removed the procedure for restoring EKS files to classic key-sequenced files. Changes to the 523325-013 Manual Added HP Encourages Your Comments (page 23). Updated Restoring Enscribe Files (page 159). Added Restoring SQL Files (page 166).
Page 19: About This Manual
This manual is written for system operators, system managers, and all other users of the disk and tape utilities. You should be familiar with: The user interface for the NonStop operating system The user interface for the HP Tandem Advanced Command Language (TACL) command interpreter Basic NonStop system operations...
Page 20: Related Documentation
Related Documentation These manuals provide additional information that relates to this manual:: File Utility Program (FUP) Reference Manual Guardian Procedure Errors and Messages Manual Guardian User’s Guide For information about other products referenced in this manual: Backup and Restore 2.0 Manual Binder Manual DSM/Tape Catalog Operator Interface (MEDIACOM) Manual DSM/Tape Catalog User’s Guide...
Page 21 TERM [\system-name.]$terminal-name INT[ERRUPTS] A group of items enclosed in brackets is a list from which you can choose one item or none. The items in the list may be arranged either vertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines.
Page 22: Notation For Messages
!i:i. In procedure calls, the !i:i notation follows an input string parameter that has a corresponding parameter specifying the length of the string in bytes. For example: error := FILENAME_COMPARE_ ( filename1:length !i:i , filename2:length ) ; !i:i !o:i. In procedure calls, the !o:i notation follows an output buffer parameter that has a corresponding input parameter specifying the maximum length of the output buffer in bytes.
Page 23: Notation For Management Programming Interfaces
In the CRE, the message type SYSTEM includes all messages except LOGICAL-CLOSE and LOGICAL-OPEN. HP Encourages Your Comments HP encourages your comments concerning this document. We are committed to providing documentation that meets your needs. Send any errors found, suggestions for improvement, or compliments to docsfeedback@hp.com.
Page 24: Disk And Tape Utilities Overview
RESTORE BACKCOPY The BACKCOPY utility makes duplicates of any tape created using the file-mode feature of the BACKUP utility. The BACKCOPY utility can create up to two duplicate tapes for archiving, distribution, or disaster recovery. BACKCOPY can be used for migrating backups from or to appendable pools.
Page 25: Backcopy Utility
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.
Page 26: Dcom Utility
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.
Page 27: Pak/Unpak
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.
Page 28: Using Backcopy, Backup, And Restore
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.
Page 29: Entering Backup And Restore Commands
For a BACKUP or BACKCOPY process, ensure the output tape media is write-enabled. For tape reels be sure the write ring is inserted. For a RESTORE or BACKCOPY ensure the input tape media is not write-enabled. For tape reels be sure the write ring is removed.
Page 30: Exiting The Program
Mount correct tape #n? Mount next tape #n? Mount previous tape #n? For each subsequent prompt, go to Step 5. When no more tape prompts appear, go to Step If you used the NOPROMPT option, this noninteractive message appears: $tape: device not ready -- beginning to poll -- Mount the first (or the next) tape.
Page 31: Tape Formats
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.
Page 32: Using Backup And Restore With Dsm/Tape Catalog
Override: Tape format 1 if DP1FORMAT BACKUP option is specified d. Override: Tape format 2 if DP2FORMAT BACKUP option is specified e. Override: Tape format 3 if ARCHIVEFORMAT BACKUP or BACKCOPY option is specified D32 (ADL)—D38, D42 a. Default: Tape format 3 (ADE)—D48, Gxx...
Page 33: Security
It can also create one or two labeled (or unlabeled) tape sets from a labeled or unlabeled tape set. Although BACKCOPY generates a tape in the same tape format as the original when it makes one duplicate copy of a tape, it generates tapes in tape format 3 (archive format) when it makes two duplicate copies of a tape.
Page 34 DEFINE name of CLASS TAPE for copying a labeled backup tape. For a list of all CLASS TAPE DEFINE attributes, see Appendix E: CLASS TAPE DEFINEs. *.*.* specifies that all files on source-tape are copied to dest-tape. You must use this syntax (*.*.*). You cannot specify individual files. BACKCOPY...
Page 35 BACKCOPY output. The value of number must be an integer in the range 20 through 100. When BACKCOPY output is sent to a printer, a form feed (or page eject) is generated after the number of lines specified in the PAGELENGTH option.
Page 36: Guidelines
Guidelines Consider these guidelines when using BACKCOPY: BACKCOPY copies all files. If BACKCOPY cannot read a file because of a parity or checksum error, it displays an error message and the tape duplication fails. BACKCOPY automatically generates tapes in tape format 3 if any of these are true: ◦...
Page 37: Examples: Different Ways To Use Backcopy
Completion Information BACKCOPY returns a completion code to the process that started it. The completion code indicates how successfully BACKCOPY ran. Its primary purpose is to support batch processing by allowing conditional execution of subsequent processes based on the success of the BACKCOPY operation.
Page 38 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.
Page 39: Security
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).
Page 40: Backup And Restore Interaction
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).
Page 41 [ / 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.
Page 42: File Sets, File-Set Lists, And Qualified File-Set Lists
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.
Page 43: File-Set List Qualifiers
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 ] ...
Page 44 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.
Page 45: Contents 1
Attribute Specifies... AUDITED Files audited by the HP NonStop Transaction Management Facility (TMF). BROKEN Files marked broken (files that need media recovery because an I/O or a consistency check failure occurred the last time it was open). A likely use is WHERE NOT BROKEN.
Page 46: File-Mode Backup Options
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).
Page 47: Volume-Mode Backup Options
CATALOGFILES NOTE: File mode BACKUP filters out but does not back up HP NonStop Storage Management Foundation (SMF) physical files (files named ZYS*.* or ZYT*.*). These files are not visible to BACKUP. If you attempt a backup for $P.ZYS*.*, BACKUP responds indicating zero files were backed up.
Page 48: Example
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.
Page 49: Backup And Tmf Interaction While Backing Up Audited Files
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.
Page 50: Blocksize
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: Ensure the safe and complete recovery of files when media recovery is needed. At a SCF prompt, type: 1>...
Page 51: Catalogfiles
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).
Page 52: Dp1Format
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 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.
Page 53: Dp2Format
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.
Page 54: Examples
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.
Page 55: Indexes
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...
Page 56: Listing Format
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: Name of the tape drive used. Tape: [\node.]$tape Version of the NonStop host. Operating System: vsn Tape format in use with this operating system.
Page 57: Msgonlock
Security of the listed file for read, write, execute, and purge access. Four RWEP rwep asterisks (****) indicate that the listed file is protected by Safeguard. File type of the listed file. The type can be any of: Type type blank = unstructured R = relative E = entry-sequenced...
Page 58: Multidrive
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. MULTIDRIVE Guideline If a tape drive is unavailable or off-line, or if a tape is not mounted when the BACKUP utility tries to write to that drive, BACKUP polls the drive and displays this message: $tape: device not ready -- beginning to poll -- The BACKUP process continues in this state until it detects that the drive is ready, with a tape...
Page 59: Noprompt
NOREWIND is mutually exclusive with NOUNLOAD. If neither is specified the default is to unload the tape. If NOREWIND is specified for an unlabeled tape and an attempt is made to read (RESTORE/BACKCOPY) or write (BACKUP/BACKCOPY) to the tape without first manually repositioning the tape, the utility abends with Error 8103. NOSAFEGUARD The NOSAFEGUARD option excludes Safeguard security information in a BACKUP process.
Page 60: Nosqldata
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.
Page 61: Nounload
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.
Page 62: Pagelength
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.
Page 63: Partial
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;...
Page 64: Guidelines
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.
Page 65: Partonly
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 ] specifies that only the partitions of a file explicitly named in backup-files are backed up.
Page 66: Remoteiosize
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.
Page 67: Scratchvol
This may result in inconsistent file data on the backup tape. This warning message also appears before a BACKCOPY or RESTORE that uses a BACKUP tape made by using the SHAREOPEN option. You cannot use OPEN and SHAREOPEN in the same BACKUP command.
Page 68: Sqlcatalogs
BACKUP command. Guidelines Use SQLCATALOGS ON to dump all SQL catalogs when reporting a problem to HP support. Otherwise, do not use this option to back up SQL objects. During a RESTORE procedure, a catalog table can be restored only as an ordinary (noncatalog) table with a file code of 0.
Page 69: Tapemode
$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>...
Page 70: Volumemode
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.
Page 71: Wholedisc
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. If you attempt a volume-mode backup from a disk with a capacity greater than 2 GB, you will be unable to restore it to an operating system version prior to D30, and this message is generated:...
Page 72: Basic Backup Procedures
Table 9 BACKUP Completion Codes (continued) Code Description 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.
Page 73: Examples: Basic Backup Commands
\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>...
Page 74: Using Qualified File-Set Lists
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.
Page 75 Always use BACKUP to back up SQL objects, but only use the SQLCATALOGS ON option to dump all SQL catalogs when reporting a problem to HP support. BACKUP and RESTORE do not work with remote SQL tables if SQL is not installed on the local node.
Page 76: Backing Up Or Converting Dp1 And Dp2 Files
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>...
Page 77: Backing Up With Labeled Tapes
76). For a description of MEDIACOM, see the DSM/Tape Catalog Operator Interface (MEDIACOM) Manual. Three types of labeled tapes can be used with BACKUP, BACKCOPY, and RESTORE: ANSI, IBM, and BACKUP. BACKUP can write to scratch ANSI, scratch IBM, and BACKUP labeled tapes.
Page 78: Labeled Backup Tape Volume Labels
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. The initialized IBM tape, as defined by the IBM-MVS standard, contains: ◦...
Page 79: Using Scratch Tapes
Table 1 1 Permissible DEFINE Attributes for Labeled-Tape Backup (continued) Attribute Description 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.
Page 80: Backing Up In Volume Mode
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. To use the DEFINE =MYBACKUP to specify using two scratch tape volumes, NY082 and NY004, as backup tapes and to give the expiration date of December 31, 2001: 1>...
Page 81 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.
Page 82 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. After the backup finishes, bring up the mirrored volume so that both halves of the mirrored volume match: START DISK $DATA EXIT...
Page 83: Disk Compression (Dcom)
4 Disk Compression (DCOM) The Disk Compression (DCOM) utility moves disk file extents to yield more usable space on a disk. You can use DCOM to: Analyze the current space allocation on a disk Relocate file extents on a disk Reduce the number of free-space extents, which reduces the effort needed to allocate or deallocate space Combine free space into larger extents so that files can be allocated with larger extents, which...
Page 84 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.
Page 85: Handling Smf Files
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.
Page 86: Dcom Completion Codes
The completion information returned by DCOM includes these fields: Field Description An integer that describes how DCOM terminated (see Table completioncode An integer that describes the nature of errors or warnings (see Table terminationinfo Contains the DCOM subsystem ID, TANDEM.32.release, where release is the subsystem release version of DCOM (D42, for example) A character string describing the code in terminationinfo (see...
Page 87 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.
Page 88: Examples Of Compression Output
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.
Page 89: Changing The Default Work File Volume
Figure 1 1 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.
Page 90: Disk Space Analysis Program (Dsap)
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.
Page 91: Dsap Syntax
DSAP Syntax DSAP is a noninteractive, privileged program that runs online while the disk is operating. It can generate reports for more than one disk volume during a single run. The default output device is the home terminal, but you can specify other types of output devices, such as a disk file or printer.
Page 92 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. For example: DSAP * Reports on ALL volumes DSAP ($DATA1,$SYSTEM) Reports on the specified volumes DSAP $D* Reports on all volumes beginning with the letter D DSAP $DATA?
Page 93: Reporting Smf Files
[ -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.
Page 94: Sample Subvolume Summary Report
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). That is, DSAP generates the SUMMARY, FREESPACE, FILESPACE, FILESIZE, BYSUBVOL, and BYUSER reports.
Page 95: Sample File-Size Distribution Report (Filesize)
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. If the EXTENTCHECK option is not specified, then directory changes occur during the copy attempt, DSAP continues the summary report without checking the extent consistency and issues this message: Free space changed during directory copy.
Page 96 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.
Page 97 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). For example, these commands produce the same results: 1>...
Page 98: For Sql/Mx Objects
$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).
Page 99: Guidelines: Running Dsap
Table 13 DSAP Completion Codes Code Explanation A normal, voluntary termination of DSAP with no errors or warnings. 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.
Page 100 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.
Page 101: Report Formats
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...
Page 102: Summary Of Space Use
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.
Page 103: Space Distribution Reports
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.
Page 104: Sample Free-Space Distribution Report
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>...
Page 105: Report By Subvolume
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.
Page 106: Report By User
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:...
Page 107: Sample User Detail Report
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: Redoneeded (or undoneeded) is necessary for the file or label (base and index tables) or for...
Page 108: Sample Of The Short Report
SQL Type: A maximum of three characters can be displayed in this field. ◦ The first position of the SQL Type field displays one of these values: SQL protection view SQL shorthand view blank Any other type of SQL object or Enscribe file ◦...
Page 109: Newformat Report
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.
Page 110: System Manager Or System Operator Examples
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.#PRTR/ $DATA, ANALYSIS, DETAIL To produce a free-space distribution report about $DATA, which can be used to track space use and detect errors on the disk before they cause problems: 1>...
Page 111: Changing The Default Work File Volume
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.
Page 112: Ddl Format Of The Permanent Work File
The format of the DSAPDDL template used by Enform to produce written reports is displayed in Figure 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. Figure 21 DDL Format of the Permanent Work File 1 12 Disk Space Analysis Program (DSAP)
Page 113 Format of the Permanent Work File 1 13...
Page 114 1 14 Disk Space Analysis Program (DSAP)
Page 115: Work File Guidelines
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.
Page 116 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.
Page 117: Pak Command Options
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.
Page 118: Pak Run Options
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.
Page 119 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.
Page 120: Unpak Command Options
-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.
Page 121: Considerations
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).
Page 122 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.
Page 123: Restore
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.) List the contents of a tape without restoring data Convert files from one disk-process type to another type (for example, from DP1 to DP2) CAUTION:...
Page 124: Restore Syntax
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).
Page 125 { 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.
Page 126: File-Mode Restore Options
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.
Page 127: Interaction Between Restore And Tmf
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.
Page 128 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.
Page 129 *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: Ensure the safe, complete recovery of files when media recovery is needed. At an SCF prompt, type: 1>...
Page 130: Autocreatecatalog
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.
Page 131: Collations
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.
Page 132: Detail
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.
Page 133: Dslack
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...
Page 134: Guidelines
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.
Page 135: Ignore
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>...
Page 136: Islack
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.
Page 137: Listonly
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. File Mode RESTORE Program - T9074D46 (07SEP98) System: \BOSTON Copyright Tandem Computers Incorporated 1981-1998...
Page 138: Map Names
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). MAP NAMES The MAP NAMES option can be used for: Renaming files as they are restored Restoring files to a new volume or node within the network where they were backed up Restoring files to a different network from the one where they were backed up...
Page 139 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.
Page 140: Examples
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>...
Page 141: Myid
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. If a tape drive is unavailable or off-line, or if a tape is not mounted when the RESTORE utility attempts to process on that drive, RESTORE polls the drive and displays: $tape: device not ready -- beginning to poll -- The RESTORE process continues in this state until it detects that the drive is ready, with the...
Page 142: Nopurgeuntil
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.
Page 143: Guidelines
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.
Page 144: Open
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).
Page 145: Guidelines
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).
Page 146: Partof
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>...
Page 147: Examples
RESTORE PARTONLY ON session. If the BACKUP tape contains partitioned or multiple indexes for a single table, HP strongly recommends that you perform the final PARTONLY ON operation specifying the primary partitions of the table and index.
Page 148: Guidelines
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.
Page 149: Physvol
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.
Page 150: Rebuild
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.
Page 151: Registeronly
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 ] 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.
Page 152: Rename
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.
Page 153: Guideline
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.
Page 154: Sqltapepartarray
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.
Page 155: Tapedate
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 ] sets the last modification and last open timestamps of the restored files to the values they had when the files were backed up.
Page 156: Turnoffaudit
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.
Page 157: Completion Information
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).
Page 158: Completion Codes Returned By Restore And The Operating System
(page 175) Restoring in Volume Mode (page 179) NOTE: The current node in a RESTORE process is where the utility is running. HP recommends that you run RESTORE on the same node where the files were backed up. 158 RESTORE...
Page 159: Viewing The Contents Of A Tape
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,*.*.*, VERIFYTAPE, LISTONLY RESTORE displays a listing at the home terminal similar to: File RESTORE Program - T9074D46 - (07SEP98) System: \GLOBE...
Page 160 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.
Page 161: Restoring Enscribe Eks Files To Classic Key-Sequenced Files
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.
Page 162: Sample Tacl Script To Convert An Enscribe 64P File To 16P
NOTE: To restore an enhanced key-sequenced file (more than 16 partitions) onto a system which only supports classic key-sequenced files (up to 16 partitions), you need to: Restore each partition from the enhanced key-sequenced file onto the system one at a time. Attach that partition to a temporary classic key-sequenced file to gain access to the data records in the partition.
Page 163 ======================================================================== #frame #push AF AN cmd parts pext sext temploc 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:63); end; #set #inlineprefix + #set #informat tacl #output +----------------------------------------------------------+...
Page 164 #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.
Page 165 #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 !!!!
Page 166: Restoring Sql Files
[#if ([#fileinfo /existence/ [tgt_file] ]) |then| #set done 1 |else| #output Error - [tgt_file] file does not exist. =========================================== == Start the restoration work =========================================== #set count [#compute ([#charfind partfile 1 .] + 1)] #set tfile [#charget partfile [count] for [#compute ([#charcount partfile] - [count] + 1) ] ] #set tloc [#charget temploc 1 FOR [#compute ([#charfind temploc 1 .] - 1) ] ] #set count 1 == no need for part 0...
Page 167 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.
Page 168 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.
Page 169: Examples: Restoring Sql Files
◦ 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:...
Page 170 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.
Page 171: Restoring Existing Disk Files
To include the MAP NAMES option in the previous example and restore the files to another volume: 1> RESTORE $TAPE, ($A.*.*, $B.*.*),& 1> &MAP NAMES ($A.*.* TO $C.*.*, $B.*.* TO $D.*.*),& 1> &CATALOGS ($C.CAT FOR $C.*, $D.CAT for $D.*),& 1> &LISTALL, AUDITED This command produces these results: ◦...
Page 172: Restoring Files From Multiple Systems
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.
Page 173: Qualified File Sets
\??.$VOL.SUBVOL Table1 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 ),&...
Page 174: Restoring Or Converting Dp1 And Dp2 Files
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.
Page 175: Restoring From Labeled-Tapes
You can perform labeled-tape BACKUP and RESTORE processes using either file mode or volume mode. BACKUP, RESTORE, and BACKCOPY send a labeled-tape request through a CLASS TAPE DEFINE to the labeled-tape server process ($ZSVR). It passes messages about labeled-tape operations to the operator console ($0) and the MEDIACOM console (if one exists).
Page 176: Using The Labels Bypass Define Attribute
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.
Page 177: Examples
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>...
Page 178 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>...
Page 179: Restoring In Volume Mode
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.SILO1_FILECAT, FILEID W00007, USE IN 3>...
Page 180: Example
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. ◦...
Page 181 1> SCF STATUS DISK $DATA 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: Use the SCF CONTROL DISK, SPARE command to correct the situation.
Page 182: A Backcopy, Backup, And Restore Messages
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*. access violation Cause. The version of BACKUP or RESTORE in use is not licensed.
Page 183 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.
Page 184 PARTONLY ON option of BACKUP. Effect. No partitions are restored. Recovery. Re-create the tape by using the PARTONLY ON option for BACKUP and RESTORE, or add the PARTONLY ON option to the RESTORE command. 184 BACKCOPY, BACKUP, and RESTORE Messages...
Page 185 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.
Page 186 If your local operation procedures require contacting the GCSC, supply your system number and the numbers and versions of all related products as well. 7014 Data bad (Error n, Address b, Length l). Cause. BACKUP encountered an error trying to read data. The IGNORE option was specified. 186 BACKCOPY, BACKUP, and RESTORE Messages...
Page 187 Effect. Because the IGNORE option was specified, BACKUP writes the bad data to tape. 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.
Page 188 Effect. BACKUP or RESTORE converts the file with the old extent sizes. Recovery. New extents can be specified only when converting an entire partitioned file. 7024 EXT parameter not applied when converting unstructured partitioned files. 188 BACKCOPY, BACKUP, and RESTORE Messages...
Page 189 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.
Page 190 Recovery. Use B10 RESTORE or B00 RESTORE2. 7033 This tape can only be restored with TNS/II RESTORE (B41, C00 or later). Cause. The tape was created by BACKUP2. Effect. BACKUP execution continues. Recovery. Use B41 RESTORE. 190 BACKCOPY, BACKUP, and RESTORE Messages...
Page 191 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.
Page 192 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. 7043 Entire partitioned file aborted. 192 BACKCOPY, BACKUP, and RESTORE Messages...
Page 193 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.
Page 194 Cause. The primary partition volume name is the same as one or more of the secondary partitions. Effect. BACKUP or RESTORE skips the partitioned file and continues processing the fileset. Recovery. Reenter the command using the PART or VOL parameter to specify a different volume name for the partitions. 194 BACKCOPY, BACKUP, and RESTORE Messages...
Page 195 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.
Page 196 Effect. BACKUP or RESTORE terminates. Recovery. Use the SCRATCHVOL parameter to specify a volume or (if the default volume is nonexistent) select an existing volume using the command interpreter VOLUME command. 196 BACKCOPY, BACKUP, and RESTORE Messages...
Page 197 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.
Page 198 Effect. The file is restored, but the Safeguard information is not restored. The file is not protected by the Safeguard product. Recovery. Repeat the RESTORE operation when the Safeguard monitor is running. 198 BACKCOPY, BACKUP, and RESTORE Messages...
Page 199 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.
Page 200 Tape boot at beginning of System Image tape not copied Cause. A BACKCOPY operation is being performed on a system image tape. Effect. The tape boot record is not copied to the destination tape; BACKCOPY continues. Recovery. Informational message only; no corrective action is needed.
Page 201 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.
Page 202 Cause. The specified file included a volume name but not a subvolume name. Subvolume defaulting will not be supported in future releases. Effect. BACKUP or RESTORE continues. Recovery. Informational message only no corrective action is needed. 202 BACKCOPY, BACKUP, and RESTORE Messages...
Page 203 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.
Page 204 RESTORE. Recovery. Informational message only no corrective action is needed. 7158 The REMOTEIOSIZE cannot exceed BLOCKSIZE. It has been rounded down to nn. Cause. BACKUP rounded down the REMOTEIOSIZE. Effect. BACKUP continues. 204 BACKCOPY, BACKUP, and RESTORE Messages...
Page 205 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.
Page 206 Recovery. Fix the disk format or change the disk name and retry the operation. 7260 Bad disk volume label. Cause. BACKUP encountered a faulty disk volume label. Effect. BACKUP terminates. Recovery. Correct the disk volume label and retry the operation. 206 BACKCOPY, BACKUP, and RESTORE Messages...
Page 207 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.
Page 208 7 track tape drive cannot be used for BACKUP/RESTORE. Must be a 9 track drive. Cause. An attempt was made to run BACKUP or RESTORE with a 7-track tape drive. Effect. BACKUP or RESTORE terminates. Recovery. Use a 9-track tape drive. 208 BACKCOPY, BACKUP, and RESTORE Messages...
Page 209 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.
Page 210 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. BACKCOPY, BACKUP, and RESTORE Messages...
Page 211 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.
Page 212 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. BACKCOPY, BACKUP, and RESTORE Messages...
Page 213 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.
Page 214 Recovery. Verify the density and try again. If the parity error persists, type STOP at the prompt. Try other tape drives. If parity errors occur on a number of tape drives, the tape cannot be restored. BACKCOPY, BACKUP, and RESTORE Messages...
Page 215 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.
Page 216 If your local operation procedures require contacting the GCSC, supply your system number and the numbers and versions of all related products as well. 7527 System image tape too short. Cause. A tape reel that was too short was specified to create a System Image Tape (SIT). BACKCOPY, BACKUP, and RESTORE Messages...
Page 217 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.
Page 218 Effect. BACKUP or RESTORE unloads the tape and prompts for the correct reel. Recovery. Mount the correct BACKUP tape, and press Return at the prompt. 7535 Bad tape format (Too many data blocks found for file on tape). BACKCOPY, BACKUP, and RESTORE Messages...
Page 219 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.
Page 220 Invalid BLOCKSIZE. Must be in the range 2 . . 30 and even. Cause. An invalid data record size was specified. Effect. BACKUP or RESTORE terminates. Recovery. Make sure your BLOCKSIZE is an even integer value from 2 through 30, inclusive. 220 BACKCOPY, BACKUP, and RESTORE Messages...
Page 221 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. 7754 Missing parameter.
Page 222 Cause. An invalid month name was used. Effect. BACKUP or RESTORE terminates. Recovery. Correct the command by using only the first three letters of the month name, and retry the command. 7764 Bad date/time (Year must be 1975 or beyond). 222 BACKCOPY, BACKUP, and RESTORE Messages...
Page 223 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.
Page 224 Effect. BACKUP terminates. Recovery. Old format tapes do not contain checksums and sequence numbers to verify. Reenter the command without specifying the VERIFYTAPE or VERIFYREEL option. 7776 Not allowed to specify both VERIFYTAPE and VERIFYREEL. 224 BACKCOPY, BACKUP, and RESTORE Messages...
Page 225 7779 '(' expected. Cause. An opening parenthesis "(" was expected. Effect. BACKUP, BACKCOPY, or RESTORE terminates. Recovery. Insert the required parenthesis, and reenter the command. 7780 ')' expected. Cause. A closing parenthesis ")" was expected.
Page 226 Cause. A volume name was specified that had already been specified in a PART parameter. Effect. BACKUP or RESTORE terminates. Recovery. Reenter the command without specifying the volume name a second time. 7787 File name has already been specified with a previous ALTFILE parameter. 226 BACKCOPY, BACKUP, and RESTORE Messages...
Page 227 Recovery. Correct the partial date and time, and reenter the command. 7791 Must be a disk file name. Cause. A name other than a disk-file name was used. Effect. BACKUP, BACKCOPY, or RESTORE terminates. Recovery. Reenter the command with a disk-file name. 7792 Too many file sets.
Page 228 Volume is not accessible or does not exist. Cause. An invalid volume name or an inaccessible volume was specified for the VOL option in the RESTORE command. Effect. RESTORE fails and terminates. Recovery. Reissue the command without the offending volume name. 228 BACKCOPY, BACKUP, and RESTORE Messages...
Page 229 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.
Page 230 Cause. START can be specified either as a qualifier or as a separate option in a BACKUP or RESTORE command, but not both. Effect. BACKUP or RESTORE fails and terminates. Recovery. Specify the START option only once and reissue the command. 230 BACKCOPY, BACKUP, and RESTORE Messages...
Page 231 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.
Page 232 The NOUNLOAD and NOREWIND options were both specified for BACKUP. The NOUNLOAD and NOREWIND options were both specified for RESTORE. The NOUNLOADIN and NOREWINDIN options were both specified for BACKCOPY. The NOUNLOADOUT and NOREWINDOUT options were both specified for BACKCOPY.
Page 233 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.
Page 234 Cause. A node was specified with a DEFINE that either does not exist or is unavailable. Effect. BACKUP or RESTORE terminates. Recovery. Specify a node that exists and is available. 234 BACKCOPY, BACKUP, and RESTORE Messages...
Page 235 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.
Page 236 DEFINE attribute DENSITY. Effect. BACKUP terminates. Recovery. Either specify the same density value for the BACKUP DENSITY parameter and the tape DEFINE attribute DENSITY, or omit one of these specifications. 236 BACKCOPY, BACKUP, and RESTORE Messages...
Page 237 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.
Page 238 8029 Tape record is out of sequence. (Expected sequence number:expected-seq-num, actual sequence number: actual-seq- num). Cause. This error could be caused by: Corruption of the tape media Dirty tape drive heads 238 BACKCOPY, BACKUP, and RESTORE Messages...
Page 239 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. If you suspect that the error is due to a software problem, contact your service provider and provide all relevant information: The information in this message...
Page 240 This error should not appear on systems using T9074 with the AEF SPR or newer versions of BACKUP and RESTORE. Instead, you should get a more specific error between 8035 and 8040. Effect. BACKUP or RESTORE terminates. 240 BACKCOPY, BACKUP, and RESTORE Messages...
Page 241 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. If you suspect that the error is due to a software problem, contact your service provider and provide all relevant information: The information in this message Description of the problem and accompanying symptoms (including the fileset specified in...
Page 242 Cause. This error is most likely a software problem in BACKUP or RESTORE but could also 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 242 BACKCOPY, BACKUP, and RESTORE Messages...
Page 243 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. If you suspect that the error is due to a software problem, contact your service provider and provide all relevant information: The information in this message...
Page 244 If your local operation procedures require contacting the GCSC, supply your system number and the numbers and versions of all related products as well. 8050 Tape format is bad (Unexpected tape record type found. Expected record type: expected-rec-type,actual record type: actual-rec-type). 244 BACKCOPY, BACKUP, and RESTORE Messages...
Page 245 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.
Page 246 8054 Tape format is bad (Actual length of the variable length file did not match the expected value). Cause. This error could be caused by: Corruption of the tape media Dirty tape drive heads 246 BACKCOPY, BACKUP, and RESTORE Messages...
Page 247 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. If you suspect that the error is due to a software problem, contact your service provider and provide all relevant information: The information in this message...
Page 248 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. 248 BACKCOPY, BACKUP, and RESTORE Messages...
Page 249 Recovery. Investigate whether a corrupt tape or the tape drive is causing the problem. If you suspect that the error is due to a software problem, 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...
Page 250 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. 250 BACKCOPY, BACKUP, and RESTORE Messages...
Page 251 Recovery. Investigate whether a corrupt tape or the tape drive is causing the problem. If you suspect that the error is due to a software problem, 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...
Page 252 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. 252 BACKCOPY, BACKUP, and RESTORE Messages...
Page 253 Recovery. Investigate whether a corrupt tape or the tape drive is causing the problem. If you suspect that the error is due to a software problem, 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...
Page 254 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. 254 BACKCOPY, BACKUP, and RESTORE Messages...
Page 255 Recovery. Investigate whether a corrupt tape or the tape drive is causing the problem. If you suspect that the error is due to a software problem, 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...
Page 256 Cause. A back space operation detected that the tape was not positioned at the load point. Effect. BACKUP or RESTORE rewinds and unloads the tape and prompts for a tape. Recovery. Reload the tape. If the problem persists, have the tape drive serviced. 8106 Unable to recognize the tape. 256 BACKCOPY, BACKUP, and RESTORE Messages...
Page 257 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.
Page 258 Effect. RESTORE rewinds and unloads the tape and prompts for the correct tape. Recovery. Check the tape and remount it. If the problem persists, see the cause and recovery for error 8025 (page 237). 81 19 File-system error n occurred on the first I/O operation attempted. 258 BACKCOPY, BACKUP, and RESTORE Messages...
Page 259 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.
Page 260 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...
Page 261 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.
Page 262 File-system error noccurred on operation operation. Cause. A file-system error occurred on the tape drive. Effect. BACKUP or RESTORE terminates. Recovery. For corrective action for the error number indicated by n, see the Guardian Procedure Errors and Messages Manual. 262 BACKCOPY, BACKUP, and RESTORE Messages...
Page 263 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.
Page 264: B Dcom/Dsap Messages
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.
Page 265 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.
Page 266 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.
Page 267 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.
Page 268 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.
Page 269 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.
Page 270 Effect. DSAP or DCOM stops. Recovery. Reenter the command correctly. filename WRITE ERROR: 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.
Page 271: C Pak/Unpak Messages
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.
Page 272 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.
Page 273 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.
Page 274 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.
Page 275 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.
Page 276 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.
Page 277 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.
Page 278 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.
Page 279 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.
Page 280 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.
Page 281: D Syntax Summaries
[ , PAGELENGTH number ] [ , PART ( sec-part-num , [ \node.][$volume] [ , pri-extent-size, [ sec-extent-size ] ] ) [ , PARTIAL partial-dump-date ] [ , PARTONLY [ ON | OFF ] ] [ , REMOTEIOSIZE ] BACKCOPY Syntax 281...
Page 282: Qualified File-Set Lists
[ , SCRATCHVOL $volume ] [ , SHAREOPEN ] [ , SQLCATALOGS [ ON | OFF ] ] [ , START [ $volume.] [ subvolume.] file-id ] [ , TAPEMODE [ STARTSTOP | STREAM ] ] [ , VERIFYREEL ] [ , VERIFYTAPE ] [ , VOL [ $new-vol.] new-subvol ] backup-files is:...
Page 283 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.
Page 284: Backup Volume-Mode Syntax
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, ... ) } , VOLUMEMODE, { $volume | $ldev } [ -P | -M ] [ , BLOCKSIZE data-record-size ] [ , { DENSITY density | TAPEMODE tapemode } ]...
Page 285: Pak/Unpak Syntax
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 } TEMPORARY UNEXPIRED UNUSED number...
Page 286 [ , 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 ...) [ , DETAIL ] [ , DSLACK percentage ]...
Page 287: Restore Volume-Mode Syntax
RESTORE Volume-Mode Syntax RESTORE [ / run-option [, run-option ]... / ] { tape-device-name { ( tape-device-name1, tape-device-name2, ... ) } , VOLUMEMODE, { $volume | * } [ , volume-mode-restore-option ] [ , LISTONLY ] [ , MULTIDRIVE ] [ , NOPROMPT ] [ , { NOREWIND | NOUNLOAD } ] [ , RENAME $volume ]...
Page 288: E Class Tape Defines
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.
Page 289 Valid values are BACKUP or OMITTED for Backup and Restore 2.0. LOGICAL { 1 | 2 } identifies which copy of a volume set created from a parallel BACKUP or BACKCOPY run contains a tape file from which you want to read data. When such tape volume sets are created, one set is cataloged as logical copy 1 and the other set as logical copy 2.
Page 290 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.
Page 291: Tape Define Consistency Checks
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.
Page 292 Table 20 TAPE DEFINE Consistency Rules (continued) Check Number Description 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. If you specify VOLUME SCRATCH, then USE IN or USE EXTEND is not allowed.
Page 293: 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.
Page 294: Ansi Hdr2/Eof2/Eov2 Label Format
Character Position in the Field Name Length (in Bytes) Content Label Record 55 - 60 Block Count Number of blocks written in this file section 61 - 73 Implementation Identifier Spaces 74 - 80 Reserved for Future Spaces Standardization ANSI HDR2/EOF2/EOV2 Label Format Character Position in the Field Name Length (in Bytes)
Page 295: Ibm Hdr1/Eof1/Eov1 Label Format
IBM HDR1/EOF1/EOV1 Label Format Character Position in the Field Name Length (in Bytes) Content Label Record 1 - 3 Label Identifier "HDR" or "EOF" or "EOV" Label Number "1" 5 - 21 Data Set Identifier Tape-file name 22 - 27 Data Set Serial Number File-set name to which this volume belongs 28 - 31...
Page 296 Character Position in the Field Name Length (in Bytes) Content Label Record Space: Records are not blocked 40 - 42 Reserved for Future Spaces Standardization 43 - 46 Serial Number (5180 Tape "NNNN": Unit's serial number in Drive only) hexadecimal Spaces: device other than 5180 Device Address (5180 Tape "0": 5180 device...
Page 297: Index
TMFCOM, 50, RESTORE, volume mode, ANALYSIS option (DSAP), guidelines for using ANSI labeled tape, label format, 293, default options, ARCHIVEFORMAT option, BACKCOPY, exiting, Attributes file conversion, 76, CLASS TAPE DEFINE, 288, labeled tape, 77, CLASS TAPECATALOG DEFINE see the DMS/TC...
Page 298 Commands, entering, Density, setting Compatibility with BACKCOPY, of DCOM and the NonStop operating system, 83, with BACKUP, of DSAP and the NonStop operating system, DETAIL option Completion codes DSAP, DCOM, RESTORE, DSAP, 98, Detail report (DSAP) RESTORE, 157, attributes, 93, 97, 106,...
Page 299 ALTFILE option see BACKUP see RESTORE Exceptional condition report (DSAP), PART option see BACKUP see RESTORE EXCLUDE qualifier, VOL option see BACKUP see RESTORE Exiting restoring BACKCOPY, audited, 127, 129, 144, BACKUP, key-sequenced, with slack value, DCOM, open, DSAP, partitioned, 140, 144, 146, 147, 149,...
Page 300 BACKUP, guidelines, RESTORE, volume labels, NOPURGEUNTILoption (RESTORE), label formats, NOREWIND option, BACKUP, 59, restoring NOREWINDIN option, BACKCOPY, DEFINE attributes supported, 175, 176, NOREWINDOUT option, BACKCOPY, examples, NOSAFEGUARD option labeled tapes, 175, BACKUP, LABELS attribute, 78, 176, RESTORE, BYPASS option,...
Page 301 command entry BACKUP, syntax, RESTORE, introduction, RENAME option (RESTORE), PART option Renaming BACKUP, 62, Enscribe files RESTORE, 144, with ALTFILE, 47, Partial backup with MAP NAMES, 138, 140, 171, attributes, 43, with PART, 62, 144, NOSAFEGUARD option, with VOL, 70, NOT option, restored disk volumes, 151, PARTIAL option, 63, 64,...
Page 302 BACKUP, 62, 63, BACKUP at a specific file, 68, during RESTORE, 144, RESTORE at a specific file, Sectors, defective, 84, STARTSTOP mode, Security Stopping of backed-up files BACKCOPY, NOMYID option, BACKUP, NOSAFEGUARD option, DCOM, of compressed files, DSAP, of program files RESTORE,...
Page 303 2, options, TAPEDATE option, RESTORE, VOLUMEMODE option TAPEMODE attribute, BACKUP, 42, TAPEMODE option RESTORE, BACKCOPY, BACKUP, TARGET option (RESTORE), WHERE qualifier, 44, 46, Temporary files, 52, 66, 67, 97, WHOLEDISC option (BACKUP), TEMPORARY option (DSAP), Wild-card characters Timestamp, controlling (RESTORE),...

This manual is also suitable for:

Pak Unpak Restore Dcom Dsap Backup ... Show all

HP BACKCOPY Reference Manual

Table of Contents

Table of Contents

Tables

2 Backcopy

4 Disk Compression (DCOM)

5 Disk Space Analysis Program (DSAP)

B DCOM/DSAP Messages

C PAK/UNPAK Messages

D Syntax Summaries

E CLASS TAPE Defines

F Tape Label Formats

Index

Figures

Quick Links

Chapters

Related Manuals for HP BACKCOPY

Summary of Contents for HP BACKCOPY