Backing up your system disk is critical for the following
reasons:
A system disk could become inoperable
if a problem occurs during a software upgrade, update, or installation. Before you
attempt any of these operations, back up the system disk. If a problem
occurs, you can restore the backup copy of the system disk.
System files could inadvertently be deleted. After you
install, upgrade, or update the operating system or any other software
products, back up the system disk. If a system file is deleted,
you can restore the backup copy and continue to use the system.
The drive that holds the system disk could malfunction.
If you have a backup copy of the operating system and your other
software, you can restore it to a functioning disk and continue
to use the system.
Disk fragmentation could occur if files are stored
noncontiguously on the disk. Perform an image backup of the system
disk to a magnetic tape or another disk and then restore the files
to the original system disk. This restores the system disk and contiguously
stores files. You can also eliminate fragmentation by performing
a disk-to-disk image backup without using the /SAVE_SET qualifier.
This creates a functionally equivalent copy of the entire system
disk, on which files are stored contiguously. (See
Backing Up the System Disk to a Disk.)
If you have access to the OpenVMS Alpha or VAX operating system
distribution compact disc, back up your system using the menu system
provided on the disc. For more information about using the menu
system, see
Starting the Menu System.
If you use the menu system to back up large system disks
on low memory VAX systems (those with less than 32 MB of memory),
BACKUP might need to page and thereby cause the operation to fail.
If this problem occurs, use standalone BACKUP to back up system
disks on VAX systems.
If you do not have access to the OpenVMS VAX operating system
distribution compact disc, use standalone BACKUP to back up and
restore your system disk. For more information about standalone
BACKUP, see
Understanding Standalone BACKUP (VAX Only).
Starting
the Menu System Use the menu system in this section to back up or restore
system disks and user disks if you have access to the OpenVMS Alpha
or VAX Version operating system distribution compact disc.
If the operating
system is not running, go to step 2. If the operating system is running, log in to the SYSTEM account.
Enter the following command and press Return:
$ @SYS$SYSTEM:SHUTDOWN
Answer the questions. When the procedure asks if an automatic
system boot should be performed, press Return for NO. When the procedure
is finished, it displays the following message:
SYSTEM SHUTDOWN COMPLETE
On VAX systems, the following message is also displayed:
USE CONSOLE TO HALT SYSTEM
Halt the system if you see this message.
Boot the system:
On OpenVMS Alpha systems, boot the
distribution compact disc.
On OpenVMS VAX systems, boot the distribution compact
disc from the SYS1 directory.
The boot command you use for your computer depends on
the type of system you have. For more information about booting
your system, see the installation and operations supplement for
your computer.
When the system boots, it displays a menu. Choose
the menu item that allows you to execute DCL commands and procedures.
Understanding
Standalone BACKUP (VAX Only) The Backup utility (BACKUP) does not copy open files (for
example, accounting files or operator log files). For this reason
you should use standalone BACKUP (VAX only) or the menu system (if
your configuration permits) to back up your system disk. You can
boot standalone BACKUP into the main memory of your computer (while
the operating system is shut down) and use a subset of BACKUP command
qualifiers to perform a complete backup of every file
on the system disk. Standalone BACKUP is supported only for OpenVMS
VAX installations and for backing up and restoring your system disk.
Valid Standalone BACKUP Qualifiers lists the qualifiers that
you can use with standalone BACKUP.
Table 10 Valid Standalone BACKUP Qualifiers
Type
Qualifier
Default
Command Qualifiers
/BRIEF
/BRIEF
/COMPARE
None
/FULL
/BRIEF
/IMAGE
/IMAGE
/[NO]INITIALIZE
Refer to the HP OpenVMS System Management Utilities Reference Manual
/LIST[=file-spec]
Refer to the HP OpenVMS System Management Utilities Reference Manual
/[NO]LOG
/NOLOG
/PHYSICAL
None
/RECORD
None
/[NO]TRUNCATE
/NOTRUNCATE
/VERIFY
None
/VOLUME=n
None
Input Save-Set Qualifiers
/[NO]CRC
/CRC
/[NO]REWIND
/NOREWIND
/SAVE_SET
None
Output Save-Set Qualifiers
/BLOCK_SIZE=n
Refer to the HP OpenVMS System Management Utilities Reference Manual
/BY_OWNER=uic
Refer to the HP OpenVMS System Management Utilities Reference Manual
/COMMENT=string
None
/[NO]CRC
/CRC
/DENSITY=n
Refer to the HP OpenVMS System Management Utilities Reference Manual
/[NO]EXACT_ORDER
/NOEXACT_ORDER
/GROUP_SIZE=n
/GROUP_SIZE=10
/LABEL=(string[,...])
Refer to the HP OpenVMS System Management Utilities Reference Manual
/PROTECTION[=(code)]
Refer to the HP OpenVMS System Management Utilities Reference Manual
/[NO]REWIND
/NOREWIND
/SAVE_SET
None
/TAPE_EXPIRATION
Today
You should have a standalone BACKUP kit that came with your
OpenVMS distribution kit; however, depending on the type of media
you have, standalone BACKUP boots faster if you build it on the
system disk or a user disk. The installation and upgrade supplement
for your computer contains instructions for building and booting
standalone BACKUP on several types of media.
This section provides information about building standalone
BACKUP on a disk or tape and using it to back up your system disk.
Building
Standalone BACKUP on a Disk (VAX Only) Standalone BACKUP boots faster on disk than it does on tape.
For this reason, you should create a standalone BACKUP kit on disk.
You can build standalone BACKUP on either the system disk
or a user disk. If you build standalone BACKUP on a user disk, the
kit occupies more disk space than if you build it on the system
disk. This is because certain files that boot the system already
exist on the system disk.
To build standalone BACKUP, execute SYS$UPDATE:STABACKIT.COM.
The procedure copies the files for booting standalone BACKUP to
a new directory on the target device that you specify, creating
the directory if necessary. When you build a kit on the system disk,
the procedure copies the files to the [SYSE] directory. When you
build the kit on a user disk, the procedure copies the files to
the [SYS0] directory.
Perform the following steps to build standalone BACKUP on
a disk:
Log in to the
SYSTEM account.
Enter the following command and press Return:
$ @SYS$UPDATE:STABACKITEnter the name of the device on which to build the kit:
Enter the device name of the disk that you are building
standalone BACKUP on. If you are building standalone BACKUP on the
system disk, enter SYS$SYSDEVICE. For example:
Enter the name of the device on which to build the kit:SYS$SYSDEVICE:
The procedure places the files in the appropriate
directories on the disk that you are using to build standalone BACKUP.
It lists the files as they are copied. When the procedure finishes,
it displays the following message:
When you perform an image backup from an RF73 disk (or a disk
with a cluster size of 4 blocks) to an RF74 disk (or a disk with
a cluster size of 7 blocks), the Backup utility does not check the
file size when it allocates space for the file being copied. Therefore,
if the file has an allocation greater than the value of the CLUSTER_SIZE
attribute established during initialization, BACKUP allocates one
more cluster size number of blocks to the allocation size even though
the actual file size is less than the cluster size. For example, during
an image backup, a file that uses 6 blocks and is allocated 8 blocks
(which displays as 6/8 on the screen if you enter a DIRECTORY/SIZE=ALfter
it is copied to the target disk.
As a result of this problem, the following files are copied
to the image system disk with a blocks used/allocation size of 6/14
blocks:
SYS$COMMON:[SYS$LDR]LIDRIVER.EXE
SYS$COMMON:[SYS$LDR]LPDRIVER.EXE
This incorrect allocation size causes standalone BACKUP to fail on
the booted image system disk.
To correct this problem, recopy the two previously listed
files to the same directory after the image backup, by using the
following command (which also specifies the correct allocation size):
Booting
Standalone BACKUP from a Disk (VAX Only) To boot standalone BACKUP from a disk, perform the following
steps:
If the operating
system is not running, go to step 2. If the operating system is running, log in to the SYSTEM account.
Enter the following command and press Return:
$ @SYS$SYSTEM:SHUTDOWN
Answer the questions. When the procedure asks if an automatic
system boot should be performed, press Return for NO. When the procedure
is finished, it displays the following message:
SYSTEM SHUTDOWN COMPLETE -- USE CONSOLE TO HALT SYSTEM
Halt the system.
Boot standalone BACKUP from the root where the kit
is located. The exact commands for booting standalone BACKUP differ
among the various computer models. Refer to the upgrade and installation supplement
for your computer for booting information. For example, to boot a MicroVAX 3100 computer, use the following
format:
>>>B/n0000000 device-name
where:
n is the number of the root on the disk containing
the standalone backup.
device-name is the device name of the disk.
For example, if the disk has a device name of DKA400:, and
the standalone BACKUP kit was created in the [SYSE] directory, enter
the following command:
OpenVMS VAX Version Vn.n Major version id = 01 Minor version id = 00
The procedure asks you for the date and time. Enter
the date and time using the 24-hour clock format and press Return.
For example:
PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM) 19-JAN-2000 15:00
The procedure displays a list of the local devices
on your system. For example:
Available device MKA500: device type TK50
Available device DKA100: device type RRD40
.
.
.
Check the list of devices. If the list is incomplete, make
sure that all the drives are properly connected to the system. Refer
to your hardware manuals for details.
When standalone BACKUP finishes booting, it displays
an identification message followed by the dollar sign prompt ($):
%BACKUP-I-IDENT, Standalone BACKUP Vn.n; the date is 19-APR-2000 15:00
$
Building Standalone BACKUP on a Tape Cartridge
(VAX Only) On VAX systems with a tape cartridge distribution kit, the
tape cartridge that came with your distribution kit contains standalone
BACKUP. Use the procedure in this section if your copy of standalone
BACKUP becomes damaged or if you want to make extra copies.
To build standalone BACKUP on a tape cartridge, perform the
following steps:
Obtain a blank,
initialized tape cartridge. Write the name S/A BKUP V7.3 on the
paper label. Insert the label into the label slot.
Write-enable the tape cartridge by sliding the write-protect
switch away from the label slot.
Insert the tape cartridge labeled S/A BKUP V7.3
into the drive.
Log in to the SYSTEM account.
Enter the following command:
$@SYS$UPDATE:STABACKIT
The procedure asks you for the name of the target
device. Enter the device name of the tape cartridge drive you are
using to build standalone BACKUP. For example:
Enter the name of the device on which to build the kit:MUA0
The procedure displays the following message:
Please place the scratch tape cartridge in drive _MUA0:
This volume will receive the volume label SYSTEM.
Enter "YES" when ready:
When you are ready to continue, enter YES.
The system displays verification messages informing
you that files are being copied.
When standalone BACKUP is built, the procedure displays
a message similar to the following one:
Ending time 19-MAY-2000 16:44:29.90
Starting time 19-MAY-2000 16:30:39.05
The Kit is complete.
$
Remove the tape cartridge labeled S/A BKUP V7.3
from the tape cartridge drive.
Write-protect the tape cartridge by sliding the
write-protect switch toward the label slot. Store the cartridge
in a safe place.
Booting Standalone BACKUP from a Tape Cartridge
(VAX Only) If the disk containing standalone BACKUP becomes unusable
(for example, if the drive fails), you can boot standalone BACKUP
from a tape cartridge. Booting standalone BACKUP from a tape cartridge
takes approximately 20 minutes.
To boot standalone BACKUP from a tape cartridge, use the following
procedure:
If the operating
system is not running, see step 2. If the operating system is running, log in to the SYSTEM account.
Enter the following command and press Return:
$@SYS$SYSTEM:SHUTDOWN
Answer the questions. When the procedure asks if an automatic
system boot should be performed, press Return for NO. When the procedure
is finished, it displays the following message:
SYSTEM SHUTDOWN COMPLETE -- USE CONSOLE TO HALT SYSTEM
Halt the system.
Insert the tape cartridge that contains standalone
BACKUP into the tape cartridge drive.
To boot standalone BACKUP, enter the BOOT command
followed by the device name of the tape cartridge drive that contains
standalone BACKUP. For example:
>>>BOOT MUA0
Standalone BACKUP displays the following message:
OpenVMS VAX Version V7.3 Major version id = 3 Minor version id = 0
The procedure might ask you for the date and time.
Enter the date and time using the 24-hour clock format and press
Return. For example:
PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM) 19-MAY-2000 15:00
The procedure displays a list of the local devices
on your system and, if you have them, HSC and MSCP-served devices.
For example:
Available device DUA0: device type Generic_DU
Available device MUA0: device type TK50
When standalone BACKUP finishes booting, it displays
an identification message followed by the dollar sign prompt ($):
%BACKUP-I-IDENT, standalone BACKUP V7.3; the date is 19-MAY-2000 15:50
$
Backing Up the System Disk to Tape When backing up your system disk, you must understand the
functions of the /IMAGE and /PHYSICAL qualifiers to the BACKUP command
before using standalone BACKUP:
Qualifier
Function
/IMAGE
Lets you create a functionally
equivalent copy of the entire system disk. When restored, files
from an image backup are placed contiguously on the system disk,
eliminating disk fragmentation.
/PHYSICAL
Copies, saves, restores, or compares
the entire system disk in terms of logical blocks, ignoring any
file structure.
For a complete description of the Backup utility qualifiers,
refer to the HP OpenVMS System Management Utilities Reference Manual.
To perform an image backup of the system disk to tape, use
the following procedure:
Obtain blank
tape cartridges or magnetic tapes that you can use for the backup
operation.
Write-enable the tape. To write-enable a tape cartridge,
slide the write-protect switch away from the tape cartridge label.
To write-enable a tape, insert a write-enable ring in the back of
the tape reel.
Insert a tape into the tape drive.
Determine the device name of the system disk you
are backing up. (See
Getting Information About Devices on the System for information about determining the names of your devices.)
To display the device name of the system disk you are booted from,
enter the DCL command SHOW LOGICAL SYS$SYSDEVICE.
Depending on your configuration, either boot standalone
BACKUP or start the menu system:
If you have access to the OpenVMS
Alpha or VAX operating system distribution compact disc, start the
menu sytem described in
Starting the Menu System.
Enter the BACKUP command in the following format:BACKUP/IMAGE/VERIFY input-specifier: output-specifier:saveset.BCK/REWIND/LABEL=labelwhere:
input-specifier is
the device name of the system disk.
output-specifier is the device
name of the drive that you want to hold the backup copy.
saveset.BCK is the name of
the save set. The name should reflect the contents of the tape (for example,
OCT_31_2000.BCK) and cannot exceed 17 characters in length.
label is the volume label of
the tape in the drive. If the tape has been initialized already,
use the same volume label that was assigned by the INITIALIZE command.
The following message indicates that BACKUP has
transferred the files and is verifying the accuracy of the backup
copy:
%BACKUP-I-STARTVERIFY, starting verification pass
If your system disk contains more data than a single
tape cartridge or magnetic tape can store, the procedure displays
the following messages and prompt:
%BACKUP-I-RESUME, Resuming operation on volume 2
%BACKUP-I-READYWRITE, Mount volume 2 on _MUA0: for writing
Enter "YES" when ready.
If you do not receive these messages, see step 9. If you do
receive these messages, perform the following steps:
Remove the
backup tape from the drive.
Label it COMPLETE SYSTEM BACKUP and include the
date and the number of the tape in the sequence.
Write-protect the backup tape.
Write-enable another scratch tape and insert it
into the drive.
When you are ready to continue, enter Y (for YES)
and press Return.
The procedure displays the following message, which
indicates that it has transferred the files and is verifying the
accuracy of the backup copy:
%BACKUP-I-STARTVERIFY, starting verification pass
Each time the procedure displays a mount request, follow steps
a through e.
If you are using standalone BACKUP, when the backup
is finished, the system displays the following message:
%BACKUP-I-PROCDONE, Operation completed. Processing finished at 19-MAY-2000
15:30. If you do not want to perform another standalone BACKUP operation,
use the console to halt the system.
If you do want to perform another standalone BACKUP operation,
ensure the standalone application volume is online and ready.
Enter "YES" to continue:
Continue with step 11.
If you are using the menu system, the DCL prompt
appears after the backup is finished. Log out and choose the Shutdown
option from the menu.
Remove the backup tape from the drive. Label it
COMPLETE SYSTEM BACKUP, number it (if you used more than one cartridge),
and include the date.
Write-protect the tape cartridge or magnetic tape.
Halt the system.
Reboot the system.
Store the backup tapes in a safe place.
Restoring the System Disk from Tape If a problem occurs that renders your system disk unbootable,
you can restore the system disk from your backup copy.
To restore the system disk from tape, use the following procedure.
The BACKUP restore operation creates a system disk that
includes a set of volume parameters provided by HP, including
a cluster size (disk access scheme). You can change most volume parameters
later with the SET VOLUME command. For cluster-mounted volumes,
changes occur to the nodes on which the SET VOLUME command is issued.
To change the cluster size, 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, see
Initializing Volumes. For more information
about the BACKUP command qualifiers, refer to the HP OpenVMS System Management Utilities Reference Manual
.
Depending on
your configuration, either boot standalone BACKUP or start the menu
system:
If you have access to the OpenVMS
Alpha or VAX operating system distribution compact disc, start the
menu system described in
Starting the Menu System.
If your system disk contained more data than one
tape could store, you receive the following messages and prompt:
%BACKUP-I-RESUME, Resuming operation on volume 2
%BACKUP-I-READYREAD, Mount volume 2 on MUA0: for reading
Enter "YES" when ready.
If you do not receive these messages, see step 7. If you do
receive these messages, perform the following steps:
Remove the
backup tape from the drive.
Insert the next backup tape into the drive.
When you are ready to continue, enter Y (for YES)
and press Return.
The procedure displays the following message:
%BACKUP-I-STARTVERIFY, starting verification pass
Each time the procedure displays a mount request, follow steps
a through c.
If you are using standalone BACKUP, when the restore
is finished the system displays the following message:
%BACKUP-I-PROCDONE, Operation completed. Processing finished at 19-MAY-2000
15:30. If you do not want to perform another standalone BACKUP operation,
use the console to halt the system.
If you do want to perform another standalone BACKUP operation,
ensure the standalone application volume is online and ready.
Enter "YES" to continue:
Continue with step 9.
If you are using the menu system, the DCL prompt
appears after the restore is finished. Log out and choose the shutdown
option from the menu.
Remove the last backup tape from the drive.
Halt the system.
Reboot the system.
Store the backup tapes in a safe place.
Backing Up the System Disk to a Disk To eliminate disk fragmentation, perform a disk-to-disk image
backup without using the /SAVE_SET qualifier. This creates a functionally
equivalent copy of the entire system disk, on which files are stored contiguously.
This procedure initializes the output disk, effectively
erasing the files on the disk.
To perform a disk-to-disk image backup, use the following
procedure:
Obtain a disk
with enough storage capacity to use for the backup. Make sure the
disk does not contain files you need, because standalone BACKUP
initializes the output disk.
Determine the device name of the system disk you
are backing up. (See
Getting Information About Devices on the System for information about determining the names of your devices.)
To display the device name of the system disk you are booted from,
enter the DCL command SHOW LOGICAL SYS$SYSDEVICE.
Depending on your configuration, either boot standalone
BACKUP or start the menu system:
If you have access to the OpenVMS
Alpha or VAX operating system distribution compact disc, start the
menu system described in
Starting the Menu System.
Enter the BACKUP command in the following format:BACKUP/IMAGE/VERIFY input-specifier: output-specifier:where:
input-specifier is
the device name of the system disk.
output-specifier is the device
name of the drive that you want to hold the backup copy.
For example:
$BACKUP/IMAGE/VERIFY DUA0: DUA1:
BACKUP displays the following message, which indicates
that it has transferred the files and is verifying the accuracy
of the backup copy:
%BACKUP-I-STARTVERIFY, starting verification pass
If you are using standalone BACKUP, when the backup
is finished the system displays the following message:
%BACKUP-I-PROCDONE, Operation completed. Processing finished at 19-MAY-2000
15:30. If you do not want to perform another standalone BACKUP operation,
use the console to halt the system.
If you do want to perform another standalone BACKUP operation,
ensure the standalone application volume is online and ready.
Enter "YES" to continue:
Continue with step 8.
If you are using the menu system, the DCL prompt
appears after the backup is finished. Log out and choose the shutdown
option from the menu.
You can use the backup output disk as the system
disk. Files are stored contiguously on the output disk, eliminating
disk fragmentation.
Store the original system disk.
Halt the system.
Reboot the system using the newly created system
disk.
Using InfoServer Tapes to Back Up and Restore
System Disks On VAX systems, you can back up the system disk to an InfoServer
tape and restore the system disk from an InfoServer tape.
Boot the system
from the SYS1 directory using the current version of the OpenVMS
CD-ROM, which can be in a reader on the InfoServer or on a local
drive.
The boot command you use for your computer depends on
the type of system you have. For more information about booting
your system, refer to the installation and operations supplement
for your computer.
Choose option 1 from the menu system.
At the prompt, you can perform the backup of your
system disks.
HP OpenVMS System Manager's Manual, Volume 1:... 
Using BACKUP
