Ref: 11640083
Title: Backing Up and Restoring Macintosh Files
Date: 8/30/90

Copyright 3Com Corporation, 1991.  All rights reserved.

If a switch-launched user is using MultiFinder and is working
from network volumes when backup occurs, the following Macintosh
files will be open and will not be backed up:

    * the resource fork of the system file
    * the resource fork of the finder file
    * the resource fork of the MultiFinder file

Also, if the user has an open mailbox under 3+ for Macintosh
Mail, the data fork of the mail index file will be open.

To avoid this problem, make sure Macintosh users are logged out
before a backup begins.  You can check backup logs for instances
of open files, in case other people are accessing a person's
files, and make sure those users are logged out the next time.
Beginning with 3+ 1.5, it is easier to check backup and restore
logs for error or warning messages because every message is
proceeded by "!!" (also noted at the top of the logs).  If you no
longer have a backup log, a tape log will have messages
indicating that a file was open at the time of the backup; for
example, "!! File truncated at offset 0."


Restoring Macintosh Files

To move Macintosh files successfully, close coordination with
Macintosh users is necessary.  For example, if you must use a
backup tape that shows that certain Macintosh fork files are not
present because they were open at the time of backup, then take
the following steps:

1.  Get the user to save current copies to another area.  This is
    vital for private user files and for customized system files
    with additional fonts and desk accessories.

2.  Restore the tapes.

3.  Do not allow access from a Macintosh user until you clean up
    the damaged version of Macintosh files and database:

    a.  From a PC, check the backup log information mentioned
        above as well as listings of Macintosh files.  Remember
        which DOS files correspond to a single Macintosh file.

    b.  If only one fork of a two-fork Macintosh file did not get
        to tape, delete the remaining fork, which will clean up
        the Macintosh database.

    c.  If there is only a single fork Macintosh file, use
        MACTOOL.EXE to delete the Macintosh database entry.

    d.  From a Macintosh, move saved versions of the files (from
        step #1) to the correct locations.

You may also need to copy over new Apple system files and delete
all references to the mail index file.  The next time the mailbox
is opened, 3+ for Macintosh Mail will rebuild the index.

A message buffer size of 2608 is recommended.
