Document revision date: 19 July 1999 | |
Previous | Contents | Index |
$ ALLOCATE MUA0:,MUA1:,MUA2:(1) %DCL-I-ALLOC, MUA0: allocated %DCL-I-ALLOC, MUA1: allocated %DCL-I-ALLOC, MUA2: allocated $ BACKUP/IMAGE/RECORD/NOASSIST/RELEASE_TAPE _From: DKA100: _To: MUA0:FULL02.SAV,MUA1,MUA2/LABEL=MNTH(2) %MOUNT-I-MOUNTED, MNTH mounted on _MUA0: %BACKUP-I-RESUME, resuming operation on volume 2 %MOUNT-I-MOUNTED, MNTH02 mounted on _MUA1: %BACKUP-I-RESUME, resuming operation on volume 3 %MOUNT-I-MOUNTED, MNTH03 mounted on _MUA2: $ |
As described in Section 10.2, an image backup of a disk provides you with an exact logical copy of all the files on the disk. You should perform image backups with no interactive users on the system because of open file considerations (described in Section 10.15.1). Also, system performance can be affected during the backup process, so it is best to schedule the backup during the least busy times for your system. You can optimize the speed of the backup procedure by ensuring that certain process and system parameters are set properly (as described in Section 10.7).
To perform an image backup to a disk, use the BACKUP command in the following format:
BACKUP/IMAGE/RECORD input-device output-specifier/SAVE_SET |
The /IMAGE qualifier identifies the backup operation as an image backup. The /RECORD qualifier records the current date and time in the file header record of each file that is backed up. This information is essential for future incremental backups. The /SAVE_SET qualifier indicates that you are creating a save set on a disk.
$ MOUNT DUA1: USER1 %MOUNT-I-MOUNTED, USER1 mounted on _DUA1: $ MOUNT DUA2: USER2 %MOUNT-I-MOUNTED, USER2 mounted on _DUA2: $ BACKUP/IMAGE/RECORD _From: DUA1: _To: DUA2:[USER.BACKUPS]USER1.SAV/SAVE_SET |
$ BACKUP/IMAGE/RECORD _From: DUA0: _To: DUB24:[USER.BACKUPS]USER1.SAV,DUB25/SAVE_SET |
As described in Section 10.2, an incremental backup of a disk provides you with an exact copy of only those files that have been created or modified since the last image or incremental backup in which the /RECORD qualifier was used.
To perform an incremental backup to tape, perform the following steps:
$ DIRECTORY/FULL LOGIN.COM Directory WORK204:[HIGGINS] LOGIN.COM;31 File ID: (23788,1,0) Size: 7/9 Owner: [ACC,HIGGINS] Created: 30-APR-1998 14:37:33.98 Revised: 30-APR-1998 14:37:34.44 (1) Expires: <None specified> Backup: 30-APR-1998 20:20:57.37 File organization: Sequential File attributes: Allocation: 9, Extend: 0, Global buffer count: 0, No version limit Record format: Variable length, maximum 94 bytes Record attributes: Carriage return carriage control RMS attributes: None Journaling enabled: None File protection: System:RWED, Owner:RWED, Group:RE, World: Access Cntrl List: None Total of 1 file, 7/9 blocks. |
If you used the /IGNORE=INTERLOCK qualifier to back up open files during your last image backup or incremental backup in which the /RECORD qualifier was used, see Section 10.18.3. If the files remain open, they will not be included in the incremental backup because their backup date fields are not as recent as the last image backup or incremental backup in which the /RECORD qualifier was used. |
BACKUP/RECORD/SINCE=BACKUP input-specifier output-specifier[/LABEL=label] [/REWIND] |
The /RECORD qualifier records the current date and time in the file
header record of each file that is backed up. This information is
essential for future incremental backups. The /SINCE=BACKUP qualifier
backs up files dated later than the last /RECORD backup. The /REWIND
qualifier is optional depending on whether you want to initialize the
tape. The /LABEL qualifier identifies the label of the tape.
The following command is an example of an incremental backup in which BACKUP saves all files on DRA1: that were modified since the previous BACKUP/RECORD command and stores them in a save set named 20APR1998.SAV:
$ BACKUP/RECORD/SINCE=BACKUP/RELEASE_TAPE From: DRA1:[000000...] To: MIA0:20APR1998.SAV/LABEL=20JUNE |
The /LABEL qualifier identifies the volume label of the tape. Also,
because BACKUP is performing an incremental rather than an image
backup, it is necessary to explicitly use the notation DRA1:[000000...]
to specify all the files on DRA1. The /SINCE=BACKUP qualifier saves all
files created or modified since the last /RECORD backup. The
/RELEASE_TAPE qualifier dismounts and unloads an output tape device
after BACKUP writes the save set and before it performs the action of
the /RECORD command.
10.15.5 Performing Incremental Backups to Disk
As described in Section 10.2, an incremental backup of a disk provides you with an exact copy of only those files that have been created or modified since the last image or incremental backup in which the /RECORD qualifier was used.
To make an incremental backup to disk, perform the following steps:
$ DIRECTORY/FULL LOGIN.COM Directory WORK204:[HIGGINS] LOGIN.COM;31 File ID: (23788,1,0) Size: 7/9 Owner: [ACC,HIGGINS] Created: 30-APR-1998 14:37:33.98 Revised: 30-APR-1998 14:37:34.44 (1) Expires: <None specified> Backup: 30-APR-1998 20:20:57.37 File organization: Sequential File attributes: Allocation: 9, Extend: 0, Global buffer count: 0, No version limit Record format: Variable length, maximum 94 bytes Record attributes: Carriage return carriage control RMS attributes: None Journaling enabled: None File protection: System:RWED, Owner:RWED, Group:RE, World: Access Cntrl List: None Total of 1 file, 7/9 blocks. $ |
If you used the /IGNORE=INTERLOCK qualifier to back up open files during your last image backup or incremental backup in which the /RECORD qualifier was used, see Section 10.18.3. If the files remain open, they will not be included in the incremental backup because their backup date fields are not as recent as the last image backup or incremental backup in which the /RECORD qualifier was used. |
BACKUP/RECORD/SINCE=BACKUP input-specifier output-specifier/SAVE_SET |
The /RECORD qualifier records the current date and time in the file
header record of each file that is backed up. The first step in an
incremental backup is an image backup (see Section 10.15.2). If you plan
to perform incremental backups, you must use the /RECORD qualifier when
you perform image backups. The /SINCE=BACKUP qualifier backs up files
dated later than the last /RECORD backup. The /SAVE_SET qualifier
indicates that you are creating a save set on a disk.
$ MOUNT DUA55: DISK1 %MOUNT-I-MOUNTED, DISK1 mounted on _DUA55: $ MOUNT/FOREIGN DJC12: %MOUNT-I-MOUNTED, DISK2 mounted on _DJC12: $ BACKUP/RECORD/SINCE=BACKUP _From: DUA55:[000000...] _To: DJC12:USER1.SAV/SAVE_SET |
$ MOUNT DUA0: USER1 %MOUNT-I-MOUNTED, USER1 mounted on _DUA0: $ MOUNT/FOREIGN DUB24: %MOUNT-I-MOUNTED, DISK2 mounted on _DUB24: $ MOUNT/FOREIGN DUB25: %MOUNT-I-MOUNTED, DISK3 mounted on _DUB25: $ BACKUP/RECORD/SINCE=BACKUP _From: DUA0:[000000...] _To: DUB24:USER1.SAV,DUB25/SAVE_SET |
An incompatibility between the operating procedures of the PATHWORKS for OpenVMS Macintosh server and OpenVMS incremental backup operations can cause BACKUP to save entire disks or directory structures, including subdirectories and files.
BACKUP can detect whether a directory file has been modified since the date indicated by the Backup Date field in the file header. If a directory file has been modified, all subdirectories and files of that directory are saved for possible later restore operations.
Updating the modification date of directory files is unusual for OpenVMS systems. However, it can happen if, for example, you rename a directory file from one location to another. In contrast, the PATHWORKS Macintosh server maintains the modification date of directory files for Macintosh users; that is, it updates the modification date for each directory change, file creation, and file deletion.
Thus, an incremental backup of a disk where PATHWORKS is used to serve files to Macintosh users may result in saving the entire disk or entire directories (including their subdirectories and files) instead of just the user files that were created or modified since the last incremental backup operation.
You can avoid saving files unnecessarily in either of the following ways:
$ BACKUP/RECORD/IGNORE=(INTERLOCK) - _$ disk:[000000...]*.DIR;* - _$ NLA0:DUMMY.BCK/SAVE/NOCRC/GROUP_SIZE=0 $ $ BACKUP/VERIFY/FAST/RECORD/IGNORE=(INTERLOCK) - _$ /NOASSIST/COMMENT="Incremental backup of DISK:" - _$ disk:[000000...]*.*;*/SINCE=BACKUP - _$ tape:incr.bck/LABEL=incr/SAVE |
On a standalone workstation, you are probably responsible for backing up files on your user disks. Section 10.15.7.1, Section 10.15.7.2, and Section 10.15.7.3 contain command procedures for making image, incremental, and interactive backups of user disks on your workstation.
Compaq also provides two template command procedures in the SYS$EXAMPLES directory for you to use in designing BACKUP command procedures. These command procedures are called BACKUSER.COM and RESTUSER.COM.
If you are not familiar with using command procedures, refer to the
OpenVMS User's Manual.
10.15.7.1 Using a Command Procedure for Nightly Image Backups
The following command procedure performs nightly image backups, backing up all the files on disk DUA2: to a tape in MUA0. The files are copied to a magnetic tape save set named FULL_BACKUP.SAV. This procedure is particularly useful for backing up files on a MicroVAX system or workstation.
To use the command procedure, perform the following steps:
$! $! Resubmit this procedure -- $ SUBMIT/AFTER="TOMORROW+2:0" SYS$MANAGER:SYSTEM_BACKUP $! $ ON ERROR THEN GOTO FAILURE $ SET PROCESS/PRIVILEGES=ALL $! $ REPLY/ALL - "Full Backup About to Begin. Open Files Will Not Be Saved" $! $ BACKUP /IMAGE DUA2: MUA0:FULL_BACKUP.SAV /REWIND /IGNORE=LABEL_PROCESSING $ DISMOUNT MUA0: $ EXIT $! $FAILURE: $ WRITE SYS$OUTPUT "---> Backup failed" $ WRITE SYS$OUTPUT "" $ DISMOUNT MUA0: $ EXIT |
. . . $! $ BACKUP/IMAGE WORK_DISK MIA0:WORK_BACK.SAV/REWIND $ BACKUP/IMAGE PAYROLL_DISK MIA0:PAYROLL_BACK.SAV $! . . . |
SUBMIT/NOPRINT/AFTER="TOMORROW+2:0"/QUEUE=queue_name SYS$MANAGER:SYSTEM_BACKUP |
To stop the procedure after you have submitted it, use the DELETE/ENTRY command. To find the entry number, use the SHOW ENTRY command. For example:
$ SHOW ENTRY Entry Jobname Username Blocks Status ----- ------- -------- ------ ------ 14 SYS_BACKUP TPROULX Holding until 19-APR-1998 02:00 On generic batch queue CLUSTER_BATCH $ DELETE/entry=583 |
You can use a similar command procedure to perform nightly incremental backups of your disks. It might be more convenient to perform nightly incremental backups and weekly image backups if either of the following conditions applies:
Suppose that you want to do nightly incremental backups at 11:00 P.M., except on Friday night, when you want to do an image backup. The following command procedure executes an incremental backup on three disks and automatically resubmits itself to run again the following night, except for Friday night.
To use the procedure, follow these steps:
$! $! Resubmit this procedure -- $ SUBMIT/AFTER="TOMORROW+23:0" SYS$MANAGER:INCREMENTAL_BACKUP $! $ TODAY = f$cvtime("today",,"weekday") $ IF TODAY .EQS. "Friday" THEN GOTO DONE $! $ ON ERROR THEN GOTO FAILURE $ SET PROC/PRIV=(OPER,BYPASS) $! $ REPLY/ALL - "Incremental Backup About to Begin. Open Files Will Not Be Saved" $! $ BACKUP/RECORD/SINCE=BACKUP DRA0:[000000...] - MIA0:INCREMENT1.SAV /LABEL=INC1 $ BACKUP/RECORD/SINCE=BACKUP DRA1:[000000...] - MIA1:INCREMENT2.SAV /LABEL=INC2 $ BACKUP/RECORD/SINCE=BACKUP DRA2:[000000...] - MIA2:INCREMENT3.SAV /LABEL=INC3 $ DISMOUNT MIA0: $ DISMOUNT MIA1: $ DISMOUNT MIA2: $ EXIT $! $FAILURE: $ WRITE SYS$OUTPUT "---> Backup failed" $ WRITE SYS$OUTPUT "" $ DISMOUNT MIA0: $ DISMOUNT MIA1: $ DISMOUNT MIA2: $ EXIT |
$ SUBMIT/AFTER=23 SYS$MANAGER:INCREMENTAL_BACKUP |
Previous | Next | Contents | Index |
privacy and legal statement | ||
6017PRO_047.HTML |