TapeWare 6.30 SP3B 5 December 2002 This document includes updated information for the documentation provided with TapeWare 6.30. In addition to addressing Service Pack 3B (SP3B) issues, it also addresses some issues from SP2B and SP3A. These issues are grouped by service pack. The information in this document and in the online help system may be more current than the information contained in the printed manuals. Many of the issues outlined in this document will be addressed in upcoming releases. Note General TapeWare corrections and new features appear in sections 2 and 3. Platform-specific corrections and new features appear in each platform's section (sections 5 through 9). 1.ACCESSING ONLINE DOCUMENTATION 2 1.VIEW OR PRINT DOCUMENTATION 2 2.ACCESSING ONLINE HELP 3 3.INSTALL AND ACCESS HTML HELP 3 2.GENERAL NEW FEATURES 3 1.UPGRADING TAPEWARE ALSO UPGRADES INSTALLED OPTIONS 3 2.AUTOPRINT LOG 4 3.TAPEWARE WORKGROUP FOR WINDOWS LICENSE AVAILABLE FOR UP TO 10 WORKSTATIONS 4 4.JOB LOG NOW INCLUDES SLOT AND BARCODE INFORMATION FOR AUTOLOADERS 4 5.TAPEWARE NOW SUPPORTS AUTOMATIC INSTALL 4 6.TAPEWARE'S SMTP CONNECTOR CAN NOW EMAIL JOB LOGS THAT ARE LARGER THAN 64KB 5 3.GENERAL CORRECTIONS 5 1.SIMPLE 5-TAPE BUILT-IN SCHEDULE CHANGED TO CREATE A FULL BACKUP FOR EACH DAY 5 2.TAPEWARE NOW ASKS FOR A CORRECT TAPE AFTER IT EJECTS A FULL TAPE 5 3.TAPEWARE WOULD OCCASIONALLY HANG WHEN A MEDIA BECAME FULL DURING LARGE BACKUP JOBS 5 4.INCREMENTAL AND DIFFERENTIAL JOBS NOW BACK UP DATABASE OBJECTS 5 5.TAPEWARE NOW CORRECTLY MANAGES BACKUP JOBS IN INSTALLATIONS THAT USE MULTIPLE TAPE DRIVES 5 6.TAPEWARE NO LONGER SETS THE LOADER STATUS TO `NOT ACTIVE' DURING STARTUP 6 7.TAPEWARE NOW BACKS UP AND RESTORES SYMBOLIC LINKS PROPERLY 6 8.MICROSOFT EXCHANGE CONNECTOR APPEARS ON THE TAPEWARE DATABASE TAB 6 9.FILTERING FOR A SINGLE MEDIA NOW WORKS PROPERLY 6 10.STREAM SYNC ERRORS NO LONGER OCCUR ON SYSTEMS WITH 1GB RAM OR MORE 6 11. STANDARDIZED FILENAME FOR DISASTER RECOVER CD IMAGE 6 12.DISASTER RECOVERY ON SYSTEMS USING A PAGE FILE LARGER THAN 2GB 6 13. DISPLAYS MEDIA NAME DURING JOB 6 14.ERROR 514: END OF DATA ERRORS WHEN BACKUP JOB SPANS MORE THAN ONE MEDIA 6 4.GENERAL NOTES 7 1.WINDOWS .NET INITIATIVE 7 2.USING MULTIPLE SCSI BUSES WITH AUTOLOADERS 7 3.DEVICE BUFFER SIZES 7 4.TAPEWARE LOADS CUSTOM DEVICE DRIVERS 7 5.WINDOWS NT/2000/XP 8 1.TAPEWARE RESTORES FILES EVEN IF THE WINDOWS ADMINISTRATOR CANNOT ACCESS THE OBJECT 8 2.TAPEWARE MAKES SURE THE USER CAN ACCESS A WINDOWS CLUSTER 2000 SERVER DRIVE 8 3.CORRECTED ISSUE WITH UNICODE SEPARATOR CHARACTERS 8 4.USB TAPE DRIVE SUPPORT FOR WINDOWS 2000/XP 8 5.TAPEWARE NOW SUPPORTS ENCRYPTING FILE SYSTEM BY DEFAULT 8 6.DYNAMIC DISKS AND DISASTER RECOVERY FOR WINDOWS 2000/XP 8 7."FILES NOT TO BACK UP" FEATURE ENABLED 8 8.WINDOWS 2000 SERVICE PACK 2 REQUIRED FOR DISASTER RECOVERY 9 9.TAPEWARE OFFERS LIMITED SUPPORT FOR WINDOWS NT/2000/XP DIRECTORY JUNCTIONS 9 10.WINDOWS 2000/XP REMOVABLE STORAGE MANAGER CONFLICTS WITH TAPEW ARE 9 11.PREVENTS SIMULTANEOUS BACKUP OF IS AND DS IN MICROSOFT EXCHANG E SERVER 5.5 9 12. MEMORY LEAK WHEN BACKING UP MICROSOFT EXCHANGE 2000 SERVER 9 13. DISASTER RECOVERY AND MICROSOFT EXCHANGE SERVER 2000 10 14. INSTALLING TAPEWARE ON WINDOWS TERMINAL SERVER 11 15. LANGUAGE TEXT DISPLAY ON LATER PHASES OF DISASTER RECOVERY 12 16. NEW MINIMUM REQUIREMENTS FOR WINDOWS NT 4.0 12 17. DISASTER RECOVERY FOR WINDOWS 2000 SMALL BUSINESS SERVER 12 6.WINDOWS 9X/ME 12 1.LANGUAGE TEXT DISPLAY ON LATER PHASES OF DISASTER RECOVERY 12 2.DISASTER RECOVERY LIMITATIONS 13 3.TAPEWARE OPERATES RELIABLY ON WINDOWS 95 SYSTEMS 13 7.NOVELL NETWARE 13 1.TAPEWARE DISASTER RECOVERY REQUIREMENTS FOR NETWARE 6 13 2.TAPEWARE DOES NOT BACK UP THE NSS ADMINISTRATION VOLUME BY DEFAULT 13 3.TAPEWARE AND NSS PARTITIONS LARGER THAN 4GB IN NETWARE 6 13 4.TAPEWARE COMPLETES PHASE 3 OF DISASTER RECOVERY IN NETWARE 6 INSTALLATIONS 13 5.UPDATED NETWARE INSTALLATION GUIDE 13 8.MS-DOS/PC-DOS/DR-DOS 14 1.TAPEWARE FOR DOS MAY NOT BE ABLE TO BE INSTALLED FROM CD 14 9.LINUX 14 1.DISASTER RECOVERY FOR LINUX 14 2.UPDATED LINUX INSTALLATION GUIDE 14 3.SGM MODULE AND KERNEL VERSIONS BELOW 2.2.14 14 4.LINUX SYMBIOS SCSI DRIVERS NOT FUNCTIONING PROPERLY 14 5.TAPEWARE TAKES LESS TIME TO LOAD 15 6.USING IDE DEVICES UNDER LINUX 15 7.TELNETING FROM WINDOWS 15 10.UNIVERSAL SERIAL BUS (USB) 16 1.USB 2.0 VS. USB 1.X 16 2.USING MULTIPLE USB TAPE DRIVES 17 3.SUPPORTED USB TAPE DRIVES 17 4.INSTALLING THE CORRECT ONSTREAM ADR2.60USB DEVICE DRIVER 17 1. Accessing Online Documentation 1. View or print documentation After installing TapeWare, you can view or print any of the following user guides on a Windows or Linux (X Windows) computer: ú TapeWare User's Guide and Technical Reference (TWusr<lng>.pdf) ú TapeWare Error Code Reference (TWerr<lng>.pdf) ú TapeWare Linux and NetWare Installation Guide (TWapp<lng>.pdf) - English only ú TapeWare Addendum (TWadd<lng>.pdf) - English only Note: The TapeWare Linux and NetWare Installation Guide has been updated for this service pack. (<lng> represents the three-letter language identifier, e.g., eng for English.) These documents are located in the /doc/<lng>/acrobat subdirectory on the TapeWare installation CD. Note: You can also download these documents from the TapeWare website. To view or print this documentation, Adobe Acrobat or Acrobat Reader (version 4.0 or higher) must be installed on your Windows or Linux (X Windows) computer. If not currently installed, you can install Adobe Acrobat Reader from the /doc/<lng>/acrobat subdirectory on the TapeWare installation CD. Note: You cannot view or print the TapeWare documentation on DOS or NetWare systems because they are not supported by Acrobat Reader. Windows - Adobe Acrobat On Windows systems, TapeWare installs the listed documents onto your computer. Then you can access them directly from the Start menu: Start | Programs | TapeWare | TapeWare Documentation | Printable Documents | <document name>. You can also install Adobe Acrobat Reader version 5.0 from the Start menu: Start | Programs | TapeWare | TapeWare Documentation | Printable Documents | Install Adobe Acrobat v5.0. Linux (X Windows) - Adobe Acrobat TapeWare does not install the listed documents onto your Linux (X Windows) computer. You must manually access or copy them from the TapeWare installation CD. Also, you can install Adobe Acrobat Reader from the /doc/<lng>/acrobat subdirectory on the TapeWare installation CD. Note: The Linux (X Windows) version of Adobe Acrobat Reader is only available in English. 2. Accessing online help Windows - Winhelp You can access both the online help system and context-sensitive help from most TapeWare screens. ú Select Help topics from the Help menu at the top of the screen. The main help screen appears. ú Press F1 or click the Help button. The help topic associated with the screen appears. ú On many screens, you can click the ? button in the top right corner. The mouse pointer changes to the help pointer. When you click a screen item, more information appears. DOS/NetWare/Linux - Onscreen You can access online help from most TapeWare screens. Simply press F1. 3. Install and access HTML help You can install the HTML help version of our online help system. Then you can access it with a web browser. Please note that TapeWare will not access HTML help topics. To install HTML help on a Windows computer, copy htmlhelp.zip from the \doc\<lng>\htmlhelp subdirectory on the TapeWare CD. Use WinZip or some other file extraction software to unpack it onto your Windows computer. To install HTML help on a Linux (X Windows) computer, copy htmlhelp.tgz from the \doc\<lng>\htmlhelp subdirectory on the TapeWare CD. Use Linux tar/gzip or some other file extraction software to unpack it onto your computer. Note: The HTML help system requires the Java Plug-in. Internet Explorer users must enable it. Netscape offers to install the plug-in if it is not installed. Note: For best results on Linux systems, we recommend that you upgrade to Netscape v6.x. Note: You can also download the HTML help system from the TapeWare website. To launch HTML help, use your browser to open index.htm. 2. General New Features Note: Platform-specific new features now appear in each platform's section. We have added the following new features: -------- SP3B -------- 1. Upgrading TapeWare also upgrades installed options When upgrading from an earlier service pack, the TapeWare installer now upgrades all installed options, whether they are licensed or not. You no longer have to reinstall your various options. For example, some customers may have been evaluating an option. When they ran the SP3A update, it only updated the licensed options automatically. Unlicensed options, such as the SMTP connector, were not updated automatically. 2. TapeWare now supports disaster recovery for DRTape drives TapeWare now includes support for tape drives using DRTape. This feature lets you create bootable tapes to simplify the disaster recovery process. -------- SP3A -------- 3. Autoprint Log TapeWare can now be configured to print the log file automatically as soon as the backup, restore or verify job is finished. You can specify the printer and its settings, including page range and number of copies. You can assign different printers to different users or groups. You can also enable the Autoprint log feature for specific jobs. Refer to Chapter 2 - Autoprint Log in the TapeWare Addendum. Note: In this service pack, this feature is only implemented for Microsoft Windows and Linux (X Windows) systems. 4. TapeWare Workgroup for Windows license available for up to 10 Workstations TapeWare Workgroup for Windows is now available with a 10- workstation license. This license is ideal for our Workgroup users who need to use TapeWare on more than five workstations. 5. Job log now includes slot and barcode information for autoloaders The job log now includes slot and barcode information for autoloaders in the media section of the log. For jobs with multiple tapes, the log lists the slot and barcode information for each tape. -------- SP2B -------- 6. TapeWare now supports automatic install You can now create a custom setup file in order for TapeWare to install itself with limited user action. 1. Create a file called autoinst.inf, as follows: ;------------------------------------------------------ ; Auto install options ;------------------------------------------------------ [license] document=3DE7FEF9-C7AFE3E7 [configuration] serviceInstalled=Yes regComp=CompanyName regUser=UserName createZone=Yes zone=TapeWare storage zone node=ComputerName targetDir=c:\Program Files\TapeWare or SYS:TWADMIN or /usr/local/tapeware protocol=Tcp Each of these variables represents an input field that appears during normal installation. Replace the values to the right of the equal sign to your specific requirements. Enter your key code in the document variable. Enter the appropriate target directory for your platform in the targetDir variable. Note: The key code that appears above is an evaluation key code. 2. Place this file in the appropriate installation folder, i.e., \win, \net or \lin. 3. Run the TapeWare installer. 7. TapeWare's SMTP connector can now email job logs that are larger than 64KB Many times a job log will be larger than 64KB. However, the SMTP connector would limit the log to 64KB. Now you can specify the maximum size of an email. To change the maximum log size, add the following lines to the TapeWare.ini file: [smt] sizeLimit=n Enter the maximum size in bytes in place of n. For example, to set the size limit to 1MB, replace n with 1048576. The default is 65536. 3. General Corrections Note: Platform-specific corrections now appear in each platform's section. In addition to resolving several minor issues, we have corrected the following: -------- SP3B -------- 1. Simple 5-tape built-in schedule changed to create a full backup for each day Now the simple 5-tape built-in schedule creates a full backup for each day it runs. Previously, it created one full and four differential backups. 2. TapeWare now asks for a correct tape after it ejects a full tape Previously, if you selected Append to all or Append to first tape, overwrite others for the Write mode for a backup, TapeWare correctly ejected the tape when it was full. Then it prompted you to re-insert the same tape. Now TapeWare asks for either a new tape or a tape that is not full. 3. TapeWare would occasionally hang when a media became full during large backup jobs Some customers reported that TapeWare would occasionally hang when a media became full. This occurred during large backup jobs. TapeWare now handles large backups and full media conditions correctly. 4. Incremental and differential jobs now back up database objects TapeWare now correctly back up database objects during incremental and differential backup jobs. 5. TapeWare now correctly manages backup jobs in installations that use multiple tape drives In installations with more than one tape drive, TapeWare tries to use all available drives. When a backup job starts, it determines whether or not it needs a second drive. Customers with this type of configuration could experience either of the following problems: ú TapeWare allocates two or more tape drives for the job. The first drive contains a tape, but the second drive is empty. As the job runs, TapeWare asks the user to insert a tape in the second drive. If the user clicks Abort, which temporarily removes the drive from the job, TapeWare would hang. Now, TapeWare runs the job correctly in this scenario. ú The media in the first drive becomes full, so TapeWare ejects the media. Then it continues backing up to the media in the second drive. When it runs the verification step, an error message occurs because the media is no longer loaded in the drive. Now, TapeWare will not eject the first media until it fills the media in the second drive. -------- SP3A -------- 6. TapeWare no longer sets the loader status to `Not active' during startup If TapeWare completes its initialization before the loader has finished initializing, TapeWare no longer sets the loader status to `Not active'. 7. TapeWare now backs up and restores symbolic links properly At times, the target file for a symbolic link (shortcut) may be moved or deleted. Now TapeWare properly backs up and restores these symbolic links. 8. Microsoft Exchange Connector appears on the TapeWare Database tab In Exchange 2000 installations, the Microsoft Exchange Connector would not appear on the TapeWare Database tab after it had been installed. Now it appears correctly on the Database tab if Exchange 2000 is installed. 9. Filtering for a single media now works properly Previously, TapeWare filters would improperly select additional media, even if you selected only one media on the Selection Filters screen. Now, if you select a specific media, the filters only search the items that are stored on that media. TapeWare does not ask for additional tapes. 10. Stream sync errors no longer occur on systems with 1GB RAM or more Some users experienced stream sync errors on systems with 1GB RAM or more. Now TapeWare computes the device buffer size correctly on these systems (see Device buffer sizes below). 11. Standardized filename for Disaster Recover CD image The default filename for the Disaster Recover CD image file is now BOOTCD.ISO on all platforms. On Windows and Linux (X Windows) computers, you may change this filename before creating the image file. 12. Disaster recovery on systems using a page file larger than 2GB Previously, TapeWare would fail during disaster recovery on systems with a page file that was larger than 2GB. Now, disaster recovery temporarily disables the use of page files during phases 3 and 4. 13. Displays media name during job TapeWare creates long paths whenever you run a custom schedule. In previous versions, you could not see the media name because the path name was too long for the screen space. TapeWare now replaces a portion of the path name with `.' For example: Media - Home\Admin Folder\Server_RC1\Zone1\daily4 now appears as Media - Home\Admin Folder\...\daily4 14. Error 514: End of Data errors when backup job spans more than one media In some installations, when a backup job spans more than one media, users could encounter Error 514: End of Data when restoring or verifying objects that were written near the end of the media. This problem will no longer occur on any future backups. However, users may still encounter this error with backups that were made with earlier service packs. 4. General Notes -------- SP2B -------- 1. Windows .NET initiative Yosemite Technologies, Inc constantly improves TapeWare and our plan for the future of TapeWare. Part of this is to make sure our product takes advantage of the latest and greatest technologies. For this reason, we have integrated the Windows portion of TapeWare with the new Microsoft .NET compiler. As a result, this version of TapeWare is a faster, smarter and more robust backup solution for you from Yosemite Technologies, Inc. 2. Using multiple SCSI buses with autoloaders If your autoloader and its devices are connected to different SCSI buses, please see Multiple SCSI buses with autoloaders in the updated TapeWare Linux and NetWare Installation Guide. Refer to Accessing Online Documentation above for more information. 3. Device buffer sizes To maintain optimal performance, TapeWare uses device buffers. It sets a default buffer size, which it allocates evenly between each device attached to your computer. For example, if two devices are attached and the buffer size is 32MB, TapeWare allocates 16MB to each device. The default (recommended) device buffer size is 25% of physical memory. If this amount is 32MB or more, TapeWare sets the buffer size to 32MB. If the 25% is not exactly equal to 16MB, 8MB, 4MB, 2MB or 1MB, TapeWare sets the buffer size to the next lower setting. For example, if 96MB is installed, 25% is 24MB, which is not one of the options. TapeWare sets the buffer size to the next lowest setting: 16MB. Setting this value higher can enhance performance, especially if more than two devices are attached to your system. TapeWare can buffer more data in memory by reading larger amounts of data from the disk at a time. However, do not set the buffer size to exceed available system memory or your performance will decrease due to excessive disk operations. To change the device buffer size, update the following line in the Device performance tuning section of the TapeWare.ini file: ;devBufferSize=n Enter one of the following in bytes in place of n: 262144 (256MB), 131072 (128MB), 65536 (64MB), 32768 (32MB), 16384 (16MB), 8192 (8MB), 4096 (4MB), 2048 (2MB) and 1024 (1MB). If you enter a different setting, TapeWare sets the device buffer size to the next lower of these options. For example, if you enter 32000, TapeWare sets the device buffer size to 16384 (16MB). Now, erase the semi-colon at the start of the line, as follows: devBufferSize=n Note: Setting device buffer size above 32MB per device will not improve performance. 4. TapeWare loads custom device drivers TapeWare comes with customized drivers. It automatically loads these drivers (SCSI and ATAPI/IDE only) when you start the TapeWare administrator or service. If you have a SCSI tape drive, you must uninstall its device drivers. (Do NOT uninstall the device drivers for the SCSI controller.) If you have a USB device, refer to Universal Serial Bus (USB) below for more information. 5. Windows NT/2000/XP -------- SP3B -------- 1. TapeWare restores files even if the Windows administrator cannot access the object The Windows NT/2000/XP file system lets you restrict access to specific files and folders. In some installations, users restricted access by the Windows administrator, which affected TapeWare's ability to restore these restricted files. TapeWare now restores these files. Note: For legal reasons, Microsoft recommends against restricting Windows administrator access to any file or folder in any business, corporate or other organizational environment. 2. TapeWare makes sure the user can access a Windows Cluster 2000 server drive Due to a Windows 2000 change, TapeWare now verifies a user's access to each drive on the Windows Cluster 2000 server before continuing. As a result, TapeWare performance has improved. 3. Corrected issue with Unicode separator characters Unicode separator characters no longer affect TapeWare operation in some non-English Windows installations. -------- SP3A -------- 4. USB tape drive support for Windows 2000/XP TapeWare now supports USB tape drives under Windows 2000/XP. See Universal Serial Bus (USB) below for more information. 5. TapeWare now supports Encrypting File System by default The Encrypting File System (EFS) lets users encrypt and decrypt files to keep their files safe from intruders. TapeWare now supports this Windows 2000/XP feature by default. To disable EFS, change the following line in the [configuration] section of the TapeWare.ini file: efsEnable=No To enable it again, change No to Yes. 6. Dynamic disks and Disaster Recovery for Windows 2000/XP The TapeWare Disaster Recovery option for Windows 2000/XP supports all disk configurations except those with dynamic disk partitions. 7. "Files not to back up" feature enabled TapeWare now automatically enables the "files not to back up" feature under Windows NT/2000/XP. This feature lets you select files to exclude from the backup. The Windows registry key is: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet\Control\BackupRestore\FilesN otToBackup To disable this feature, add the following lines to the TapeWare.ini file: [Ods-File System Connector] filterRegExclude=No To enable it again, change No to Yes. 8. Windows 2000 Service Pack 2 required for Disaster Recovery Due to problems with registry quotes in the original Windows 2000 release, TapeWare checks your version of Windows 2000. If the Windows 2000 Service Pack 2 is not installed, it disables all Disaster Recovery functions. Access the following webpage link to download the Windows 2000 Service Pack 2: http://www.microsoft.com/downloads/release.asp?releaseid=29423&Fe atList=3 Note: This Internet address may change without notice. After you install the Windows 2000 service pack, TapeWare should enable Disaster Recovery. 9. TapeWare offers limited support for Windows NT/2000/XP directory junctions TapeWare offers limited directory junction support in Windows NT/2000/XP. Directory junctions are also known as volume mount points. If you use these junctions in your installation, TapeWare treats each directory junction as a basic folder. During backup, TapeWare only saves the basic access control list (ACL) for each directory junction. It does not back up the metadata, which is the descriptor block that tells Windows where the directory junction is mounted or linked to. As a result, during restore, TapeWare does not re-create the directory junction as it originally existed. Instead, it is restored as a simple folder with its original ACL. Access the following link for more information on directory junctions: http://support.microsoft.com/default.aspx?scid=kb;en-us;Q262797 10. Windows 2000/XP Removable Storage Manager conflicts with TapeWare If the Windows 2000/XP removable storage manager (RSM) feature is enabled during TapeWare operation, it generates messages in the Windows Event Log. These messages state that the TapeWare and RSM services have not started even though they have. For this reason, TapeWare disables RSM by default. If your system requires RSM, you can enable it by changing the following line in the [configuration] section of the TapeWare.ini file: disableRSM=No Then you must re-enable RSM on the Component Services screen under Windows. 11. Prevents simultaneous backup of IS and DS in Microsoft Exchange Server 5.5 Microsoft Exchange Server 5.5 does not support simultaneous backup of the information store (IS) and the data store (DS). TapeWare no longer lets you set up multiple streams when backing up this version of the Exchange server. 12. Memory leak when backing up Microsoft Exchange 2000 Server When you back up a Microsoft Exchange 2000 server, the server may experience a memory leak during the job. This is a Microsoft problem, which is fixed in Microsoft Exchange 2000 Server Service Pack 3. Whether or not you experience this problem, we recommend that you download and install the service pack. Access the following link for more information and to download the service pack: http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q314952 Note: Per Microsoft, this update requires Microsoft Exchange 2000 Server Service Pack 2. Note: Before installing any Exchange 2000 service pack, refer to Compatibility between different Microsoft Exchange 2000 service packs under Disaster recovery and Microsoft Exchange Server 2000 below. 13. Disaster recovery and Microsoft Exchange Server 2000 The previous TapeWare connector for Microsoft Exchange Server 2000 let you back up individual information stores instead of a whole storage group. This caused problems with disaster recovery. During disaster recovery, Exchange would try to play back logs from databases that were backed up separately. These logs would refer to non-existent databases. To solve this problem, storage groups are now identified as objects. Now you will back up and restore each storage group as a single entity. Disaster recovery procedure In the event of a disaster, use the following general steps to recover your Microsoft Exchange 2000 databases. a.Perform the general system-level disaster recovery to restore the basic system data. b.Restore the Windows active directory: 1.When the Starting Windows screen appears during bootup, press F8. 2.Select Directory Services Restore Mode and press Enter. 3.Log in to the system. 4.Access TapeWare. 5.Create a restore job. 6.Select Windows Active Directory for the restore job from the list on the Selection tab. 7.Run the restore job. 8.Exit TapeWare. 9.Restart the computer, letting Windows 2000 load normally. c.Verify that the various Microsoft Exchange services are loaded and running. d.Access Microsoft Exchange | System Manager from the Start menu. e.For each storage group to be restored, dismount and change the properties for each database: 1.Right-click the database within the storage group. A popup menu appears. 2.Select Properties. The Properties screen appears. 3.Select the Database tab. 4.Select This database can be overwritten by a restore. 5.Click OK. 6.Right-click the database again. A popup menu appears. 7.Select Dismount Store, if the option is available. 8.Click Yes to confirm. The database is dismounted, which means it can be restored. f.Exit the System Manager. g.Access the Exchsrvr subdirectory on the computer, e.g., c:\Program Files\Exchsrvr\mdbdata. h.Delete all database and log files associated with each storage group to be restored. Do NOT delete the actual subdirectories. Note: If you do not have a default installation, use the exchange system manager to locate and delete the following files: ú Log file (.LOG) for each storage group. ú Exchange database (.EDB) for each database in the storage group. ú Exchange streaming database (.STM) for each database in the storage group. i.Restore the Microsoft Exchange MTA database: 1.Access TapeWare. 2.Create a restore job. 3.Select Microsoft Exchange 2000 Server for the restore job from the list on the Selection tab. 4.Select Queued Messages (MTA) from the list on the Selection tab. 5.Run the restore job. 6.Exit TapeWare. j.Start the MTA service: a.Right-click My Computer on the desktop. A popup menu appears. b.Select Manage. The Computer Management screen appears. c.Expand the Services and Applications folder. d.Scroll down and right-click on Microsoft Exchange MTA Stacks. A popup menu appears. e.Select Start. f.Close the Computer Management screen. k.Restore the appropriate Exchange databases: 1.Access TapeWare. 2.Create a restore job. 3.Select Microsoft Exchange 2000 Server for the restore job from the list on the Selection tab. 4.Run the restore job. 5.Exit TapeWare. l.Mount the Exchange databases for each storage group that you restored: 1.Access Microsoft Exchange | System Manager from the Start menu. 2.Right-click the database within the storage group. A popup menu appears. 3.Select Mount. The system mounts the database. 4.Click OK. 5.Exit the System Manager. Restoring instances from backups created with earlier versions of TapeWare If an error 617 occurs when restoring Microsoft Exchange, you have selected old instances of Exchange for restoring. By default, you cannot restore your old backups. If you selected the old instances by mistake, simply deselect them in the restore job. Their icons are marked with a black X on a yellow dot. If you want to restore the old instances: a.Add the following line to the [msExcServer] section in the TapeWare.ini: restoreOldFormat=Yes. b.Stop and restart the TapeWare service. c.Restore from the old tapes: 1.Access TapeWare. 2.Create a restore job. 3.Deselect the new storage group objects from the list on the Selection tab. 4.Select the old storage group objects from the list on the Selection tab. 5.Run the restore job. 6.Exit TapeWare. e.When you finish restoring your old instances, either remove the restoreOldFormat=Yes line from the TapeWare.ini or change the line to restoreOldFormat=No. Then stop and restart the TapeWare service. Compatibility between different Microsoft Exchange 2000 service packs Microsoft changed the internal backup format for Exchange 2000 databases in Service Pack 2 (SP2). Consequently, you cannot restore backups that were created under Service Pack 1 (SP1) or earlier. Likewise, you cannot restore SP2 and later backups to SP1 or earlier computers. Access the following link for more information: http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q316794 Access the following link for information on available Microsoft Exchange service packs: http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q301378 14. Installing TapeWare on Windows Terminal Server Windows Terminal Server lets you configure individual workstation computers as terminals to the server. To install TapeWare in this environment: 1.Log on as the administrator; otherwise, you cannot install the software. 2.Access the command prompt. 3.Type user change /install. This locks out other users during installation. 4.Install TapeWare according to the installation instructions in Chapter 2 - The TapeWare Workplace in the TapeWare User's Guide and Technical Reference. 5.During installation, be sure to select .run TapeWare as a service. 6.After installation, log off. Then the other users can access the Terminal Server again. 15. Language text display on later phases of Disaster Recovery The final phases of Disaster Recovery in Windows installations are not displayed in Japanese. Due to font problems, these screens appear in English on Japanese installations. However, all files will be recovered with their correct names in their correct locations. The final phases of Disaster Recovery in all other languages display correctly. Also, during the final phases of Disaster Recovery, some non- English characters may display as black boxes on the log screen. You can ignore this. It will not affect file names and locations. 16. New minimum requirements for Windows NT 4.0 The Microsoft Foundation Class Library (MFC 7.0) that TapeWare uses has new dependency requirements. As a result, the minimum requirements for TapeWare have changed for Windows NT 4.0 users. TapeWare now requires the following: ú Microsoft Windows NT Service Pack 6a, which includes the new Active Accessibility dynamic-link library (oleacc.dll). ú Microsoft Internet Explorer 4.x or above, which includes the common controls dynamic-link libraries (shlwapi.dll). 17. Disaster Recovery for Windows 2000 Small Business Server After performing disaster recovery on a Windows 2000 Small Business Server, you cannot use the Small Business Server console tools. Microsoft registers the short path names for the SBS program files (DLLs) in its registry instead of long path names. To resolve this problem, run the following from the command prompt immediately after a disaster recovery: regsvr32 "c:\program files\microsoft backoffice\Management\BOMsnap.dll" regsvr32 "c:\program files\microsoft backoffice\Management\BOHome.dll" 6. Windows 9x/Me -------- SP3A -------- 1. Language text display on later phases of Disaster Recovery The final phases of Disaster Recovery in Windows installations are not displayed in Japanese. Due to font problems, these screens appear in English on Japanese installations. However, all files will be recovered with their correct names in their correct locations. The final phases of Disaster Recovery in all other languages display correctly. Also, during the final phases of Disaster Recovery, some non- English characters may display as black boxes on the log screen. You can ignore this. It will not affect file names and locations. 2. Disaster Recovery limitations While TapeWare supports most Windows 9x/Me functionality, it has the following limitations: ú Protected-mode 32-bit disk drivers must control all disks and volumes. Real mode drivers are not supported. To determine if your system uses only 32-bit drivers: a.Right-click the My Computer icon. A popup menu appears. b.Select the Performance tab. If any 16-bit real mode drivers are in use, Windows indicates that your system is not optimally configured. This is common for most systems. ú The tape device must use a 32-bit protected mode driver. This is common for most SCSI and ATAPI controllers. ú TapeWare does not support the use of disk compression software, such as DriveSpace or Stac. 3. TapeWare operates reliably on Windows 95 systems TapeWare SP2B did not operate reliably on Windows 95 systems. This was due to new minimum requirements for Windows 95 systems and the Windows .NET initiative (see Windows .NET initiative above). Now, TapeWare works reliably on Windows 95 systems after you install the required Microsoft Active Accessibility (MSAA) patch. Use the following link to download this Microsoft patch: http://www.tapeware.com/ftp/servicepacks/63sp2b/msaardk.exe Note: Microsoft no longer supports Windows 95. As a result, this workaround is only available in English. Users with non-English versions of Windows 95 should not install this patch. 7. Novell NetWare -------- SP3B -------- 1. TapeWare Disaster Recovery requirements for NetWare 6 In NetWare 6 installations, you must install NetWare 6 SP1 to support TapeWare Disaster Recovery. 2. TapeWare does not back up the NSS administration volume by default The NSS administration volume is dynamic, being created at system startup and updated each time it is accessed. Therefore, TapeWare does not back it up by default. This volume's name changed with NetWare 6, causing TapeWare to back it up by default. This has been corrected, so that TapeWare no longer backs up either NSS administration volume by default: NSS_ADMIN under NetWare 5, _ADMIN under NetWare 6. 3. TapeWare and NSS partitions larger than 4GB in NetWare 6 Now TapeWare properly restores NSS partitions that are larger than 4GB under NetWare 6. 4. TapeWare completes Phase 3 of Disaster Recovery in NetWare 6 installations In some NetWare 6 installations, TapeWare could Abend the server during Phase 3 of Disaster Recovery. Now this phase finishes properly in these installations. -------- SP3A -------- 5. Updated NetWare installation guide For this service pack, we have updated the TapeWare Linux and NetWare Installation Guide. In addition to general updates, we have added material that was previously in the release notes. Refer to Accessing Online Documentation above for more information. 8. MS-DOS/PC-DOS/DR-DOS -------- SP3A -------- 1. TapeWare for DOS may not be able to be installed from CD Under some versions of MSCDEX, it may be necessary to copy the \DOS directory from the TapeWare CDROM to your local hard drive and install from there. The DOS4/G DOS extender will be unable to correctly link the strlen symbol. The DOS extender may try to open the TWdosclb.dll file in read/write mode, which MSCDEX does not allow. 9. Linux -------- SP3A -------- 1. Disaster Recovery for Linux TapeWare can now perform disaster recovery in Linux installations. In addition to the standard TapeWare disaster recovery features, TapeWare also supports Hewlett-Packard's One- Button Disaster Recovery (OBDR) on Linux systems with OBDR- enabled tape drives and autoloaders. Refer to Chapter 3 - Linux Disaster Recovery in the TapeWare Addendum. 2. Updated Linux installation guide For this service pack, we have updated the TapeWare Linux and NetWare Installation Guide. In addition to general updates, we have added material that was previously in these release notes. Refer to Accessing Online Documentation above for more information. 3. SGM module and kernel versions below 2.2.14 On systems with kernel versions below 2.2.14, TapeWare automatically loads and uses the sgm module that comes with the software. sgm offers additional features that are required by TapeWare, but not provided by older versions of sg. If your kernel is version 2.2.14 or higher, you may ignore the included sgm module. TapeWare uses the sg module that comes with Linux. To identify the version of your Linux kernel, use the following command: uname -a 4. Linux Symbios SCSI drivers not functioning properly A problem with the Linux SCSI Generic (sg) module causes it to incorrectly determine the direction of dataflow in Symbios SCSI cards. As a result, a message similar to the following may appear: kernel: sym53c1010-33-1-<3,0>: extraneous data discarded. kernel: sym53c1010-33-1-<3,0>: COMMAND FAILED (89 0) @dfe17000. When the SCSI card driver tries to use this information, it becomes confused and information is lost, which triggers the extraneous data discarded error message. Please note that this is not a TapeWare problem. It is a problem with the Linux SCSI Generic (sg) kernel module (sg.o). Choose one of the following to resolve this problem: ú Install a different SCSI card that works properly with Linux. ú Find out from your Linux distributor when they will change the sg module to accommodate the latest Symbios driver. ú Compile the latest sg.o drivers for the current version of the Linux kernel yourself. Note: Yosemite Technologies, Inc only provides this information as a service to our customers. We assume no liability for the driver or end-user failure. To fix this problem, you must rebuild the SCSI Generic (sg.o) driver for the Linux kernel. Your Linux distributor typically performs this complicated procedure. If you perform this procedure, we recommend that you test the result on a non- production machine in case if the steps are performed incorrectly. Access the Linux sg.o kernel patch at http://gear.torque.net/sg/p/sg3123.tgz. Access the SCSI Generic site at http://gear.torque.net/sg/. Access the Linux kernel HOWTO at http://www.linuxhq.com/ldp/howto/Kernel-HOWTO.html. To apply the kernel patch: a.Obtain your kernel source code as described in the Kernel HOWTO. b.Apply the SCSI Generic source code to the kernel source as described under SG Device Driver downloads on the SCSI Generic site. c.Compile the new patched kernel as described in the Kernel HOWTO. d.Install the new kernel as described in the Kernel HOWTO. -------- SP2B -------- 5. TapeWare takes less time to load TapeWare decreases its load time by only scanning for five SCSI hardware devices instead of 26. However, if your machine has more than five SCSI hardware devices, you need to modify the configuration file so TapeWare can scan for all of them. Simply update the following line in the [configuration] section of the TapeWare.ini file: maxScsiDevices=n Enter the number of SCSI devices in place of n. 6. Using IDE devices under Linux To properly manage IDE tape drives under Linux, TapeWare uses the IDE-SCSI command to link the IDE device to a SCSI identifier. If an IDE CDROM is installed, this command links the device from /dev/cdrom to /dev/scd0. As a result, you may not be able to access the CDROM. To re-link the CDROM to /dev/cdrom, execute the following command from the command prompt: ln -sf /dev/scd0 /dev/cdrom Note: You only have to execute this command once. 7. Telneting from Windows For TapeWare to respond correctly in CRT, follow these steps: a.Copy the mappings below and save them into a file called TapeWare.key b.Select Session Options from the CRT's Options menu. c.Select the Emulation category. d.Select vt100 for the terminal. e.Check ANSI Color. f.Select Custom for the keyboard and enter full path to TapeWare.key. g.Select the Appearance category and use the vt100 font. Make sure you export the variable TERM to xterm-color using the command: export TERM=xterm-color If xterm-color is not available on your system, use xterm, which only supports back and white. You can also add export TERM=xterm-color to the /etc/profile or ~/.bash_profile as a 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~" 10. Universal Serial Bus (USB) -------- SP3B/SP3A -------- 1. USB 2.0 vs. USB 1.x The tape drives listed below are designed for USB 2.0, which operates at an increased device-to-PC speed to 480Mbps (about 40 times faster than USB 1.1). Unfortunately, most computers currently ship with onboard USB 1.x ports. If you connect your new tape drive to a USB 1.x port, the device-to-PC speed decreases to the USB 1.1 speed of 12Mbps. Therefore, we recommend that you install a USB 2.0 adapter card with its drivers. Then your system can take full advantage of USB 2.0 performance. We have confirmed USB 2.0 functionality on USB 2.0 adapters with the NEC chip. These adapter drivers include nusbd.sys and nehcd.sys. Note: Even though some newer computers implement USB 2.0 on their motherboards, we still recommend that you use a USB 2.0 adapter card for proper operation. 2. Using multiple USB tape drives TapeWare can support up to 15 USB tape devices, but its performance depends on server resources, including number of CPUs and amount of memory. Therefore, we recommend that you only attach one or two USB tape drives to a server. 3. Supported USB tape drives TapeWare now supports the following USB tape drives under Windows 2000/XP: ú OnStream ADR2.60usb ú Seagate Travan 40 ú Seagate Travan 20 Note: TapeWare only supports USB tape drives under Windows 2000/XP. All TapeWare features are available for these drives, including Disaster Recovery. These features are only limited by the TapeWare edition and installed options. For an OnStream ADR2.60usb drive, install the drive hardware according to the manufacturer's documentation. Then refer to Installing the correct OnStream ADR2.60usb device driver below to install the correct hardware device driver. For a Seagate Travan 40 or 20 drive, install the drive according to the manufacturer's documentation. You do not have to install any special device drivers. Once installed, the USB tape drive should appear under "port0" on the TapeWare Device tab. Note: TapeWare is not "Plug and Play" aware. If you attach or detach a tape drive, you must restart the TapeWare service. Otherwise, TapeWare will not recognize the device configuration change. Refer to the TapeWare Users Guide and Technical Reference for more information about restarting the service. 4. Installing the correct OnStream ADR2.60usb device driver When you install an OnStream ADR2.60usb tape drive, your computer may install the wrong device driver. Therefore, you must install the OnStream USB tape driver (ADR2K.sys) before starting TapeWare. The ADR2K driver is located in the /Drivers subdirectory on the TapeWare CD that ships with the OnStream ADR2.60usb tape drive. You can also download the driver from the OnStream website (http://www.onstreamdata.com/support/win_drivers.shtml). Before you proceed, identify the location of the driver. Then connect the tape drive to the computer and power it on. Finally, refer to the appropriate instructions below: Windows 2000 or Windows XP. Windows 2000 To install the OnStream ADR USB Driver for Windows 2000, follow the steps below. a.If the Insert Disk screen appears, insert the TapeWare CD and click OK. After the system installs the drivers, skip to step 1 in step e below. b.Access the Hardware tab on the System Properties screen: 1.Right-click My Computer. A popup menu appears. 2.Select Properties. The System Properties screen appears. 3.Select the Hardware tab. c.Run the Hardware wizard: 1.Click the Hardware Wizard button. The Add/Remove Hardware Wizard screen appears. 2.Click Next. The Choose a Hardware Task screen appears. 3.Select Add/Troubleshoot a device and click Next. The system searches for the hardware and displays the Choose a Hardware Device screen. 4.Select OnStream ADR Series USB Device and click Next. The Add/Remove Hardware Wizard screen appears again. 5.Click Finish. The Add/Remove Hardware Wizard screen closes. 6.Close the Hardware Troubleshooter screen. d.Upgrade Device Driver 1.If the Upgrade Device Driver Wizard starts automatically, skip to step 7 below. 2.Click the Device Manager button on the System Properties screen. The Device Manager screen appears. 3.If not already open, double-click Tape drives to open its category. 4.Double-click OnStream ADR Series USB Device. The Device Properties screen appears. 5.Click the Driver tab. 6.Click the Update Driver button. The Upgrade Device Driver Wizard screen appears. 7.Click Next. The Install Hardware Device Drivers screen appears. 8.Select Display a list of the known drivers. and click Next. The Select a Device Driver screen appears. 9.Select OnStream ADR Series USB. 10. If installing the drivers from the TapeWare or a different CD, insert the CD. 11. If installing the drivers from a diskette, insert the diskette. 12. Click Have Disk. The Install From Disk screen appears. 13. Click Browse. The Locate File screen appears. 14. Select the directory location of ADR2K.INF, e.g., d:\drivers on the TapeWare CD. 15. Select the ADR2K.INF file and click Open. The Locate File screen closes. 16. Click OK. The Install From Disk screen closes. 17. Select OnStream ADR Series USB and click Next. The Start Device Driver Installation screen appears. 18. Click Next. The system installs the device driver. Then the Upgrade Device Driver Wizard screen appears. 19. Click Finish. 20. If the Device Properties screen is open, click Close to close it. 21. If the Device Manager screen is open, close it. 22. If the System Settings Change screen appears, close all applications. Then click Yes to restart your computer and complete driver installation. e.Check the device status to make sure it is properly installed: 1.If the Hardware tab of the System Properties screen is already open, skip to step 5 below. 2.Right-click My Computer. A popup menu appears. 3.Select Properties. The System Properties screen appears. 4.Select the Hardware tab. 5.Click the Device Manager button. The Device Manager screen appears. 6.Double-click Tape drives. The Tape drives category opens. 7.Double-click OnStream ADR Series USB Device. The Device Properties screen appears. 8.Check the Device status section of the Device Properties screen. It should read: This device is working properly. If not, click Troubleshoot to open the Tape Drive Troubleshooter screen. 9.Close the Device Properties, Device Manager and System Properties screens. Windows XP To install the OnStream ADR USB Driver for Windows XP, follow the steps below. a.If the Found New Hardware Wizard screen appears, skip to step 7 in step d below. b.Access the Hardware tab on the System Properties screen: 1.Right-click My Computer. A popup menu appears. 2.Select Properties. The System Properties screen appears. 3.Select the Hardware tab. c.Run the Hardware wizard: 1.Click the Add Hardware Wizard button. The Add Hardware Wizard screen appears. 2.Click Next. The system searches for the hardware. If the Found New Hardware Wizard screen appears, skip to step 7 in step d below. 3.When the Is the hardware connected? screen appears, select Yes, I have already connected the hardware and click Next. 4.Select OnStream ADR Series USB Device and click Next. The Add Hardware Wizard screen appears again. 5.Click Finish. The Add Hardware Wizard screen closes. 6.Close the Tape Drive Troubleshooter screen if it appears. d.Upgrade Device Driver 1.If the Hardware Update Wizard starts automatically, skip to step 7 below. 2.Click the Device Manager button on the System Properties screen. The Device Manager screen appears. 3.If not already open, double-click Tape drives to open its category. 4.Double-click OnStream ADR Series USB Device. The Device Properties screen appears. 5.Click the Driver tab. 6.Click the Update Driver button. The Hardware Update Wizard screen appears. 7.Select Install from a list. 8.If installing the drivers from the TapeWare or a different CD, insert the CD. 9.If installing the drivers from a diskette, insert the diskette. 10. Click Next. The Install Hardware Device Drivers screen appears. 11. Select Search for the best driver. 12. Select Search removable media. 13. If installing the driver from a local or network drive location (neither diskette nor CD): i.Select Include this location. and click Browse. The Browse For Folder screen appears. ii. Locate the subdirectory on the drive that contains the ADR2K.INF file. iii. Click OK. The Browse For Folder screen closes. 14. Click Next. The computer searches for the driver. 15. If two or more drivers are available, select the correct driver and click Next. 16. If a Hardware Installation warning screen appears, click Continue Anyway. 17. After the computer installs the drivers, the hardware wizard complete screen appears. 18. Click Finish. The hardware wizard complete screen closes. 19. If the Device Properties screen is open, click Close. 20. If the Device Manager screen is open, close it. e.Check the device status to make sure it is properly installed: 1.If the Hardware tab of the System Properties screen is already open, skip to step 5 below. 2.Right-click My Computer. A popup menu appears. 3.Select Properties. The System Properties screen appears. 4.Select the Hardware tab. 5.Click the Device Manager button. The Device Manager screen appears. 6.Double-click Tape drives. The Tape drives category opens. 7.Double-click OnStream ADR Series USB Device. The Device Properties screen appears. 8.Check the Device status section of the Device Properties screen. It should read: This device is working properly. If not, click Troubleshoot to open the Tape Drive Troubleshooter screen. 9.Close the Device Properties, Device Manager and System Properties screens. Notice Information in this document is subject to change without notice. Yosemite Technologies, Inc makes no representations or warranties with respect to the contents of this document and specifically disclaims any implied warranties of merchantability or fitness for any particular purpose. Further, Yosemite Technologies, Inc reserves the right to revise this publication and to make changes without obligation to notify any person or organization of such revisions or changes. Copyright Under copyright laws, the contents of this document may not be copied, photocopied, reproduced, translated or reduced to any electronic medium or machine-readable form, in whole or in part, without prior written consent of Yosemite Technologies, Inc. Copyright c 2002 Yosemite Technologies, Inc www.TapeWare.com Trademarks TapeWarer is a registered trademark of Yosemite Technologies, Inc. NetWarer is a registered trademark of Novell, Inc. Windowsr and Windows NTr are registered trademarks of Microsoft Corporation. Linuxr is a registered trademark of Linus Torvalds.Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.