home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 29 Fixes_o
/
29-Fixes_o.zip
/
SU2CSD11.RME
< prev
next >
Wrap
Text File
|
1994-04-18
|
13KB
|
359 lines
SaveUtility/2 Corrective Service Diskette (CSD) 1.11
This Corrective Service Diskette (CSD) applies to SaveUtility/2
Version 1.1.
This READ.ME file contains the following sections:
SECTION 1 Directions for applying the contents of this CSD to
an existing SaveUtility/2 installation.
SECTION 2 Directions for using this CSD in conjunction with
your original SaveUtility/2 installation diskette to
re-install SaveUtility/2, including the contents of
the CSD.
SECTION 3 Problems fixed in this CSD.
SECTION 4 Differences between Version 1.1 and this CSD
(Version 1.11)
SECTION 5 Usage notes, including technical information about
restrictions, compatibility, and coexistence with
other products.
SECTION 1: CSD update
To apply the CSD to an existing installation:
1. Shut down your SaveUtility/2 system, including the Librarian and
Archiver(s)
2. Insert the CSD diskette into the diskette drive of your existing
SaveUtility/2 Librarian system. This procedure assumes that the
diskette drive is the A: drive, but it can be any drive.
3. Open an OS/2 command prompt window.
4. Make the Librarian directory the current directory. For example
if your librarian is called LIBA and it is installed on your D
drive, your current directory should be D:\LIBA
5. Type the following command:
a:\applycsd
6. If there were no errors, the CSD is now installed. The local
Subscriber has been updated. When other existing Subscribers back
up their workstations, the necessary parts of the code affected by
this CSD will be automatically downloaded to the Subscriber
workstation.
7. If, and only if, you are backing up to tape, add this line to your
Archiver profile:
TAPE_CAPACITY n
Where n is the capacity of your tape in millions of bytes. For
example, tape with a capacity of 250 million (250,000,000) bytes
should be specified as "TAPE_CAPACITY 250". A two gigabyte
(2,000,000,000) tape should be specified as "TAPE_CAPACITY 2000".
The Archiver profile is in the PROFILES subdirectory of your
Librarian directory. Its name is archiver.PRO where "archiver" is
your local name.
IMPORTANT: See "SECTION 5: Usage notes" for additional
information.
8. Recreate all Subscriber install diskettes you may be using. Do
not attempt to use a pre-CSD Subscriber install diskette after
installing this CSD. If you do, the installation will fail.
9. If possible, avoid restoring files to a particular workstation
before running its next backup. If you need to restore files and
for some reason cannot run the backup necessary to execute the
refresh of the Subscriber code, copy the contents of the \SAVEU2
subdirectory on the local subscriber on the Librarian workstation
onto a diskette, take the diskette to the affected workstation and
copy the files to its \SAVEU2 subdirectory, overwriting whatever
is there. This will have the same effect as the automatic code
update. The pre-CSD Subscriber code will not execute correctly
when backing up or restoring to/from a post-CSD Archiver/Restorer.
SECTION 2: Reinstallation with CSD
IMPORTANT: If you are using tape for your backups, see "SECTION 5: Usage
notes -- Filling up an Archiver Tape" for additional information BEFORE
YOU RUN YOUR NEXT BACKUP.
To completely reinstall SaveUtility/2 while applying this CSD:
1. Insert the CSD diskette into the diskette drive.
2. Open an OS/2 command prompt window, and type:
a:\install
(Substitute the appropriate drive letter if you are not using the
A: drive.)
3. Shortly, you will be prompted to insert your original
SaveUtility/2 Version 1.1 installation diskette. Follow
screen instructions from there.
See "SECTION 5: Usage notes -- Filling up an Archiver Tape"
when asked to specify your tape capacity.
4. Recreate all Subscriber install diskettes you may be using. Do
not attempt to use a pre-CSD Subscriber install diskette after
installing this CSD. If you do, the installation will fail.
5. Reinstall all Subscribers. If your Archive device is the same as
it was before you installed the CSD, your past backups will still
be valid. If you switched, for example to NovaBack, your old
backups are no longer usable.
SECTION 3: Problems fixed
The following problems have been corrected in this release:
o Cannot restore to the root directory from a MO drive archive
device.
o During interactive restore, "Restore to alternate path" failed.
o SU2UTIL error message 013 incorrect.
o Scroll bars in the interactive restore window do not work.
o Backups done rapidly, one after another, are lost.
o Unable to restore "read only" files.
o Restorer event log filling up with information-only messages.
o Error message 332 not set.
o Error message 387 occurring unnecessarily.
o The "iteration" keyword on SU2SCHED was not working.
o Restore request does not timeout at the specified interval.
o Option 5 on boot diskette menu not working.
o Pre-backup commands do not run before the backup.
o ACLs not backed up or restored.
o Archive bits not reset after DOS backup.
o "Sector not found" during DOS full-system restore.
o Logs not pruned as specified.
o Temporary Archiver .STA files not deleted.
o Redundant restore not working for FAT file system: DOS and OS/2.
o Directory not shown in interactive window.
o Boot diskettes missing SYSINSTX.COM.
o OS2KRNL missing from full backup.
o Mouse not enabled in Help screen under interactive restore.
o Boot diskettes do not work for HPFS386
o SYS3175 during interactive restore.
o "Restore to alternate path" drops ACLs.
o End-of-Tape not handled properly.
o Archiver cannot display tape backup amounts greater than one
gigabyte.
o SYS3178 during interactive restore.
o Temporary Subscriber .STA file not deleted.
SECTION 4: Differences from Version 1.1
This section describes changes to the product and publications that
have been made since Version 1.1 was produced.
Online Documentation
Information in Version 1.11 of the online documentation supersedes
information in Version 1.1 of the original printed manuals. In
particular:
o The online command reference for the SU2CRITF command is a
complete replacement for the same section in the SaveUtility/2
Handbook.
o The Handbook command reference for the SU2BDSK0 command is in
error. See the online version for corrections.
o The online version of the SU2RREQ command in the command reference
section has been revised to show function not described in the
Handbook.
o In Handbook Chapter 5: Restoring to a DOS Workstation.
- There is a new section describing how to restore files to a
directory other than the one from which they were backed up.
- Step 1 in the section Restoring One or More Files has been
replaced by three steps.
- The SU2RREQ command under Restoring One or More Files has been
changed.
- Restoring a Full System has changed and been split into two
parts.
o Handbook Chapter 7: Reviewing and Changing Profiles, has been
eliminated and the information consolidated in Chapter 9: Profile
Reference.
o In Handbook Chapter 8: Command Reference
- The SU2BDSK0 section has changed.
- Separate DOS and OS/2 descriptions of SU2RREQ have been
combined.
o In Handbook Chapter 9: Profile Reference:
- There is a new section for the DOS subscriber function profile.
SECTION 5: Usage notes
This section contains technical information about restrictions,
compatibility, and coexistence with other products.
FILLING UP AN ARCHIVER TAPE
Prior to this CSD, there was a risk of lost data if a backup was split
across two tapes.
Now, SaveUtility/2 compares a pending backup to the space remaining on
a tape volume and calls for a new volume if there is not enough
remaining space. However, it needs to know the size of your tapes.
To that end, there is a new parameter for your Archiver profile: the
TAPE_CAPACITY parameter.
To specify your tape size, ensure that your Archiver profile contains
this line:
TAPE_CAPACITY n
Where n is the capacity of your tape in millions of bytes. For
example, tape with a capacity of 250 million (250,000,000) bytes
should be specified as "TAPE_CAPACITY 250". A two gigabyte
(2,000,000,000) tape should be specified as "TAPE_CAPACITY 2000".
The Archiver profile is in the PROFILES subdirectory of your Librarian
directory. Its name is archiver.PRO where "archiver" is your local
name.
During a complete reinstall as described in "SECTION 2:
Reinstallation with CSD," SaveUtility/2 asks for the size of your tape
and uses your response to build the TAPE_CAPACITY parameter in your
Archiver profile.
If you do not provide a value (if you press ENTER without entering a
value, for instance) tape capacity defaults to 250 megabytes. If you
are using tapes larger than 250 megabytes, SaveUtility/2 will treat
them as if they were 250 megabytes and call for a new tape when it
believes it is nearing the end.
If, for this or any other reason, you need to change the TAPE_CAPACITY
parameter, edit your Archiver profile.
If you applied the CSD as described in Step 7 in "SECTION 1: CSD
update," you must manually edit your Archiver profile to add the
TAPE_CAPACITY parameter.
ATTENTION NOVABACK USERS
If you are running NovaBack, SaveUtility/2 requires changes to your
CONFIG.SYS:
o If there is not one already, add a BASEDEV statement for
OS2ASPI.DMD after the existing BASEDEV statements.
o If there is a DEVICE statement for NOVADRV.SYS, replace it with
one for NOVASPI.SYS.
These changes will not affect NovaBack, but SaveUtility/2 cannot
coexist with NovaBack without them.
DETERMINING THE SAVEUTILITY/2 RELEASE LEVEL
Sometimes, you might want to be absolutely sure that workstations and
archivers are all using the current version of SaveUtility/2 as
specified in the Librarian. There are two otherwise undocumented
commands that do this: SU2REFR and SU2REFA. Issuing SU2REFR from a
user's workstation or SU2REFA from an archiver workstation forces an
immediate, unconditional refresh of SaveUtility/2 on the respective
workstation
HANDLING ACCESS CONTROL LISTS (ACLS)
Access Control List support has changed with this CSD. The SU2TSN.ACL
module is no longer required. The SU2TSN.EXE transport module
contains all ACL processing logic. ACL processing is enabled by an
entry in the Subscriber customization file. To enable ACL processing
on Subscribers who are already installed, you must modify the
customization files of all affected Subscribers at the Librarian.
Edit the Subscriber.OS2 file in the Librarian\PROFILES subdirectory
and ensure that it contains the following line
SET ACLSUPPORT=YES
The customization file is processed by both the Backup and Restore
processes. The Build Boot Diskette function will detect the presence
of the HPFS386 File System and the diskettes will be configured to
support the HPFS386 File System.
ACLs will only be restored when the restore is being performed from a
system booted from the hard drive when full ACL support is present.
When the System is booted from diskettes built by SaveUtility/2, files
may be restored to any drive, however, ACLs will NOT be restored.
When performing a full system restore use the RESTACC utility provided
by OS/2 LAN Server to restore the ACLs.
When performing restores on a running system with local security is
enabled, a local logon must be performed prior to starting the restore
process. The logon ID must have Write and Create access to any and
all files and or directories to be restored. If restoring to a system
booted from diskette, local security must be removed and restored via
PREPACL and THIN386 utilities provided by the LAN Server. Otherwise,
SaveUtility/2 will respect local security and not move the data.
When restoring data to a running system, it is possible that the
existing data has ACLs and the incoming data also has ACLs. In this
case the incoming ACLs will be dropped. If you want the incoming ACLs
to be preserved then you must remove the existing ACLs before
performing the restore. This can be accomplished either via the OS/2
LAN Server panels or the command line invocation of NET ACCESS.