Ref: 03250340
Title: Reviewing 3+ Backup/Restore Instructions and Parameters
Date: 1/15/88

Copyright 3Com Corporation, 1991.  All rights reserved.

This article discusses backup/restore information in the manuals
and applies only to 3+ Backup.

1) System level backup

All objects (server, disk partition, directory, subdirectory, and
files) that are backed up in system level can be restored only to
their EXACT origin. You cannot, for example, restore files or
directories that are backed up from drive C: to drive D:.

Command format:

I am going to use system level restore command to illustrate the
general command format. This format applies to the manuals for
both levels of the tape backup.

    restore [\\server][\drv:[\path\[file[.ext]]]] [/date=dd-mm-
    yy[,hh:mm]]

(See Tape backup Guide p/n:1943-00 page 8-13.)

The square brackets surrounding a parameter following a command
indicate that the parameter entry is OPTIONAL. If you choose to
enter the parameter, you must include //, or /, \, or the comma
signs that precede them as described in the command format.
Those signs are landmarks for the command parser in 3B, and
unfortunately the signs are confusingly similar to the 3+
signs. If you choose not to enter a parameter, the default value
will be used.

Some brackets are nested. This means that the nested or inner
parameter may not be entered by itself; it may only follow the
outer parameter. In other words, if you want to restore a file
in system level backup, you must supply \drv:\path\file.ext
parameters in the command line. And you type the command as
follows: restore \\servername\drv:\path\file.ext.

However, there is an easier way-- backup ? and restore ? commands
which prompt you for parameters.  (By the way, I tried to use
this restore command line but 3B did like my date entry.)

2) User level backup

The user level backup/restore is a wide open game. You can backup
and restore DIRECTORIES from a server/user to any server/user as
long as you have read and write access rights.

The example below illustrates the most general case.

   Server A:Domain A:Org A has 2 users - user1 and user2.
   Server B:Domain B:Org B has also 2 users - user3 and user4.
   Both servers have tape backup units.

User2 backs up all contents of user1's shareable directory called
Shr1_rwc. Here is how user2 does it from 3B:

BACKUP ? <cr>
SOURCE DIRECTORY: \\user1\Shr1_rwc <cr>
SOURCE PATH: <cr> (ie. wants everything in Shr1_rwc directory).
PASSWORD: password to access Shr1_rwc <cr>
FULL BACKUP: <cr> (ie. yes).
APPEND: <cr> (ie. no).
WHICH SERVER: <cr> (ie. login server A has a tape unit).

User2 gives the tape cartridge to user3 who then restores it into
user4's shareable directory called Shr4_rwc under subdirectory
called Frm_usr1.  Note: Frm_usr1 subdirectory does not exist yet;
the tape backup will create it.

Here is how user3 does it from 3B:

RESTORE ? <cr>
SOURCE DIRECTORY: \\user1:Domain A:Org A\Shr1_rwc <cr>
SOURCE PATH: <cr>
SOURCE FILE: <cr>
DESTINATION DIRECTORY: \\user4\Shr4_rwc <cr>
DESTINATION PATH: \Frm_usr1
PASSWORD: password to access Shr4_rwc <cr>
LIMITING DATE: <cr>
WHICH SERVER: <cr> (ie. login server B has a tape unit).

3) Full backup vs. incremental.

Full backup is obvious; just backup everything that is readable.
Incremental: the archive bit in the file descriptor is used as
the flag.  DOS and Ciosys both set this bit whenever the contents
of a file changes.  Backup looks at the bit; it backs up those
files whose archive bits are set, and resets them to 0.
