Virtual TapeServer 6.04.02 for NonStop Servers Release Notes
Resolved Issues and Enhancements | 8
checkbox is checked in the EMS Configuration page. In addition, the “Enable Host 
Notifications” option must be checked because this enables sending notices of any type to 
the host. (Use “ems_hsm_backup_notification='YES'” if manually editing vts.conf.) (TL-
2975)
Utilities
 Services that were started using the web interface are not restarted after logs 
are rotated. Previously, all processes started using the web interface were shutdown 
during the process of rotating logs. The processes were not restarted. (If the processes 
were started outside of the interface, they were not shutdown.) Now, the processes are 
restarted after the logs are rotated. (TL-3197)
 VTS no longer supports version 1 of the SSH protocol. Support for SSH v1 has been 
removed. (TL-3078)
 getVTS_dbginfo log size doubled after upgrade or downgrade. getVTS_dbginfo no 
longer gathers /tmp/vts* directories. (TL-2887)
 The vtmeta utility was called with the lock option and failed because cartridges 
were already locked. Log messages were logged in /var/log/httpd/error_log* and were 
similar to this: Error /VAULT00/P1/P10002: Unable to lock file. This no longer occurs. 
(TL-2574)
 SNMP messages cluttered the /var/log/messages file. Now, log messages from snmpd 
are directed to /var/log/snmpd.log by the syslog facility. (TL-2546)
 getVTS_dbginfo did not gather correct information for new version of GFS. This 
has been resolved and getVTS_dbginfo now correctly collects the data. (TL-2464)
 CLIM did not find correct inquiry data for devices if VTS was rebooted or the 
FC cable was disconnected. This caused the CLIM to lose the mapping for the VTDs 
after the CLIM or VTS was restarted. This has been fixed. (TL-2164)
Installation, upgrades, updates, downgrade, and restore
 Patch installation messages were not logged. Actions and status in the Software 
Code Change process are now added to the debug log for review by support personnel if 
needed. (TL-3030)
 Upgrade did not apply fixes. Previously, the upgrade did not apply fixes. Now, the 
6.04.02 upgrade file must be applied twice. The first time the upgrade is applied, it 
corrects an issue with the 6.04.01 VTS application. The second time it is run, VTS is 
upgraded. This is documented in the upgrade section of the Virtual TapeServer 
Operations and Administration Guide. (TL-2890)










