Previous | Contents | Index |
You can change the job command list by using the VMS text editor EDT. See your VMS Manual for a complete discussion of EDT.
The command format is
$ BCKMGR EDIT JOB_NAME |
The same qualifiers are used with EDIT as with INSERT.
12.5 Looking at jobs
There are three commands for looking at particular parts of jobs:
Command | Description |
---|---|
DIRECTORY | displays information about the job on-line |
EXTRACT | extracts a list from the database and writes it to a file |
TYPE | types out the various list sections that can be associated with a job definition |
BCKMGR DIRECTORY allows you to create a line display of certain fields of the job or the full display.
The full display mode is used to display all the information about a single job by using the qualifier /FULL, in the format:
$ BCKMGR DIRECTORY JOB_NAME/FULL |
For example, to show a full display of an INCREMENTAL backup that a user has also created type:
$ BCKMGR DIRECTORY INCREMENTAL/FULL |
An example of the full BCKMGR DIRECTORY display follows:
DRIVE_1_BACKUP Comment = Incremental Backup of DRIVE_1: Username = SYSTEM Last submit = July 6, 1996, 09:01 Last completed = July 6, 1996, 23:00 Log file = Priority = 100 Flags = Media_Job,Cycle,NoHold,Keep,NoPrint Backup mode = Next media = 764 Generations = 4 Required = 4 Media type = TK50 Up count = 307 Down count = infinite Owner = [SYSTEM] Protection = S:RWED,O:RWED,G:R,W:R |
The line display mode can be used to display any of the fields associated with a job definition. You can show one or more columns of information about job definitions by specifying a qualifier or series of qualifiers for the BCKMGR DIRECTORY command, in the format:
$ BCKMGR DIRECTORY JOB_NAME/QUALIFIERS |
The job name can include VMS wildcard characters6. There is a complete list of qualifiers in the Reference Manual. An example of a line display follows:
$ BCKMGR DIRECTORY UPDATE*/COMMENT/START_TIME [BCKMGR] directory on 20-JAN-1996 12:33 UPDATE 20-JAN-1996 13:00 Daily Newsletter Update BACKUP_JOB1 20-JAN-1996 16:30 Daily Update of Backup Jobs BACKUP_JOB2 23-JAN-1996 08:00 Weekly Backup Job Printout BACKUP_JOB3 05-JAN-1996 17:30 Monthly Backup Report UPDATE99 20-DEC-1996 13:00 Upgrade Pricelist Total of 5 |
The BCKMGR TYPE command will type to the screen the command list. The command format is:
$ BCKMGR TYPE/QUALIFIER JOB_NAME |
You indicate which list associated with the job definition is to be displayed on the screen by adding a qualifier ( /COMMANDS or /MEDIA). The default qualifier is /COMMANDS.
For example, if a user wants to look at the command list of his job BACKUP_JOB1, he enters:
$ BCKMGR TYPE/COMMANDS BACKUP_JOB1 |
12.5.3 BCKMGR EXTRACT
The BCKMGR EXTRACT command is similar to the command TYPE as it types
out a list from the job definition, but the list is typed to an output
file instead of to the screen. An output file must be added to the end
of the command:
$ BCKMGR EXTRACT JOB_NAME OUTPUT_FILE_NAME |
For example, if a user wants to extract a command list from the job BACKUP_JOB1 to a command file COMFILE.COM, he types:
$ BCKMGR EXTRACT BACKUP_JOB1 COMFILE.COM |
6 The wildcard characters are an asterisk (*) and a percent sign (%) |
There are a few other BCKMGR commands that you may find useful. They are listed in the following table.
Command | Description |
---|---|
RENAME | changes the name of a job definition |
SUBMIT | submits the job for immediate execution regardless of any parameters |
DELETE | permanently removes a job definition from the database |
REBUILD | rebuilds all connections between the MEDIA and BCKMGR database |
The RENAME command changes the name of a job definition, using the format:
$ BCKMGR RENAME OLD_JOB_NAME NEW_JOB_NAME /QUALIFIERS |
The only qualifiers that can be applied are the general qualifiers /LOG and /CONFIRM. For example, to rename the job TEST to DAILY_UPDATE, type:
$ BCKMGR RENAME TEST BACKUP_JOB/LOG |
When the rename operation has successfully finished, the LOG qualifier
causes the system to issue a note to you.
12.6.2 The SUBMIT command
The SUBMIT command causes a job to be considered for immediate submission. There are two qualifiers, in addition to the general qualifiers, that can be applied to the command. They are listed in Table 12-3.
Qualifier | Description |
---|---|
/CURRENT | The job can be submitted in the context of either the current process or of the server process. During normal job submission, all of the submits are performed by the server process. See Reference Section for more detail. |
For example, if a user wants to submit BACKUP_JOB1 in the context of the current process he types:
$ BCKMGR SUBMIT BACKUP_JOB1/CURRENT |
and the job will be submitted as the current process rather than the
server process.
12.6.3 The DELETE command
The DELETE command permanently removes a job definition from the BCKMGR database, using the command format:
$ BCKMGR DELETE JOB_NAME/QUALIFIERS |
The only qualifiers that can be used with this command are LOG and
CONFIRM. It is a good idea to always use the CONFIRM qualifier with the
DELETE command so that you do not delete the wrong job due to a typing
error.
12.6.4 The REBUILD command
The BCKMGR command REBUILD reviews the media used in a job and compares the current MEDIA DATABASE with the current BCKMGR DATABASE. It rebuilds all connections between the two databases which can be useful for correcting any disparities between them. The command format is:
$ BCKMGR REBUILD JOB_NAME/QUALIFIER |
There are four special qualifiers for this command:
Qualifier | Description |
---|---|
/ADD | adds any medium mentioned in the BCKMGR database but not in the Media database to the Media database |
/MOVE | changes the ownership of all media assigned to a job to be the same as the ownership of the job |
/REMOVE | removes any medium named in the BCKMGR database but not in the Media database from the BCKMGR database |
/TRIM | returns any medium shown as NOT USED in the BCKMGR database to the available pool |
For example, if the job INCREMENTAL1 had allocated five tapes each time it ran, but only used three, you can force the job to release all the unused tapes back to the available pool by the command:
$ BCKMGR REBUILD INCREMENTAL1/TRIM |
This chapter familiarizes the user with VAULT Saveset Manager
from the DCL command line and includes the syntax and operation of the
program. It also explains how to restore selective files using a search
criteria and how to do a full disk recovery.
13.1 VAULT command syntax
VAULT commands deal only with files, not directly with media. The basic format of a VAULT command is:
$ VAULT/COMMAND [DIRECTORY_NAME]FILE_NAME/QUALIFIERS |
At the VMS prompt $, you type the keyword VAULT to invoke the VAULT program. The keyword VAULT is followed immediately by a command. The command qualifier SELECTs the VAULT function. The default command qualifier is /DIRECTORY The directory name and filename are both optional. You can specify a directory 1 and a file name.
Some examples of VAULT command syntax, using the command qualifier DIRECTORY, are:
$ VAULT/DIRECTORY $ VAULT/DIRECTORY [SALES.RESULTS] $ VAULT/DIRECTORY/DATE/COMMENT [TRANSACT.DATA]TEST.DAT;1 |
The first command will produce a listing of all of the files from your current VMS default directory that have been backed up. The second example will produce a listing of all your files that have been backed up from the directory [SALES.RESULTS]. The third command will show the file TEST.DAT from the directory [TRANSACT.DATA] and display the date and comment fields for that file. Because DIRECTORY is the default command qualifier, you can also type the last command as:
$ VAULT/DATE/COMMENT [TRANSACT.DATA]TEST.DAT;1 |
to see the same information displayed.
1 The default is the current default directory |
To restore a file, you must first determine which versions have been
backed up and decide which version you want to restore. The
VAULT/DIRECTORY command can be used to determine which of your files
are contained on the backup tapes and information about those files.
13.2.1 The VAULT/DIRECTORY command
The command format for the VAULT/DIRECTORY is:
$ VAULT/DIRECTORY/QUALIFIERS FILE_NAME |
The default command qualifier is DIRECTORY, so if you type:
$ VAULT |
you will see a display of the Vault directory listing the files that have been backed up for you from the current directory:
Vault directory DISK$SALES0:[HOSKINS.SALES] FEBSALES.DAT;1 FEBSALES.DAT;2 FEBTAX.DAT;1 FEBTAX.DAT;2 JANSALES.DAT;1 JANSALES.DAT;2 JANTAX.DAT;1 JANTAX.DAT;2 TEST1.DAT;1 TEST3.DAT;4 PLOT.FOR;2 PLOT.FOR;3 Total of 12 files |
To display a file from a directory other than the current one, you can specify the directory using its logical name. For example, if a user wants to see the files backed up from her login directory:
$ VAULT SYS$LOGIN:* Vault directory DISK$SYSTEM:[JOHNSON] LOGIN.COM;1 BATCH23.LOG;1 BATCH23.LOG;2 TEST.COM;1 LOG_NOTE.TXT;27 LOG_NOTE.TXT;28 LOG_NOTE.TXT;29 Total of 7 files |
As with the VMS DIRECTORY command, there are search qualifiers
and column qualifiers that can be applied to VAULT/DIRECTORY. The
qualifiers can include VMS wildcards in their file
specifications.
13.2.2 Search qualifiers
The search qualifiers for the VAULT/DIRECTORY command are the same as for the VMS DIRECTORY command:
Qualifier | Description |
---|---|
/SINCE=date | selects all files with a date field after this date |
/BEFORE=date | selects all files with a date field before this date |
/EXCLUDE=file_name or (file_name,file_name,...) | selects all files but those named |
The date fields2 allowed for VAULT search qualifiers include:
Qualifier | Description |
---|---|
/CREATED | the date the file was first created or added |
/EXPIRED | the date the file expired |
/MODIFIED | the date the file was last modified |
/VAULTED | the date the file was recorded in Vault |
In Table 13-1 is a list of column qualifiers for the VAULT/DIRECTORY command.
Qualifier | Description |
---|---|
/COMMENT | displays the comment field of the file header |
/DATE=field_name or = (field_name,field_name...) | selects which date fields will be displayed Some of the date fields possible: ALL, BACKUP, CREATED, EXPIRED, MODIFIED |
/FORMAT | displays the record format of the file header |
/FULL | displays a complete listing of all information about the file |
/LOCATION | displays the storage location of the file. The format of the display is: volume_set_name (saveset_name/volume_number/volume_name) |
/OWNER | displays the ownership of the file |
/PROTECTION | displays the UIC access rights for the file |
/SECURITY | displays the ownership and protection attributes of a file. This is equivalent to /OWNER/PROTECTION |
/TOTAL | suppresses all of the individual file names and displays just the total line for each directory |
The /FULL qualifier produces a display like the following: $ VAULT/FULL SALES.DAT;10 DBA0:[HOSKINS.SALES] SALES.DAT;10 Size: 130 Created: 31-OCT-1996 17:00 Owner: [ISE,HOSKINS] Revised: 23-JAN-1996 15:30 Protection: Expires: (not set) (S:RWID,O:RWID,G,W) Backup: 28-JAN-1996 17:33 Record size: 80 Vaulted: 29-FEB-1996 14:23 Record format: Sequential, variable size Note: Incremental backup Location: 5523(DBA0.BAK/2/5524) |
You can also change the characteristics of the directory display using the qualifiers listed in Table 13-2.
Qualifier | Description |
---|---|
/OUTPUT=file_name | routes the directory display into the specified file instead of to the screen |
/COLUMNS=n | specifies how many columns of file names will be displayed across the screen |
2 These dates refer to the date the original file was created, modified or expired, not to the date the backup was created. These date-fields are mutually exclusive. |
Previous | Next | Contents | Index |