ITEM: DD5518L
Sysback Fix History 4.1.1.0 - 4.1.1.9
Question:
\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#
\# AIX System Backup & Recovery/6000 \#
\# Version 4 Release 1 Mod 1 \#
\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#
\# FIX HISTORY \#
\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#
\# The change history below indicates the specific fixes applied to the
\# current version 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 03/31/97 - Initial Release 4.1.
1 04/22/97 1 Network performance problem performing backups to
remote server. (sbclient)
2 SMIT error 1800-027 when verifying or restoring from
remote disk files - indicates no additional screens
available. (SMIT)
2 04/23/97 2 Error reading System Backup header when block size
of backup is not 512 and current block size is set
to 512. (readsbheader/sbread)
3 04/28/97 1 Error indicating "chdev" command not found when
performing system install onto previously unused disks.
(sysinstall)
1 Error restoring data from remote server during network
install. The / and /usr filesystems restored properly
and system is bootable, but restore of other filesystem
data failed. Data may be restored properly after booting
the system in normal mode and using SMIT. (sysinstall)
2 Network install cannot contact server after booting
from one network server and selecting to install from
another (sysnet).
4 Various temporary files not being removed from /tmp
directory on completion of File/Directory Backup.
(mkdirback)
4 Temporary file "*cmdfile*" not being removed from /tmp
directory if user terminates a backup or restore
process. (sbpipelist)
** FIX LEVEL 3 DISTRIBUTED TO ALL VERSION 4 CUSTOMERS **
4 04/30/97 3 User could not change intra-pv policy for an LV when
recreating or installing from backup.
(editvginfo/sysmain)
3 Adding a stripe size to a logical volume when recreating
a logical volume or installing a system did not create
a striped logical volume if the user omitted the 'K'
extension from the strip size. User interface was changed
so as NOT to include or require the 'K' extension,
but adds automatically before creating the LV.
(sysmakevg/remakevg)
3 File/Directory backup to a disk image file did not
exclude the backup file itself from the backup.
(mkdirback)
4 Sysback was not being removed at the end of the install
process if customer chose to do so. (sysinstall)
4 Incorrect message prompt for selection of terminal
type when installing using ascii display. (sysinit)
4 Change to frequency at which progress indicator is
updated during installation from remote device/file.
(sbpipelist)
4 Dont allow user to change PP size of a VG if installing
from a Power backup. (sysmain/editvginfo)
4 Dont allow user to select to use a PP map if striping
is also used. (sysmain/editvginfo)
5 05/26/97 3 remakevg command would not work correctly when executed
from command line when using a System Backup. Error was
"Cannot read table of contents from backup media!".
Worked correctly from SMIT or using all other backup
types. (remakevg/readsbheader)
3 Custom installation diskette containing a custom LVM
information file was not properly overriding the LVM
information on the install media. (sysinit/sysinstall)
4 remakevg process continues on error recreating a single
LV of filesystem and terminated wish successful return
code and message. Command will continue on error but
will terminate with message and non-zero return code.
(remakevg)
4 SMIT changed so as not to allow non-numeric input for
the backup sequence number. (SMIT)
6 06/12/97 4 Selecting to create boot tape only will continue
even if BOS Install Utilities are not installed.
Warning indicated that tape will not be bootable but
backup will continue. Process now fails in this case
when only creating a bootable tape. (mkboottape)
4 When configuring remote services, must wait after
stopsrc command for ypbind to terminate before
configuring sbnet user id. (cfgremsvs)
4 Permission of boot image, when created, set to 644 in
case user is using a non-default umask. (mksbnetboot)
4 Tape devices in 'defined' (not available) state were
still showing up in SMIT as backup options. (lsbackdevs)
3 Unable to verify the second backup when backups are
stacked onto a parallel virtual device. Error from SMIT
indicates "Unable to read table of contents from
device vdev0". Two problems:
1) sbdevice command was not properly reversing filemarks
on the secondary physical device(s) in the virtual device.
2) sysrestore command inadvertently rewound secondary
device(s) before attempting to read the header info.
(sbdevice/sysrestore).
7 06/16/97 2 Incorrect (untested) level of programs were applied to
fix \#6 above, causing syntax errors when creating a
bootable tape on AIX version 4 or when configuring remote
services. (mkboottape/cfgremsvs)
8 07/10/97 C If a failure occurs configufing the console during
a network boot, the LED would not display a value
indicating the error. (rc.boot)
E CHRP (Common Hardware Reference Platform) platform type
added to SMIT options. This is a common hardware
platform currently supportinf model F50 and future
RS6Ks (SMIT/sysback/mkvginfo/mkboottape/mksbnetboot)
E Add ability to boot or verify CHRP boot tapes.
(sysinstall/readsbheader/setbs)
4 If /usr/sbin directory not included in user's PATH,
some SMIT errors would occur indicating getlvminfo,
lsdev and lsjfs programs not found.
3 Filesystem backup failed with error indicating a
filesystem was not mounted if the logical volume name and
the filesystem mount point were identical. (mkjfsback)
3 Verbose (-v) flag with backup commands did not produce
filelist output as requested. (mkvgback/mkjfsback)
9 07/15/97 P Restoring select files or directories from a level 0
incremental filesystem or volume group backup will
inadvertently remove all files in the filesystem before
the restore. This should occur only when restoring all
files in the filesystem or volume group. If this occurs,
all files in the filesystem or volume group will need
to be restored from the backup. (sysrestore)
-------------------------------------------------------------------------------
============
SYSBACK.SBOM
============
FIX DATE SEV CHANGE DESCRIPTION(S)
=== ======== === =======================================================
0 03/31/97 - Initial Release 4.1.
1 05/26/97 3 If sbom_backup command started in the background using
'at' or 'cron' commands, command would terminate on
errors without resyncing the volume groups. If run in
background using '&' specifier, the command would hang
waiting for user input. New "-n" flag added to specify
that command is run in the background and no attempt
should be made to read from standard input.
(sbom_backup)
2 07/10/97 E CHRP (Common Hardware Reference Platform) platform type
added to SMIT options. This is a common hardware
platform currently supportinf model F50 and future
RS6Ks (SMIT).
Support Line: Sysback Fix History 4.1.1.0 - 4.1.1.9 ITEM: DD5518L
Dated: August 1997 Category: N/A
This HTML file was generated 99/06/24~13:30:16
Comments or suggestions?
Contact us