ITEM: DI5262L
Sysback Fix History 4.1.2
Question:
\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#
\# AIX System Backup & Recovery/6000 \#
\# Version 4 Release 1 Mod 2 \#
\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#
\# FIX HISTORY \#
\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#
\# The change history below indicates the specific fixes applied to the
\# current version/fix/mod level of Sysback. The last digit if the product
\# level is the FIX ID, and is incremented by 1 each time a new fix level is
\# released. Each fix level may contain more than one change. A fix level is
\# released when either a high severity fix is included or after a
\# number of low severity problems are accumulated.
\#
\# To tell whether a fix has been appiled, run "lslpp -h sysback.rte".
\# For trial intallations:
\# 04.01.0000.1005 = Ver 4 Rel 1 Mod 1 Fix 5
\# For product installations:
\# 04.01.1000.0005 = Ver 4 Rel 1 Mod 1 Fix 5
\#
\# The SEVERITY or TYPE of problem is indicated prior to each specific
\# fix. The codes are as follows:
\# 1 = Very High Severity. Fixes a problem which could potentially
\# cause data or system to be unavailabe until fix is applied.
\# Affects less customers than pervasive problems.
\# 2 = High Severity. Customers experiencing the problem would require
\# technical support assistance in a resolution, although the
\# problem does not pose potential data loss or system outage.
\# 3 = Medium Severity. Fixes a problem in a function which is not
\# working as expected but customer can continue working
\# normally.
\# 4 = Low Severity. This is usually a trivial fix which is not
\# noticed by most customers and is easily worked around.
\# C = Cosmetic fix only. Has no affect on program.
\# D = Documentation change.
\# E = Enhancement. Provides new or enhances existing function.
\# P = Pervasive! Fixes a bug that will strongly affect many customers
\# (i.e. fixes failure with installation process or a backup
\# problem that is not apparent until restore is attempted).
===========
SYSBACK.RTE
===========
FIX DATE SEV CHANGE DESCRIPTION(S)
=== ======== === =======================================================
0 08/05/97 Initial Release of modification level 4.1.2
Includes the following changes and enhancements not
available in prior mod levels:
2 Various potential problems verifying, restoring or
installing from virtual devices.
3 Permission problems prevented non-root users from
performing local or remote backups.
4 Progress indicator indicated incorrect megabytes when
reading or writing greater than 4 gigabytes. (sbpipelist)
4 Creating a network boot image failed at some AIX levels
if a network device did not exist. (mksbnetboot)
E Added "...backup successful" message output upon
completion of all high-level backup commands.
E New (-X) flag and SMIT option added to exclude all non-
non-JFS logical volumes from volume group backups
without the need to add each LV to the exclude list.
E Bigfile support and allocation group size values added
to system configuration report for AIX 4.2+ systems.
E Added ability to display both status indicator and
file list during verify and restores. Both are selected
by default from SMIT.
E Added output at beginning and end of all backups and
restores showing estimated MB, actual MB, start and
end dates and times, and number of volumes.
E Added ability to alert any process of a volume change
occuring during a backup, verify or restore. User
may set VOLPID environment variable to one or more
process IDs (i.e. "22811:34663"), and the processes
will be sent a SIGUSR1(30) signal when a tape reaches
end of volume.
E Added messages to SMIT menus that a user must be
logged on as root to use certain functions.
-------------------------------------------------------------------------------
============
SYSBACK.SBOM
============
FIX DATE SEV CHANGE DESCRIPTION(S)
=== ======== === =======================================================
0 08/05/97 - Initial Release of modification level 4.1.2
Includes the following changes and enhancements not
available in prior mod levels:
3 If user interrupts (CTRL-C) during backup, command
could hang trying to unmount temporary filesystems.
User could kill process, then use recovery option
to complete. (sbom_backup)
Support Line: Sysback Fix History 4.1.2 ITEM: DI5262L
Dated: August 1997 Category: N/A
This HTML file was generated 99/06/24~13:30:16
Comments or suggestions?
Contact us