ITEM: S5418L
Sysback Fix History 3.2.1.0 - 3.2.1.29 and 3.2.0.0 - 3.2.0.29
Sysback/6000 Version 3.2.1 is Production Code
Sysback/6000 Version 3.2.0 is Demo Code
\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#
\# AIX System Backup & Recovery/6000 \#
\# Version 3 Release 2 Mod 1 \#
\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#
\# FIX HISTORY \#
\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#
\# The change history below indicates the specific fixes applied to the
\# current version of Sysback. Each time a fix is applied, the last digit
\# (FIX ID) will be incremented by 1. This may be cosmetic or bug fix.
\#
\# To tell whether a fix has been appiled, run "lslpp -l sysback.obj" and
\# look at the last portion of the version number (i.e. 3.2.1.12 = "12").
\# Any changes listed below prior to and including this number have been
\# applied to the level installed.
FIX DATE DESCRIPTION
==== ======= =======================================================
0 2/9/95 Sysback Version 3.2.1 Initial Availability
1 2/21/95 Cosmetic changes:
a) LED "\< 0 >" appears if certain device code not
installed when performing anetwork boot. Changed to
"0 0 0" for consistency.
b) Listing available volume group backup image files
from SMIT only listed /usr/lpp/sysback/images contents
even if user added other directories to the imagelist
file. Now lists images in any directory specified in
in imagelist file.
2 2/21/95 Client not setup correctly for network boot if client
hostname also had aliases defined. Fix appled.
WORKAROUND: Edit the /etc/bootptab file and remove the
comma (,) which appears immediately after the client
IP address.
3 3/1/95 Syntax error in /usr/sbin/editvginfo program occurs if
on AIX version 4 when striped logical volume exists in
the volume group.
4 3/1/95 When creating full system backup from client to server,
the following errors may occur:
a) When creating full system backup on AIX Version 3,
error message displayed if \<8MB space available on
local system when backing up to a server. The space
checking should occur on server on AIX Verison 3.
b) Warning message displayed indicating client and server
are not at same release level, although both were the
same.
5 3/1/95 Device Configuration was not recovered from original
system when installing a client who was booted from a
network install server and the network install server
had never run a sysback full system backup.
6 3/2/95 getrootfs would not work when executed from a system
booted from a network boot server.
7 3/7/95 Fix \#5 above causes mkboottape to fail because rda
program is not found in /usr/lpp/sysback/inst dir.
8 3/7/95 Network boot failed at c28 LED when booting from
standard ethernet adapter on AIX 3.2 system.
9 3/7/95 Message "No install options available on the server"
appeared when performing remote tape installation and
multiple volume groups are to be installed.
10 3/23/95 Provided more detailed error message when number of
copies and logical partitions in device configuration
database does not match actual physical partition map
for a logical volume. Full system backup halts with this
error to prevent erroneous re-creation of the LV.
11 3/23/95 Installing a system from tape with multiple volume
groups may create the VGs in different order than
VG data is restored, resulting in data restored for
filesystems which had not yet been created.
If this problem occurs, you can continue through
install process and reboot in normal mode. Remove the
offending volume groups and recreate and restore the
volume group properly from the full system backup.
12 3/30/95 jfsrestore command fails on AIX Verison 4 with syntax
error due to -B flag being removed from restbyinode
command in AIX.
If necessary, customer can manually edit the jfsrestore
command and remove -B flag from all occurrances of
restbyinode command (do not remove on AIX V3 systems).
13 3/30/95 Errors when creating a bootable tape when backing up
from an AIX V3 system to an AIX V4 system. Caused by
inability to mount the /ethan (temporary) directory
when executing remote process. Since the bootable image
is not compatible with the backup anyway (warning
messages point this out), the process has changed so as
not to create a boot image at all when backing up from
AIX V3 to AIX V4 (and appropriate warning message is
displayed). This is not a problem when backing up from
AIX V4 to AIX V3 or from same to same.
14 4/3/95 The prompt: "7) Inter-PV policy:" should read
"6) Inter-PV policy:" when recreating a logical volume
or volume group on an installed system. This occurs only
when the LANG variable is set to En_US.
15 4/21/95 The prompt "7) Physical Volume list: (If specified,...)"
should read "7) Physical Volumes:" when recreating a
logical volume or volume group on an installed system.
This occurs only when the LANG variable is set to En_US.
16 4/21/95 getrootfs did not properly mount filesystems for
maintenance work after booting over the network from an
AIX Version 4 server.
17 4/21/95 When recreating a logical volume on an installed system,
you were unable to change the number of copies on a
3.2 system. Erroneous message indicated that you could
not change stripe size on a striped logical volume.
18 4/21/95 When recreating a logical volume, either on an installed
system, or during the installation process, multi-copy
logical volumes would only be created with one copy if
not enough disks were selected, even if user selected to
allow multiple copies on a single disk.
19 4/25/95 When fowarding a single image which spans more than 2
volumes, received message "Backup header on /dev/rmt0.1
does not match previous volume". Also reduce time
between checking that new volume has been inserted.
20 4/26/95 1) Could not boot a client machine from a network boot
server over a gateway. System LED stopped at 517. To
prevent this, new options for entering gateway address
and subnet mask added to mksbnetboot program and to
SMIT options for configuring network boot client.
2) Removed hardware adapter address option as this
is not needed to boot a standalone machine.
3) Allow entry of "ethernet" or "token-ring" for creating
network boot image and configuring network boot client,
even if adapter does not exist on the server. This allows
ethernet clients over a gateway to boot from a server on
a token-ring network and vice-versa.
21 5/8/95 Fix \#20 above produced the following error when executed
against a token-ring adapter:
"Invalid network device specified!"
If encountered, edit /usr/sbin/mksbnetboot, and change
line \#147 from "tr0" to "tok0".
22 5/8/95 Added a dummy password to the tapesvs user due to problems
with rsh command at some levels. This user id does not
allow login access, but rsh sometimes requires password
be set anyway.
23 5/8/95 Changed permissions on /usr/lpp/sysback/images and
/usr/lpp/sysback/bf directories to prevent users from
removing eachothers backup image files. Users could never
write over, but could remove others files.
24 5/11/95 Fix \#22 above did not work on all levels of rsh. Required
encrypted password. This problem will prevent remote
backups from being performed with one of the following
errors:
Permission Denied
Your encrypted password is invalid
25 5/24/95 Added support for 3480 & 3490 drives when attached to a
channel adapter.
26 5/26/95 LV names larger than 14 characters caused errors when
recreating volume groups or logical volumes. AIX allows
LV names up to 15 characters. Changed to allow unlimited
LV name size but only displays first 14 characters.
27 5/31/95 User recieves the message "Another boot image is currently
being created .. waiting ..". This message appears every
15 seconds forever. This occurs only after the user
typed CTRL-C when previously creating a tape boot image.
To remedy the problem, type the following:
mv /usr/lpp/bosinst/bi_main.sbsv /usr/lpp/bosinst/bi_main.
28 6/1/95 Hardcoded path for rsh command in all programs. This is
needed on systems with kerberos installed so all Sysback
commands call AIX rsh and not kerberos rsh.
29 6/1/95 Added Network Hardware Address option back into the
mksbnetboot command for configuring a network boot
client. Usnig the H/W address allows client system to
be booted from bootp screen without entering client
and server IP addresses as long as server and client
are on the same local network (i.e. no routes).
CHANGES FROZEN FOR 3.2.1
SEE 3.2.2 FOR FUTURE CHANGES
Support Line: Sysback Fix History 3.2.1.0 - 3.2.1.29 and 3.2.0.0 - 3.2.0.29 ITEM: S5418L
Dated: March 1995 Category: N/A
This HTML file was generated 99/06/24~13:30:36
Comments or suggestions?
Contact us