Previous | Contents | Index |
The Remote NFS backup mode can back up a disk on a remote UNIX or WindowsNT NFS server. This procedure automatically connects to the remote system, does the back up and then disconnects. If the remote NFS disk is permanently mounted on the VMS system then use the On-line backup mode. This procedure expects each parameter to establish the source node node and disk (or share) name to backup from. A sample parameter list is as follows:
parameter(1) = "wnt1::/c:" parameter(2) = "unix2::/usr:" parameter(3) = "unix3::/usr:[smith...]*.*.*" |
If the file name is not specified it defaults to "*.*.*". If the
directory name is not specified it defaults to "[*...]". This node
requires that a TCP/IP network communication package is available on
the OpenVMS system where this back up is running. The packages that
have been tested are TCPware10, MultiNet11 and
TCP/IP Services (or UCX)12
2.4.6 Agent UNIX backups
The UNIX remote backup procedure described in this section utilizes Task/Agent and MEDIA software from ISE. If either of these products is not installed, the procedure will not work1
The UNIX remote backup controls a UNIX tar archive operation on a remote UNIX node. BCKMGR Backup Manager software must be configured with a backup mode of 26 in order to perform this type of backup. All other backup modes will be rejected if attempted on a remote UNIX node.
See the MEDIA documentation for more on setting backup modes. |
2.4.6.1 Configuring the backup
The symbols in the following table can be used to affect how the backup
is performed. They are assigned in the the parameter list. The symbols
are:
Symbol | Description |
---|---|
+USERNAME="username" | username on target node 1 |
+PASWWORD="password" | password on target node 1 |
+NODE="remote_node" | target remote node 2 |
+DEVICE="remote_device" | tape device on remote node 3 |
+OPERATOR="LOCAL"(D) | (Default) local OPCOMS |
+OPERATOR="REMOTE" | messages on remote node |
+EJECT=0,1(D) | eject tape at end of job |
In addition, the values in the following table are picked up from the backup job settings for the job.
Setting | Description |
---|---|
HISTORY | history record options |
BLOCKSIZE | blocking factor use |
OPTIONS | tar options to specify |
All other VMS specific backup settings will be ignored by the job since
they are only applicable to a VMS backup.
2.4.6.2 Specifying tar options
The tar command generated by the backup procedure always uses the option -c (create) and -v (verbose) options. The resulting output is captured and added to the MEDIA library.
BCKMGR parameters can contain a list of paths for tar to write to tape. For example you may want to back up user paths as in the following example of a parameter listing from a job:
Parameter (6) = "/usr/users/jones/*" (7) = "/usr/users/tseng/*" (8) = "/usr/users/pparks/*" (9) = "/usr/users/plewis/*" (10) = "/usr/users/ypringle/*" |
The resulting backup tape produced by the tar procedure is a sequence of "tar" archives. The parameters in the list cause a new archive to be created. The first archive container consists of volume label information. The MEDIA database formats the information in the following way.
The following listing example demonstrates how to display the files backed up on a select medium selectively using wildcards. Note the quote marks are used to designate the string to be searched within the listing.
$ MEDIA 9019;0>"*/brown/ns*" Directory of DAILY_BACKUP;20>[] 3 5-JUN-1997 15:37 /usr/users/brown/ns_startup 1 Blocks 3 5-JUN-1997 15:37 /usr/users/brown/nsmail 1 Blocks | | | | | +- saved file and size | +--- date files added to tape +---tar archive container number |
In order to restore the nsmail file in the example above enter the following commands:
mt rewind tar -tz -f /dev/ntmt0h > /dev/null 2> /dev/null (skip container 1) tar -tz -f /dev/nrmt0h > /dev/null 2> /dev/null (skip container 2) tar -x -f /dev/nrmt0h /usr/users/brown/nsmail |
The following is an example of a typical remote UNIX backup job. Note the backup mode is 26 and the parameters are UNIX style listings of directories to be backed up.
UNIX_REMOTE_BACK Comment = Demonstration of mode 26 Username = PSMITH Last submit = June 6, 1997, 16:11 Last completed = June 5, 1997, 15:38 Job Log = Priority = 0 Flags = Remote,Media_Job,Cycle,NoHold,Keep, NoPrint,NoRestart Status = %x00000000 P1 = Queue = BWS$BATCH Backup mode = 26 Next media = 9020 Generations = 6 Required = 1 Media type = 4MMBWS Up count = 36 Down count = infinite Owner = [PSMITH] Protection = S:RWED,O:RWED,G,W Parameter (6) = "+node="osfws1"" (8) = "/usr/users/psmith/*" (9) = "/usr/users/kbrown/*" (10) = "/usr/users/scozzari/*" |
The Windows NT remote backup procedure described in this section utilizes Task/Agent and MEDIA software from ISE. If either of these products is not installed, the procedure will not work1
The Windows NT remote backup controls a ntbackup operation on a remote Windows NT node. BCKMGR Backup Manager software must be configured with a backup mode of 25 in order to perform this type of backup. All other backup modes will be rejected if attempted on a remote Windows NT node.
See the MEDIA documentation for more on setting backup modes. |
2.4.7.1 Configuring the backup
The symbols in the following table can be used to affect how the backup
is performed. They are assigned in the the parameter list. The symbols
are:
Symbol | Description |
---|---|
+USERNAME="username" | username on target node 1 |
+PASSWORD="password" | passowrd on target node 1 |
+NODE="remote_node" | target remote node 2 |
+DEVICE="remote_device" | tape device on remote node 3 |
+OPERATOR="LOCAL"(D) | (Default) local OPCOMS |
+OPERATOR="REMOTE" | messages on remote node |
+EJECT=0,1(D) | eject tape at end of job |
In addition, the values in the following table are picked up from the backup job settings for the job.
Setting | Description |
---|---|
HISTORY | history record options |
VERIFY | do a verify pass on the data |
OPTIONS | ntbackup options to specify |
NTbackup options that may be used include:
/b - backup local registry
/t {backup type} - type of backup
backup types are:
Backup type | Description |
---|---|
Normal | backs up all selected items and marks the archive bit accordingly. |
Incremental | backs up selected files that have been modified since the last backup and marks the archive bit. |
Copy | same effect as normal but doesn't mark the archive bit. |
Daily | backs up only selected files that are changed on the day the backup is run. |
Differential | same effect as incremental but doesn't mark the archive bit. |
All other VMS specific backup settings will be ignored by the job since
they are only applicable to a VMS backup.
2.4.7.2 Specifying ntbackup options
BCKMGR parameters can contain a list of paths for ntbackup to write to tape. Wild cards cannot be used. Only devices and/or directories can be specified. For example you may want to back up user paths as in the following example of a parameter listing from a job:
Parameter (6) = "C:\WINDOWS" (7) = "C:\SCU" (8) = "c:\scsi" (9) = "d:\office97" (10) = "E:\LOTUS" |
If the MEDIA database indicates DATA COMPACTION for the relevant media for the job then hardware compression is turned on.
Each tape produced by this procedure is a sequence of "ntbackup" savesets. Each parameter causes a new saveset to be created. The first saveset contains the volume label information.
The following listing example demonstrates how to display the files backed up on a select medium selectively using wildcards. Note the quote marks are used to designate the string to be searched within the listing.
$ MEDIA 9020;0>"\SCU*.EXE" DIR Directory of INCREMENTAL_BACKUP;21>[] 3) C:\SCU\EMM386.EXE 120926 8/23/97 5:55PM 3) C:\SCU\LOGO.EXE 27039 8/23/97 5:55PM 3) C:\SCU\MOUSE.EXE 87554 8/23/97 5:55PM | | | | | | +- size and date created -+ | +- file name and directory +- saveset number |
In order to restore a file, bring up the NTbackup program in Windows NT
and select the necessary files.
2.4.7.3 Example job
The following is an example of a typical remote WindowsNT backup job. Note the backup mode is 25 and the parameters are Windows style listings of directories to be backed up.
NT_REMOTE_BACK Comment = Demonstration of mode 25 Username = TJAMESON Last submit = June 16, 1997, 14:24 Last completed = June 16, 1997, 14:32 Job Log = Priority = 0 Flags = Remote,Media_Job,Cycle,NoHold,Keep, NoPrint,NoRestart Status = %x00000001 P1 = Queue = BWS$BATCH Backup mode = 25 Next media = 9019 Generations = 6 Required = 1 Media type = 4MM Up count = 14 Down count = infinite Owner = [TJAMESON] Protection = S:RWED,O:RWED,G,W Parameter (6) = "+node="isents"" (10) = "c:\dskpie95" (11) = "c:\scsi" (12) = "c:\scu" |
The RDB backup can be used to back up the contents of an RDB database that resides on a local device. The parameter list is a list of the RDB database files that are to be backed up with the job. This must include the complete path to the database files. Portions of databases can be designated by area using the following statements adjacent to the database file in the list:
A sample parameter list would appear as follows:
parameter(1) = "RDBFILES:DATABASE1.RDB" parameter(2) = "X:AREA3" parameter(3) = "RDB$FILES:DATA.RDB" parameter(4) = "I:FILES" parameter(5) = "RDB$FILES:DATAFILE.RDB" parameter(6) = "I:RESUMES" |
10 TCPware from Process Software Corp.11 MultiNet from TGV Software Inc.12 TCP/IP Services from Digital Equipment Corp.1 This procedure is designed for Task/Agent V3.0 or later. If V2.0 or earlier is detected, the procedure used to perform the backup will be from an earlier revision. If both versions are present then the BCKMGR P1 parameter is checked for either "TA" (Agent 3.0) or "XSOPENTASK" (Agent 2.0 or earlier) to decide which version to use.1 This procedure is designed for Task/Agent V3.0 or later. If V2.0 or earlier is detected, the procedure used to perform the backup will be from an earlier revision. If both versions are present then the BCKMGR P1 parameter is checked for either "TA" (Agent 3.0) or "XSOPENTASK" (Agent 2.0 or earlier) to decide which version to use. |
A list of 30 parameters can be associated with any BCKMGR job. These
parameters are text fields (up to 30 characters in each). They can be
used for anything that the backup mode processing routine supports. In
general they are a list of disk drives, directories or file names to
backup. Each of the processing routines look for various control
parameters. They are documented in the following sections. Certain
features are common to all the routines.
2.5.1 Specifying backup sources
Most of the time the parameter list specifies what is to be backup. A typical parameter can contain any of the following. Other items that can here are described in the subsequent sections.
A typical parameter is given below:
parameter(1) = "DISK$ISE0:" parameter(2) = "DISK$ISE2:[SYSMGR]" parameter(3) = "DISK$ISE3:" parameter(4) = "DISK$ISE4:[DB]SPECIAL.DAT" |
Previous | Next | Contents | Index |