Ref: 14980001
Title: Tips for Installing and Using 3+Open Backup 1.0
Date: 05-17-89

Copyright 3Com Corporation, 1991.  All rights reserved.

With user-level security, 3+Open Backup allows users access to
three different interfaces.  BACKUP2, the menus interface, allows
OS/2 netstations to back up and restore 3+ and OS/2 servers.
BACKMAN, the command line interface of BACKUP2, can be used by
both OS/2 and DOS netstations.  3BACKUP, a unique command line
utility, allows both DOS and OS/2 netstations to use the server's
tape unit for backup and restore operations.

Most 3+Open Backup problems are caused by insufficient access to
either the backup server, the tape device, or the BACKINFO
subdirectory.  Following the steps below should eliminate most
error messages associated with improper access.

1.  Follow the installation procedures outlined in Appendix A of
    the 3+Open Backup Guide to make sure the tape server's name
    and password is added to each server to be backed up.

    Don't forget to add the backup server's name and password to
    itself.

2.  Assign all 3+Open Backup users read, write, create, delete,
    and attribute permissions to the BACKINFO subdirectory and
    the Tape sharename.

    Users must also have permissions for files to be backed up.

3.  When using BACKMAN and BACKUP2 use the NET ADMIN command,
    referring to the tape server's name, to log into the tape
    server.  For example:

    net admin \\tapeservername /c net logon tapeservername password

4.  Then link to OS2APPS (for BACKUP2) or FAMAPPS (for BACKMAN)
    using the NET USE command.

The four examples below illustrate the most common sequences of
3+Open Backup commands.  If errors occur when using these
commands, refer to appendix A of the 3+ Open Backup Guide for
proper setup instructions.


Example 1:  Full server backup of the tape server (Server2)

1.  Type NET ADMIN \\SERVER2 /C NET LOGON SERVER2 password to log
    in as the Backup server.  (For "password," substitute the
    appropriate password.)

2.  Type NET USE G: \\SERVER2\OS2APPS to link a drive letter to
    the OS2APPS or FAMAPPS sharename.  (In this example, the
    linked drive is G:.)

3.  Type BACKMAN BACKUP \\SERVER2 \\SERVER2\TAPE /S /W to change
    to the linked drive and begin the backup.  (/S=include
    subdirectories, /W=write files to log.)


Example 2:  Full server backup from Server1 to Server2 (the tape
server)

1.  Type NET ADMIN \\SERVER2 /C NET LOGON SERVER2 password to log
    in as the Backup server.  (For "password," substitute the
    appropriate password.)

2.  Type NET USE I: \\SERVER2\OS2APPS to link a drive letter to
    the OS2APPS or FAMAPPS sharename.  (In this example, the
    linked drive is I:.  Substitute FAMAPPS for OS2APPS as
    needed.)

3.  Type BACKMAN BACKUP \\SERVER1 \\SERVER2\TAPE /S /W to change
    to the linked drive and begin the backup.


Example 3:  Back up the sharename OS2APPS on Server1 to Server2
(the Backup server)

1.  NET LOGON the user with (R,W,C,D,A) access to the sharename.

2.  Type NET USE I: \\TEST_BUG\FAMAPPS to link a drive letter to
    the FAMAPPS sharename.

3.  Type BACKMAN BACKUP \\SERVERNAME\SHARENAME
    \\TAPESERVERNAME\TAPE /S /W to change to the linked drive and
    begin the backup.


Example 4:  Back up a local drive to Server2 (the Backup server)

1.  NET LOGON as yourself.

2.  Type NET USE I: \\SERVER2\TAPE to link to the tape.

3.  Type NET USE J: \\SERVER2\FAMAPPS to link a drive to the
    FAMAPPS sharename.

4.  (Optional)  Type BACKMAN REWIND \\TAPESERVERNAME\TAPE to
    rewind the tape.

5.  Type 3BACKUP C:\  I:\TAPE /S to begin the backup.  "C" can
    be substituted for any drive.

If you use "*.*" a tape error 31 can occur.  This command creates
a log file in the directory from which it was invoked.  Make sure
the user has proper permissions for this directory.
