.FLAGS BOLD .FLAGS BREAK .FLAGS SUBSTITUTE .STYLE HEADERS 7, 0 .PAGE SIZE 60,70 .LEFT MARGIN 0 .RIGHT MARGIN 70 .FIGURE 20 .CENTER; ^&VAX-11/780_ DISK_ BACKUP_ PROCEDURES\& .BLANK 2 .CENTER; $$MONTH $$DAY, $$YEAR .PAGE .LAYOUT 2, 2 .DISPLAY NUMBER RL .REQUIRE 'BACKUP.RNT' .SEND TOC .FIGURE 5 .PAGE .DISPLAY NUMBER D .LEFT MARGIN 0 .RIGHT MARGIN 70 .SUBTITLE .CHAPTER Introduction .PARAGRAPH This document describes the procedure for doing backups on the VAX-11/780. The procedure consists of logging into a captive command procedure account and following the steps presented by the command procedure. .HEADER LEVEL Backup Schedule .PARAGRAPH The backup command procedure implements the backup schedule suggested in the Guide to VAX/VMS System Management and Daily Operations manual. The suggested schedule is as follows: .LIST 'o' .LIST ELEMENT Daily incremental backups are performed Monday through Saturday. This backup covers the files that are created or modified each day. Six tapes are dedicated to Daily backups (marked Monday, .._. Saturday) and are re-used each week. .LIST ELEMENT Weekly incremental backups are performed on all Sundays except the first Sunday of the month. This backup covers all files that are created or modified during the previous week. Four tapes are dedicated to Weekly backups (marked Weekly_#1, .._. Weekly_#4) and are re-used each month. .LIST ELEMENT Image backups are performed on the first Sunday of each month. This backup saves the entire contents of the disk regardless of creation or modification date. .END LIST .HEADER LEVEL +1 Daily Backups .PARAGRAPH Daily incremental backups are performed on-|line and create a BACKUP save set for each disk being backed up. The save sets are named ddcu.DAY, where 'ddcu' is the device name of the disk. The save sets for all disks being backed up are written on one tape set (i.e_. the command procedure will not ask for additional tapes after the first one, however BACKUP may ask for additional tapes if all of the save sets do not fit on one tape). .HEADER LEVEL Weekly Backups .PARAGRAPH Weekly incremental backups are performed on-|line and create a BACKUP save set for each disk being backed up. The save sets are named ddcu.WEK, where 'ddcu' is the device name of the disk. The save sets for all disks being backed up are written on one tape set (i.e_. the command procedure will not ask for additional tapes after the first one, however BACKUP may ask for additional tapes if all of the save sets do not fit on one tape). .HEADER LEVEL Image Backups .PARAGRAPH Image backups create a BACKUP save set for each disk being backed up. The save sets are named ddcu.IMG, where 'ddcu' is the device name of the disk. A new tape set is started for the save set of each disk being backed up (i.e_. the command procedure will ask for a new tape before starting each disk, and BACKUP may ask for additional tapes if the save set does not fit on one tape). .PARAGRAPH Image backups are performed with no other users on the system. The system disk (SYS_$SYSDEVICE) is backed up last using stand-|alone BACKUP. All other disks are backed up on-|line. .HEADER LEVEL -1 Features .PARAGRAPH The backup command procedure can type a file on the system console to relay special instructions for the backup procedure. These special instructions could be to override either the type of backup to perform, the list of disks to be backed up, or the backup date for a Weekly backup. .PARAGRAPH The default list of disks to be backed up can be either all disks on the system, a restricted group of disks or an explicit list of disks. .PARAGRAPH The tape device to be used can be selected from any on the system, with preference given to certain types of tape drives or particular individual drives. .PARAGRAPH The recording density used can be specified explicitly or the command procedure can select the highest density that the allocated tape drive supports. .PARAGRAPH For Image backups, the backup command procedure will force users to logout, if necessary, to insure a complete backup of the disks. Before an image backup of the system disk the command procedure instructs the operator how to boot Stand-|alone BACKUP, what command to use to backup the system disk, and how to re-|boot VAX/VMS, before performing a system shutdown. .PARAGRAPH The BACKUP commands issued by the command procedure create a BACKUP journal file which can be used to locate files to be restored. The command procedure also maintains a log of the backups that are performed. Log file entries record the type of backup performed, the date and time of the backup, the list of disks that were backed up, and the backup date for Weekly backups. .CHAPTER Backup Procedure .PARAGRAPH The backup command procedure interacts with the user either by telling the user to perform a function, or by requesting information from the user before proceeding. Prompts requesting information are of the form .SKIP 1 .LEFT MARGIN +8 "text [default]" .LEFT MARGIN -8 .SKIP 1 where 'text' tells you what information is being requested and 'default' is an answer that can be selected just by pressing the key. The defaults always reflect the normal backup schedule. ^*The default answer should only be overridden by special instructions.\* When it is necessary, the defaults presented can be overridden simply by typing a new answer before pressing the key. .PARAGRAPH The following sections describe the steps to be performed. .HEADER LEVEL Login .PARAGRAPH Login on the system console: 1) press the key; 2) at the "Username:" prompt type "BACKUP" and press the key; 3) at the "Password:" prompt type the password and press the key (the password will not print). This will invoke the backup command procedure. If there are any special instructions the command procedure will type them on the console now. .PARAGRAPH On any terminal other than the system console the message .SKIP 1 .LEFT MARGIN +8 "This command procedure must be executed from the system console" .LEFT MARGIN -8 .SKIP 1 will be printed and the command procedure will logout. .HEADER LEVEL Backup Type .PARAGRAPH The first prompt, .SKIP 1 .LEFT MARGIN +8 "BACKUP Type_: DAILY, WEEKLY or IMAGE []", .LEFT MARGIN -8 .SKIP 1 asks what type of backup to perform; Daily incremental, Weekly incremental, or Image backup. The default, , is determined by the command procedure based on the current date and will be either "DAILY", "WEEKLY", or "IMAGE". If, when overriding the default, an invalid backup type is entered the message .SKIP 1 .LEFT MARGIN +8 "Please enter DAILY, WEEKLY or IMAGE or press " .LEFT MARGIN -8 .SKIP 1 will be printed and the prompt will be repeated. .HEADER LEVEL Disks To Be Backed Up .PARAGRAPH The command procedure asks which disks are to be backed up with the prompt .SKIP 1 .LEFT MARGIN +8 "List of disks to BACKUP [<__ddcu:, __ddcu:, ...>]". .LEFT MARGIN -8 .SKIP 1 The disks are backed up in the order specified (except for Image backups where the system disk is backed up last). The default is determined by the command procedure. If, when overriding the default, an invalid device name is entered one of the following messages will be printed: .list "o" .le; "Device __ddcu_: does not exist" .le; "Device __ddcu_: is not a disk" .le; "Device __ddcu_: is not mounted" .le; "Device __ddcu_: is mounted foreign" .end list where '__ddcu:' is the invalid device name. The prompt will be repeated. .HEADER LEVEL Date To Backup From .PARAGRAPH For Weekly backups, the prompt .SKIP 1 .LEFT MARGIN +8 "Weekly BACKUP /SINCE=Date []", .LEFT MARGIN -8 .SKIP 1 asks for the date to backup from. All files created or modified since this date will be backed up. The date can be entered in any of the standard VMS date/|time formats. The default date, , is determined by the command procedure and is the date of Sunday of the previous week. If, when overriding the default, an invalid date is entered the message .SKIP 1 .LEFT MARGIN +8 "Invalid date - use DD-MMM-YYYY format (e.g_. 15-APR-1955)" .LEFT MARGIN -8 .SKIP 1 will be printed and the prompt will be repeated. .HEADER LEVEL Logout Users .PARAGRAPH Because Image backups are performed with no users on the system, if an Image backup is being performed the message .SKIP 1 .LEFT MARGIN +8 "Let's give the users time to clean up and get off" .LEFT MARGIN -8 .SKIP 1 is printed and a command procedure is executed to logout any users. The users are given 10 minutes notice and are asked to logout. Periodic reminders are given until the 10 minutes are up at which point the users are logged off. The backup command procedure then continues with the message .SKIP 1 .LEFT MARGIN +8 "BACKUP procedure continuing". .LEFT MARGIN -8 .HEADER LEVEL Mount Tape On Drive .PARAGRAPH The command procedure next allocates a tape drive for backup tape media. The command procedure asks that you physically mount a tape on the allocated tape drive with one of the following prompts: .LIST 'o' .LIST ELEMENT "Mount tape marked on drive __mtcu:, press when done" for a Daily backup. .LIST ELEMENT "Mount tape marked WEEKLY_# on drive __mtcu:, press when done" for a Weekly backup. .LIST ELEMENT "Mount a scratch tape on drive __mtcu:, press when done" for an Image backup. .END LIST where is MONDAY, TUESDAY, etc., '__mtcu:' is the tape drive that the command procedure has allocated, and 'n' is a number 1 through 4. During an Image backup, this step and the next are repeated for each disk. .PARAGRAPH If no tape drive is available the message .SKIP 1 .LEFT MARGIN +8 "Tape device not currently available" .LEFT MARGIN -8 .SKIP 1 is printed and the command procedure logs off. The backup command procedure should be re-executed when a tape drive is free. .HEADER LEVEL Label The Tape .PARAGRAPH After the tape has been physically mounted the command procedure will initialize and logically mount the tape. It will then print the following information for tape identification: .SKIP 1 .LEFT MARGIN +8 .TEST PAGE 8 .LITERAL Label the BACKUP tape with the following information: Date = dd-mmm-yyyy Label = yymmdd Density = density Node = node Format = BACKUP Contents: DAILY INCREMENTAL BACKUP OF _ddcu:, _ddcu:, ... or WEEKLY INCREMENTAL BACKUP OF _ddcu:, _ddcu:, ... or IMAGE BACKUP OF _ddcu: .END LITERAL .LEFT MARGIN -8 .SKIP 1 where 'dd-mmm-yyyy' is the current date, 'yymmdd' is the year, month, and day of the current date in numeric form, 'density' is the density that the tape was recorded at, 'node' is the DECnet node name (if any), and '__ddcu:, __ddcu:, ...' or '__ddcu:' are the disk(s) being backed up. .HEADER LEVEL BACKUP Command .PARAGRAPH At this point the command procedure will proceed with the BACKUP command(s) to backup the disk(s). Each BACKUP command is of one of the following forms: .SKIP 1 .LEFT MARGIN +8 .TEST PAGE 4 .LITERAL Daily: $ BACKUP/FAST/RECORD/VERIFY - /JOURNAL=SYS$MANAGER:BACKUP.BJL - _ddcu:[*...]/SINCE=BACKUP - _mtcu:ddcu.DAY/PROTECTION .END LITERAL .LEFT MARGIN -8 .SKIP 1 .LEFT MARGIN +8 .TEST PAGE 4 .LITERAL Weekly: $ BACKUP/FAST/RECORD/VERIFY - /JOURNAL=SYS$MANAGER:BACKUP.BJL - _ddcu:[*...]/SINCE="date" - _mtcu:ddcu.WEK/PROTECTION .END LITERAL .LEFT MARGIN -8 .SKIP 1 .LEFT MARGIN +8 .TEST PAGE 5 .LITERAL Image: $ BACKUP/IMAGE/RECORD/VERIFY - /JOURNAL=SYS$MANAGER:BACKUP.BJL - /LIST=SYS$MANAGER:BACKUP.LIS - _ddcu: - _mtcu:ddcu.IMG/PROTECTION .END LITERAL .LEFT MARGIN -8 .SKIP 1 where '__ddcu:' is the disk being backed up, '__mtcu:' is the tape drive being used, and 'date' is the backup date selected for Weekly backups. During an Image backup, this step is repeated for each disk except the system disk. .HEADER LEVEL Additional Tapes .PARAGRAPH If a save set does not fit on one tape the BACKUP utility will ask for additional tapes. Requests for additional tapes are of the form .SKIP 1 .TEST PAGE 3 .LEFT MARGIN +8 .BREAK; %BACKUP-I-RESUME, resuming operation on volume 'n' .BREAK; %BACKUP-I-READYWRITE, mount volume 'n' on __mtcu_: for writing .BREAK; Respond with YES when ready: .LEFT MARGIN -8 .SKIP 1 and should be satisfied by physically mounting a scratch tape, entering "YES" and pressing the key. Additional tapes should be labeled with the same information as the first tape in the save set (see section 2.7). .HEADER LEVEL Logging Out/System Shutdown .PARAGRAPH When the backup command procedure is finished doing a Daily or Weekly backup it will automatically logout. .PARAGRAPH If an Image backup is being performed the backup command procedure will either reboot or shutdown the system. If the system disk was not selected to be backed up then the command procedure will print the message .SKIP 1 .LEFT MARGIN +8 "The system will now be rebooted" .LEFT MARGIN -8 .SKIP 1 and reboot the system. .PARAGRAPH If the system disk is to be backed up, which is the normal procedure, then the command procedure will issue the following information/|instructions: .SKIP 1 .TEST PAGE 37 .LITERAL ****************************************************************************** ** ** ** The system will now be shut down for a Stand-alone BACKUP of the ** ** system disk. When the message ** ** ** ** "SYSTEM SHUTDOWN COMPLETE - USE CONSOLE TO HALT SYSTEM" ** ** ** ** appears, reboot with the commands: ** ** ** ** ^P ! Press the "P" key while holding down the "CTRL" key ** ** ** ** >>>HALT ** ** ** ** >>>BOOT STB ** ** ** ** When Stand-alone BACKUP has been booted it will identify itself ** ** with the message ** ** ** ** %BACKUP-I-IDENT, Stand-alone BACKUP Vx.y; the date is ** ** dd-mmm-yyyy hh:mm:ss.cc ** ** ** ** and issue a "$" prompt. Then, make sure that the line printer is ** ** on-line and backup the system disk with the command: ** ** ** ** $ BACKUP/IMAGE/RECORD/VERIFY/LIST=LPA0: _ddcu: _mtcu:ddcu.IMG/PROTECTION ** ** ** ** When Stand-alone BACKUP has completed backing up the system disk it ** ** will identify itself as before. Now perform a Top-of-Form on the line ** ** printer and reboot the system with the commands: ** ** ** ** ^P ! Press the "P" key while holding down the "CTRL" key ** ** ** ** >>>HALT ** ** ** ** >>>BOOT ** ** ** ****************************************************************************** .END LITERAL .SKIP 1 where '__ddcu:' is the system disk and '__mtcu:' is the tape drive being used. At this point the backup command procedure will either reboot or shutdown the system. .CHAPTER VAX/VMS System Messages .PARAGRAPH This chapter covers messages not specifically discussed in the previous chapter that will be seen during a backup session, and explains the recovery actions possible when the BACKUP utility encounters a fatal error. .HEADER LEVEL Format of System Messages .PARAGRAPH Most of the messages displayed by the VAX/VMS operating system have the following format: .SKIP 1 .LEFT MARGIN +8 %FACILITY-L-IDENT, Text .LEFT MARGIN -8 .SKIP 1 'FACILITY' is a VAX/VMS facility or component name; in general the DCL command that issued the message. 'L' is a severity level indicator with one of the following values: .SKIP 1 .LEFT MARGIN +8 .TEST PAGE 5 .BREAK; S - Success .BREAK; I - Information .BREAK; W - Warning .BREAK; E - Error .BREAK; F - Fatal, or severe error .LEFT MARGIN -8 .SKIP 1 'IDENT' is an abbreviation of the message text. 'Text' is the explanation of the message. .PARAGRAPH Here are some examples of VAX/VMS system messages that will be seen during a backup session: .SKIP 1 .LEFT MARGIN +8 %DCL-I-ALLOC, __mtcu_: allocated .SKIP 1 %MOUNT-I-MOUNTED, mounted on __mtcu_: .SKIP 1 %BACKUP-I-STARTVERIFY, starting verification pass .SKIP 1 %BACKUP-I-STARTRECORD, starting backup date recording pass .LEFT MARGIN -8 .HEADER LEVEL +1 Severity Levels .PARAGRAPH The severity level of a message helps determine what action, if any, must be taken in response to the message. Success and informational messages inform you that the system has performed the requested action. In some cases, the command processing continues after issuing a success message. In other cases, the message indicates that the command processing is complete. .PARAGRAPH Warning messages indicate that the command may have performed some, but not all, of the actions requested, and that you may have to verify the command or program input. .PARAGRAPH Error messages indicate the the output or program result is incorrect, but the system may attempt to continue execution. .PARAGRAPH Fatal messages indicate that the system cannot continue execution of the request. .HEADER LEVEL Linked Messages .PARAGRAPH Frequently, a system message will appear with more than one message. When more than one message is issued, subsequent messages are prefixed with a hyphen (-) rather than a percent sign (%). A series of messages can help you determine the location of an error. Linked messages usually display the return status of the different facilities called and provide a detailed explanation of the error. .PARAGRAPH For example, the BACKUP utility calls operating system services to open a file. If the file is in use, the BACKUP utility displays a message indicating that it cannot open the file; a SYSTEM message follows, indicating the reason. .SKIP 1 .LEFT MARGIN +8 .TEST PAGE 2 .BREAK; %BACKUP-E-OPENIN, error opening as input .BREAK; -SYSTEM-W-ACCONFLICT, file access conflict .LEFT MARGIN -8 .HEADER LEVEL -1 BACKUP-I-SPECIFY Message .PARAGRAPH When the BACKUP utility encounters a fatal error, it issues the message .SKIP 1 .LEFT MARGIN +8 .TEST PAGE 2 .BREAK; %BACKUP-I-SPECIFY, specify option .BREAK; BACKUP> .LEFT MARGIN -8 .SKIP 1 where is a list of two or more of the recovery options CONTINUE, RESTART or QUIT and 'BACKUP>' is a prompt for one of these recovery actions. If the CONTINUE option is selected, BACKUP ignores the error and continues processing as if the error never occurred. If the RESTART option is selected, BACKUP restarts the operation at the beginning of the current save-|set volume. If the QUIT option is selected, the backup operation terminates. The option to choose will have to be determined from the preceding error messages. .PARAGRAPH The CONTINUE option should only be used if the magnetic tape positioning has not changed since the original error and the error does not imply that data has already been lost. For example, the offline button has accidently been hit. BACKUP detects that the magnetic tape has gone offline and issues the BACKUP-|I-|SPECIFY message. If the drive is placed back online and the CONTINUE option is specified, BACKUP then resumes the save operation from where it left off. .PARAGRAPH If you select the RESTART option in response to a BACKUP-|I-|SPECIFY prompt, a new magnetic tape must be mounted. After the new magnetic tape is mounted, BACKUP restarts the save operation from where it was when the original reel was mounted. For example, if an excessive error rate occurs on volume 3 of a magnetic tape save set and you specify RESTART after the BACKUP-|I-|SPECIFY message, the save operation restarts at the beginning of the new volume 3; no data is lost. .CHAPTER Implementation Details .PARAGRAPH This chapter describes, in more detail, the operation of some of the features provided by the backup command procedure. .HEADER LEVEL Special Instructions File The file SYS_$MANAGER:|BACKUP.TXT is used to relay special instructions for the backup procedure. Special instructions are given to the user at the start of the command procedure. If the file exists, the command procedure will check the expiration date of the highest version of the file. If the expiration date has passed, SYS_$MANAGER:|BACKUP.TXT will be appended to SYS_$MANAGER:|OLDBACKUP.TXT (creating it if necessary) and then deleted. The checks for file existence and expiration date will then be repeated until either no version of the file exists, a version of the file exists which has an expiration date in the future, or a version of the file exists that has no expiration date. If the file exists the command procedure will then type it on the console. .HEADER LEVEL Logout Users .PARAGRAPH For Image backups, the command procedure will force users to logout, if necessary, to insure a complete backup of the disks. This is done using a command procedure derived from SYS_$SYSTEM:|SHUTDOWN.COM which stops all user processes (except the backup process), DECnet, and all batch and print queues. .HEADER LEVEL Disks to be Backed Up .PARAGRAPH The default list of disks to be backed up can be either all disks on the system, a restricted group of disks or an explicit list of disks. If an explicit list of disks is specified it is used as the default list of disks. If an explicit list of disks is not specified the SHOW DEVICES command is used to find all the mounted disks. A parameter can be specified for the SHOW DEVICES command to restrict the devices it will select. .HEADER LEVEL Tape Drive Selected .PARAGRAPH The tape device to be used can be selected from any on the system, with preference given to certain types of tape drives or particular individual drives. The choice of tape drive can be tailored by means of a parameter supplied to the ALLOCATE command. .HEADER LEVEL Tape Density .PARAGRAPH The command procedure will initialize the backup tapes at either an explicitly specified density, or the highest density that the allocated tape drive supports. If an explicitly specified density is not supported by the allocated tape drive the specified density is minimized with the drive's maximum density and maximized with the drive's minimum density. .HEADER LEVEL Journal File .PARAGRAPH All of the BACKUP commands that the command procedure issues (except for the command to do the Image backup of the system disk) include a /JOURNAL=|SYS_$MANAGER:|BACKUP.BJL qualifier. Before each set of Image backups the old journal file is renamed SYS_$MANAGER:|OLDBACKUP.BJL and purged, and a new journal file is started. The journal file can be used to locate the last backup of a file so that it can be restored. .HEADER LEVEL Log File .PARAGRAPH The command procedure maintains a log of the backups that are performed. Log file entries are of the form .SKIP 1 .LEFT MARGIN +8 BACKUP ON OF [SINCE ] .LEFT MARGIN -8 .SKIP 1 where is the type of backup performed, is the date and time of the backup, is the list of disks that were backed up, and is the Weekly backup date. "SINCE " appears only for Weekly incremental backups. .HEADER LEVEL System Disk Image Backup .PARAGRAPH Before an image backup of the system disk the command procedure instructs the operator how to boot Stand-|alone BACKUP, what command to use to backup the system disk, and how to re-|boot VAX/VMS, before performing a system shutdown using SYS_$SYSTEM:|SHUTDOWN.COM.