Document revision date: 30 March 2001

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.)

Example 1

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:

Example 2

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:

B.5.4 Logout, Shutdown, and Reboot

After you complete the restore operation:

1. Enter the LOGOUT command to exit from the DCL environment and return to the menu.
2. Choose the shutdown option (8).
3. After the shutdown completes, boot from the system disk.

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:

• If you do not have access to the operating system CD-ROM and its menu system
• If you want to back up a shadowed system disk without disabling the shadow set

Prepare an alternate system disk as follows:

1. Log in to a privileged account on your running Compaq OpenVMS Alpha system.
2. Using the SHOW DEVICE command, identify a data disk on which you can install the operating system, with no options. This will be your target disk during that installation. Note the following:
   • You will need approximately 75,000 blocks to install the operating system with no options
   • Existing data will remain on the disk
3. The target disk must be mounted privately to your process. (This prevents other users from accessing this disk during the installation and backup procedures.) Therefore, if the target disk was mounted with /SYSTEM, /CLUSTER, /GROUP, or /SHARE, dismount that disk and mount it without using those qualifiers or the /FOREIGN qualifier. For example:

   $ MOUNT/OVERRIDE=IDENTIFICATION DKA200

4. Enter the following command to install the Compaq OpenVMS Alpha operating system, with no options, on the target disk:

   $ @SYS$SYSTEM:AXPVMS$PCSI_INSTALL_MIN.COM [target-disk]

   
   (The procedure will prompt you for a device name if you do not specify it on the command line.)

5. As the procedure completes the installation, the display is similar to the following:

   DEC AXPVMS OPENVMS V7.3: OpenVMS and related products platform COPYRIGHT (c) 12-SEP-2001 -- All rights reserved Compaq Computer Corporation Execution phase starting ... The following product will be installed: DEC AXPVMS VMS V7.3 Portion Done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% The following product has been installed: DEC AXPVMS VMS V7.3 . . . The installation of minimum OpenVMS Alpha is now complete. Use the following command to boot minimum OpenVMS: BOOT -FLAGS E,O <device-name> (Your system may require additional parameters to boot.)

   Caution If your system is a cluster member, Compaq recommends that you shut down the entire OpenVMS Cluster system before you back up your system disk. This will prevent you from creating a partitioned cluster and from jeopardizing the integrity of your data in any other way.

Use the alternate system disk (on which you installed the operating system with no options) to perform backup and restore operations as follows:

1. Shut down your system.
2. Boot the alternate system disk from the SYSE root. For example:

   >>> BOOT -FLAGS E,0 DKA200

   
   The system automatically logs you in to the SYSTEM account and then displays a triple dollar sign prompt ($$$).

   Note During the boot and login operations on this minimum version of the operating system, you can ignore license messages that are similar to the following:

   %LICENSE-I-NOLICENSE, no license is active for this software product

3. If your system disk is shadowed, install and load a Volume Shadowing license on this data disk. You will then be able to back up the shadowed system disk from this data disk without disabling the shadow set.

   Note Compaq recommends that you do not install any other licenses, including OpenVMS licenses, on this alternate system. You will be able to use the system only from the console.

4. Mount the system disk and any output devices you plan to use during the backup or restore operations. See Section B.5.2 for more information.
5. Perform the necessary backup and restore operations by entering the appropriate BACKUP commands. See Section B.5.3 for more information.
6. Shut down the system.
7. Boot from your original system disk.

This appendix contains information that supplements the license instructions in this manual and in the OpenVMS License Management Utility Manual.

After you install the Compaq OpenVMS Alpha operating system, you must register Compaq OpenVMS Alpha licenses, which let you use the Compaq OpenVMS Alpha operating system. You must also register the licenses for the Compaq OpenVMS Alpha layered products you have purchased, such as DECnet for OpenVMS. (Note that after an upgrade, however, you do not have to reregister licenses for the Compaq OpenVMS Alpha operating system or for the layered products.) To register a license, you need to obtain a Product Authorization Key (PAK). A PAK is a printed document provided by Compaq that contains the appropriate information to authorize access to software on an Alpha computer (or in an OpenVMS Cluster environment). You can obtain a PAK from a Compaq support representative in the same way as you obtain software.

C.1 Using the License Unit Requirement Table (LURT)

Many PAKs contain a table name in the availability or activity fields. This name refers to a column in the License Unit Requirement Table (LURT), which is shown in Table C-1. Column A in the LURT indicates the number of license units required for each processor listed in the System Marketing Model column. Column H refers to layered products you may choose to register as well. For example, if your PAK specifies availability = A, you would require 50 license units to load the license on a DEC 3000 Alpha Model 500 series computer, or 500 license units to load the license on a DEC 7000 Alpha Model 610 computer.

Note that some PAKs specify MOD_UNITS in the options field. The MOD_UNITS option allows the system manager to use the DCL command LICENSE MODIFY/UNITS to temporarily increase the size of the PAK. This permits a product to be used, in certain emergency situations, on a processor larger than the processor size specified in the license. Check your license terms and conditions before modifying license units. Reset the PAK size to its original size after the emergency situation is resolved.

Table C-1 License Unit Requirement Table (LURT)

System Marketing Model	A	H
ALPHAbook 1	12	1050
AlphaServer 400	12	1050
AlphaServer 800, 1000, 1000A	15	1050
AlphaServer 1200 (1 CPU)	25	1050
AlphaServer 1200 (2 CPU)	75	1050
AlphaServer 2000, 2000A (1 CPU)	400	1100
AlphaServer 2000, 2000A (2 CPU)	500	1100
AlphaServer 2100, 2100A (1 CPU)	400	1100
AlphaServer 2100, 2100A (2 CPU)	500	1100
AlphaServer 2100, 2100A (3 CPU)	600	1100
AlphaServer 2100, 2100A (4 CPU)	700	1100
AlphaServer 4100 (1 CPU)	400	1100
AlphaServer 4100 (2 CPU)	500	1100
AlphaServer 4100 (3 CPU)	600	1100
AlphaServer 4100 (4 CPU)	700	1100
AlphaServer 8200 (1 CPU)	2000	1150
AlphaServer 8200 (2 CPU)	2100	1150
AlphaServer 8200 (3 CPU)	2200	1150
AlphaServer 8200 (4 CPU)	2300	1150
AlphaServer 8200 (5 CPU)	2400	1150
AlphaServer 8200 (6 CPU)	2500	1150
AlphaServer 8400 (1 CPU)	2600	1150
AlphaServer 8400 (2 CPU)	2700	1150
AlphaServer 8400 (3 CPU)	2800	1150
AlphaServer 8400 (4 CPU)	2900	1150
AlphaServer 8400 (5 CPU)	3000	1150
AlphaServer 8400 (6 CPU)	3100	1150
AlphaServer 8400 (7 CPU)	3200	1150
AlphaServer 8400 (8 CPU)	3300	1150
AlphaServer 8400 (9 CPU)	3400	1150
AlphaServer 8400 (10 CPU)	3500	1150
AlphaServer 8400 (11 CPU)	2600	1150
AlphaServer 8400 (12 CPU)	2600	1150
AlphaStation 205, 250, 255, 500	12	1050
AlphaStation 400	12	1050
AlphaStation 600	12	1050
DEC 2000-300/300S	12	1050
DEC 2000-500/500S	12	1050
DEC 3000-300	15	1050
DEC 3000-300L	15	1050
DEC 3000-400/400S	20	1050
DEC 3000-600/600S	20	1050
DEC 3000-500/500S	50	1100
DEC 3000-500X	50	1100
DEC 3000-800/800S	50	1100
DEC 4000-610	300	1150
DEC 4000-620	400	1200
DEC 4000-710	300	1150
DEC 4000-720	400	1200
DEC 7000-610	500	1200
DEC 7000-620	600	1250
DEC 7000-630	700	1250
DEC 7000-640	800	1250
DEC 10000-610	800	1250
DEC 10000-620	900	1300
DEC 10000-630	1000	1300
DEC 10000-640	1100	1300

A---The number of Compaq OpenVMS Alpha operating system license units (Unlimited or Base) required for the system.
B through G---Omitted from table; reserved for future use.
H--- The number of Compaq OpenVMS Alpha layered products license units required for the system.

C.2 License Management Facility (LMF) Notes

• If you do not have a valid Compaq OpenVMS Alpha license that is registered and activated, the system displays a warning message as part of system startup and restricts system use to the operator's console, OPA0.
• If a checksum error is displayed when you register a license, check all the fields of data that you entered, including the checksum itself.
• After your PAKs are registered, they are activated (loaded) automatically as part of each system startup.
• If an Compaq OpenVMS Alpha license is registered with insufficient license units, the system displays the following message when the user (process) attempts to log in:

  %LICENSE-F-EXCEEDED, licensed product has exceeded current license limits

  Users can always log in to the operator's console, OPA0, however.

• The default LICENSE database is located in the file SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB. You can move the database, although Compaq does not recommend doing so. If you move the database, you must either define the logical name LMF$LICENSE at the system level to point to the new database or use the /DATABASE=filespec qualifier with all LICENSE commands. To redirect LMF to another database location on a more permanent basis, add the following line to the command procedure SYS$MANAGER:SYLOGICALS.COM:

  $ DEFINE/SYSTEM LMF$LICENSE device:[directory]LMF$LICENSE.LDB

  
  If you specify a device other than SYS$SYSDEVICE, you must also mount the specified disk from the SYLOGICALS.COM command procedure.

• Each Compaq OpenVMS Alpha find license is restricted to a single node for permanent PAKs. You must assign a System Communications Services (SCS) name to the license when you register with the VMSLICENSE.COM command procedure, or you must enter a LICENSE MODIFY/INCLUDE=node-name command after you register the license.

  Note The SCS node name is not necessarily the DECnet node name. SCSNODE is a system parameter; it can be a maximum of six alphabetic characters.

Availability Product Authorization Keys (PAKs) are available for the Compaq OpenVMS Alpha Alpha operating system. An Compaq OpenVMS Alpha PAK is identified by the keyword ALPHA in the PAK's option field. Note the following restrictions:

• PAKs having the ALPHA option can be loaded and used only on Alpha computers. However, they can safely reside in a license database (LDB) shared by both VAX and Alpha systems.
• Because the LMF for Alpha systems is capable of handling all types of PAKs, including those for VAX systems, Compaq recommends that you perform your LDB tasks using the Alpha LMF.
• Availability PAKs for VAX systems (availability PAKs without the ALPHA option) will not load on Alpha systems. Only those availability PAKs containing the ALPHA option will load on Alpha systems.
• Other PAK types such as activity (also known as concurrent or n-user) and personal use (identified by the RESERVE_UNITS option) work on both VAX and Alpha systems.
• Avoid using the following LICENSE commands from a VAX system on a PAK containing the ALPHA option:
  • REGISTER
  • DELETE/STATUS
  • DISABLE
  • ENABLE
  • ISSUE
  • MOVE
  • COPY
  • LIST
• Caution: By default, all Alpha availability PAKs look disabled to a VAX system. Never use the DELETE/STATUS=DISABLED command from a VAX system on an LDB that contains Alpha PAKs. If you do, all Alpha PAKs will be deleted.
• With the exception of the DELETE/STATUS=DISABLED command, if you inadvertently use one of the previously listed LICENSE commands on an Alpha PAK while using a VAX system, the PAK and the database will not be adversely affected. Repeat the command using LMF running on an Alpha system, and the PAK should return to a valid state.
• If you do not repeat the command using LMF on an Alpha system, the system that you intended to disable will remain enabled (the system is not otherwise affected). Only the Alpha LMF can disable an Alpha PAK.
  However, if you attempt to use any of the previously listed commands on a PAK located in an LDB that is shared with a VAX system, the following serious problems may result:
  • Because Alpha PAKs look disabled to a VAX system, they are normally ignored at load time by VAX systems. However, if one of the previously listed commands is entered from a VAX system and the PAK information is not set to a valid state by an Alpha system, there is a chance the VAX system will attempt to load the Alpha PAK. Because the VAX system will be unable to load the PAK, the VAX LMF will report an error.
  • Even if a valid VAX PAK for the affected product is in the LDB, it too may not load. In this case, system users might be denied access to the product.
  
  If the PAK cannot be restored to a valid state because all Alpha systems are inaccessible for any reason, use your VAX system to disable the Alpha PAK. This prevents your VAX system from attempting to load the Alpha PAK.

	privacy and legal statement
6629PRO_014.HTML