Virtual TapeServer 8.3 Release Notes
Resolved Issues and Enhancements | 10
Resolved Issues and Enhancements
The following changes have been incorporated into the software since the 8.2 release.
Hardware, configuration, and hardware replacement
Bootup was delayed without Ethernet configuration or connection. If the
Ethernet was not configured, or in some cases, if there was no Ethernet cable plugged into
the appliance, bootup may have been delayed when bringing up the processes for the web
interface. This is no longer an issue. (TL-6552, EAR-7648)
The 3ware RAID card did not follow the schedule set for disk verification. The
3ware card would run disk verify at times other than scheduled which could cause some
performance degradation. This issue was resolved by updating the RAID controller
firmware. Version 8.3 checks, and if necessary automatically updates 3ware RAID card
firmware. (TL-7894, EAR-9075, EAR-9494, EAR-9497)
The 2Gb Fibre channel card would lock up and stop communicating. This
occurred when the 2Gb Fibre channel (FC) driver failed to acknowledge a message from
the 2Gb FC card. The message from the card is now acknowledged. (TL-8024, EAR-9484)
Changer was not detected with 8Gb NPIV on AIX 6.1 Power 7. This issue has been
resolved. It is no longer necessary to rescan for VTL devices after initial discovery to find
library devices. (TL-7139)
A syntax error occurred when setting hostname using netconfig when DHCP
was configured. The following error was displayed when setting the hostname using
netconfig if DHCP was configured: “Syntax error on line 1 of /etc/http/conf.d/
server_name.conf”. This error is no longer reported. (TL-7656)
Upgrade, downgrade, and reinstallation
The sysbackup file listed in the upgrade log was not always correct. The variable
that was used to hold the sysbackup filename during upgrade processing was sometimes
incorrectly overwritten, which resulted in the wrong sysbackup name being listed in the
upgrade log. This was a logging issue only and did not affect functionality. This issue has
been resolved. (TL-6150)
Version was updated even though upgrade fails. If an upgrade fails, the system
might have displayed the incorrect version. This was misleading. The system will now
display an error message, informing the user that the upgrade failed and to downgrade.
(TL-6180, EAR-7386)
Reverting to a previous version might have reverted the system to an
unexpected version. The upgrade process determined the version to revert to by
checking the timestamps of all system backup images in the /home/bill directory and
reverting to the last (newest) backup image in that directory. If the timestamps had been
changed on the backup images due to touching or moving the images, the wrong image
may have been used to revert. This has been resolved, the system now keeps track of the
filename of the backup image during an upgrade and will report an error if that file
cannot be found. (TL-6152, EAR-7329)