![[Digital logo]](../../IMAGES/DIGITAL-LOGO.GIF){kind=logo}
![[HR]](../../IMAGES/REDBAR.GIF)
Use the EXCHANGE/NETWORK command to perform the following operations:
For details on using the EXCHANGE/NETWORK command, refer to online help or the OpenVMS DCL Dictionary.
How to Perform This Task
To issue the EXCHANGE/NETWORK command, use the following format:
EXCHANGE/NETWORK input-filespec[,...] output-filespec
where:
| input-filespec | Specifies the name of an existing file to be transferred. (Wildcard characters are allowed.) |
| output-filespec | Specifies the name of the output file into which the input is to be transferred. |
Example
$ EXCHANGE/NETWORK MYSYS_FILE.DAT FOO::FOREIGN_SYS.DAT
The command in this example transfers the file MYSYS_FILE.DAT, which is located in the current default device and directory, to the file FOREIGN_SYS.DAT on node FOO, which is not an OpenVMS node. By default, the command automatically determines whether the transfer method should be block or record I/O.
You can guard against data loss or corruption by using the OpenVMS Backup utility (BACKUP) to create copies of your files, directories, and disks. In case of a problem---for example, a disk drive failure---you can restore the backup copy and continue your work with minimal disruption.
Information Provided in This Chapter
This chapter describes the following tasks:
| Task | Section |
|---|---|
| Formulating a BACKUP strategy | Section 10.3 |
| Setting up a BACKUP account | Section 10.7 |
| Initializing, mounting, and dismounting disks and tapes | Section 10.8 |
| Listing the contents of a BACKUP save set | Section 10.10 |
| Backing up user disks and volume shadow sets | Section 10.15 |
| Restoring user disks and volume shadow sets | Section 10.16 |
| Backing up and restoring the system disk | Section 10.17 |
| Building and booting standalone BACKUP | Section 10.17.2 |
| Ensuring data integrity | Section 10.18 |
| Troubleshooting | Section 10.19 |
This chapter explains the following concepts:
| Concept | Section |
|---|---|
| Types of backups | Section 10.2 |
| The BACKUP command line | Section 10.4.1 |
| The Backup Manager | Section 10.4.2 |
| Save sets | Section 10.5 |
| BACKUP file formats | Section 10.6 |
| Volume initialization | Section 10.8.1 |
| OPCOM and volumes | Section 10.9 |
| Multivolume BACKUP operations | Section 10.11 |
| BACKUP tape label processing | Section 10.12 |
| Standalone BACKUP | Section 10.17.2 |
For BACKUP to effectively guard against data loss, you must back up important data on a regular basis and be familiar with how to restore the data when necessary.
Besides backing up your own files, directories, and disks, you should back up your system disk. If you have a standalone workstation, backing up the system disk is probably your responsibility. If your system is part of a large clustered computer system, an operator or system manager is probably responsible for backing up the system disk.
The two ways to back up your system disk are:
Note
Standalone BACKUP is not supported on OpenVMS Alpha systems beginning with Version 6.1; you must use the menu system provided on the distribution CD--ROM.
Performing an image backup using BACKUP also eliminates disk fragmentation. Fragmentation can occur as you create and extend files on a disk. If the file system cannot store files in contiguous blocks, it stores them in noncontiguous pieces. Eventually, the disk can become severely fragmented and system performance suffers.
To eliminate fragmentation, perform an image backup of the disk and restore the backup copy. When you restore the image backup, BACKUP places the files on the disk contiguously. Alternatively, you can 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.
Note
Some layered products have their own special backup procedures. For more information, see the layered product documentation.
| Operation | Description |
|---|---|
| File operation | Processes individual files or directories. Section 10.13 describes file operations. |
| Selective operation |
Processes files or volumes selectively, according to criteria such as
version number, file type, UIC, date and time of creation, expiration
date, or modification date.
Perform selective save operations by using wildcard characters and input file-selection qualifiers (for example, /BACKUP, /BEFORE, /BY_OWNER [/OWNER_UIC], /CREATED, /EXCLUDE, /EXPIRED, /MODIFIED, and /SINCE). Section 10.13 describes selective operations. |
| Physical operation | Copies, saves, restores, or compares an entire volume in terms of logical blocks, ignoring any file structure. |
| Image operation |
Processes all files on the input disk. The types of image operations
are:
Because an image copy or backup operation processes all files on the input volume, you cannot specify file-selection qualifiers for these operations. You can, however, restore files and directories selectively from an image save set. |
| Incremental operation |
The two types of incremental operations are:
|
For example, if you have a standalone workstation, a nightly image backup might be your best approach.
Under other circumstances, you may want to choose some combination of image and incremental backups. For example, daily image backups might be inconvenient if your system always has interactive users logged in. You could choose to perform a weekly image backup and nightly incremental backups.
Table 10-1 compares image and incremental backups.
| Backup Type | Advantages | Disadvantages |
|---|---|---|
| Image | Faster to restore than incremental backups. Backs up entire disk. | Uses more space and time than incremental backups. Requires that no interactive users are logged in because of the effect on system performance and because of open file considerations (see Section 10.15.1). |
| Incremental | Takes less time and media storage space. | More difficult to restore files. Still requires periodic image backups. |
Notes
Before you perform an image backup, note the following:
- The first time you back up a disk, you must perform an image backup using the BACKUP/IMAGE/RECORD command before you perform regular incremental backups. The image backup saves a copy of the entire disk and marks each file as being saved. Subsequent incremental backups assume that an image backup has been performed; only new or modified files are saved.
If an image backup is not performed first, the incremental backups save more files than might be necessary to ensure that an incremental restore operation will be successful.- If you perform an ANALYZE/DISK operation immediately after a BACKUP/IMAGE restore operation of a disk, the system might display a warning message similar to the following:
%ANALDISK-W-ALLOCCLR, blocks incorrectly marked allocated LBN 97 to 105, RVN 1
This can occur if you attempt to perform a BACKUP/IMAGE restore operation where alias file entries are restored as separate (primary) file entries. (The primary file, which uses the same file header but allocates different data storage blocks, is also restored.)
However, despite the error message, note that there is no BACKUP error or loss of data.
You do not have to change tapes or disks during a backup if any of the following are true:
In these cases, the backup can be performed by a batch job that runs late at night or at some other time when interactive use of the system is likely to be at a minimum. Section 10.15.7 contains some sample command procedures that you can run in a batch job to back up your disks.
Two interfaces are available to the OpenVMS Backup utility:
To back up files, you must specify what you want to back up (the input) and where you want BACKUP to place the resultant save set or file (the output). You can also use BACKUP qualifiers to perform different functions depending upon their position on the command line:
BACKUP/qualifiers input-specifier/qualifiers output-specifier/qualifiers
Table 10-2 lists the types of BACKUP command qualifiers.
| Type | Position | Effect |
|---|---|---|
| Command qualifier | Anywhere on the command line | Affects both input and output specifiers. |
| Input specifier qualifier | Directly after the input specifier | Affects only the input specifier. |
| Output specifier qualifier | Directly after the output specifier | Affects only the output specifiers. |
When you use BACKUP, make sure you place BACKUP qualifiers in their correct positions on the command line. For more information about the BACKUP command line, see OpenVMS System Management Utilities Reference Manual.
Backup Manager is a screen-oriented interface to the OpenVMS Backup utility (BACKUP) that presents BACKUP's capabilities in an intuitive, task-oriented, self-documenting manner. Backup Manager can ease backup tasks by guiding you through the backup process. No real performance differences exist between using the Backup Manager and using the BACKUP command line.
Backup Manager runs on:
The Backup Manager interface is based on the OpenVMS Screen Management Run-Time Library (RTL) routines.
Backup Manager can perform the following backup operations:
Three types of online assistance are available with Backup Manager:
To start Backup Manager, enter the following command at the DCL prompt:
$ RUN SYS$SYSTEM:BACKUP$MANAGER
Output from the Backup utility is automatically displayed when an operation starts. You can suspend output at any time (Ctrl/P) and scroll through it. You can also use Ctrl/T to display status or Ctrl/C to stop the current BACKUP operation.
When you enter a BACKUP command to save files to a tape, BACKUP writes the files to a special file called a save set. You can also create a save set on a disk using the /SAVE_SET qualifier. Save sets are classified according to the media on which they reside. Table 10-3 lists the types of media that you write a save set to.
| Media Type | For More Information |
|---|---|
| Magnetic tape | Section 10.5.1 |
| Files--11 disk | Section 10.5.2 |
| Files--11 disk on a remote node (network save set) | Section 10.5.3 |
| Sequential disk | Section 10.5.4 |
Magnetic tape is the most commonly used media for storing BACKUP save sets. It is less expensive than disk media, and its compact size makes it easy to store. You can use more than one tape device at a time to save or restore data; this allows processing to continue on another tape while the one most recently used is rewinding.
BACKUP treats all magnetic tape files as BACKUP save sets. Because you cannot use save-set specifications as both the input and output specifiers in a BACKUP command line, you cannot perform a BACKUP operation from one magnetic tape to another.
Digital recommends that you copy magnetic tape save sets to disk with the BACKUP command; however, you can use the DCL command COPY on magnetic tape save sets that were created with the /INTERCHANGE qualifier.
Save-set specifications on magnetic tape are limited to 17 characters, including the period delimiter (.) and file type. The following is a valid save-set specification:
WKLY27JAN1996.BCK
When restoring data from tape, if you do not include a save-set name with an input magnetic tape, BACKUP reads the next save set it encounters on the tape. (If you specify the input save-set qualifier /REWIND, BACKUP rewinds the tape and reads the first save set on the tape.)
To write save sets on a Files--11 disk, you must include the output save-set qualifier /SAVE_SET. The /SAVE_SET qualifier indicates to BACKUP that you want to create a save set, rather than a copy of the selected files, on the output volume. The disk must be mounted as a Files--11 volume; all volumes in a volume set must be mounted.
BACKUP can read a Files--11 save set as a Files--11 save set or as a sequential-disk save set:
A save set stored on a Files--11 disk is a standard file, however, and can be copied, renamed, deleted, or backed up.
You can create or read a network save set on a Files--11 disk attached to a remote node by specifying the node name of a remote node in the save-set specification. A remote node is accessible to the node you are working on (the host node) over a network. The network save set must be located on a publicly accessible disk (a disk mounted from the remote node with the /SYSTEM, /GROUP, or /CLUSTER qualifier) on the remote node.
Depending on the volume and file protection at the remote node, you may need to specify an access control string in the network save-set specification. An access control string includes the user name and password, and has the following format:
remote_nodename"username password"::device_name:[directory]
Example
The following example creates a network save set on the remote node DOUBLE:
$ BACKUP _FROM: [MY_DIR] _TO: DOUBLE"username password"::DBA0:SAVEIT.BCK/SAVE_SET
Omit the access control string if it is not required to gain access to the remote node, such as in the case of proxy network access. See the DECnet for OpenVMS Networking Manual for more information about access control strings and proxy network access.
Sequential-disk save sets allow you to treat a Files--11 disk volume sequentially, (like a magnetic tape volume). The primary advantage of using sequential-disk save sets is that you can mount multivolume save sets one volume at a time. This is particularly useful on systems without tape drives that have a large fixed-media disk and a small removable disk.
When one sequential disk is full, BACKUP prompts you to mount another disk. You can use more than one disk device at a time to save or restore data; this allows processing to continue on another disk while the one most recently used is spinning down.
You must have the privilege LOG_IO or PHY_IO to read or write a multivolume sequential-disk save set.
Before creating a sequential-disk save set, mount the first volume of the sequential-disk save set using the DCL command MOUNT/FOREIGN. Although the disk is mounted with the /FOREIGN qualifier, BACKUP manages the disk using Files--11 structure.
When you perform a save operation to a sequential disk, you must use the output save-set qualifier /SAVE_SET. When you perform a restore operation from a sequential disk, you must specify the input save-set qualifier /SAVE_SET. If you do not specify the /SAVE_SET qualifier, BACKUP displays the following error message:
%BACKUP-F-IMGFILSPE, /IMAGE specification must only have device name
Do not specify a directory name for the save set; sequential-disk save sets are always entered in the master file directory [000000]. Even if you specify a directory other than the master file directory in a save operation, the save set is entered in the master file directory. If you specify a directory other than the master file directory in a restore or list operation, BACKUP returns an error message indicating that it cannot locate the file.
BACKUP does not initialize the first sequential-disk volume because the default is /NOINITIALIZE; however, continuation volumes are initialized. Unless you specify the command qualifier /INITIALIZE, the following restrictions apply to the first sequential-disk volume:
Volumes you use for sequential-disk save sets should contain only save sets. You must initialize a volume that has been used for general file processing before using it as a sequential-disk volume. You can place a maximum of 12 save sets on a single sequential disk. Use Files--11 disk save sets if you want to create more than 12 save sets on a single disk.
BACKUP can read a sequential-disk save set either as a sequential-disk save set or as a Files--11 save set:
On VAX systems, BACKUP saves files and directories from Files--11 Structure Level 1 and 2 disks to disks or magnetic tapes. If necessary, you can use BACKUP to restore the saved files and directories to Files--11 Structure Level 1 and 2 disks.
If a VAX system performs image backup of an Alpha system disk, a restore operation causes the Alpha system to reboot successfully.
On Alpha systems, BACKUP saves files and directories from Files--11 Structure Level 2 disks to disks or magnetic tapes. If necessary, you can use BACKUP to restore the saved files and directories to Files--11 Structure Level 2 disks.
Note
The OpenVMS Alpha operating system does not support the Files--11 Structure Level 1 format.
You cannot back up files on ISO 9660-formatted media, but you can restore save sets stored on ISO 9660-formatted media.
For more information about the Files--11 disk structure, see Section 8.1.1.2. For more information about ISO 9660 devices, see Section 7.2.2.
You can optimize the efficiency of backups on your system by properly setting the process quotas for the process from which backups will be made (the process from which you enter the BACKUP command or submit your backup command procedure). This is especially important if you are using a streaming tape drive.
How to Perform This Task
To set process quotas for efficient backups, do the following:
$ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE UAF> SHOW SYSTEM
$ RUN SYS$SYSTEM:SYSMAN SYSMAN> PARAMETERS SHOW WSMAX %SYSMAN-I-USEACTNOD, a USE ACTIVE has been defaulted on node DIEM Node DIEM: Parameters in use: ACTIVE Parameter Name Current Default Minimum Maximum Unit Dynamic -------------- ------- ------- ------- ------- ---- ------- WSMAX 2600 1024 60 100000 Pages SYSMAN> PARAMETERS SHOW CHANNELCNT Parameter Name Current Default Minimum Maximum Unit Dynamic -------------- ------- ------- ------- ------- ---- ------- CHANNELCNT 127 127 21 2047 Channels SYSMAN> EXIT $
| Process Quota | Recommended Setting |
|---|---|
| WSQUOTA | Equal to system parameter WSMAX |
| WSEXTENT | Equal to WSQUOTA quota |
| PGFLQUOTA | Equal to or greater than WSEXTENT quota |
| FILLM | Less than system parameter CHANNELCNT |
| DIOLM | Either 4096 or three times the value of FILLM quota, whichever is greater |
| ASTLM | Either 4096, at least 100 greater than DIOLM quota, or three times the value of FILLM quota, whichever is greater |
| BIOLM | Equal to FILLM |
| BYTLM | Equal to or greater than the following value: (256*FILLM)+(6*DIOLM) |
| ENQLM | Greater than FILLM quota |
6017P029.HTM OSSG Documentation 22-NOV-1996 14:21:58.76
Copyright © Digital Equipment Corporation 1996. All Rights Reserved.