TapeWare 6.30 SP1B 13 February 2002
This document includes updated information for the documentation provided with TapeWare Version 6.30. The information in this document and in the Help system may be more up-to-date than the information contained in the printed manuals. Many of the issues outlined in this document will be corrected in upcoming releases.
1. Corrections in this
Service Pack
1. “Restored 0 files” when doing
Disaster Recovery under NetWare all versions
2. Extended partitions and Disaster
Recovery under Windows NT/2000/XP
3. “Building backup file selection list”
takes a long time
4. Windows XP/2000 Disaster Recovery
support for USB mouse
5. Disaster Recovery fails when a
Windows NT/2000/XP partition has not been formatted
6. “Operation completed” but no database
was restored
7. Service “hangs” on starting under
Windows 2000/XP
8. “error in loading shared libraries:
libncurses.so.4”
2. Accessing Online
Documentation
1. How to view or print the CD based
documentation
2. How to view WebHelp HTML based help
3. Linux Online Documentation/Help
1. Using multiple SCSI buses with
autoloaders
2. Increasing Device Buffer Sizes
4. Notes for Windows
NT/Windows 2000
1. Windows 2000 Service Pack 2 required
for Disaster Recovery Option
2. Windows 2000 Japanese Disaster
Recovery
4. Installing TapeWare on Windows
Terminal Server
5. Later phases of Disaster Recover on
Japanese systems is partly in English
6. Location of updated drivers
5. Notes for Windows
95/Windows 98/Windows ME
1. Later phases of Disaster Recover on
Japanese systems is partly in English
2. Limitations of the Windows 95/98
Disaster Recovery Module
1. Using NWASPI.CDM and Fibre Channel on
the NetWare operating system
3. Disaster Recover cannot find an
updated SCSI driver
4. Recovering mirrored partitions
7. Notes for
MS-DOS/PC-DOS/DR-DOS
1. TapeWare for DOS may not be able to
be installed from CD
1. Key prompts being cut from bottom of
screen
2. TERM= environment variable not
correctly set
4. Online help is not automatically
installed
5. Copying the installation program to a
local disk
6. TCP/IP may not see other TapeWare
servers
7. SCSI autoloaders may not be detected
12. TapeWare for Linux requires ncurses
version 4.0 or higher to function properly
On certain configurations of NetWare, disaster recovery would restore 0 files during phase 4. This was due to nwaspi.cdm not being correctly added to the autoexec.ncf which has now been fixed.
On certain partition configurations under Windows NT/2000/XP, extended partitions would be created incorrectly when using Disaster Recovery. TapeWare now restores these partition layouts correctly.
When building a backup selection list, TapeWare takes longer then usual to do so under windows. This was due to a routine which incorrectly opened a file twice, and added entries into the filter list twice causing the increased overhead during the selection list process. The routine has been fixed.
TapeWare Disaster Recovery now supports the USB mouse during phase 4 of Disaster Recovery under Windows XP/2000.
When a Windows NT/2000/XP partition has been created and not formatted, Disaster Recovery fails. This problem has been fixed.
Fixed and ambiguous completion code when a database restore operation is run on a tape which has no instance of a TapeWare database.
Enhanced the startup code so the TapeWare service starts faster under Windows 2000/XP.
Added a routine to automatically create a sym link from libncurses.so.4 to the proper version of libncurses on the user’s Linux machine.
After installing TapeWare, select Start|Programs|TapeWare|TapeWare Documentation|Printable Documents. In order to view or print this documentation, you must have the Adobe Acrobat v4.0 read installed on your system. If you do not already have this installed, you may install it from the TapeWare CD by selecting Documentation|Install Acrobat from the main TapeWare installation screen.
Use a Windows workstation to access the \DOC\language\ACROBAT subdirectory on the TapeWare CD where language is the localized language name. You must have the Adobe Acrobat v4.0 reader installed on your Windows workstation in order to view or print the documentation. The localized version of Acrobat Reader for Windows is also included in the Acrobat subdirectory in case you do not have Acrobat installed on your system.
You may also use the HTML formatted documentation from the \DOC\language\HTMLHELP subdirectory. The two files contained in the directory are identical. One is compressed with standard DOS/Windows PKZIP while the other is compressed with Linux GZIP and TAR. Copy this file over to a separate subdirectory on your hard disk, and decompress the file. Approximately 1600 files will be extracted which is the HTML version of TapeWare online help. To start the help system, use you browser to open the index.htm file. This will open the TapeWare table of contents and the opening pages.
HTML Web based help is included in the \DOC\lng\HTMLHELP\HTMLHELP.ZIP and HTMLHELP.TGZ. Both files are the same but zipped differently. The TGZ file uses Linux tar/gzip while the ZIP file uses standard WinZip. Unzip either of these files to your local hard disk and launch the index.htm file as the root of the Help tree.
To use the documentation system for the Linux X-Window based U/I, unzip either HTMLHELP.TGZ or HTMLHELP.ZIP to the “installation “directory\htmlhelp”. By default, this would be /usr/local/TapeWare/htmlhelp.
If your autoloader and the devices within the autoloader are connected to different SCSI buses, the driver may become confused as to which device is contained in the autoloader. If the drives and autoloader use the new SCSI-3 serial number detection protocol, all devices will be correctly assigned. However, if the autoloader supports only SCSI-2 protocol, you must connect the devices to the same SCSI bus as the autoloader, or manually configure the drivers as follows:
1. Run the administrator as you normally would. Note that names of the device and the autoloader. For this example, the loader will be “Ldr-2.0.3.0: ADIC Scalar” with the two devices being “Dev-3.0.3.0: DLT 4000” and “Dev-4.0.3.0: DLT 4000”.
2. Add a line in the .ini configuration file as follows:
[Ldr-2.0.3.0: ADIC Scalar]
device1=Dev-3.0.3.0: DLT 4000
device2=Dev-4.0.3.0: DLT 4000
3. Restart the service, if necessary, and the administrator as usual.
The default buffer size assigned to each device during read or write operations is 1Mb. The limit for this value has been increased from 32Mb to 256Mb. On high performance servers with enough available memory, you may change the buffer size on a device by device basis. To change all devices on the system, edit the TapeWare.Ini using a standard text editor. Under the [configuration] section, add the following line:
devBufferSize=n
where n is the buffer size in Kb. For example, to set the buffer size to 4Mb, uset devBufferSize=4096.
Setting this value higher can significantly enhance performance. This causes TapeWare to buffer more data in memory that is enroute to the tape device. By doing this, TapeWare can read larger amounts of data from the disk subsystems and fill the buffers faster. This has the effect of "smoothing" file sizes by taking advantage of larger files. However, setting this value too high will cause the operating system to "page" these data buffers to/from disk when accessed by TapeWare. This will significantly reduce the performance since additional disk operations will be required.
The original release of Windows 2000 has a problem with registry quotas. When running TapeWare to build a Disaster Recovery diskette set, CD-R or tape, the registry quota would soon become exhausted. For this reason, TapeWare checks the running version of Windows 2000 and specifically disables all Disaster Recovery functions if Service Pack 2 is not installed. To obtain this patch, follow this link to obtain SP2:
http://www.microsoft.com/downloads/release.asp?releaseid=29423&FeatList=3
(note that this URL is subject to change)
After the update is applied, TapeWare should recognize the new update and enable the Disaster Recovery option after it has been installed.
The fix mentioned above does not currently fix this problem when running Japanese Windows 2000. This problem has been reported to Microsoft.
TapeWare currently supports most Windows 2000 functionality. However, a couple of areas that are not supported:
1. If you use junction points, TapeWare will consider the junction as a complete volume, in other words, it will follow the junction point and backup all the files in the junction rather than simply backing up the metadata. If on restore, if the junction point is not mounted, TapeWare will create a subdirectory with the same name as the junction point and restore to the same disk that was previously hosting the junction point.
2. RSM – Remote/removable storage manager is not currently supported. If TapeWare is run, the RSM is temporarily disabled, TapeWare will allocate all tape device and tape loader devices, then RSM is restarted. This behavior will be changed in the next release of TapeWare.
3. The TapeWare Disaster Recovery option for Windows NT/2000 will support basic disk configurations only. If you attempt to restore your system with dynamic disks enabled, TapeWare will not be able to restore the volume information.
If you are running Terminal Server, you must install TapeWare as a service. This allows multiple user interfaces to share the common resources of the service.
The final phases of Disaster Recovery are not translated into Japanese. All other languages are supported, but the Japanese will be deferred to English. In addition, some non-English characters may be displayed as black boxes when displayed on the log screen. This is normal and can be ignored. All files will be recovered to the correct names.
The Windows Disaster Recovery requires all drivers to be located in the %SYSTEMROOT%\SYSTEM32\DRIVERS subdirectory. If you have a driver that is required to run your tape device or disk devices and it installs to a different location, put a copy of this driver into the DRIVERS directory.
The final phases of Disaster Recovery are not translated into Japanese. All other languages are supported, but the Japanese will be deferred to English. In addition, some non-English characters may be displayed as black boxes when displayed on the log screen. This is normal and can be ignored. All files will be recovered to the correct names.
TapeWare now supports Windows 95 and Windows 98 disaster recovery. Some limitations are present in the current release:
1. Protected-mode 32-bit disk drivers must control all disks and volumes. No real mode drivers are supported. You can determine if your system is using 32-bit drivers exclusively by right clicking on “My Computer” on your desktop and selecting the “Performance” tab. If any 16-bit real mode drivers are being used, Windows will indicate that your system is not optimally configured. This is common for most systems.
2. Compressed volumes using DriveSpace, Stac, etc. are not supported.
3. The tape device must also use a 32-bit protected mode driver. This is common for most SCSI and ATAPI controllers.
If all devices are not detected during auto detection, or devices are missing within the device explorer, make sure that you are loading NWASPI with the /LUN option as follows:
load NWASPI.CDM /LUN
This line is typically found in your STARTUP.NCF.
For systems using .HAM drivers, make sure that NWASPI.CDM is loaded from your AUTOEXEC.NCF or STARTUP.NCF. If not, the final phase of Disaster Recovery will not be able to access the tape device.
TapeWare searches for required drivers, first in the C:\NWSERVER directory, followed by the SYS:SYSTEM directory. If you update a driver, make sure the updated driver is also placed in C:\NWSERVER.
All mirrored partitions are now correctly initialized during the recovery procedure if a full system recovery is selected. To prevent any data loss on other partitions, mirror pairs are not automatically recreated if only the boot disk recovery method is used.
Under some versions of MSCDEX, it may be necessary to copy the \DOS directory to your local hard drive and install from there. The DOS4/G DOS extender will be unable to correctly link the strlen symbol. This is due to the DOS extender attempting to open the HPdosclb.dll file in read/write mode, which the MSCDEX does not allow.
TapeWare displays key prompts on the bottom of the screen using logical keys. The terminal you are using may map these keys differently on your keyboard. For example, for the Shift-F1 key, some keyboards drivers may map this as F11 while others will map this as Shift-F1. If this is the case, the TapeWare Shift-F1 maps to F11, Shift-F2 maps to F12, Shift-F3 maps to Shift-F1, etc. In addition, if your screen driver is setup for less than 25 rows, TapeWare will remove the bottom line of the screen.
Under Redhat Linux, when running the TapeWare character based interface under the xterm console in X-Windows, the screen may be corrupted. This is due to a bug in the console driver. You can correct this problem by using specifying the following command prior to starting TapeWare:
export TERM=xterm-color
You should install to the default /usr/local/tapeware directory. If you install to any other directory, you must manually enter the path name when upgrading, installing options or removing TapeWare as the installation program will not search for existing installations except in the default /usr/local/tapeware directory.
The online help is not installed by default since it is rather large. You may find the online documentation under the /doc directory on the CD. The documentation is in HTML format and can be viewed with the Netscape browser. See “Documentation”, section 1 above.
If you copy the installation files from the CD, make sure you mark the install and lin/HPunxins files with the eXectuable attribute.
Under some conditions, the Linux TCP/IP driver will not be able to display other Storage Servers on the TCP/IP network. Make sure that you have entered a valid TCP/IP default gateway, or specify the server address in the TapeWare host address dialog box during installation.
By default, most SCSI drivers under Linux do not enable LUN support, which is required to support integrated autoloaders. To enable LUN support on Linux, add the following line to the end of /etc/lilo.conf:
append= “max_scsi_luns=2”
After this line is added, make sure you run lilo to update the configuration with the following command:
lilo
After this is completed, reboot your system.
TapeWare for Linux can use IDE/ATAPI tape devices. If the Linux distribution has compiled the ide-tape.o module into the kernel, you need to add the one of the following lines to the end of /etc/lilo.conf:
append= “hda=ide-scsi” If your tape device is the master device on the primary IDE interface
append= “hdb=ide-scsi” If your tape device is the slave device on the primary IDE interface
append= “hdc=ide-scsi” If your tape device is the master device on the secondary IDE interface
append= “hdd=ide-scsi” If your tape device is the slave device on the secondary IDE interface
After this line is added, make sure you run lilo to update the configuration with the following command:
lilo
After this is completed, reboot your system.
Note: The current distributions that, during testing, we have found require these statements are:
RedHat 5.2
Corel Linux 1.0 and 1.1
SuSe 6.2
If you are upgrading from an earlier version of TapeWare, you must restart your machine so that the latest version of sgm.o would be loaded. You may also manually unload any running version of sgm.o by using the Linux rmmod command.
We recommend you to use CRT 3.0 from www.vandyke.com. Here are the steps you need to configure in order for the TapeWare to respond correctly:
1. Copy the mappings below and save them into a file called TapeWare.key
2. Select Session Options from the CRT's Options menu
3. Select the Emulation category
4. Select vt100 for the terminal
5. Check ANSI Color
6. Select Custom for the keyboard and enter full path to TapeWare.key
7. Select the Appeance category and use the vt100 font
Make sure you export the variable TERM to xterm-color using the command:
export TERM=xterm-color
On some systems, such as CorelLinux, xterm-color is not available so you must use xterm instead. Unlike xterm-color, xterm is only back and white.
You can also put "export TERM=xterm-color" in /etc/profile or ~/.bash_profile for permanent setting.
Key mappings placed in TapeWare.key:
N VK_INSERT "\e[2~"
N VK_F1 VT_PF1
N VK_F2 VT_PF2
N VK_F3 VT_PF3
N VK_F4 VT_PF4
N VK_F5 "\e[15~"
N VK_F6 "\e[17~"
N VK_F7 "\e[18~"
N VK_F8 "\e[19~"
N VK_F9 "\e[20~"
N VK_F10 "\e[21~"
E VK_INSERT "\e[2~"
S VK_F1 "\e[23~"
S VK_F2 "\e[24~"
S VK_F3 "\e[25~"
S VK_F4 "\e[26~"
S VK_F5 "\e[28~"
S VK_F6 "\e[29~"
S VK_F7 "\e[31~"
S VK_F8 "\e[32~"
S VK_F9 "\e[33~"
S VK_F10 "\e[34~"
When using IDE devices under Linux, make sure that
the module IDE-SCSI is loaded. If it is not loaded, you can load it by typing:
modprobe ide-scsi
Some of the newer Linux distributions may require a symbolic link to the version of libncurses in the library directory. If so, use the following command:
ln -sf /lib/libncurses.so.5 /lib/libncurses.so.4