Virtual TapeServer 8.3 Release Notes
Resolved Issues and Enhancements | 15
 Instant DR did not check vaults when checking for duplicate files. Instant DR 
incorrectly copied the same file into different vaults if the same cartridge exists in the 
same pool in multiple vaults. The vault name should have be added to the duplicate check 
(it only checked the cartridge and pool). The vault name is now checked for as well as the 
cartridge and pool. (TL-7452, EAR-8585) 
Data Encryption (SecureVTS)
 Virtual Tape Details page reported a virtual tape as unencrypted when it was 
encrypted. The Virtual Tape Details page would display that a virtual tape was 
unencrypted when it was encrypted. This has been corrected. (TL-8030)
Clustering (GFS)
 Unmigrating a virtual tape might have failed in a GFS environment if the 
migrate was performed on a different node in the GFS cluster than the node 
which performed the unmigrate. This has been resolved. (TL-7572, EAR-8787)
Utilities and services
 The script used to obtain file system usage did not use the correct tool. The script 
used to get file system usage used the system utility df, which was correct for non-gfs 
storage, but systems that use gfs should use gfs_tool instead. The tool will now check the 
type of storage in use and use the appropriate tool. (TL-6788, EAR-9039) 
 Postgres logs filled up with RMDR errors. RMDR is not supported on VTS systems. 
The RMDR error messages are no longer created. (TL-7591)
Documentation and help
 A device that is disabled then disconnected will not appear on the Physical 
Device Settings page. A device that is disabled, and then disconnected from the VTS 
will no longer appear on the Physical Device Settings page. This information has been 
added to the Help page for the Physical Device Settings page. (TL-7791)
 Instructions for inserting blank tapes into a library have been improved. The 
online help has been updated to improve the instructions for inserting blank tapes into a 
library for stacked export. (TL-7810)
 Documentation of web user passwords correctly listed $ as acceptable but it 
would fail if used. Commonly used characters in passwords were not allowed. For 
example, if you used a $ (dollar sign), the web interface password was not set correctly 
and the account was either removed from the list of available accounts or had no password 
at all. The commonly used characters are now allowed. (TL-7588, EAR-8813)










