![[Digital logo]](../../IMAGES/DIGITAL-LOGO.GIF){kind=logo}
![[HR]](../../IMAGES/REDBAR.GIF)
Note that when you set this variable, Digital recommends that you set
the operating system boot parameters as well, using the SET
BOOT_OSFLAGS command.
A.2.2.1 Setting the Boot Device
At the console prompt (>>>), enter the SET BOOTDEF_DEV command in the following format:
SET BOOTDEF_DEV device-name
Substitute the device name of the system disk for device-name. For example, to boot from a drive with a device name of DKA400 on a DEC 3000 Alpha series computer, enter the following command and press the Return key:
>>> SET BOOTDEF_DEV DKA400
The next time you boot the system, you can enter the BOOT command without specifying a device name (because DKA400 is now the default boot device). For example:
>>> BOOT
Note: If you have not used the SET BOOTDEF_DEV
command to set the drive to boot from and you enter the BOOT command
without specifying a device name, the system displays an error message.
A.2.2.2 Showing the Boot Device
Use the SHOW BOOTDEF_DEV command to find out what drive was specified in the last SET BOOT command. For example:
>>> SHOW BOOTDEF_DEV
To cancel the drive specified in a previous SET BOOTDEF_DEV command, enter the following command and press the Return key:
>>> SET BOOTDEF_DEV
Note: This command is not valid on DEC 3000
Alpha series systems.
A.2.3 Setting Boot Parameters
By default, when you boot the operating system, the flags parameter is
set to 0. If you want to define parameters to enable specific functions
during the booting process, use the SET BOOT_OSFLAGS console command.
A.2.3.1 List of Valid Parameters
The following is a list of values you can specify with the SET BOOT_OSFLAGS command:
| Hexadecimal Value | System Response |
|---|---|
| 1 | Allows a conversational boot (the system displays the SYSBOOT> prompt). |
| 2 | Maps XDELTA to a running system. |
| 4 | Stops the boot procedure at the initial system breakpoint. |
| 8 | Performs a diagnostic bootstrap. |
| 10 | Stops the boot procedure at the bootstrap breakpoints. |
| 20 | Omits header from secondary bootstrap image. |
| 80 | Prompts for the name of the secondary bootstrap file. |
| 100 | Halts the system before the secondary bootstrap. |
| 2000 | Marks corrected read data error pages as bad. |
| 10000 | Displays extensive, detailed debug messages during the boot process. |
| 20000 | Displays selected user-oriented messages during the boot process. |
The following examples show how to use the SET BOOT_OSFLAGS command:
>>> SET BOOT_OSFLAGS 0,1
>>> SET BOOT_OSFLAGS 1,0
>>> SET BOOT_OSFLAGS 0,20007
To display the parameters you have just set, use the SHOW BOOT_OSFLAGS command. For example:
>>> SHOW BOOT_OSFLAGS BOOT_OSFLAGS = 0,20007
The Writeboot utility (WRITEBOOT.EXE) is copied to your system disk during the installation procedure. It allows you to create a bootable OpenVMS Alpha system disk from one that was originally created by one of the following methods:
The Writeboot utility also allows you to rewrite the boot block of an OpenVMS Alpha system disk to point to a new version of the OpenVMS Alpha primary bootstrap file (APB.EXE) that you have previously copied to the disk. (Note that the file must be contiguous.)
To invoke the Writeboot utility, enter the following command:
$ RUN SYS$SYSTEM:WRITEBOOT
The utility prompts you as follows:
Update VAX portion of boot block (default is Y): Update Alpha portion of boot block (default is Y):
Answer N (No) to the VAX prompt. If you answer Y (Yes) to update the Alpha boot block, the utility prompts you for the Alpha boot file:
Enter Alpha boot file:
Specify device-name:[VMS$COMMON.SYSEXE]APB.EXE in response to
this prompt, where device-name: indicates the device on which
the system disk is mounted.
A.3 Halt and Shutdown Operations
The following sections describe halt and shutdown operations for Alpha
computers.
A.3.1 Halting the System
During installation, upgrade, and related system operations, you might need to halt your system. The methods for halting Alpha computers differ slightly with certain models, as described in the next section.
The following table summarizes the ways you can halt specific Alpha computers:
| Alpha Computer | How to Halt |
|---|---|
| AlphaServer 1000, 2000, 2100 series |
Do one of the following:
|
| AlphaServer 8200, 8400 series | Press Ctrl/P. |
| AlphaStation 200, 400, 600 series |
Do one of the following:
|
| DEC 2000, 3000 series |
Do one of the following:
|
| DEC 4000 series |
Do one of the following:
|
| DEC 7000, 10000 series | Press Ctrl/P. |
Before you shut down the operating system, decide if you want it to reboot automatically or if you want to enter console-mode commands after the shutdown completes.
You can perform the following three types of shutdown operations:
If you want the system to reboot automatically after the shutdown, see
Section A.2.1.
A.3.2.1 Orderly Shutdown
The SHUTDOWN.COM procedure shuts down the system while performing maintenance functions such as disabling future logins, stopping the batch and printer queues, dismounting volumes, and stopping user processes. To use the SHUTDOWN.COM command procedure, log in to the SYSTEM account, enter the following command, and press the Return key:
$ @SYS$SYSTEM:SHUTDOWN
For more information about the SHUTDOWN.COM command procedure, see the
OpenVMS System Manager's Manual.
A.3.2.2 Emergency Shutdown with OPCCRASH.EXE
If you cannot perform an orderly shutdown with the SHUTDOWN.COM procedure, run the OPCCRASH.EXE emergency shutdown program. To run the OPCCRASH.EXE program, log in to the SYSTEM account, enter the following command, and press the Return key:
$ RUN SYS$SYSTEM:OPCCRASH
For more information about the OPCCRASH program, see the OpenVMS System Manager's Manual.
A.3.2.3 Emergency Shutdown with Crash Commands
Use crash commands only if the system is "hung" (stops responding to any commands) and you cannot log in to the SYSTEM account to use the SHUTDOWN.COM procedure or the OPCCRASH.EXE program.
Note: The method described here works on all Alpha computers. However, on certain systems, you can force your processor to fail (crash) by entering a specific console command. See the hardware manuals that came with your computer for that information.
To force your processor to fail, do the following:
>>> E -N F R0 >>> E PS
>>> D PC FFFFFFFF00000000 >>> D PS 1F00
>>> CONTINUE
$ ANALYZE/CRASH SYS$SYSTEM:SYSDUMP.DMP SDA> SHOW CRASH
The following sections describe procedures that you can follow if you
encounter problems with your system.
A.4.1 If the System Does Not Boot
If the system does not boot because a hardware problem occurs, a
question mark (?) usually precedes the error message displayed on the
console terminal. An example of a hardware problem is a read error on a
disk or tape cartridge drive.
A.4.1.1 For Hardware Problems
If you suspect a hardware problem, do the following:
When the operating system is loaded into memory, a message similar to the following appears on the terminal screen:
SYSTEM job terminated at 19-DEC-1996 15:05:03.17
If the system does not display this message, a software problem has probably occurred. Do the following:
If your system exhibits unexpected behavior, note the following:
To determine if the failure is a system problem, do the following:
If you determine that you have a system problem, do the following:
This appendix describes how to perform backup and restore operations on the system disk. You perform these tasks by entering commands from a specialized backup environment. You access this environment through the menu that is displayed when you boot the OpenVMS Alpha operating system CD--ROM or through an alternate method that does not require the CD--ROM.
This specialized backup environment is required because it allows you to create an exact copy of the system disk. You cannot create an exact copy in a standard operating system environment because the OpenVMS Backup utility saves only what is on the disk at the moment the BACKUP command is executing, excluding portions of open files contained in memory or data about files not yet written back to the disk (cache).
For more information about backup operations, including procedures for
backing up and restoring files and directories, see the OpenVMS System Manager's Manual.
B.1.1 Reasons for Backing Up the System Disk
The primary reason why you should have a backup copy of the system disk is so you can fully restore your system in response to any hardware or software problem that affects the integrity of your original system disk or your ability to access it. For example, you would need to use the backup copy to restore your system under the following conditions:
Another reason for backing up the system disk is to eliminate disk
fragmentation, which occurs when files are stored noncontiguously on
the disk. The BACKUP/IMAGE command creates a copy on which files are
stored contiguously.
B.1.2 Suggested Procedures
Digital recommends the following:
If any nodes except the node used to run BACKUP are booted during the backup operations described in this appendix, your cluster will become partitioned, where nodes in the existing cluster divide into two or more independent clusters. This condition can cause data file corruption.
In addition, these backup environments do not restrict your use of DCL
commands to the BACKUP command only, which further increases your risk
of accidentally destroying or corrupting data on a disk. Therefore, to
avoid jeopardizing the integrity of your data in any way, Digital
recommends that you shut down the entire OpenVMS Cluster system before
you back up your system disk.
B.2 Backing Up the System Disk
The following sections describe how to back up the system disk.
B.2.1 Getting Started
Before you back up the system disk, do the following:
****************************************************************
You can install or upgrade the OpenVMS Alpha operating system.
You can also execute DCL commands and procedures to perform
"standalone" tasks, such as backing up the system disk.
Please choose one of the following:
1) Install or upgrade OpenVMS Alpha Version V7.1
2) Display products that this procedure can install
3) Install or upgrade layered products
4) Show installed products
5) Reconfigure installed products
6) Remove installed products
7) Execute DCL commands and procedures
8) Shut down this system
Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/?) 7
When you have determined which devices will be the source drive and target drive, mount those devices (and any other output devices you plan to use) before you perform any backup operations. Enter the MOUNT commands in the following format:
$$$ MOUNT/OVERRIDE=IDENTIFICATION source-drive $$$ MOUNT/FOREIGN target-drive
Note the following conventions:
When the system disk and output devices are mounted, back up the system disk by entering the BACKUP command in the following format:
$$$ BACKUP/IMAGE/VERIFY source-drive: target-drive:
(You must also include the save set name and the /SAVE_SET qualifier if
the target drive is a tape device.)
B.2.4 Examples
In this example the system disk and a target disk are mounted so the BACKUP command can create a backup disk. (You can use a backup disk as a system disk.)
$$$ MOUNT/OVERRIDE=IDENTIFICATION DKA200 $$$ MOUNT/FOREIGN DKA300 $$$ BACKUP/IMAGE/VERIFY DKA200: DKA300:
In this example the system disk and a target tape device are mounted so the BACKUP command can create a backup tape.
$$$ MOUNT/OVERRIDE=IDENTIFICATION DKA200 $$$ MOUNT/FOREIGN MKA300 $$$ BACKUP/IMAGE/VERIFY DKA200: MKA300:APR_06_BACKUP.BCK/SAVE_SET
The BACKUP command creates a system disk that includes a set of volume parameters provided by Digital, including a CLUSTER_SIZE (disk access scheme) that is appropriate for your system. (The CLUSTER_SIZE refers to the way files are stored on the disk, not to cluster environments.) You can change most volume parameters later with the SET VOLUME command.
However, to change the CLUSTER_SIZE, you must back up the system disk
to a disk that has been previously initialized with the CLUSTER_SIZE
that you want. For more information about initializing a disk and using
the BACKUP command, see the OpenVMS System Manager's Manual and the OpenVMS System Management Utilities Reference Manual, and
see the description of the INITIALIZE and BACKUP commands in the
OpenVMS DCL Dictionary.
B.2.6 What to Do Next
After you complete the backup operation, do the following:
The following sections describe how to restore the system disk.
B.3.1 Getting Started
Before you can restore the system disk, you must do the following:
****************************************************************
You can install or upgrade the OpenVMS Alpha operating system.
You can also execute DCL commands and procedures to perform
"standalone" tasks, such as backing up the system disk.
Please choose one of the following:
1) Install or upgrade OpenVMS Alpha Version V7.1
2) Display products that this procedure can install
3) Install or upgrade layered products
4) Show installed products
5) Reconfigure installed products
6) Remove installed products
7) Execute DCL commands and procedures
8) Shut down this system
Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/?) 7
When you have determined which devices will be the source drive and target drive, mount those devices (and any other output devices you plan to use) before you perform any restore operations. Enter the MOUNT commands in the following format:
$$$ MOUNT/OVERRIDE=IDENTIFICATION source-drive $$$ MOUNT/FOREIGN target-drive
Note the following conventions:
Enter the BACKUP command in the following format:
$$$ BACKUP/IMAGE/VERIFY source-drive: target-drive:
(You must also include the save set name and the /SAVE_SET qualifier if
the source drive is a tape device.)
B.3.4 Examples
In this example a backup disk and a target disk are mounted so the BACKUP command can restore the system disk from the backup disk:
$$$ MOUNT/OVERRIDE=IDENTIFICATION DKA300 $$$ MOUNT/FOREIGN DKA200 $$$ BACKUP/IMAGE/VERIFY DKA300: DKA200:
In this example a backup tape and a target disk are mounted so the BACKUP command can restore the system disk from the backup tape:
$$$ MOUNT/FOREIGN MKA300 $$$ MOUNT/FOREIGN DKA200 $$$ BACKUP/IMAGE/VERIFY MKA300:APR_06_BACKUP.BCK/SAVE_SET DKA200:
After you complete the restore operation, do the following:
This section describes an alternate method of performing backup and restore operations on your system disk. With this method, you install the operating system (without options) on another disk and perform your backup and restore operations on the system disk from there. Use this method under the following conditions:
6486P008.HTM OSSG Documentation 6-DEC-1996 10:35:19.52
Copyright © Digital Equipment Corporation 1996. All Rights Reserved.