Backup and Restore 2 Manual

ManualsBrandsHP ManualsServerHP NonStop G-Series

Backup and Restore 2

Manual

Abstract

This manual describes the components of the Backup and Restore 2 software product

and the BRCOM commands. You can use Backup and Restore 2 to back up HP

NonStop™ Open System Services (OSS) and SQL/MX objects to tape for archiving or

recovery, list the contents of a tape without restoring data, restore objects from

magnetic tape to disk, or move objects from one system to another.

Product Version

For T2721, T2722, T2749, T2750, and T2826 – G06 and H02

For T0744 – H02

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.23 and all subsequent G-series RVUs, until

otherwise indicated by its replacement publications. Additionally, all considerations for

H-series throughout this manual will hold true for J-series also, unless mentioned

otherwise.

Part Number Published

522696-019 February 2013

Summary of content (246 pages)

PAGE 1
Backup and Restore 2 Manual Abstract This manual describes the components of the Backup and Restore 2 software product and the BRCOM commands. You can use Backup and Restore 2 to back up HP NonStop™ Open System Services (OSS) and SQL/MX objects to tape for archiving or recovery, list the contents of a tape without restoring data, restore objects from magnetic tape to disk, or move objects from one system to another.
PAGE 2
Document History Part Number Product Version Published 522696-013 H02 August 2009 522696-014 H02 August 2010 522696-015 H02 February 2011 522696-016 H02 August 2011 522696-017 H02 October 2011 522696-018 H02 August 2012 522696-019 H02 February 2013
PAGE 3
Legal Notices  Copyright 2013 Hewlett-Packard Development Company L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
PAGE 4
PAGE 5
Backup and Restore 2 Manual Index Examples Figures Tables Legal Notices What’s New in This Manual ix Manual Information ix New and Changed Information ix About This Manual xiii Audience xiii Organization of This Manual xiii Notation Conventions xiv HP Encourages Your Comments xvii 1.
PAGE 6
2. Installing Backup and Restore 2 Contents 2. Installing Backup and Restore 2 Hardware Required 2-1 Software Required 2-1 Required SPRs—G-Series RVUs 2-1 Required SPRs—H-Series RVUs 2-4 Installing Software 2-5 Installing Backup and Restore 2 to Support SQL/MX Installing the Heap Manager 2-5 Post-Installation Tasks 2-6 2-5 3.
PAGE 7
5. BRCOM Commands Contents Handling Operations That Use the BRCOM Terminal Using the Break Key 4-6 Using DEFINEs With Backup and Restore 2 4-6 Creating and Using a Command File 4-6 Using an IN File 4-7 Using the BRCMD File 4-8 Reusing a JOB ID After a BRCOM Error 4-8 4-5 5.
PAGE 8
6. BRCOM BACKUP Command Contents Guideline 5-14 Examples 5-14 INFO CONFIG Command 5-15 Guideline 5-15 Example 5-15 INFO JOB Command 5-15 Example 5-16 OBEY Command 5-16 Guidelines 5-16 Example 5-16 PAUSE Command 5-17 Guideline 5-17 Example 5-17 RESTART Command 5-17 Guidelines 5-19 Example 5-19 RESTORE Command 5-19 STATUS JOB Command 5-20 Guideline 5-20 Examples 5-21 STOP JOB Command 5-21 Guidelines 5-21 Example 5-22 6.
PAGE 9
7. BRCOM RESTORE Command Contents INDEXES Job Option 6-27 JOB Job Option 6-27 LISTALL Job Option 6-28 NEEDBOTH Job Option 6-28 OPEN Job Option 6-29 OSSACL Job Option 6-30 OUT Job Option 6-31 PAGELENGTH Job Option 6-31 PARTONLY Job Option 6-32 SQLDATA Job Option 6-33 TAPEDISPOSITION Job Option 6-34 VERIFYTAPE Job Option 6-34 Examples 6-34 OSS Backup Examples 6-35 SQL/MX Backup Examples 6-44 Backing Up Both OSS and SQL/MX Objects 6-52 7.
PAGE 10
8.
PAGE 11
Index Contents Index Examples Example 3-1. Example 3-2. Example 7-1. Example 7-2. Example 7-3. Example 7-4. Example 8-1. Example 8-2. Example 8-3. Example 8-4.
PAGE 12
Contents Table 7-6. Table 7-7. Table 7-8. Table 7-9. Table 7-10. Table 7-11. Table 7-12. Table 7-13. Table 7-14. Table 7-15. Table 7-16. Table 7-17. Table 8-1. Table B-1. Table B-2.
PAGE 13
What’s New in This Manual Manual Information Backup and Restore 2 Manual Abstract This manual describes the components of the Backup and Restore 2 software product and the BRCOM commands. You can use Backup and Restore 2 to back up HP NonStop™ Open System Services (OSS) and SQL/MX objects to tape for archiving or recovery, list the contents of a tape without restoring data, restore objects from magnetic tape to disk, or move objects from one system to another.
PAGE 14
What’s New in This Manual   Changes to the H06.25/J06.14 (522696-018) manual Updated Summary of Backing Up OSS or SQL/MX Files on page 6-1. Updated Summary of Restoring SQL/MX or OSS Objects on page 7-1. Changes to the H06.25/J06.14 (522696-018) manual      Renamed the section “Unsupported SQL/MX Objects” to Restore of Views, Stored Procedures, Triggers, and Referential Integrity Constraints on page 1-13. Added a new section Automatically Creating SQL/MX Objects During Restore on page 1-13.
PAGE 15
Changes to the H06.21/J06.10 Manual What’s New in This Manual      Added Setting the File Privilege on Backup and Restore 2 Executables Required in the Restricted-Access Fileset on page 3-6. Added Backing Up the Restricted-Access Fileset on page 6-5. Added Backing Up the Unrestricted Fileset on page 6-5. Added Restoring to the Restricted-Access Fileset on page 7-7. Added Restoring to the Unrestricted Fileset on page 7-8. Changes to the H06.21/J06.
PAGE 16
Changes to the H06.15/J06.04 Manual What’s New in This Manual            Added the following SQL/MX Backup examples:   Backing Up SQL/MX Indexes Separately on page 6-54 Backing Up SQL/MX Index Partitions on page 6-54 Updated Restoring SQL/MX Objects on page 7-7. Updated Table 7-1, Restoring to a Different Target, on page 7-20. Updated applicability note of the BRCOM RESTORE command on page 7-27. Updated KEEPGFN Job Option on page 7-41.
PAGE 17
About This Manual This manual provides an overview and describes the installation, and configuration of Backup and Restore 2. It describes the various Backup and Restore Command Interface (BRCOM) commands, and error messages. It explains the usage of the BRCOM command interface in addition to monitoring the Backup and Restore 2 jobs.
PAGE 18
Notation Conventions About This Manual Notation Conventions Hypertext Links Blue underline is used to indicate a hypertext link within text. By clicking a passage of text with a blue underline, you are taken to the location described. For example: This requirement is described under Backup DAM Volumes and Physical Disk Drives on page 2 General Syntax Notation This list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS.
PAGE 19
General Syntax Notation About This Manual { } Braces. A group of items enclosed in braces is a list from which you are required to choose one item. The items in the list can be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: LISTOPENS PROCESS { $appl-mgr-name } { $process-name } ALLOWSU { ON | OFF } | Vertical Line.
PAGE 20
Notation for Messages About This Manual Line Spacing. If the syntax of a command is too long to fit on a single line, each continuation line is indented three spaces and is separated from the preceding line by a blank line. This spacing distinguishes items in a continuation line from items in a vertical list of selections.
PAGE 21
Change Bar Notation About This Manual either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: obj-type obj-name state changed to state, caused by { Object | Operator | Service } process-name State changed from old-objstate to objstate { Operator Request. } { Unknown. } | Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces.
PAGE 22
HP Encourages Your Comments About This Manual Backup and Restore 2 Manual—522696-019 xviii
PAGE 23
1 Backup and Restore 2 Overview This section describes the major Backup and Restore 2 components and files. Backup and Restore 2 Components Backup and Restore 2 lets you back up and restore OSS and SQL/MX files.
PAGE 24
Data Management Application (DMA) Backup and Restore 2 Overview        Interfaces to the disk subsystem Communicates with the DMA for backup jobs Communicates information to the DMA about the files backed up or restored Receives data from the Tape Service for restore jobs Passes file image date to the Tape Service during backup Enumerates objects during backup Issues error messages The Data Service object files BR2ODS, which supports only the OSS file system and BR2Ds, which supports both OSS and
PAGE 25
Backup and Restore 2 Files Backup and Restore 2 Overview  Verifies tapes The Tape Service object file is located in $SYSTEM.SYSnn .BR2TS. Backup and Restore 2 Files     Backup and Restore Configuration (BRCONFIG) File Backup and Restore Command (BRCMD) File Backup and Restore Jobs (BRJOBS) File Backup and Restore Intermediate Catalog (BRIC) File on page 1-4 Backup and Restore Jobs (BRJOBS) File BRJOBS is an Enscribe key-sequenced file that stores information about each backup or restore job.
PAGE 26
Backup and Restore Intermediate Catalog (BRIC) File Backup and Restore 2 Overview Backup and Restore Intermediate Catalog (BRIC) File The BRIC file contains information for a single backup job. It contains disk file catalog information, including the list of files backed up on tape and their location. The BRIC is a temporary disk file and a permanent tape file until the tape file expires. The DMA normally purges the BRIC disk file at the end of the backup job.
PAGE 27
Open System Services (OSS) Backup and Restore 2 Overview OSS files less than and greater than 2 GB that you need to restore to a fileset that does not support files greater than 2 GB, Backup and Restore 2 restores the files less than 2 GB but skips the files greater than 2 GB.
PAGE 28
Open System Services (OSS) Backup and Restore 2 Overview A hard-linked file has multiple file names associated with a single inode number. The inode number is the internal storage pointer to the disk file. Ordinary files and named pipes can be hard-linked files. To back up or restore hard-linked files, you must back up and restore the complete set of files. Named Pipes A named pipe is an OSS file used for unidirectional, FIFO, interprocess communication.
PAGE 29
SQL/MX Backup and Restore 2 Overview Unsupported OSS Objects You cannot back up or restore device special files (character special files and block special files) and socket files. These objects are skipped if you attempt to back them up, either implicitly (by specifying a directory that contains the file) or explicitly (by specifying the file). SQL/MX NonStop SQL/MX is the NonStop relational database management system based on ANSI SQL-92.
PAGE 30
SQL/MX Backup and Restore 2 Overview Supported SQL/MX Objects BRCOM supports the SQL/MX objects listed in Figure 1-1. You can directly specify catalog, schema, table, and table partition objects in BACKUP or RESTORE commands. You cannot specify constraints explicitly. Figure 1-1.
PAGE 31
SQL/MX Backup and Restore 2 Overview For each of the objects that you specify directly, all its subordinate objects are automatically backed up or restored unless you exclude them using the job options or a WHERE expression. For example, constraints, indexes, and index partitions are included by default. However, you can use the CONSTRAINTS EXCLUDED or INDEXES EXCLUDED job options to exclude them.
PAGE 32
SQL/MX Backup and Restore 2 Overview The schema’s creator owns the schema object and all its subordinate objects:  Sequence Generator Note. Starting with SQL/MX Release 3.2.1, sequence generators are supported.      Tables Table partitions Indexes Index partitions SG_TABLEs associated with those base table that contains an IDENTITY column. Note. IDENTITY column feature is supported only in SQL/MX 3.1 versions and above.
PAGE 33
SQL/MX Backup and Restore 2 Overview     Droppable constraints unless you specify the CONSTRAINTS EXCLUDED job option All table data unless you specify the SQLDATA OFF job option Indexes and index partitions unless you specify the INDEXES EXCLUDED job option SG_TABLE, if the table contains an IDENTITY column. Note. IDENTITY column feature is supported only in SQL/MX 3.1 versions and later.
PAGE 34
SQL/MX Backup and Restore 2 Overview Table Partitions A table partition is a subordinate object of the table object. A table partition is a physical object:   Backing up an individual table partition includes the partition data only when you specify the PARTONLY job option. Restoring an individual table partition includes the partition data and is only permitted when you specify the PARTONLY ON job option. Indexes An index is a subordinate object of the table object. It is a logical object.
PAGE 35
Relationship between Backup Restore and Backup Restore 2 Backup and Restore 2 Overview Restore of Views, Stored Procedures, Triggers, and Referential Integrity Constraints With SQL/MX release 3.2, HP introduces the OBEYDDL option to restore the objects in Table 1-1. For more information, see the OBEYDDL Job Option on page 7-51.
PAGE 36
Difference between BR and BR2 Backup and Restore 2 Overview as a common interface for Backup Restore 2 (BR2) and Backup Restore (BR) commands. However, the syntax of Backup and Restore commands for Backup Restore (T9074) and Backup Restore 2 (T0744) must be entered in the BRCOM prompt exactly as updated in the respective Backup Restore Utility Manuals. BRCOM supports only basic Backup and Restore commands of Backup Restore (T9074) and does not support any run options and features.
PAGE 37
Related Products Backup and Restore 2 Overview         BLOCKLEN DENSITY LOGICAL PHYSICAL RECFORM RECLEN EBCDIC TAPEMODE The RECLEN, record length used internally is always user-specified or default value of the BLOCKSIZE job option. EBCDIC is not supported by BR2. TAPEMODE is valid but ignored by BR2. The value of TAPEMODE used internally is always STREAM.
PAGE 38
HP NonStop Transaction Management Facility (TMF) Backup and Restore 2 Overview For Backup and Restore 2:   If you use CLASS TAPECATALOG DEFINEs with CATALOG ON, the DSM/TC catalog manager (MEDIADBM) keeps track of the tapes used as part of a back up job. During a restore job, the correct set of tapes can be retrieved from DSM/TC. However, DSM/TC does not maintain information about the objects and files backed up on each tape.
PAGE 39
2 Installing Backup and Restore 2 This section lists the hardware and software required to use Backup and Restore 2. Hardware Required Backup and Restore 2 supports all HP NonStop S-series servers and all tape drives supported for NonStop S-series servers except the 517x open-reel tape drives. Backup and Restore 2 works with tape devices that support logical block addresses (LBAs).
PAGE 40
Required SPRs—G-Series RVUs Installing Backup and Restore 2 Backup and Restore 2 AAB SPRs The G06.24 RVU includes these AAB SPRs that are the minimum SPRs required to back up or restore OSS objects:      T2721AAB (BR 2 BRCOM) T2722AAB (BR 2 Tape Services) T2749AAB (BR 2 DMA & Cmd Stream Proc) T2750AAB (BR 2 Data Services) T2826AAB (BR 2 OSS Agent) The AAB SPRs do not support SQL/MX. For more information about the SPRs, see the softdocs.
PAGE 41
Required SPRs—G-Series RVUs Installing Backup and Restore 2   T2749AAF (BR 2 DMA & Cmd Stream Proc) T2750AAF (BR 2 Data Services) The AAF SPRs include these fixes:           During the restore of a backup job operation produced by a parallel backup job, the backup and restore job operation requests the alternate tape if the first tape is not available or the mount request for it is rejected by the user. Backup and Restore 2 creates an alternate target for the restore job.
PAGE 42
Required SPRs—H-Series RVUs Installing Backup and Restore 2 The AAG SPRs include these fixes:    Backup or restore operation for OSS succeeds even if SQL/MX is not installed on the system. The two new object files, BR2ODMA and BR2ODS, included in these SPRs are launched only to backup or restore OSS objects if SQL/MX software is not installed on the system. FFDC no longer triggers when a local invalid BRCONFIG file is used.
PAGE 43
Installing Software Installing Backup and Restore 2 Installing Software Installing Backup and Restore 2 to Support Open System Services (OSS) To back up or restore OSS objects: 1. Install OSS 2. For the G06.23 RVU, install:   The tape process T0021ABH or a superseding SPR The Backup and Restore 2 AAB SPRs on page 2-2 or superseding SPRs For additional defect repair, you can install the Backup and Restore 2 AAC SPRs on page 2-2 or superseding SPRs. 3. For the G06.24 RVU, the AAB SPRs are included.
PAGE 44
Post-Installation Tasks Installing Backup and Restore 2 Post-Installation Tasks 1. If you plan to back up or restore to labeled tapes, check that labeled tape processing is enabled on the system and that the $ZSVR labeled tape server (T6958) is installed, up, and running. 2. Before you use a TAPECATALOG DEFINE for backup or restore jobs on labeled tape, you must upgrade the DSM/TC database using the ALTER MEDIADB command and longname attribute.
PAGE 45
3 Configuring Backup and Restore 2 This section describes managing Backup and Restore 2. Managing Configuration Information BRCONFIG contains the configuration information for the DMA, the Data Service, and the Tape Service. BRCOM uses the BRJOBS volume configured in the BRCONFIG file for all jobs. You can override any of the other values when you specify a BACKUP or RESTORE command.
PAGE 46
Displaying Configuration Information for a Job Configuring Backup and Restore 2 Example 3-1. INFO CONFIG Command Display BRJOBS Volume $data00 EMS Collector $0 Service CPU List Unspecified Service Priority -1 Work Volume $data00 Field Description BRJOBS Volume The disk volume on which the BRJOBS file is on. Collector The collector for EMS messages. Service CPU List The list of the processors in which the DMA starts the Data Service and Tape Service.
PAGE 47
Changing the Volumes for All Jobs Configuring Backup and Restore 2 Field Description JOB The job identifier DMA Program File The executable program for the DMA Data Service Program File The executable program for the Data Service Service CPU List The list of the processors in which the DMA starts the Data Service and Tape Service. If the value is unspecified, the Data Service and Tape Service are started in the DMA’s processor.
PAGE 48
Configuring Backup and Restore 2 Changing the Work Volume 6. Change the BRJOBS volume. For example: BR> ALTER CONFIG, BRJOBSVOLUME BR+> $brjobsvolume.ZBR2.BRJOBS ; 7. Delete the original BRJOBS volume. For example: > PURGE $SYSTEM.ZBR2.BRJOBS Changing the Work Volume To distribute activity over multiple disk volumes, you can specify different work volumes for different backup or restore jobs. To create a new work volume for a job, use the WORKVOLUME configuration option when starting the job.
PAGE 49
Example: Overriding the Configured Values for SERVICECPULIST and SERVICEPRI Configuring Backup and Restore 2 Example: Overriding the Configured Values for SERVICECPULIST and SERVICEPRI For this example, the configured values in the BRCONFIG file are: BRJOBS Volume $SYSTEM EMS Collector $0 Service CPU List Unspecified Service Priority -1 Work Volume $SYSTEM To override the configured values for SERVICECPULIST and SERVICEPRI: BR> BACKUP $A8, OSS / , SERVICECPULIST 2,3, SERVICE PRI 120 ; The backup
PAGE 50
Setting the File Privilege on Backup and Restore 2 Executables Required in the Restricted-Access Configuring Backup and Restore 2 To verify that the license of the files is set, change the volume to the sysnn location, and then use the FILEINFO command. For example: TACL> volume TACL> fileinfo BR2* The following output appears: BR2DS BR2ODS 800L 800L 51671328 27OCT2010 8502184 27OCT2010 6:58 255,255 NUNU 6:59 255,255 NUNU 504 504 504 504 where,   File code 800 is the attribute name.
PAGE 51
4 Using the BRCOM Command Interface This section describes the BRCOM command interface. Security BRCOM uses the NonStop security, based on the logon user ID. The data management application (DMA) process and other Backup and Restore 2 components adopt the user ID that you used to log on. BRCOM runs in a Guardian environment. You can use Safeguard user ID aliases. You cannot log on using the scalar view of the user ID. Before Starting BRCOM Before you start BRCOM: 1. Log on to a NonStop S-series server 2.
PAGE 52
Using the BRCOM Command Interface               Stopping BRCOM BACKCOPY (H-series only) BACKUP DELETE EXIT FC HELP HISTORY INFO OBEY PAUSE RESTART (H-series only) RESTORE STATUS STOP For more information on BRCOM commands, see Section 5, BRCOM Commands Stopping BRCOM BRCOM exits automatically after executing the commands specified on the command line. If BRCOM enters interactive mode, use the EXIT command to stop BRCOM.
PAGE 53
Using the BRCOM Command Interface Including Multiple Commands on the Same Line Including Multiple Commands on the Same Line If you terminate each command with a semicolon, you can include multiple commands on the same line. For example: BR> INFO JOB jobid; STATUS JOB jobid; However, you cannot include !, ?, or FC commands on the same line with other commands. For example: BR> FC; STATUS JOB jobid; The !, ?, and FC commands and any subsequent commands on that line result in syntax errors.
PAGE 54
Octal ASCII Character Code Using the BRCOM Command Interface In this example, the lines are split and indented for readability in an IN file or command file: BR> BACKUP $TAPE, OSS BR+> "/longDirName/longerDirName/EvenLongerDirName/Longest" BR+> "DirName/filename"; Octal ASCII Character Code You can specify any character as an octal ASCII character code such as \0nnn. nnn is a three-digit octal number from 000 through 377. For example, you could specify the tab character, octal 11, as \011.
PAGE 55
Using the BRCOM Command Interface Managing Jobs Specifying a Space Character A backslash followed by a space is interpreted as a space character. Space is the octal character code 40.
PAGE 56
Using the Break Key Using the BRCOM Command Interface Using the Break Key From the BRCOM prompt, the Break key returns you to the HP Tandem Advanced Command Language (TACL) prompt. To interrupt an operation that is using the BRCOM terminal: 1. Press the Break key to return to the BRCOM prompt. 2. Enter BRCOM commands to start any operation that does not require use of the terminal. 3. To return control of the terminal to the original operation, use the PAUSE command.
PAGE 57
Using the BRCOM Command Interface Using an IN File BRCOM generally continues processing the command file even if an error occurs while processing the commands. However, when BRCOM processes concatenated commands, subsequent commands are ignored if an error occurs. Using an IN File You can use an IN file to start BRCOM or for a BACKUP or RESTORE command.
PAGE 58
Using the BRCOM Command Interface  Using the BRCMD File Configuration options, if being used, must be in the IN file. Using an IN File for a Standard (T9074) BACKUP or RESTORE Command You can use an IN file from the BRCOM prompt to start a standard (T9074) BACKUP or RESTORE job. For example: BR> backup/in grdnin/; where, grdnin is the IN file. The following is the sample of the IN file called grdnin: $tape, $system.system.
PAGE 59
5 BRCOM Commands This section describes the BRCOM commands. Command Use the ! command to execute a command you entered previously during the current session. You can request the command by line number, relative line number, or text string. Terminating this command with a semicolon is optional. ! [ [ [ [ linenum ] -linenum ] string ] "string" ] [;] ! entered with no line number or text string, displays and executes the last command line in the command history buffer.
PAGE 60
Examples BRCOM Commands Examples BR> ! ; BR> ! 2 BR> ! INFO BR> ! "CONFIG" ; ? Command Use the ? command to retrieve a command you entered previously during the current session. You can request the command by line number, relative line number, or text string. Terminating this command with a semicolon is optional. ? [ [ [ [ linenum ] -linenum ] string ] "string" ] [;] ? entered with no line number or text string, displays the last command line in the command history buffer.
PAGE 61
Guideline BRCOM Commands Guideline Do not use the ? command in a command file or IN file. Examples BR> ? ; BR> ? 2 BR> ? INFO BR> ? "CONFIG" ; ABORT JOB Command The ABORT JOB command terminates the backup, restore, parallel backup or restart job as quickly as possible. The BRCMD file and BRIC file are not deleted. However, the DMA updates the STATUS record in the BRJOBS file and changes the job state to ABORTED. ABORT JOB jobid ; jobid is a valid unique job identifier with a maximum of eight characters.
PAGE 62
ALTER CONFIG Command (Super Group Only) BRCOM Commands ALTER CONFIG Command (Super Group Only) The ALTER CONFIG command sets the configuration options in the BRCONFIG file for all backup and restore jobs. ALTER CONFIG , config-option [ , config-option ][ , config-option ... ] ] ; config-option is one or more of: BRJOBSVOLUME valid disk name EMSCOLLECTOR[\node.]$process-name SERVICECPULIST [ processor [, processor] ...
PAGE 63
Guidelines BRCOM Commands Guidelines     You must be a super-group user to use the ALTER CONFIG. You can override these configuration options, except BRJOBSVOLUME, when you specify a BACKUP or RESTORE command. Be careful while altering the SERVICEPRI number parameter. Setting the value of the SERVICEPRI number parameter higher than DMA priority may result in unpredictable behavior. For more information about setting the configuration options, see Managing Configuration Information on page 3-1.
PAGE 64
BACKCOPY Command BRCOM Commands dest-tape is the tape device on which the backup image is copied from the source tape. You can specify the name of a tapedrive, the logical device number of a tape drive, or a define name. run-option specifies how BRCOM starts DMA. The options are the same as those of the BACKUP command. For more information, see Table 6-2 on page 6-10 and Table 7-3 on page 7-23 backup-object-spec specifies the object to be backed up.
PAGE 65
Guidelines BRCOM Commands Guidelines    The tape set from which the image data is being copied must be created using Backup and Restore or Backup and Restore 2. You can specify a backup job (tape file) or a tape to copy. If a fatal error is received from either the source tape device or the destination tape device, BACKCOPY returns event message 5006 (file-system error) and aborts. The job status output for BACKCOPY is the same as the output for a backup job, except: 1.
PAGE 66
Example BRCOM Commands Objects not found = 0 Objects skipped = 0 Total tapes used = 1 Total Mbytes moved = 0 Example BR> BACKCOPY ($a8,$a9),*,tapedispositionin bot, tapedispositionout bot,listall on ; For the brief job status and the detailed job status, see Example 8-2 on page 8-2 and Example 8-4 on page 8-5, respectively. BACKUP Command Use the BACKUP command to copy OSS and SQL/MX files from disk to magnetic tape.
PAGE 67
Guidelines BRCOM Commands Guidelines     Each job normally deletes its BRCMD file and BRIC file automatically. However, these files might be left on disk if the job is terminated abnormally. The job must be in a correct state for a cleanup process. The proper states for a cleanup operation to be performed are: DONE, STOP, ABRT, ABND. You cannot use the CLEANUP JOB command to delete BRJOBS records. The job must be present in the BRJOBS file.
PAGE 68
DELETE JOB Command BRCOM Commands user-id is a user ID. It is one of these: {group-name.user-name } {group-name.* } {group-number, user-number} {group-number,* } group-name is the group name of the user. Each name can contain from one through eight letters or digits, and the first character must be a letter. user-name is the name of the user. Each name can contain from one through eight letters or digits, and the first character must be a letter.
PAGE 69
Guidelines BRCOM Commands Today’s date is the default. The default time is 00:00:00 (midnight) of today’s date. day is a 2-digit integer in the range 1 through 31 that specifies the day. month is one of these: JAN, FEB, MAR, APR, MAY, JUN, JULY, AUG, SEP, OCT, NOV, DEC year is a 4-digit integer in the range 1900 through 2999. hour is a 2-digit integer in the range 0 through 23. minute is a 2-digit integer in the range 0 through 59. second is a 2-digit integer in the range 0 through 59.
PAGE 70
EXIT Command BRCOM Commands EXIT Command Use the EXIT command to end the BRCOM session and return to the TACL prompt. EXIT Note. A separate EXIT command is not required when BRCOM commands are specified on the command line. Example BR> EXIT ; FC Command Use the FC command to retrieve, edit, and execute a command you have previously entered during the current session. You can request the command by line number, relative line number, or text string.
PAGE 71
Guidelines BRCOM Commands "string" is a text string enclosed in quotation marks. The FC command finds and displays the most recent command in the history buffer that contains the specified text string. The command need not begin with the specified string. Searching for previous commands is case-sensitive. Guidelines   Do not use the FC command in a command file or IN file. FC displays the specified command line and prompts you to make your changes on the next blank line.
PAGE 72
Examples BRCOM Commands is a variable item in the command syntax that you want help with. The < and > characters are required around the variable name. * lists all the BRCOM command names. Syntax is not displayed. Examples BR> HELP INFO CONFIG; BR> HELP INFO ; BR> HELP ; BR> HELP * ; HISTORY Command Use the HISTORY command to display lines from the history buffer. BRCOM maintains a history buffer of the command lines you enter during the current session.
PAGE 73
INFO CONFIG Command BRCOM Commands INFO CONFIG Command Use the INFO CONFIG command to display the configuration information in the BRCONFIG file. INFO CONFIG [ , OUT out-file ] ; CONFIG displays the configuration information in the BRCONFIG file. out-file specifies where the report is displayed or written. You can name a disk file or a device such as a printer or terminal. If not specified, the information is sent to your current default output file (usually your home terminal).
PAGE 74
Example BRCOM Commands For example: A1234567 aaaaaaaa abcdEFG D1 I607 I*07 I* I??? out-file specifies where the report is displayed or written. You can name a disk file or a device such as a printer or terminal. If not specified, the information is sent to your current default output file (usually your home terminal). Example BR> INFO JOB Feb0402, OUT $system.sys00.jobinfo ; OBEY Command Use the OBEY command to execute one or more BRCOM commands in a command file.
PAGE 75
PAUSE Command BRCOM Commands PAUSE Command Use the PAUSE command to stop BRCOM from prompting for commands. PAUSE ; Guideline This command allows another process to take control of the terminal. Press the Break key to return control to BRCOM. For more information, see Handling Operations That Use the BRCOM Terminal on page 4-5 Example BR> PAUSE ; RESTART Command Use the RESTART command to restart a failed backup or restore job.
PAGE 76
RESTART Command BRCOM Commands Table 5-1 describes the use of the LISTALL and OUT job options in manual restart: Table 5-1. LISTALL Job Option and OUT Job Option (page 1 of 2) Parent job LISTALL Restart job LISTALL Parent job OUT Restart job OUT ON ON Specified Not specified List information will be appended to parent job OUT destination. ON ON Specified Specified Restart job OUT file will take precedence and no information will be appended to parent job's list file.
PAGE 77
Guidelines BRCOM Commands Table 5-1. LISTALL Job Option and OUT Job Option (page 2 of 2) Parent job LISTALL Restart job LISTALL Parent job OUT Restart job OUT OFF ON Not Applicable Specified Restart job OUT file will take precedence and no information will be appended to parent job's list file. OFF ON Not Applicable Not Specified List information will be logged to current BRCOM home term.
PAGE 78
STATUS JOB Command BRCOM Commands STATUS JOB Command Use the STATUS JOB command to display current status information about a job ID. STATUS JOB jobid [ , OUT out-file ][ , BRIEF | DETAIL ] jobid is a valid unique job identifier with a maximum of eight characters. The characters can be alphabetic, numeric, wild-card (* or ?), or a combination. The first character cannot be numeric. Job IDs are not case-sensitive. You can use asterisks (*) or question marks (?) as wild-card characters in a job ID.
PAGE 79
Examples BRCOM Commands Examples BR> STATUS JOB Feb0402 ; BR> STATUS JOB Feb0402, OUT $system.sys00.jobinfo ; BR> STATUS JOB Feb0402, OUT $system.sys00.jobinfo, BRIEF ; BR> STATUS JOB Feb0402, OUT $system.sys00.jobinfo, DETAIL ; STOP JOB Command Use the STOP JOB command to stop a job. STOP JOB jobid ; jobid is a valid, unique job identifier with a maximum of eight characters. The characters can be alphabetic, numeric, wild-card (* or ?), or a combination. The first character cannot be numeric.
PAGE 80
Example BRCOM Commands Example BR> STOP JOB Feb0402 ; Backup and Restore 2 Manual—522696-019 5-22
PAGE 81
6 BRCOM BACKUP Command The BACKUP command copies files from disk to magnetic tape. You can use BACKUP to:    Store files on tape for recovery in case they are ever lost or damaged on the disk Free disk space by archiving files that are used infrequently Move files from one system to another Note. The other system must have both Backup and Restore 2 and any other required software installed.
PAGE 82
BRCOM BACKUP Command Summary of Backing Up OSS or SQL/MX Files The summary information after the backup displays the status of the backup, which includes processed, backed up and skipped objects. The count of backed up objects includes an extra file, BRIC.
PAGE 83
Summary of Backing Up OSS or SQL/MX Files BRCOM BACKUP Command BR>backup \HPIDMR5.$Z3XT, MX ( sch sqlcat.sqlsch), listall on, wait on; * WARNING-2030 ** Enscribe and SQL/MP objects will not be backed up. Started job ZBR0013A File Mode BACKUP Program - T0744H02 - (21JAN2013) (C)2000 Compaq (C)2003, 2004 Hewlett Packard Development Company, L.P. backup \HPIDMR5.$Z3XT, MX ( sch sqlcat.sqlsch) , listall on,wait on; Unlabeled Tape.
PAGE 84
Summary of Backing Up OSS or SQL/MX Files BRCOM BACKUP Command SQLCAT.SQLSCH.SQLTAB *SQL 255,255 550 A+ HPIDMR5_SYSTEM_ZSD PJB33_Q452KH00 0 10Jan2013 14:43 ATP *** Meta object BRIC backed up *** Summary Information Job completed. Last error or warning occurred on page 1 Process elapsed time = 0:00:16.
PAGE 85
Summary of Backing Up OSS or SQL/MX Files BRCOM BACKUP Command  SG_TABLE, if the table contains an IDENTITY column. Note. IDENTITY column feature is supported only in SQL/MX 3.1 versions and above.  Backing up an index includes:    All index partitions. Backing up individual index partitions includes the partition data only when you specify the PARTONLY job option. You cannot directly specify a constraint in a BACKUP command.
PAGE 86
BRCOM BACKUP Command Summary of Backing Up OSS or SQL/MX Files When multiple filesets (restricted-access and unrestricted) are present in a hierarchy, and backup is executed at the highest level directory by a super ID, it is recommended that you use the Exclude filter during backup to filter out the restricted-access filesets. For information on the Exclude filter, see Filters for OSS Files on page 6-17.
PAGE 87
BACKUP Command Processing BRCOM BACKUP Command BACKUP Command Processing When you issue a BRCOM BACKUP command: 1. If you specify a job ID, BRCOM checks if that job ID exists in the BRJOBS file or if any files exist in $workvolume.jobid. If the job ID already exists or if there are files in the $workvolume.jobid subvolume, the job aborts with error 2023. 2. If you do not specify a job ID, BRCOM automatically generates a job ID. 3. BRCOM places a copy of the command in the $workvolume.jobid.
PAGE 88
BRCOM BACKUP Command Syntax BRCOM BACKUP Command BRCOM BACKUP Command Syntax The syntax for a BRCOM BACKUP command is: BACKUP tape-device-name ( tape-device-name1, tape-device-name2 ) [, run-option [, run-option ] ... ] , backup-object-spec ( backup-object-spec1 ), ( backup-object-spec2 ) [ , backup-job-option, [backup-job-option]...] [ , config-option, [config-option]...
PAGE 89
BRCOM BACKUP Command Syntax BRCOM BACKUP Command define-name is a DEFINE name of CLASS TAPE or TAPECATALOG for a backup to labeled tape. For more information, see Using DEFINEs With Backup and Restore 2 on page 4-6   If you specify a DEFINE of CLASS TAPECATALOG with CATALOG ON, the tape information is recorded in the DSM/TC volume catalog. When you specify CATALOG OFF, information about the tape is not recorded in the DSM/TC volume catalog.
PAGE 90
BRCOM BACKUP Command Syntax BRCOM BACKUP Command run-option specifies how BRCOM starts the DMA. The run options are supported as described in the TACL Reference Manual, except as listed in Table 6-2. Any run option specified on the command line overrides a corresponding run option in the IN file. Table 6-2. Run Option Exceptions for the BACKUP Command Run Option Meaning CPU This option specifies the number of the processor where the DMA is to run.
PAGE 91
BRCOM BACKUP Command Syntax BRCOM BACKUP Command The backup-object-spec is one of these: {oss-backup-object-spec } {sqlmx-backup-object-spec } {(oss-backup-object-spec) , (sqlmx-backup-object-spec) } {(sqlmx-backup-object-spec), (oss-backup-object-spec) } oss-backup-object-spec For more information, see OSS Backup Object on page 6-13 sqlmx-backup-object-spec For more information, see SQL/MX Backup Object on page 6-14 backup-job-option specifies one or more conditions for the BACKUP command.
PAGE 92
BRCOM BACKUP Syntax When Using an IN File BRCOM BACKUP Command service processes are started in the processor in which the DMA is running. If you specify SERVICECPULIST configuration option but do not specify any processors, the service processes are started in the DMA's processor. SERVICEPRI priority is either no value, a value of -1, or a value from 1 through 199 that specifies the priority at which the DMA starts the Data Service and Tape Service. A value of 0 is not permitted.
PAGE 93
Backup Object BRCOM BACKUP Command run-option is supported as described in the TACL Reference Manual, except as listed in Table 6-2 on page 6-10. Any run option that you specify on the command line overrides a corresponding run option in the IN file. in-file is the name of a IN file. You cannot specify any option after the IN run option. Therefore, you cannot specify job options or configuration options on the command line.
PAGE 94
Backup Object BRCOM BACKUP Command For example: backup $tape1, oss (/usr/b*/c*, /usr/local/b?), tapedisposition bot; Note. Wild carding is supported only on systems running H06.05 or later H-series RVUs. WHERE expression allows further exclusions from oss-source-directory. It specifies qualifying criteria for including objects from the source directory for backup. The order of precedence in expression evaluation is parentheses, NOT, AND, and OR. Parentheses within a WHERE expression are optional.
PAGE 95
Backup Object BRCOM BACKUP Command sqlmx-object is the set of SQL/MX objects to be backed up, which can be regular or delimited. Note. SQL/MX tables, catalogs, and schemas containing delimiters are supported only on systems running J06.03 or later J-series RVUs and H06.06 or later H-series RVUs. SQL/MX indexes containing delimiters are supported only on systems running J06.08 or later J-series RVUs and H06.19 or later H-series RVUs.
PAGE 96
Backup Object BRCOM BACKUP Command IND | INDEX is the object type for an index. sqlmx-source-object is the set of SQL/MX objects to be backed up. It is a valid SQL/MX object such as the name of a catalog, schema, table, or index. The specified object and all subordinate objects are backed up. Wild cards are not permitted in sqlmx-source-object. TPART is the object type for a table partition. Table partitions are physical objects. sqlmx-table is a valid SQL/MX table name.
PAGE 97
Backup Object BRCOM BACKUP Command OWNER = user-id sqlmx-timestamp time-conditional time-value EOF eof-conditional eof-number TABLE For more information, see Filters for SQL/MX Objects on page 6-20 Filters for OSS Files For OSS objects, filters other than the EXCLUDE filter are applied only to files and not to the OSS directories. You can filter the OSS directories using the EXCLUDE filter. OWNER = user-id selects a file based on a NonStop user ID in one of these forms: { { { { group-name.
PAGE 98
Backup Object BRCOM BACKUP Command oss-timestamp is any of: CREATIONTIME LASTOPENTIME MODTIME CREATIONTIME selects a file based on the time that the file was created. LASTOPENTIME selects a file based on the time that the file was last opened. MODTIME selects a file based on the time that the file was last modified.
PAGE 99
Backup Object BRCOM BACKUP Command year is a 4-digit integer in the range 1900 through 2999. hour is a 2-digit integer in the range 0 through 23. minute is a 2-digit integer in the range 00 through 59. second is a 2-digit integer in the range 00 through 59. EOF eof-conditional eof-number selects a file based on its number of bytes. eof-conditional is any of: < > <= = >= <> (not equal to) eof-number is the size of a file in bytes.
PAGE 100
Backup Object BRCOM BACKUP Command exclude-object spec is the list of OSS files or directories separated by a comma ‘,’. Note.   Wild cards allowed in the exclude-object spec are *,!,?. EXCLUDE filter is an exclusion criterion and not an inclusion criterion. Exclusion criterion, if applied and satisfied, prevents the particular OSS object from being backed up. Any inclusion criterion, if applied and satisfied, allows an OSS object to be backed up.
PAGE 101
Backup Object BRCOM BACKUP Command user-name is the name of the user. Each name can contain from one to eight letters or digits, and the first character must be a letter. group-number is an integer in the range from 0 through 255 that uniquely identifies a group. 255 is reserved as the super-group ID. user-number is an integer in the range from 0 through 255 that uniquely identifies a user within a group. 255 is reserved for group managers (group,255) and the super ID (255,255).
PAGE 102
Backup Object BRCOM BACKUP Command time-conditional is any of: < BEFORE > AFTER time-value is one of these: {{day month |month day }year [hour:minute[:second]] } {[{day month|month day }year] hour:minute[:second]} For example: 1 JAN 2003 06:30 JAN 1 2003 06:30 02 JUL 2003 08:25:30 The default time-value is 00:00:00 (midnight) of today's date. The default for {day month | month day } year is today's date. day is an integer in the range 1 through 31.
PAGE 103
Backup Job Options BRCOM BACKUP Command eof-conditional is any of: < > <= = >= <> (not equal to) eof-number is the size of the table partition in bytes. TABLE specifies to back up only SQL/MX tables. Backup Job Options Backup and Restore 2 provides support for SQL/MX databases and OSS files. There are several categories of backup job options. Table 6-4.
PAGE 104
Backup Job Options BRCOM BACKUP Command Table 6-4.
PAGE 105
ALLOWMYID Job Option BRCOM BACKUP Command ALLOWMYID Job Option This job option specifies whether the MYID option is allowed during a RESTORE command. ON is the default. ALLOWMYID{ OFF | ON } ON allows the MYID option during a RESTORE command. OFF does not allow the MYID option during a RESTORE command. Guidelines  The ALLOWMYID job option supports only OSS objects. If you specify this option but do not specify an OSS object, an error occurs. This option is not supported for SQL/MX objects.
PAGE 106
BRICONDISK Job Option BRCOM BACKUP Command OFF BRIC is written to the last tape of the Backup. Note. The BRICONFRESHTAPE job option is supported only on systems running J06.08 and later J-series RVUs and H06.19 and later H-series RVUs. Guidelines  The BRICONFRESHTAPE job option is intended primarily for setups involving Virtual Tape Server (VTS). Since BRIC will now be present on a fresh tape, staging of tape with BRIC file from physical tape media to VTS cache during restore will be faster.
PAGE 107
CONSTRAINTS Job Option BRCOM BACKUP Command       BRIC is an unstructured binary code 0 file and contains the metadata of the backup operation. BRCMD is a code 101 file and contains the command that was used for the backup operation. You must manage the BRIC and BRCMD files because BR2 does not catalog these files or the information inside them. If the CLEANUP command is used from BRCOM for a JOB ID, the files are removed from the location.
PAGE 108
CONSTRAINTS Job Option BRCOM BACKUP Command    If you specify CONSTRAINTS EXCLUDED, you must specify the INDEXES EXCLUDED. The constraints that are backed up varies depending on whether you specify CONSTRAINTS INCLUDED or CONSTRAINTS EXCLUDED:. CONSTRAINTS INCLUDED EXCLUDED Check Yes No Not Null Yes Yes Unique Yes No Primary key droppable Yes No Primary key not droppable Yes Yes Referential integrity No No You cannot directly back up referential integrity constraints.
PAGE 109
FOLLOWMOUNTPTS Job Option BRCOM BACKUP Command FOLLOWMOUNTPTS Job Option This job option specifies whether other OSS filesets are included. ON is the default. FOLLOWMOUNTPTS { OFF | ON } OFF does not back up files in other OSS filesets that are mounted on the directories being backed up. For more information, see Backing Up OSS Objects Excluding Mount Points on page 6-45 ON backs up files in other OSS filesets that are mounted on the directories being backed up.
PAGE 110
INDEXES Job Option BRCOM BACKUP Command INDEXES Job Option This job option specifies whether or not table indexes are backed up. INCLUDED is the default. INDEXES { EXCLUDED | INCLUDED } EXCLUDED does not back up the table indexes and index partitions for each of the tables selected for backup. INCLUDED backs up the table indexes and index partitions for each of the tables selected for backup. Guidelines     The INDEXES job option is supported only for SQL/MX objects.
PAGE 111
LISTALL Job Option BRCOM BACKUP Command Guidelines  If you do not specify this job option, BRCOM automatically assigns a job identifier and displays it after the job has been started.   You cannot use a job ID if any files exist in $workvolume.jobid. The job ID cannot be present in the BRJOBS file. LISTALL Job Option This job option lists the names of the backed-up objects and objects that cause errors to an OUT file or a current terminal. OFF is the default.
PAGE 112
OPEN Job Option BRCOM BACKUP Command The syntax for the NEEDBOTH job option is: NEEDBOTH { ON | OFF } ON indicates that the occurrence of the first error in either tape is considered a parallel backup error, and the operation performs the same steps as the backup operation for this error. A warning message is displayed in the LIST output.
PAGE 113
OSSACL Job Option BRCOM BACKUP Command Guidelines Caution. If you restore a file that was modified or open for write access while being backed up, file-system error 59 (file is bad) can occur, and data can be lost. Whenever possible, close all files before running the BACKUP command. If audited files are backed up in the WRITE OPEN state, they could be corrupt. Restoring such files and using them in audited mode can cause TMF to leave the whole volume in an inconsistent state.
PAGE 114
OUT Job Option BRCOM BACKUP Command Guideline When backing up an OSS object containing an ACL, if the system call to retrieve ACL data fails, Backup and Restore 2 displays an EMS message: ZBRU-EVT-OSSACL-BACKUP-WRN OUT Job Option This job option specifies the location of the output for LISTALL ON. The default output location is your current terminal. OUT list-file list-file is a valid Guardian disk file, terminal, or spooler location that specifies the output location for the LISTALL ON option.
PAGE 115
PARTONLY Job Option BRCOM BACKUP Command PARTONLY Job Option This job option backs up individual tables or index partitions. OFF is the default. PARTONLY { OFF | ON } OFF disallows the back up of individual table or index partitions. ON backs up the table or index partitions that are explicitly specified for each of the tables or indices selected for backup. Table or index partitions that are not explicitly specified are not backed up. Guidelines Caution.
PAGE 116
SQLDATA Job Option BRCOM BACKUP Command  If you do not specify any index partitions or table partitions, you must not specify PARTONLY ON.  If you specified the PARTONLY ON job option during a backup operation, you must also specify PARTONLY ON for the RESTORE command.  The PARTONLY ON job option supports only SQL/MX objects. If you specify this job option but do not specify any SQL/MX objects, an error occurs. This option is not supported for OSS.
PAGE 117
TAPEDISPOSITION Job Option BRCOM BACKUP Command TAPEDISPOSITION Job Option This job option specifies the position and location of the tape at the end of the backup job. UNLOAD is the default. TAPEDISPOSITION { BOT | NOREWIND | UNLOAD } BOT rewinds the tape to the beginning and leaves it online when the backup job completes. NOREWIND leaves the tape positioned at its current location and online at the end of the backup job. UNLOAD dismounts the tape at the end of the backup job.
PAGE 118
OSS Backup Examples BRCOM BACKUP Command OSS Backup Examples The OSS examples assume a basic knowledge of these topics:      The UNIX directory structure and the OSS implementation of the directory structure OSS filesets, including the special nature of the root fileset Restricted-Access Fileset File privileges set on executables Mount points For more information about OSS, see the Open System Services Management and Operations Guide.
PAGE 119
OSS Backup Examples BRCOM BACKUP Command  To filter OSS files by modification time, use a WHERE expression and the MODTIME timestamp.
PAGE 120
OSS Backup Examples BRCOM BACKUP Command The /usr directory is backed up even if it does not meet the filter criteria. Filtering does not apply to directories. The /usr/usr1 and /usr/usr3 files have not been active since January 7th 2004 and are not backed up. These objects are backed up: Subdirectory of the root directory usr usr2  File in the /usr directory (last modified on 02 APR 2004) To filter OSS files by the creation time, use a WHERE expression and the CREATIONTIME timestamp.
PAGE 121
OSS Backup Examples BRCOM BACKUP Command The /usr/temp directory is excluded but the files in the /usr directory are backed up. Subdirectory of the root directory usr  usr1 File in the /usr directory usr2 File in the /usr directory usr3 File in the /usr directory To filter the OSS files by directory or filename, use a WHERE expression and the EXCLUDE filter combined with other filters using AND.
PAGE 122
OSS Backup Examples BRCOM BACKUP Command dirfi110 File in the /usr/dir1 directory usr1 File in the /usr directory usr3 File in the /usr directory Note. While using the EXCLUDE filter:  1. Verify the result of the filter, which is the set of files that will be included in the backup. 2. Use this result set with the other filter criteria. To filter the OSS files by directory or filename, use a WHERE expression and the EXCLUDE filter combined with other filters using OR.
PAGE 123
OSS Backup Examples BRCOM BACKUP Command The following objects are backed up.
PAGE 124
OSS Backup Examples BRCOM BACKUP Command The following objects are backed up.
PAGE 125
OSS Backup Examples BRCOM BACKUP Command In this example, the /local directory is a mount point for a separate fileset in the /usr directory. The fred and bill files are in another OSS fileset.
PAGE 126
OSS Backup Examples BRCOM BACKUP Command /usr/local/home/fred /usr/local/home/bill The mount point /local directory is itself not backed up.  This command also excludes files in other OSS fileset from the back up: BR> BACKUP =mytape, OSS / , FOLLOWMOUNTPTS OFF; The /mp directory is a mount point for the fs2 fileset. The files fs2d1, file1, and file2 are located in the other OSS fileset. Assume this directory structure.
PAGE 127
SQL/MX Backup Examples BRCOM BACKUP Command For more information, see Specifying Special Characters on page 4-4 Backing Up OSS Objects Containing ACLs To backup ACLs contained in OSS objects specify the OSSACL job option. For example: BR> backup $m1,oss /acls/file1,ossacl on,listall on,tapedisposition bot; Backing Up Using BRICONDISK Job Option To retain the BRIC and BRCMD files at the workvolume.jobid location, set the BRICONDISK job option to ON.
PAGE 128
SQL/MX Backup Examples BRCOM BACKUP Command           Backing Up an SQL/MX Table on page 6-51 Backing Up a Delimited SQL/MX Table on page 6-52 Backing Up SQL/MX Table Partitions on page 6-52 Backing Up a Delimited SQL/MX Table Partition on page 6-53 Backing Up SQL/MX Objects Using Filtering on page 6-54 Backing Up SQL/MX Indexes on page 6-53 Backing Up SQL/MX Indexes Separately on page 6-54 Backing Up SQL/MX Index Partitions on page 6-54 Excluding SQL/MX Indexes on page 6-54 Backing Up SQL/MX O
PAGE 129
SQL/MX Backup Examples BRCOM BACKUP Command Table 6-5.
PAGE 130
SQL/MX Backup Examples BRCOM BACKUP Command Table 6-6. Catalog and Subordinate Objects Catalog Schema Table Table Partition or Index Index Partition Description Catalog cat1 Subordinate schema of cat1 -sch1 Subordinate table of cat1.sch1 -tab1 -tpart1 Subordinate table partition of cat1.sch1.tab1 -ind1 Subordinate index of cat1.sch1.tab1 -ipart1 Subordinate index partition of the index for cat1.sch1.tab1 Subordinate schema of cat1 -sch2 Subordinate table of cat1.
PAGE 131
SQL/MX Backup Examples BRCOM BACKUP Command Table 6-7. Schema and Subordinate Objects Backed Up Catalog Schema Table Table Partition or Index Index Partition Description Subordinate schema of cat1 cat1.sch2 Subordinate table of cat1.sch2 -tab2 -tpart1 Subordinate table partition of cat1.sch2.tab2 -tpart2 Subordinate table partition of cat1.sch2.tab2 -tpart5 Subordinate table partition of cat1.sch2.
PAGE 132
SQL/MX Backup Examples BRCOM BACKUP Command To back up only the DDL for tables, specify the SQLDATA OFF option. User data is not backed up. For example: BR> BACKUP =mytape, MX TABLE cat1.sch2.tab2, SQLDATA OFF ; Backing Up a Delimited SQL/MX Table Backing up a delimited table also backs up all the subordinate indexes and partitions. For example, to back up all objects in “TAble1”: BR> BACKUP =mytape, MX TBL ”CATalog1”.”SCHema1”.”TAble1”; Note.
PAGE 133
SQL/MX Backup Examples BRCOM BACKUP Command Table 6-10. Individual Table Partitions Backed Up Catalog Schema Table Table Partition or Index Index Partition Description -tpart1 Subordinate table partition of cat1.sch2.tab2 -tpart5 Subordinate table partition of cat1.sch2.tab2 Backing Up a Delimited SQL/MX Table Partition To back up individual table partitions, specify TPART, the table that contains the partitions, the partitions to be backed up, and the job options.
PAGE 134
SQL/MX Backup Examples BRCOM BACKUP Command Backing Up SQL/MX Indexes Separately To back up indexes individually, specify the INDEX option. For example: BR> BACKUP $tape01, MX (IND cat.sch.ind1, INDEX cat.sch.ind2), tapedisposition bot; Backing Up SQL/MX Index Partitions To back up index and index partitions, specify the IPART option. For example: BR> BACKUP $tape01, MX (IPART cat.sch.ind1 PARTITION (ipart5), IPART cat.sch.
PAGE 135
Backing Up Both OSS and SQL/MX Objects BRCOM BACKUP Command Backing Up Both OSS and SQL/MX Objects You can back up both OSS and SQL/MX objects in the same command. For example: BR> BACKUP =mytape,(OSS ((/usr/bin, /home/sv/myfile, BR+> /usr/local/bin) WHERE (EOF > 200000 AND OWNER = BR+> super.super), (/etc/rc, /var/x) WHERE MODTIME AFTER BR+> JAN 17 1999)), (MX (CATALOG cat1, TABLE cat2.sch.tab1, BR+> TPART cat2.sch.
PAGE 136
BRCOM BACKUP Command Backing Up Both OSS and SQL/MX Objects Backup and Restore 2 Manual—522696-019 6-56
PAGE 137
7 BRCOM RESTORE Command You can use the BRCOM RESTORE command to:    Copy files from magnetic tape to disk. List the contents of a tape without restoring data. For more information, see Listing the Contents on Tape Without Restoring Data on page 7-10 Move files from one system to another. Note. The other system must have both Backup and Restore 2 and any other required software installed. For more information, see Installing Backup and Restore 2 on page 2-1 Managing Restore Jobs Note.
PAGE 138
Summary of Restoring SQL/MX or OSS Objects BRCOM RESTORE Command or a CLASS TAPE DEFINE. For more information, see Using DEFINEs With Backup and Restore 2 on page 4-6 4. To locate the set of tapes associated with a specific backup job, you can query the DSM/TC. However, DSM/TC does not contain file information. You must know which tape contains the files you need. To obtain a list of objects on a tape, see Listing the Contents on Tape Without Restoring Data on page 7-10 5.
PAGE 139
Summary of Restoring SQL/MX or OSS Objects BRCOM RESTORE Command SQL/MX Total Objects Restored Count The count of the total objects restored does not match the total objects backed up for the following reasons:       You can backup a catalog with all the schemas and tables, but choose to restore only a schema, table, index, table partition, or index partition. Restore does not include the BRIC in the restored objects count.
PAGE 140
Summary of Restoring SQL/MX or OSS Objects BRCOM RESTORE Command BR> backup \HPIDMR5.$Z3XT, MX ( sch sqlcat.sqlsch) , listall on,wait on; ** WARNING-2030 ** Enscribe and SQL/MP objects will not be backed up. Started job ZBR0013A File Mode BACKUP Program - T0744H02 - (21JAN2013) (C)2000 Compaq (C)2003, 2004 Hewlett Packard Development Company, L.P. backup \HPIDMR5.$Z3XT, MX ( sch sqlcat.sqlsch) , listall on,wait on; Unlabeled Tape.
PAGE 141
Summary of Restoring SQL/MX or OSS Objects BRCOM RESTORE Command SQLCAT.SQLSCH *SQL 255,255 SQLTAB ATa SQLCAT.SQLSCH.SQLTAB *SQL 255,255 550 A+ HPIDMR5_SYSTEM_ZSD 0 10Jan2013 14:43 ATP PJB33_Q452KH00 *** Meta object BRIC backed up *** Summary Information Job completed. Last error or warning occurred on page 1 Process elapsed time = 0:00:16.
PAGE 142
Summary of Restoring SQL/MX or OSS Objects BRCOM RESTORE Command *WARNING-5035* 14:45 10JAN13 254,00,234 Job ID: ZBR0013B, Process Name: $Z3Y1, Component: BR2DMA. This tape can only be restored with Backup/Restore 2.0. Job id: ZBR0013B Page: 1 Restore time: 10 Jan 2013, 14:45 Backup time: 10 Jan 2013, 14:44 *** Meta object \HPIDMR5.$SYSTEM.ZBR0013B.BRIC restored *** File System: SQLMX Tape: 1 RWEP Name Owner Code EOF Last modif Type ACa SQLCAT SQLCAT 255,255 SQLSCH ASc SQLCAT.
PAGE 143
Summary of Restoring SQL/MX or OSS Objects BRCOM RESTORE Command Restoring OSS Objects Restoring a directory includes all its subdirectories and files. Restoring SQL/MX Objects    Restoring a catalog includes restoring all its subordinate objects in its object hierarchy such as schemas, tables, and the subordinate objects of the tables. Restoring a schema includes restoring all the subordinate tables. Restoring a table includes:   Nondroppable constraints.
PAGE 144
BRCOM RESTORE Command Processing BRCOM RESTORE Command  The PRIVSOARFOPEN file privilege is set on the BR2DS, BR2ODS, BR2DMA, and BR2ODMA executable files. For information on how to set the file privileges on executable files, see Configuring Backup and Restore 2 on page 3-1. The backed up files can be restored to a restricted-access or unrestricted target fileset. Note.   Only the members of the SECURITY-PRV-ADMINISTRATOR security group can set or remove the fileset restrictions.
PAGE 145
Using the BRIC File BRCOM RESTORE Command   For labeled tapes, Backup and Restore 2 requests tapes in the order in which the volumes are specified in the DEFINE until it finds the last tape. If the BRIC file is on the last tape, Backup and Restore 2 restores it from that tape. If the BRIC file is on the last two tapes, Backup and Restore 2 requests the second to last tape and then the last tape again to restore the file.
PAGE 146
BRCOM RESTORE Command Listing the Contents on Tape Without Restoring Data Listing the Contents on Tape Without Restoring Data A list of objects on each tape is located in the BRIC file for each backup job. To obtain the list of the objects without restoring any data, use the RESTORE command with either the LISTONLY ON or LISTONLY DETAIL job options. For more information, see to LISTONLY Job Option on page 7-43.
PAGE 147
BRCOM RESTORE Command Listing the Contents on Tape Without Restoring Data Listing the Contents and Restoring the BRIC File to Disk You can restore the BRIC file to disk if you plan to issue multiple RESTORE commands for the same backup job. You can then avoid restoring the BRIC from tape each time you issue a RESTORE command for that backup job. Use the RESTOREDIR job option to restore the BRIC file from tape to disk. For more information, see RESTOREDIR Job Option on page 7-49.
PAGE 148
BRCOM RESTORE Command Listing the Contents on Tape Without Restoring Data Listing the Contents Using the BRIC Tape File To list the contents on tape without restoring any data: 1. Mount the tape containing the BRIC file. If there is only one tape, mount that tape. If the backup job spans multiple tapes, mount the last tape. 2. Check for mount requests in the EMS event log. 3. Use the RESTORE command with either the LISTONLY ON or LISTONLY DETAIL job option.
PAGE 149
Listing the Contents on Tape Without Restoring Data BRCOM RESTORE Command Example 7-1. LISTONLY ON Display for OSS Objects BR> RESTORE $TAPE, OSS /, LISTONLY ON ; *First tape* Tape #1 *WARNING-5035* 10:36 14MAY04 071,02,210 Job ID: ZBR00623, Process Name: $Z8SJ, Component: BR2DMA. This tape can only be restored with Backup/Restore 2.0.
PAGE 150
Listing the Contents on Tape Without Restoring Data BRCOM RESTORE Command Fields Description Job ID The job identifier File System OSS or SQL/MX Tape The number of the tape volume Mode The first character indicates the mode or type of file. For example:    d Directory l Symbolic link - Ordinary file The second through tenth characters indicate the permissions code. The code is divided into three sets of three characters each.
PAGE 151
Listing the Contents on Tape Without Restoring Data BRCOM RESTORE Command Example 7-2. LISTONLY DETAIL Display for OSS Objects Job id: ZBR000FC Restore(ListOnly) time: 01 Apr 2004, 09:28 Backup time: 01 Apr 2004, 08:22 File System: OSS Tape: 1 / OSS DIRECTORY INODE NUMBER 2 DEVICE ID 1082331758592 NUMBER OF LINKS 1 OWNER 255,65535 SECURITY: rwxr-xr-x DATA MODIF: 31 Mar 2004, 09:02 CREATION DATE: 31 Mar 2004, 09:02 LAST OPEN: 01 Apr 2004, 08:22 Summary Information Job completed.
PAGE 152
Listing the Contents on Tape Without Restoring Data BRCOM RESTORE Command Field Description The type of object. For example, OSS DIRECTORY or OSS FILE. INODE NUMBER The internal storage pointer to the disk file. DEVICE ID The device ID for OSS directories. NUMBER OF LINKS The number of links. The number is normally 1. For each hard link, the number is increased by 1. OWNER The OSS owner of the file.
PAGE 153
Listing the Contents on Tape Without Restoring Data BRCOM RESTORE Command Example 7-3. LISTONLY Display for SQL/MX Objects *First tape* Tape #1 Job id: ZBR003E1 Restore(ListOnly) time: 03 Aug 2004, 17:45 Page: 1 Backup time: 03 Aug 2004, 14:34 File System: SQLMX RWEP Tape: 1 Owner Code EOF Last modif Type Name CATALOG1 ACa CATALOG1 CATALOG1.SCHEMA1 ASc SCHEMA1 *SQL ATa EMPLOYEE1 255,255 255,255 CATALOG1.SCHEMA1.
PAGE 154
Listing the Contents on Tape Without Restoring Data BRCOM RESTORE Command Field Description Job ID The job identifier Backup Time The time the objects were backed up File System: SQL/MX The type of objects backed up Tape The number of the tape volume RWEP *SQL For a description of SQL/MX security, see SQL/MX on page 1-7.
PAGE 155
Listing the Contents on Tape Without Restoring Data BRCOM RESTORE Command Example 7-4. LISTONLY ON Display with RESTOREDIR for OSS Objects BR> RESTORE $TAPE2, OSS /, RESTOREDIR $FC23.SOL0952.RESBRIC, LISTONLY BR+> ON; *First tape* Tape #1 *WARNING-5035* $Y1J9, 15:42 12JUN08 050,03,055 Job ID: ZBR0020F, Process Name: Component: BR2DMA. This tape can only be restored with Backup/Restore 2.0.
PAGE 156
Specifying a Different Target for an Object BRCOM RESTORE Command Specifying a Different Target for an Object When restoring an SQL/MX object to a different parent object, you must specify a target that is one level higher in the hierarchy as shown in Table 7-1. Table 7-1.
PAGE 157
BRCOM RESTORE Command Syntax BRCOM RESTORE Command BRCOM RESTORE Command Syntax The syntax for the RESTORE command is: RESTORE tape-device-name [ , run-option [ , run-option ] ... ] [ { , restore-object-spec }] [ , restore-job-option, restore-job-option ...] [ , config-option, config-option ...] tape-device-name is the name of a tape drive that contains the unlabeled tape for the restore operation or a DEFINE name for a labeled-tape restore operation.
PAGE 158
BRCOM RESTORE Command Syntax BRCOM RESTORE Command Table 7-2. DEFINE Attribute Exceptions for the RESTORE Command Option Meaning BLOCKLEN Valid but ignored. The value of BLOCKLEN is always the default value or the value you specified for the BLOCKSIZE job option when you backed up the file. DENSITY Not supported. EBCDIC Not supported. LABELS Valid values are BACKUP or OMITTED. LOGICAL Valid but ignored. PHYSICAL Valid but ignored. RECFORM Valid but ignored.
PAGE 159
BRCOM RESTORE Command Syntax BRCOM RESTORE Command Table 7-3. Run Option Exceptions for the RESTORE Command Run Option Meaning CPU This run option is not supported. This option specifies the number of the processor where the Data Management Application (DMA) is to run. You specify the list of processors in which the Data Service and Tape Service using the SERVICECPULIST config-option. DEFMODE This run option is not supported. GUARANTEEDSWAPSPACE This run option is not supported.
PAGE 160
BRCOM RESTORE Command Syntax BRCOM RESTORE Command RESTORE job options for the BACKUP and RESTORE utilities (T9074), see Changed or Unsupported Restore Job Options on page B-6. config-option specifies the RESTORE configuration options that you can use to supersede the configuration option settings in the BRCONFIG file. It is any of: EMSCOLLECTOR[\node.]$process-name SERVICECPULIST [processor [, processor ] ]...
PAGE 161
BRCOM RESTORE Syntax When Using an IN File BRCOM RESTORE Command BRCOM RESTORE Syntax When Using an IN File The RESTORE command in the IN file must not itself specify the IN run option. If you specify an IN file, the tape-device-name specified on the command line overrides the tape-device-name specified in the IN file. For more information, see Using an IN File on page 4-7. When you are using an IN file, the syntax is: RESTORE tape-device-name [ , run-option [ , run-option ] ...
PAGE 162
Restore Objects BRCOM RESTORE Command OSS RESTORE Object oss-restore-object-spec specifies the objects to be restored. It is one of these: OSS { oss-restore-object } { (oss-restore-object [ , oss-restore-object ] ...) } { (oss-restore-object [ , oss-restore-object ] ... ) WHERE expression } { (oss-restore-object [ ,oss-restore-object ] ... ) WHERE expression [ ,(oss-restore-object [ ,oss-restore-object ] ... ) WHERE expression ]... } oss-restore-object specifies the OSS objects to be restored.
PAGE 163
Restore Objects BRCOM RESTORE Command or the number of bytes in the file. The order of precedence in expression evaluation is parentheses, NOT, AND, OR. Parentheses within a WHERE expression are optional. For OSS, it is any of: { { { { oss-qualifier NOT oss-qualifier (oss-qualifier AND oss-qualifier ... ) (oss-qualifier OR oss-qualifier ...
PAGE 164
Restore Objects BRCOM RESTORE Command It is one of these: { sqlmx-source } { (sqlmx-source [{, TARGET | TGT} sqlmx-object-type sqlmx-target)]) } sqlmx-source is the set of SQL/MX objects to be restored. The object specified and all its subordinate objects are restored unless specifically excluded. It is one of these: {sqlmx-object-type sqlmx-source-base {TPART sqlmx-table [ , sqlmx-part PARTITION ( sqlmx-part ]...
PAGE 165
Restore Objects BRCOM RESTORE Command sqlmx-table is a valid SQL/MX table name. PARTITION(sqlmx-part[,sqlmx-part ]...) is one or more valid SQL/MX table partition names of the table specified in sqlmx-table. If you specify the TPART object type, you must specify at least one table partition name and the PARTONLY job option. You must enclose the names of the table partitions in parentheses. sqlmx-index is a valid SQL/MX index name. IPART is the name of an index partition.
PAGE 166
Restore Objects BRCOM RESTORE Command sqlmx-qualifier is any of: OWNER = user-id sqlmx-timestamp time-conditional timevalue EOF eof-conditional eof-number TABLE For more information, see Filters for SQL/MX Objects on page 7-33 Backup and Restore 2 Manual—522696-019 7-30
PAGE 167
Restore Objects BRCOM RESTORE Command Filters for OSS Files For OSS, filtering applies only to files, not directories. OWNER = user-id selects a file based on the user ID. It is a NonStop user ID in one of these forms: { group-name.user-name { group-name.* { group-number, user-number { group-number,* } } } } group-name is the group name of the user. Each name can contain from one to eight letters or digits, and the first character must be a letter. user-name is the name of the user.
PAGE 168
Restore Objects BRCOM RESTORE Command LASTOPENTIME applies only to files. MODTIME applies only to files. time-conditional is one of these: < BEFORE > AFTER time-value is one of these: {{day month|month day}year[hour:minute[:second] ] } {[{day month|month day}year]hour:minute[:second] } For example: 1 JAN 2003 06:30 JAN 1 2003 06:30 02 JUL 2003 08:25:30 The default time-value is 00:00:00 (midnight) of today's date. The default for {day month | month day} year is today's date.
PAGE 169
Restore Objects BRCOM RESTORE Command second is a 2-digit integer in the range 00 through 59. EOF eof-conditional eof-number selects a table partition based on its number of bytes. eof-conditional is any of: < > <= = >= <> (not equal to) eof-number is the number of bytes in a table partition. Filters for SQL/MX Objects For SQL/MX objects, the filters are applied only to certain types of objects as shown in Table 7-4. You cannot filter SQL/MX constraints.
PAGE 170
Restore Objects BRCOM RESTORE Command { group-number,* } group-name is the group name of the user. Each name can contain from one to eight letters or digits, and the first character must be a letter. user-name is the name of the user. Each name can contain from one to eight letters or digits, and the first character must be a letter. group-number is an integer in the range from 0 through 255 that uniquely identifies a group. 255 is reserved as the super-group ID.
PAGE 171
Restore Objects BRCOM RESTORE Command REDEFINITIONTIME selects a table based on the time that the table was last redefined. time-conditional is one of these: < BEFORE > AFTER time-value is one of these: {{day month|month day}year[hour:minute[:second] ] } {[{day month|month day}year]hour:minute[:second] } For example: 1 JAN 2003 06:30 JAN 1 2003 06:30 02 JUL 2003 08:25:30 The default time-value is 00:00:00 (midnight) of today's date. The default for {day month | month day} year is today's date.
PAGE 172
RESTORE Job Options BRCOM RESTORE Command EOF eof-conditional eof-number selects a table partition based on its number of bytes. eof-conditional is any of: < > <= = >= <> (not equal to) eof-number is the number of bytes in a table partition. TABLE specifies to restore only SQL/MX tables.
PAGE 173
CONSTRAINTS Job Option BRCOM RESTORE Command Table 7-5.
PAGE 174
DIRECTORY Job Option BRCOM RESTORE Command     If you specify CONSTRAINTS INCLUDED, you cannot specify INDEXES EXCLUDED or PARTONLY ON. If you specify CONSTRAINTS EXCLUDED, you must specify the INDEXES EXCLUDED. If you specify a WHERE expression and CONSTRAINTS INCLUDED, a constraint is not restored unless it meets the filter criteria of the WHERE expression. The constraints restored vary depending on whether you specify INCLUDED or EXCLUDED. Some types of constraints are not supported.
PAGE 175
FOLLOWMOUNTPTS Job Option BRCOM RESTORE Command You must specify a valid tape device name, but the device does not need to exist because the tape drive is not used. FOLLOWMOUNTPTS Job Option Use this job option to specify whether to include OSS filesets or not. ON is the default. FOLLOWMOUNTPTS { OFF | ON } ON restores other filesets mounted on a directory. OFF does not restore other filesets mounted on a directory. Guidelines  The FOLLOWMOUNTPTS job option is supported only for OSS objects.
PAGE 176
JOB Job Option BRCOM RESTORE Command EXCLUDED does not restore the table indexes and index partitions for each of the tables being restored. INCLUDED restores the table indexes and index partitions for each of the tables being restored. Guidelines   The INDEXES job option is supported only for SQL/MX objects. If you specify this job option but do not specify any SQL/MX objects, an error occurs. If you specify INDEXES EXCLUDED, you must specify CONSTRAINTS EXCLUDED.
PAGE 177
KEEP Job Option BRCOM RESTORE Command  Use this option with caution. Job creation fails if there is already a job in BRJOBS with the same job identifier or if there are any files in $workvolume.jobid. If you omit this option and let BRCOM assign the job identifier, job creation will not fail for these reasons. KEEP Job Option Use this job option to specify whether a tape file is restored if a file with the same name already exists on disk. OFF is the default.
PAGE 178
LISTALL Job Option BRCOM RESTORE Command ON restores the partitions with same Guardian file names as is in the backup image. OFF restores the partitions with the system-generated Guardian file names. Guidelines         This job option is not supported for OSS file-system objects. This job option is supported only for SQL/MX objects. If you specify this job option without specifying any SQL/MX objects, syntax error occurs.
PAGE 179
LISTONLY Job Option BRCOM RESTORE Command ON lists the names of the objects that are restored successfully from tape and the names of objects that are not restored because of errors. DETAIL lists the characteristics of each object restored. OFF lists only object names that are associated with error messages to the EMS log. Guidelines  If you specify LISTALL ON or LISTALL DETAIL, you cannot specify LISTONLY ON or LISTONLY DETAIL.
PAGE 180
LOCATION Job Option BRCOM RESTORE Command Guidelines         If you specify VERIFYTAPE ON, you must specify either LISTONLY ON or LISTONLY DETAIL. To specify a list of all the objects on tape, you can specify mx cat * and oss /. If you specify LISTONLY ON or LISTONLY DETAIL:   The restore job runs without restoring any objects. You cannot specify LISTALL ON or LISTALL DETAIL.
PAGE 181
MYID Job Option BRCOM RESTORE Command [\node.]$dest-vol is the volume on the magnetic disk where the SQL/MX objects are to be restored. Specifying the node is optional. [\node.]$source-vol.source-subvol.source-file is the fully qualified file name on the tape. Specifying the node is optional. [\node.]$dest-volume.dest-subvol.dest-file is the fully qualified file name on the magnetic disk where the SQL/MX objects are to be restored. Specifying the node is optional.
PAGE 182
OSSACL Job Option BRCOM RESTORE Command   MYID job option is applicable only for super users. If the requestor performing the restore is a non super.super user, then, only the OSS file system objects that the requestor owns are restored, regardless of the MYID job option being specified. Note. This behavior is different from the B/R 1 (T9074). This behavior is supported only on systems running J06.03 RVU.
PAGE 183
OUT Job Option BRCOM RESTORE Command  Backup and Restore 2 displays the EMS message, ZBRU-EVT-SMART-AGENT-ERR, if a system call fails when restoring the OSS ACL data of an object. OUT Job Option Use this job option to specify a location for listing output. The default output location is your current terminal. OUT list-file list-file is a valid Guardian disk file, terminal, or spooler location.
PAGE 184
PARTONLY Job Option BRCOM RESTORE Command PARTONLY Job Option Use this job option to specify which table partitions are to be restored. This option applies to SQL/MX objects. OFF is the default. PARTONLY { OFF | ON } ON restores only the partitions explicitly specified for each of the tables selected to be restored. Partitions that are not specified explicitly are not restored. OFF does not allow individual table partitions to be restored. Guidelines Caution.
PAGE 185
RESTOREBKUPSPEC Job Option BRCOM RESTORE Command resulting in an inconsistent table. Accessing the data from the table can lead to unpredictable results.      If you explicitly specify any table partitions or index partitions, you must specify PARTONLY ON. If you do not specify any table partitions or index partitions, you must not specify PARTONLY ON. If you specify PARTONLY ON, you cannot specify SQLDATA OFF or LOCATION.
PAGE 186
SHOWDDL Job Option BRCOM RESTORE Command SHOWDDL Job Option Use this job option to generate OSS files containing DDL information. SHOWDDL { OFF | ON } ON generates one or more OSS files containing DDL information. These files are created in addition to the objects normally being restored. OFF does not generate OSS files containing DDL information. OFF is the default. Guidelines     This job option is not supported for OSS. The SHOWDLL job option is supported only for SQL/MX objects.
PAGE 187
OBEYDDL Job Option BRCOM RESTORE Command oss-directory is the name of an OSS directory in which the restore operation should generate the files. Guidelines   If you specify this job option, you must also specify the SHOWDDL ON job option. The SHOWDDLLOC job option is supported only for SQL/MX objects. If you specify this job option but do not specify any SQL/MX objects, an error occurs.
PAGE 188
SQLDATA Job Option BRCOM RESTORE Command  To use OBEYDDL job option, you must specify the SHOWDDLLOC option and set SHOWDDL option to ON.  OBEYDDL job option is used for restoring catalogs, schemas, and tables. Restoring table partitions, indexes, and index partitions is not supported with this option. SQLDATA Job Option Use this job option to use the DDL information to re-create an empty version of table partitions and index partitions. ON is the default.
PAGE 189
TAPEDISPOSITION Job Option BRCOM RESTORE Command OFF changes the lastopen and modification timestamps of the restored objects to the time of the restore job. The creation date for the object is the restore date regardless of the value of TAPEDATE. TAPEDISPOSITION Job Option Use this job option to specify the position and location of the tape at the end of the backup job. UNLOAD is the default.
PAGE 190
VERIFYTAPE Job Option BRCOM RESTORE Command ON verifies the integrity of data on tape. OFF does not verify the integrity of data on tape. Guideline You do not need to use the VERIFYTAPE ON option unless you also specify the LISTONLY ON or LISTONLY DETAIL. When you restore objects, the data is always verified as it is restored.
PAGE 191
Examples BRCOM RESTORE Command Examples    OSS Restore Examples SQL/MX Restore Examples on page 7-60 Restore Examples With Both OSS and SQL/MX Objects on page 7-75 OSS Restore Examples To restore any OSS directory, specify the directory on tape to be restored. The directory and all its subordinate objects are restored to disk unless you specifically excluded them using a WHERE expression or job options.
PAGE 192
OSS Restore Examples BRCOM RESTORE Command usr2 usr3  To restore objects to different target directories, specify a TARGET.
PAGE 193
OSS Restore Examples BRCOM RESTORE Command etc rc var x Directory File in the /etc directory (last modified on 20 JAN 1999) Directory File in the /x directory (last modified on 12 DEC 1998) The /etc and /var directories are both restored. The x file is not restored. etc rc var  Directory File in the /etc directory (created on 07 JAN 2004) Directory If you specify a WHERE expression for one set of OSS objects, you must specify a WHERE expression for each other set of OSS objects in the command.
PAGE 194
OSS Restore Examples BRCOM RESTORE Command Assume this directory structure on tape: Directory /usr /bin /local /bin Subdirectory of the /usr directory Directory Subdirectory of the /local directory /file1 File in the /bin directory (1000000 bytes and owned by software.sitaramv) /file2 File in the /bin directory (2500000 bytes and owned by software.
PAGE 195
OSS Restore Examples BRCOM RESTORE Command Restoring OSS Objects Including Mount Points To include the files from another fileset in the restore, specify the FOLLOWMOUNTPTS ON job option.
PAGE 196
SQL/MX Restore Examples BRCOM RESTORE Command  To restore hard link, you must restore the complete set of hard-linked files. For example: BR> RESTORE =mytape, OSS (/usr/project/file1, BR+> /usr/project/file2,/usr/project/file3); If you have backed up and restored all the hard links, the links all point to a single inode. If you backed up an incomplete set of hard links, the hard links are severed after you restore the files.
PAGE 197
SQL/MX Restore Examples BRCOM RESTORE Command            Restoring a Delimited SQL/MX Schema on page 7-67 Restoring SQL/MX Tables on page 7-67 Restoring a Delimited SQL/MX Table on page 7-68 Restoring SQL/MX Table Partitions on page 7-69 Restoring a Delimited SQL/MX Table Partition on page 7-70 Restoring SQL/MX Indexes on page 7-70 Restoring SQL/MX Indexes Separately on page 7-71 Restoring SQL/MX Index Partitions on page 7-72 Restoring an SQL/MX Object to a Different Target on page 7-72 Restor
PAGE 198
SQL/MX Restore Examples BRCOM RESTORE Command Table 7-7.
PAGE 199
SQL/MX Restore Examples BRCOM RESTORE Command To restore the table cat1.sch1.tab1 to the target schema cat2.
PAGE 200
SQL/MX Restore Examples BRCOM RESTORE Command RESTORE $tape01, MX (table cat1.sch1.tab1, target schema cat2.sch1), KEEPGFN ON, location ($data01 TO $System1 , $data02.ZSDSCH01.TPARTB00 TO $System02.ZSDSCH02.PARTTB00), listall on, tapedisposition BOT;    The partition at $data02.ZSDSCH01.TPARTB00 will be restored to $System02.ZSDSCH02.PARTTB00. All partitions on volume $data01 will be restored to volume $system1.
PAGE 201
SQL/MX Restore Examples BRCOM RESTORE Command   If the schema cat1.sch1 already exists with the subvolume name as that of the BACKUP-OBJECTS, the schema will be restored with the subvolume name and physical file names of the partitions as that of the BACKUP-OBJECTS. While restoring to the remote node, if the schema cat1.
PAGE 202
SQL/MX Restore Examples BRCOM RESTORE Command Table 7-8.
PAGE 203
SQL/MX Restore Examples BRCOM RESTORE Command Restoring a Delimited SQL/MX Schema To restore all objects in “CATalog1”.”SCHema1” BR> RESTORE =mytape, MX SCHEMA “CATalog1”.”SCHema1”; Note. SQL/MX schemas containing delimiters are supported only on systems running H06.06 or later H-series RVUs. Restoring SQL/MX Tables To restore all objects in table cat1.sch2.tab2: BR> RESTORE =mytape, MX TABLE cat1.sch2.tab2; The table cat1.sch2.tab2 and all its subordinate objects as shown in Table 7-10 are restored.
PAGE 204
SQL/MX Restore Examples BRCOM RESTORE Command Table 7-11. Two Tables and Subordinate Objects Restored Catalog Schema Table Table Partition or Index Index Partition Description Subordinate table of cat1.sch1 cat1.sch1.tab1 -tpart1 Subordinate table partition of tab1 -tpart2 Subordinate table partition of tab1 -ind1 Subordinate index of tab1 -ipart1 Subordinate index partition of the index for tab1 Subordinate table of cat1.sch2 cat1.sch1.
PAGE 205
SQL/MX Restore Examples BRCOM RESTORE Command Restoring SQL/MX Table Partitions When you restore a table, the table’s partitions are also restored. To restore only an individual table partition, you must specify the PARTONLY ON job option. For example: BR> RESTORE =mytape, MX TPART cat1.sch2.tab2 PARTITION BR+> (TPART5), PARTONLY ON, INDEXES EXCLUDED, CONSTRAINTS BR+> EXCLUDED ; As shown in Table 7-12, only TPART5 is restored. Table 7-12.
PAGE 206
SQL/MX Restore Examples BRCOM RESTORE Command Restoring a Delimited SQL/MX Table Partition To restore individual delimited table partitions, PARt1 and PARt2, you must specify the PARTONLY ON job option. For example: BR> RESTORE =mytape, MX (TPART “CATalog1”.”SCHema1”.”TAble1” BR+>PARTITION (“PARt1”, “PARt2”)), PARTONLY ON, CONSTRAINTS BR+> EXCLUDED,INDEXES EXCLUDED; Note. SQL/MX tables partitions containing delimiters are supported only on systems running H06.06 or later H-series RVUs.
PAGE 207
SQL/MX Restore Examples BRCOM RESTORE Command For both these commands, the objects shown in Table 7-14 are restored: Table 7-14. Table and Subordinate Objects Restored Including the Index and Index Partition Catalog Schema Table Table Partition or Index Index Partition Description Subordinate table of cat1.sch1 cat1.sch1.
PAGE 208
SQL/MX Restore Examples BRCOM RESTORE Command For more information on target keyword, see Restoring an SQL/MX Object to a Different Target. For example: BR> RESTORE $tape01, MX (IND cat.sch.ind1, TGT TABLE cat.sch.t1); Restoring SQL/MX Index Partitions To restore index partitions individually, specify the IPART option. For example: Restore $tape01, mx (IPART cat.sch.
PAGE 209
SQL/MX Restore Examples BRCOM RESTORE Command  However, all the objects from the backup job under the catalog cat1 are restored to the same parent object they were backed up from. Table 7-17.
PAGE 210
SQL/MX Restore Examples BRCOM RESTORE Command  If the names of the target table partitions match with the partition names in the source but their ranges mismatch, BR2 will restore the data to the partitions whose names match. This will result in an inconsistent table. Note. The behavior for index partitions with respect to indexes will be same as mentioned for the target tables.
PAGE 211
Restore Examples With Both OSS and SQL/MX Objects BRCOM RESTORE Command Restoring a Delimited SQL/MX Object to a Different Target To restore a delimited SQL/MX object to a different delimited target: BR> RESTORE =mytape, MX CATALOG “SAMPle”). (SCHEMA “CATalog1”.”SCHema1”, TGT Note. SQL/MX objects containing delimiters are supported only on systems running H06.06 or later H-series RVUs.
PAGE 212
Restore Examples With Both OSS and SQL/MX Objects BRCOM RESTORE Command RESTORE =mytape, OSS ( ( (/usr/bin, TGT /newdir),/usr/local/bin ) WHERE (EOF > 200000 AND OWNER = software.sitaramv), ( (/home/sv/myfile, TGT /home/sv), /etc/rc,/var/x ) WHERE MODTIME AFTER JAN 17 1999 ), MX ( ( CATALOG cat1, (TABLE cat2.sch2.tab1, TGT SCH sch3), (TPART cat2.sch.tab2 PARTITION (tpart5), TGT TAB catn1.schn1.
PAGE 213
8 Monitoring Backup and Restore 2 Jobs This section describes troubleshooting Backup and Restore 2 jobs. Monitoring Job Information You can use BRCOM, MEDIACOM, and EMS event messages to monitor job information:    Using DSM/TC (MEDIACOM) Using EMS Event Messages Using BRCOM to Display Current Status for a Job Using EMS Event Messages You must monitor the EMS events for job status. Many errors that require operator intervention are reported only through EMS events.
PAGE 214
Using BRCOM to Display Current Status for a Job Monitoring Backup and Restore 2 Jobs To quickly check the status of a job, use the STATUS JOB, BRIEF command. BRIEF is the default, so it does not have to be specified. For example, these two commands are equivalent: BR> STATUS JOB zbr005be, BRIEF; BR> STATUS JOB zbr005be ; Example 8-1.
PAGE 215
Monitoring Backup and Restore 2 Jobs Using BRCOM to Display Current Status for a Job Source The process name of the source service. For a backup job, the source is the Data Service. For a restore job, the source is the Tape Service. Dest1 The process name of the first destination service. For a backup job, the first destination service is the Tape Service. For a restore job, the first destination service is the Data Service. Dest2 The field does not provide any information.
PAGE 216
Using BRCOM to Display Current Status for a Job Monitoring Backup and Restore 2 Jobs Example 8-3.
PAGE 217
Using BRCOM to Display Current Status for a Job Monitoring Backup and Restore 2 Jobs Example 8-4.
PAGE 218
Using BRCOM to Display Current Status for a Job Monitoring Backup and Restore 2 Jobs Field Description Owner The owner of the job. Start Time The day and time the job was started. End Time The day and time the job ended. Operation The operation being performed: BACKUP Backup PARALLEL BACKUP Parallel Backup RESTORE Restore BACKCOPY Backcopy Comments The backcopy operation is supported only on systems running H06.06 or later Hseries RVUs. Status The status of the job.
PAGE 219
Using BRCOM to Display Current Status for a Job Monitoring Backup and Restore 2 Jobs Field Description Comments Estimated Remaining Time Estimated time remaining for operation for a verifytape operation. A value is displayed only if you used the VERIFYTAPE job option. Otherwise, the value is 0. DMA Process The process name of the DMA. CPU The processor the DMA is running in. Pri The initial priority at which the DMA process was started.
PAGE 220
Using BRCOM to Display Current Status for a Job Monitoring Backup and Restore 2 Jobs Field Description Tapedrive1 If present, first tapedrive used by a Parallel Backup operation. Tapedrive2 If present, second tapedrive used by a Parallel Backup operation Tapedrive If present, the first tape drive used by the destination service for a parallel backup job. Comments Monitoring Job States To monitor job states, use the STATUS JOB command. Table 8-1 describes the status for backup and restore jobs.
PAGE 221
A BRCOM Error Messages This appendix describes the BRCOM error messages. When a message is displayed on your terminal, it is preceded by either **ERROR** or **WARNING**. For event messages, see the Operator Messages Manual. Error Messages 2001 Unrecognized command. Cause. The command you specified is not recognizable. Effect. The command does not execute. Recovery. Check the syntax and specify the correct command. 2002 You do not own this job and you are not a member of the Super-group.
PAGE 222
Error Messages BRCOM Error Messages 2003 Insufficient privilege to execute this command. Your user ID is (your user-ID). your user-ID is your user ID. Cause. You issued a command that requires a super-group user ID. Effect. The command does not execute. Recovery. Log on using a super-group user ID and reissue the command. 2004 Specified Job ID jobid does not exist. jobid is a valid unique job identifier with a maximum of eight characters. The characters can be alphabetic, numeric, or a combination.
PAGE 223
Error Messages BRCOM Error Messages 2007 Unable to abort/stop the job because the current status must be INIT, RUN, WAIT, or CAT. Cause. You issued an ABORT JOB or STOP JOB command for a job whose status was not INIT (initializing), RUN (running), WAIT (waiting on tape open), or CAT (cataloging). Effect. The command does not execute. Recovery. You normally do not need to abort or stop the job if its status is already TERM (terminating), DONE, STOP (stopped), ABRT (aborted), or ABND (abended).
PAGE 224
Error Messages BRCOM Error Messages Recovery. Examine the EMS message log to determine why the job might have failed. Retry the BACKUP or RESTORE command if necessary. 2010 Unable to perform CLEANUP operation because the current status is not DONE, STOP, ABRT, or ABND. Cause. The CLEANUP JOB command is valid only for jobs in the DONE, STOP (stopped), ABRT (aborted), or ABND (abended) state. You issued a CLEANUP JOB command for a job that was not in one of these states. Effect.
PAGE 225
Error Messages BRCOM Error Messages 2014 File system error file-system-error occurred when attempting [operation] operation on file filename. file-system-error is the number of the file-system error. filename is the name of the file. Cause. A file-system error occurred when you attempted the indicated operation on the file filename. Effect. The operation does not complete. The operation is displayed if known. Recovery. Determine the cause of the error based on the error number.
PAGE 226
Error Messages BRCOM Error Messages Recovery. If necessary, restore a valid version of the file from a backup or, for BRCONFIG, reenter the desired configuration with the ALTER CONFIG command. 2017 Attempt to execute filename failed with process creation error error[, error-detail]. filename is the name of the file. error is the process creation error number. error-detail is the detail of the error. Cause. BRCOM attempted to start a new process, but a process creation error occurred. Effect.
PAGE 227
Error Messages BRCOM Error Messages 2021 Internal error: detailed error information. detailed-error-information is the detailed error information. Cause. An internal BRCOM error occurred. Effect. Results vary. Recovery. Retry the operation. If the problem persists, contact your service provider. 2022 No more automatically generated Job IDs available. Cause. No more automatically generated job IDs are available.
PAGE 228
Error Messages BRCOM Error Messages 2024 Cannot run multiple Backup or Restore operations using the BRCOM home terminal. Cause. You attempted to perform a BACKUP or RESTORE command that requires the BRCOM home terminal while another backup or restore operation was already running from the same BRCOM session. For more information, see Handling Operations That Use the BRCOM Terminal on page 4-5 Effect. The second command fails. The first operation is unaffected. Recovery.
PAGE 229
Error Messages BRCOM Error Messages 2028 The PAUSE command may only be run from an interactive BRCOM session. Cause. You attempted to issue the PAUSE command from a BRCOM session that was not interactive. A BRCOM session is considered to be interactive if its IN and OUT devices are terminal devices. Effect. The command does not execute. If the command occurred in an IN file, BRCOM stops processing the file and ABENDs. If the command occurred in a command file, BRCOM stops processing the file. Recovery.
PAGE 230
Error Messages BRCOM Error Messages 2031 Restart error: . Cause. An error was found when processing the Restart command. Effect. The command does not execute. Recovery. Examine the detailed error information and reissue the command. 2032 Only OSS objects will be backed up. Cause. You used Backup and Restore 2 to back up OSS on a system where SQL/MX is not installed. Effect. Enscribe, SQL/MP, and SQL/MX objects are not backed up. Recovery. None.
PAGE 231
Error Messages BRCOM Error Messages 2035 OSS objects are restored without ACL data. Cause. You used Backup and Restore 2 to restore backup image which can contain OSS files with ACL data. Effect. OSSACL data of the files will not be restored. Recovery. None. This is an informational message only. 2036 To avoid any data inconsistency issue, use TPART, INDEX, or IPART in the BACKUP or RESTORE command. Cause. TPART, INDEX, or IPART keyword is used in the BACKUP or RESTORE command. Effect.
PAGE 232
Error Messages BRCOM Error Messages Backup and Restore 2 Manual—522696-019 A-12
PAGE 233
B Comparison With the BACKUP and RESTORE Utilities This appendix describes the differences between Backup and Restore 2 and the BACKUP and RESTORE utilities (T9074). BRCOM (T2721), the interface to Backup and Restore 2, coexists with the BACKUP and RESTORE utilities (T9074). Note. The syntax for Backup and Restore 2 is different from the syntax for the BACKUP and RESTORE utilities (T9074).
PAGE 234
Comparison With the BACKUP and RESTORE Utilities Unsupported Tape Format Unsupported Tape Format BRCOM and the BACKUP and RESTORE utilities (T9074) support different tape formats. Therefore, you cannot mix Enscribe and SQL/MP files on the same tape with the OSS and SQL/MX files. Unsupported Restore Operation You cannot use a previous product version update (PVU) of Backup and Restore 2 to restore a backup created using a later PVU.
PAGE 235
Comparison With the BACKUP and RESTORE Utilities  Unsupported File-Set List Qualifiers You can exclude a SQL/MX object based on its creation time, last open time, modification time, or redefinition time. You can also limit a backup or restore to objects owned by a specific user ID.
PAGE 236
Comparison With the BACKUP and RESTORE Utilities Changed or Unsupported Backup Job Options Table B-1. Backup Job Options Not Supported or Changed (page 2 of 3) Option SQL/MP or Enscribe SQL/MX or OSS MSGONLOCK Enscribe This option is not supported. SQL/MP MULTIDRIVE Enscribe This option is not supported. SQL/MP NEEDBOTH Enscribe SQL/MP NOMYID Enscribe SQL/MP NOPROMPT Enscribe SQL/MP BACKUP and RESTORE utilities (T9074) run in waited mode.
PAGE 237
Comparison With the BACKUP and RESTORE Utilities Changed or Unsupported Backup Job Options Table B-1. Backup Job Options Not Supported or Changed (page 3 of 3) Option SQL/MP or Enscribe SQL/MX or OSS REBUILD Enscribe This option is not supported. REGISTERONLY SQL/MP SQL/MX does not register programs. REMOTEIOSIZE Standard This option is not supported. SQL/MX bulk I/O defaults to 56 kilobytes. SCRATCHVOL Enscribe This option is not supported.
PAGE 238
Comparison With the BACKUP and RESTORE Utilities Changed or Unsupported Restore Job Options Changed or Unsupported Restore Job Options BRCOM does not support any options that apply only to SQL/MP or Enscribe files. In some cases, the option has been replaced, or the function is provided in another way. Table B-2. Restore Job Options Not Supported or Changed (page 1 of 3) Restore Options SQL/MP and Enscribe SQL/MX and OSS ALTFILE Enscribe This option is not supported.
PAGE 239
Comparison With the BACKUP and RESTORE Utilities Changed or Unsupported Restore Job Options Table B-2. Restore Job Options Not Supported or Changed (page 2 of 3) Restore Options SQL/MP and Enscribe SQL/MX and OSS MYID Enscribe For OSS, this option has been replaced by the ALLOWMYID ON option. This restores the files with the creator (ownership) information. Non super.super users can restore only the files that they own regardless of the MYID option specified.
PAGE 240
Comparison With the BACKUP and RESTORE Utilities Changed or Unsupported Restore Job Options Table B-2. Restore Job Options Not Supported or Changed (page 3 of 3) Restore Options SQL/MP and Enscribe SQL/MX and OSS REGISTERONLY SQL/MP SQL/MX does not register programs. REMOTEIOSIZE Standard This option is not supported. SQL/MX bulk I/O defaults to 56 kilobytes. RENAME Enscribe SQL/MP This option is not applicable because BRCOM does not support volume mode.
PAGE 241
Index Numbers 123 1-9 1234 1-9 A abcd 1-10 ABORT JOB command 5-3 ALLOWMYID job option 6-22 B BACKCOPY Command backcopy-job-option 5-6 backup-object-spec 5-6 config-option 5-6 dest-tape 5-6 run-option 5-6 source-tape 5-5 BACKCOPY command 5-5 Backing up all SQL/MX catalogs, example 6-46 both OSS and SQL/MX objects 6-52 delimited SQL/MX catalog, example 6-47 delimited SQL/MX schema, example 6-48 delimited SQL/MX table partition, example 6-50 delimited SQL/MX table, example 6-49 excluding SQL/MX indexes, exam
PAGE 242
C Index BRCONFIG file description of 1-3 displaying configuration information 3-1 Break key 4-6 BRIC file description of 1-4 listing contents on tape 7-7 listing contents on tape using the BRIC disk file 7-6 restoring to disk 7-6 using during restore 7-5 BRICONFRESHTAPE job option 6-22 BRJOBS file changing the volume 3-3 description of 1-3 C Catalogs description of 1-9, 6-2 SQL/MX security 1-9 supported SQL/MX object 1-9, 6-2 Changing BRJOBS volume 3-3 work volume 3-4 CLEANUP JOB command 5-8 Command ABOR
PAGE 243
E Index attribute exceptions for the RESTORE command 7-17 using with BACKUP command 4-6 DELETE JOB command 5-9 Delimiters backing up SQL/MX objects 6-12 DENTITY column 1-11 DIRECTORY job option 7-33 Displaying configuration information 3-1 configuration information for a job 3-2 configuration information in the BRCONFIG file 3-1 job status 8-1 DSM/TC description of 1-16 MEDIACOM RECOVER DISKFILE command 7-1 upgrading the catalog database 2-6 using to monitor jobs 8-1 E EMS event messages, using to monito
PAGE 244
M Index LISTALL job option 6-28, 7-37 Listing contents on tape 7-5 LISTONLY job option 7-38 LOCATION job option 7-39 PARTONLY job option 6-32, 7-42 PAUSE command 5-17 Program, exiting 4-2 R M Managing configuration information 3-1 jobs 4-5 MEDIACOM 2-6 MediaSRV 2-6 Monitoring job information 8-1 job states 8-8 Monitoring jobs using DSM/TC 8-1 using EMS event messages 8-1 MYID job option 7-40 N NEEDBOTH Job Option 6-28 O OBEY command 5-16 OBEYDDL Job Option 7-46 OPEN job option 6-29 OSS backing up 6-1
PAGE 245
S Index OSS objects excluding mountpoints 7-54 OSS objects including mountpoints 7-54 OSS objects with filtering, example 7-51 OSS objects, examples 7-50 SQL/MX indexes, example 7-65 SQL/MX objects to a different target 7-67 SQL/MX objects with filtering 7-70 SQL/MX objects, examples 7-55 SQL/MX schema, example 7-61 SQL/MX table partitions, example 7-64 SQL/MX tables, example 7-62 RUN command 4-1 Run-option exceptions for the BACKUP command 6-7 for the RESTORE command 7-18 S Schemas description of 1-9 SQ
PAGE 246
V Index V VERIFYDISK job option 7-48 VERIFYTAPE job option 6-34, 7-48 Views manually creating 1-13 unsupported SQL/MX objects 1-13 W Wild cards 6-10, 7-21 Work volume, changing 3-4 Special Characters ! command 5-1 ? command 5-2 Backup and Restore 2 Manual—522696-019 Index-6