Ref: 11640057 Title: Changes in 3+Backup from 1.0 to 1.5 Date: 2/21/90 Copyright 3Com Corporation, 1991. All rights reserved. 8/86 1.1 3BCKIN.BAT Fixed 1.1 3BCKIN.BAT so that Install works equally well on both 1.0 and 1.1 servers. 9/25/86 3BCKIN.BAT old 1.1 to 1.1.1 Made the interface conform with the other installation batch files. 10/15/86 BACKUP.EXE 1.1 to 1.1.1 Fixed the "unable to interpret tape format" error. Added the "see tape log" error message for the LCD if an error occurs during server-level backups or restores. 10/15/86 TDRIVE.SYS 1.1a to 1.1.1b Modified the time-out interval for searching to the end of recorded data to minimize "internal 5" errors that appear during append on a tape that is almost full. 10/16/86 TAPETEST.COM 1.1a created to diagnose hardware errors with tape drive units and controllers. Put on the 3+ Backup diskette. 10/17/86 TAPETEST.TXT 1.1 to 1.1.1 describing TAPETEST.COM changed to add the word "error" to the last sentence. 2/2/87 BACKUP.EXE 1.1.2a to 1.1.2b changed so that Restore first attempts to open a file. If there is an existing file on the disk and the open succeeds, then the restored file is written to the same physical locations on disk as before. This facilitates restore of certain position-sensitive files (copy protection files, IBMBIO.COM, etc.) Solves the "happy face" problem and the problem where 3BIO.COM is damaged when restore is cancelled. If the open fails, then the create is attempted. The restored file will be placed at an arbitrary location on disk. Also, when reading a file during backup or writing a file during restore, a check is made for the "lock violation" error code. During a backup, the locked file is simply skipped over and the backup continues. During a restore, a message "file access error; file in use" displays in the log and the restore is aborted. Restores may only be done when people are not using the system. 6/1/87 MAC 1.2.1b to 1.2.1c Fixed user-level restore problem when restoring to a root partition directory whose total DOS path length is longer than 64 characters. The fix does not affect server-level actions. 6/9/87 BACKUP.EXE 1.1.2 to 1.3a Allows for DMA switching between Backup and APPLE.SYS if Appletalk is installed as a secondary network on the server. 6/11/87 BACKUP.EXE 1.3a to 1.3b Fixed the EMS DMA switching problem that occurred when the 3+Backup server is running Ethernet as primary and Appletalk as secondary protocol. (A 2608 message buffer size was used, but 3+Backup defaulted to 4144 only.) 7/13/87 3BCKIN.BAT 1.1 to 1.2a Changed all occurrences of MKDIR to \3UTIL\CRDIR to prevent error messages from displaying when the directory already exists. 8/10/87 TDRIVE.SYS 1.2 to 1.3a Changed the write mode from non-buffered to buffered to facilitate streaming on 3Servers. 8/19/87 BACKUP.EXE 1.3d to 1.3e Changed the SCSI ID to be 7 for 3Server3s and 0 for 3S/400s. 8/21/87 3BCKCK.EXE 1.2.1a to 1.3a Modified to calculate the new size of the new BACKUP.EXE depending on whether or not the ETH driver is allocating receive buffers. 12/87 Copy protection removed for 1.2.1 and later. User-level backup option removed for 1.2.1 and later. 12/14/87 BACKUP.EXE 1.3 to 1.3.1a (Needed for definition of Macintosh file system support filenames.) Added MacFS support to open and search routines. New module added to stop compiler errors related to lack of memory. All "across net" backup changes in this module. Added ISMACDBF as new function. 12/16/87 TDRIVE.SYS 1.2.1 to 1.2.2a Changed to support 3S/40x tape expansion unit installed with the 3S/200 system. 12/16/87 TDRIVE.SYS 1.2.2a to 1.2.2 Fixed "debugger active" problem. 12/21/87 3BCKCK.EXE 1.3b to 1.2.2a (for 3S/20x and PC servers) and 3BCKCK.EXE 1.3b to 1.3.1a Goes with the newly submitted versions of BACKUP.EXE which increase the stack size from 2 KB to 3 KB. The two checkers, one for the 1.2.2 release and one for the 1.3.1 release, have the same resource file but are built slightly differently. 12/21/87 TDRIVE.SYS 1.3.1b to 1.3.1c Changed the request sense byte length from 27 to 26, because the 3Server DMA requires even numbers of bytes to transfer. 12/27/87 TTST3.COM 1.2.1 to 1.2.2a Created to help isolate hardware-related failures in the 3Server tape system. This version is modified to support 3S/40x tape expansion unit installed with the 3S/200 system. 12/87 3+Backup 1.3 New features: * On-line backup (using 3BMEN) and off-line backup * Ability to restore to a different directory or server * Ability to back up single or multiple partitions * "Verify after restore" feature (tape read after backup for data integrity) * On-line backups are about twice as fast (1.5-2 MB/minute, depending on buffers and on whether tape drive is on same server as the disk being backed up or is remote) * Power-fail support (to gracefully shut down all services and notify users that network is going down) 1/13/88 BACKUP.EXE 1.3.1a to 1.3.1b Fixed windowing problem related to transfer buffers and interface to 3+Share. Also fixed logging problems in which the value of 92 (MAXPLEN) was not being used globally. 1/21/88 TTST3.COM 1.3.1a to 1.3.1b Changed the request sense byte length from 27 to 28 because a 3Server's DMA requires an even number of bytes to transfer. 2/88 3+Backup 1.3.1 Supports 3+ for Macintosh. Supports off-line backup for 3S/20x and 3Servers. Provides menu-driven interface. Accepts different message buffer sizes to correct problem with backing up across the network when the buffer size is not 4144. 3+ Backup 1.2 (shipped with 3+ for Macintosh 1.2.1 release) ensured that hidden Macintosh file system database files on the server are backup up to tape. Previously, 3+Backup skipped over files that were open when it attempted to put them on tape. 3+ Backup version 1.2.2 Retries backup (100 times, one second apart) of Macintosh database files (which are never open long) and makes sure they contain the latest information when they are backed up. If a Macintosh database file is not backed up, then a message will appear in the backup log. A Macintosh file is implemented on the server as two DOS files that represents the data and resource forks. If a Macintosh client has one of the two forks open, then 3+Backup will save only half of a Macintosh file to tape. A record of this appears in the backup log. MacFS 1.3.1 and 3+Backup 1.3.2 The following information is correct for MacFS 1.3.1 and 3+Backup 1.3.2 and earlier: 3+ Backup treats hidden database files of Macintosh properties on 3Com servers as DOS files. Performing a backup of a Macintosh database that describes the state of other fields in a directory, changing the directory, and then restoring the database files can make the database inconsistent with the current state of the file system. Restoring an earlier Macintosh database may lose information on Macintosh files that were added after the backup. 3+Backup 1.3.2 (Shipped with 3+ for Macintosh 1.3.1 release) Always checks the backup and restore logs. Directory-level (not file-level) restore is the lowest level possible for the restoration of Macintosh files. 3+Backup chokes on DOS file names that have spaces in them. When a user creates the actual DOS files used to represent the Macintosh file on the server. If the Macintosh name is short enough to be a legal DOS name, then the DOS file that represents the data fork for the Macintosh file will have the same name. If the short Macintosh name has spaces in it, they will appear in the DOS file name, which 3+Backup cannot handle properly. If the user creates a Macintosh file name that is too long to be a legal DOS name, all spaces are converted to underscores (_) if they are to appear in the DOS file name. 2/8/88 BACKUP.EXE 1.3.1b to 1.3.1c Changed the stack size of the main server backup process from 2 KB to 3 KB, to eliminate server crashes when the directory lengths approach maximum size. Fixed the SMB transmit size so that it is not used for local backups; eliminates "file size different than expected" errors during local backups. 2/16/88 TDRIVE.SYS 1.3.1c to 1.3.1d Requires 5 KB memory to run. Set the forced streaming count parameter for MODE SELECT to zero to guarantee 150 MB capacity for backup. 2/16/88 BACKUP.EXE 1.3.1d to 1.3.1e Changed the routine that waits for a tape to be inserted in the drive at tape change point, so that it polls every second rather than every ten seconds. Also, it checks for the condition if TE_OK after a condition of TE_CNI. 3/1/88 3BMEN.EXE, 3BDOS.EXE, ONLCD.EXE, OFFLCD.EXE 1.3.1a 3S/200 and 3S/400. Added two programs, OFFLCD.EXE and ONLCD.EXE, to disable and enable the LCD driver. The programs are automatically run before running off-line backup. Two new programs, 3BDOS.EXE and 3BMENDOX.EXE, will run off LCD.EXE (the off-line backup program) and then the on-line ONLCD.EXE. 11/88 BACKUP.EXE 1.3.2 to 1.5 Made the on-line restore capability aware of the 3+ for Macintosh file database. The restore code now permits restoration of files and directories to non-empty directories that contain existing Macintosh files. The restore code is now aware of the internal structure of the 3+ for Macintosh database files so that merging database files in the target directories can be done with the database files on tape. The potential for loss of information is now far less likely to happen and the restore log will contain messages if any problems are detected. Directory-level (not file-level) restore is still the lowest level possible for the restoration of Macintosh files. Changes were made in error messages that appear in the logs. Fixed problem where a file open at time of backup (contents not put on tape) does not cause backup EOF (end of file) to occur on existing file when a restore from same tape occurs. Fixed problem where TAPE_LOG incorrectly associated a "truncated to 0" error message with a good file and did not list it. (Files are truncated to 0 if they are open at time of backup.) 4/14/89 BACKUP.EXE 1.5a to 1.5b Restores and merges Macintosh attributes if MacFS is not installed and displays "see tape log" at end of restore. Lists Macintosh file names on restores where no Macintosh files were previously present in the directory.