EVault InfoStage Agent for Windows Version 5.33.2010 Release Notes, February 22nd, 2006 _______________________________________________________________ =============================================================== Contents 1 Overview 1.1 Release History and Changes 1.2 Supported Platforms 2 Features 3 Fixes 4 Known Issues 5 Installation Notes 5.1 Installation Requirements 5.2 Conditional Requirements 5.3 Installation Files 5.4 Licensing 5.5 Install/Uninstall Procedure 5.6 Configuration 6 Product Support 6.1 Technical Support 6.2 Product Updates 6.3 Documentation 7 Legal Information _______________________________________________________________ =============================================================== 1 OVERVIEW This document contains release notes for the latest release of the Agent for Windows. The Agent software kit consists of VV.exe which is a command line version of the system which performs tasks such as backup, restore, re-synch and other requests. --------------------------------------------------------------- 1.1 Release History and Changes for Agent version 5.30 July 27th, 2005 - First release, version 5.30.1873 October 17th, 2005 - Second release, version 5.31.1903 February 22nd, 2006 - Third release, version 5.33.2010 --------------------------------------------------------------- 1.2 Supported Platforms This Agent is supported on the following platforms: OS - Windows NT4 Server (sp6a), with IE 5.5 minimum - Windows 2000 Server (sp4) - Windows 2000 Advanced Server (sp4) - Windows 2003 Server Standard Edition (sp1) - Windows 2003 Server Enterprise Edition (sp1) - Windows 2003 Server Small Business Edition (sp1) - Windows Storage Server 2003 (sp1) - Windows XP Professional (sp2) _______________________________________________________________ =============================================================== 2 FEATURES New Features in this Release: 1. Windows Cluster Support. Vault profiles, schedules and tasks are associated with a virtual node in a cluster, to be able to backup the system volume and system state. 2. UTF-8 Encoding. An Agent can now backup and restore filenames with characters not from the ANSI set. This includes backing up files on “File Services for Macintosh”. Plug-Ins (MS Exchange and MS SQL Server) do not use UTF-8 Encoding for the object names they create. 3. Common File Filters. Able to make a list of files to be excluded from backups. 4. Overwrite/Rename option. On a Restore, the user has more choices instead of a simple Yes/No to overwriting files: Rename incoming restore files; Rename existing files; Do not Restore (overwrite) existing files; Overwrite existing files. With Renaming, the files are appended with an additional extension (.0001, etc.). 5. Configuration Files Security. The directories where the program files and configuration files are stored are locked down to prevent reading and writing by non-privileged users. The only users/groups with permissions are Administrators, BackupOperators, and LocalSystem. [Note: Cluster shared directories are also locked down] 6. Package Agents with Plug-Ins. (Installation). Plugins are installed along with the Agent, so it does not require a separate install. 7. Stronger encryption for backups. AES 256-bit is now supported for a stronger cipher. 8. Windows Agent “silent” install. InstallShield can use an “answer” file to install the Agent without user interaction. 9. Exchange DR Plug-In changes: Parallel backups for Exchange DR 2000/2003; Restore Exchange DR 2000 to 2003; Clustering supported for Windows Agents, with a separately licensed Cluster Support Plug-In. _______________________________________________________________ =============================================================== 3 FIXES for 5.33.2010 DTS#5831: Instances of failure 'error opening file E:\Shared\' alternate stream not properly null-terminated before conversion. This has been fixed in this release. DTS#6335: BRTP issue with high bandwidth, high latency connections, transmitting slowly. This has been fixed in this release. DTS#6725: Able to backup Mac directories with special characters with no errors, however it restores two directories for each. This has been fixed in this release. --------------------------------------------------------------- FIXES for 5.31.1883 DTS#5449: Unable to create clustered agent on server with a "logical disk" resource. After installing the agent software on a virtual node, and when you select Global Settings, and are asked for the resource, the drop-down box is empty. If you look at the disk within the Group, the disk resource type is "IBM ServeRAID Logical Disk", not a standard Microsoft "Physical Disk". This patch provides a script program that will modify the registry to recognize the IBM disk. --------------------------------------------------------------- FIXES for 5.30.1844 DTS#3054: OTM fails to start, gives "OTM ERROR(1) - Incorrect function." and "OTM was unable to synchronize." in the backup log file (on XP only). This has been fixed in this release. DTS#4214: VV.exe gives "Dr Watson" on NT 4.0 with CC 5.30 and Agent 5.30. This has been fixed in this release. DTS#5056: Deleting two incremental generations should not allow another backup that follows to be an incremental backup. It will now force the next backup to be a Full backup. --------------------------------------------------------------- FIXES for 5.30.1832 PR-1-28545: Unable to backup files on FAT32 filesystem. This has been fixed in this release. PR-1-30863: License validation fails at GMT+12 and GMT+13 timezones on Windows 2003. This has been fixed in this release. PR-1-6528: Rainmaker database running on Foxpro has files "marked no backup". This has been fixed in this release. DTS#2000: The boot process on Windows 2003 servers was hanging the system, at the "preparing network connection" stage. This was caused by different versions of ASPI kernel drivers. This has been fixed in 5.02. DTS#2955: Version 5.00 backups appear to start looping during the backup of system drive. Problem was in properties of MAC folders that had alternate data streams, with the alternate first and data next. This has been fixed in 5.20. _______________________________________________________________ =============================================================== 4 KNOWN ISSUES 4.1 Due to changes in the delta file format, Quick File Scanning will be temporarily disabled during the first backup following an upgrade. This could result in the first backup after an upgrade taking longer than usual. If the QFS option is enabled (the default), QFS will automatically be re-enabled on subsequent backups. --------------------------------------------------------------- 4.2 It is NOT RECOMMENDED to run the current release of the Windows Agent with OFM release 7.0.005 or OFM release 8.0 --------------------------------------------------------------- 4.3 The system has a problem backing up MAC folders & files (pre OSX platforms) with certain characters {extra spaces ( ), double periods (..), forward slashes (/)}. The Agent can backup and restore Mac created files (including alternate streams) provided the path to the file does not contain "special" characters. Special characters are any characters not permitted under Windows when creating a path (for example "*", "?", "\", ">" etc.). Files containing special characters in the path will be omitted from the backup. This restriction has existed since the Agent begun supporting Mac name space. At the present the only workaround to the problem is to rename the affected directories and files. Keep in mind that some system created files (like "Icon?") also contain special characters and those items cannot be renamed. Some MAC filenames longer than 256 characters may produce an error message such as: "The data area passed to a system call is too small." --------------------------------------------------------------- 4.4 If you are doing a bare metal restore on a Windows 2000 server, it may work correctly without installing the SP before the restore, but it is recommended to install the SP before the restore. --------------------------------------------------------------- 4.5 (I-9307) If you are running version 3.2 (and above, i.e.: 3.2+) of the Agent, and it contains a task created by an older Agent, you may receive an error if you attempt to upgrade the Agent, using the upgrade program "cupgd240.exe". The upgrade may not recognize the older backup type "Type=SAF" in the configuration file. To resolve this problem you should use the version 3.2 (and above, i.e.: 3.2+) Administrator program to open the task property and click OK to save it. This will change the task file format to be upgradeable to the 4.x version. The upgrade program will now run successfully. (Note: to upgrade earlier versions (from 2.2E, up to 3.10) you need to first run the version 3.3 installation. From here (as noted above) you can now run the upgrade program.) --------------------------------------------------------------- 4.6 Windows 2003 handling of services/databases/features: After a bare metal restore the following items may not be fully functional, as they are handled as "regular files", as opposed to APIs or other special techniques. 1. Replicated data other than SYSVOL 2. Primary restoration of replicated data including SYSVOL 3. Content indexing server metadata 4. Terminal service database 5. Removable storage management database 6. Event logs 7. Single instance store volumes 8. Installed applications shortcuts 9. Hard links In addition, the following features are not supported: 1. Disk quotas 2. Volume Shadow Copy history --------------------------------------------------------------- 4.7 OFM 9.1 will give log errors if the Agent directories are not excluded. You may see: "Backup log file not renamed.", and "Parse Errors." In the OFM configuration (Properties) you should add the Agent installation and executable directories and subdirectories to be excluded by OFM. --------------------------------------------------------------- 4.8 Authentication for the Agent on Windows XP Professional or on a 2003 Server Domain requires a password. In these cases, the password field cannot be left blank. --------------------------------------------------------------- 4.9 Cannot create a "Mapped Drive" Task with Agent running Windows XP Professional Workaround: 1. Create a local drive Task 2(a)Open a Task File in text mode and modifying the "Mapped_Drive" parameter from "Mapped_Drive = False" to "Mapped_Drive = True". 2(b)Within that Task File, modify the "Include" path to the appropriate drive letter. 3. Re-open the Task Properties in GUI mode and change the Logon option to match the settings required for the Mapped Drive (Computername). --------------------------------------------------------------- 4.10 If a "non EVault" formatted tape is used, you will notice "invalid FID size detected" and "invalid SIDF table" errors in the backup log files (this applies for agent versions 4.x as well as 5.x). You must use EVault format. If the tape was used previously by EVault tape backup, these errors do not occur. DTS4213 Restores involving multiple tapes may fail with SIDF errors when the incorrect sequence of tapes is used. --------------------------------------------------------------- 4.11 If port 2546 is found absent from any vault profile(s) during an upgrade, port 2546 will be added automatically. If you do not require/wish this port to be utilized, please remove this port manually from your vault profile(s) following the upgrade. --------------------------------------------------------------- 4.12 Agent silent installation does not run if an Agent is already installed on the target PC. The silent install will only install an Agent if one is not there already; it does not do an upgrade. --------------------------------------------------------------- 4.13 OFM 9.4 does not exclude EVault Infostage folder in the OFM Manager's exclusion list. OFM excludes the EVault installation folder and produces some errors in the backup log. But, the Agent will still back up the installation folder, unless you explicitly add it to the task's exclusion list. --------------------------------------------------------------- 4.14 OTM should not be used in bare metal scenarios. If all data files and system state were backed up with OTM and only the system state was restored, after rebooting, the system may remain in a continuous boot situation. --------------------------------------------------------------- 4.15 Do not uninstall the Agent on a Windows XP machine with the Windows Add/Remove programs. You should always use the Agent Installation kit to uninstall the product. _______________________________________________________________ =============================================================== 5 INSTALLATION NOTES 5.1 Installation Requirements The installation requirements for the Agent under Windows OS - Windows NT4 Server(sp6a), with IE 5.5 minimum - Windows 2000 Server(sp4) - Windows 2000 Advanced Server(sp4) - Windows 2003 Server Standard Edition (sp1) - Windows 2003 Server Enterprise Edition (sp1) - Windows 2003 Server Small Business Edition (sp1) - Windows Storage Server 2003 (sp1) - Windows XP Professional (sp2) * A minimum of an Intel 80486 or 100% compatible processor (Pentium 200 or faster recommended) * Video properties of 16-bit (or greater) for optimum GUI display * At least 10MB of available disk space * 64MB of RAM recommended * A TCP/IP stack (for communicating with the Vault and the CentralControl software) * Optionally, Open Transaction Manager (OTM) 1.12.211 or Open File Manager (OFM) 9.5 (OTM is a product of Columbia Data Products and OFM is a product of St. Bernard Software). * Director version 4.3 and up. * CentralControl version 5.3 --------------------------------------------------------------- 5.2 Conditional Requirements In General * In order to graphically configure and administer the Agent, the CentralControl will need to be installed on a network-connected Windows system. * If transparent processing of open and/or locked files is a requirement, OTM by Columbia Data Products or OFM by St. Bernard Software should be installed. * The Agent should NOT be installed on a Windows 2000/2003 encrypted directory. For Tape Backups * Currently, the only supported tape devices are generic SCSI-2 devices. Supported devices include all 4mm DAT drives, all 8mm drives (except SCSI-1 drives such as the Exabyte- 8200) and all DLT devices. Excluded from this list are many QIC tape drives, including Travan QIC drives. However, some tape drives that are not SCSI-2 or even SCSI at all may function correctly using proper drivers through NT but are not specifically supported. Two standard tape interfaces are supported. Under Windows NT, both ASPI drivers and native NT drivers can be used to access tape drives. This will allow use of a tape drive with the Agent even if NT does not directly support it. Windows NT does not come with ASPI, but it is not required if you have the correct NT tape driver installed. To use ASPI under NT, the correct ASPI drivers for the SCSI card must be installed. The following SCSI cards are supported: Adaptec 2940 series (PCI) Adaptec 2944 differential (PCI) Adaptec 2920 (PCI) Adaptec 1540 series (ISA) Adaptec 1542 series (ISA) Symbios SMC810 Adaptec 1520 Adaptec 1522 Other PCI SCSI --------------------------------------------------------------- 5.3 Installation Files The following files are installed by the Agent installation kit: * Agent software * Online help files * Release notes (this document) * Open Transaction Manager, OTM 1.12.211 (optional) --------------------------------------------------------------- 5.4 Licensing The Agent does not require a license to function properly; however, to back up to and restore data from a Data Protection Vault, a valid account, username and password are required. Contact your Service Provider to obtain the required information. --------------------------------------------------------------- 5.5 Install/Uninstall Procedure All products have appropriate installation guides which can be viewed using a Web browser at: http://support.evault.com/ --------------------------------------------------------------- 5.6 Configuration To configure the Agent software, use the CentralControl program from any network-connected Windows * OS - Windows 2000(sp4) - Windows 2000 Server(sp4) - Windows 2000 Advanced Server(sp4) - Windows 2003 Server Standard Edition (sp1) - Windows 2003 Server Enterprise Edition (sp1) _______________________________________________________________ =============================================================== 6 PRODUCT SUPPORT 6.1 Technical Support Complete contact information for your provider is available under the Help Support menu. --------------------------------------------------------------- 6.2 Product Updates Product updates are available from your provider's web site. --------------------------------------------------------------- 6.3 Documentation The documentation available for the Agent is as follows: The CentralControl Operations Guide The Agent User's Guide The Agent Release Notes (this document) All documentation is available at the following location on the EVault site: http://support.evault.com/ _______________________________________________________________ =============================================================== 7 LEGAL INFORMATION Software License Agreement - Agent Software This legal document is an agreement between you, the end user, and the licensor (herein referred to as "licensor"). BY INSTALLING THIS AGENT SOFTWARE PRODUCT, YOU ARE CONSENTING TO BE BOUND BY THIS AGREEMENT. IF YOU DO NOT AGREE TO ALL OF THE TERMS OF THIS AGREEMENT, UNINSTALL THIS PRODUCT AND RETURN IT TO THE PLACE OF PURCHASE FOR A FULL REFUND. AGENT FOR WINDOWS SOFTWARE LICENSE 1. GRANT OF LICENSE. In consideration of your payment of the license price to an authorized Dealer, as Licensor, grants to you, the Licensee, a non-exclusive right to use and display this copy of the Agent software program (hereinafter the "Software") on specific computer(s) at your location(s). The licensor reserves all rights not expressly granted to Licensee. If you have not paid a license fee for the Software, then the licensor grants to you the right to use the Software ONLY for evaluation or educational purposes. This latter grant specifically excludes production use of the Software. 2. OWNERSHIP OF SOFTWARE. As the Licensee, you own the magnetic or other physical media on which the software is originally or subsequently recorded or fixed, but the licensor retains title and ownership of the Software recorded on the original media and all subsequent copies of the Software, regardless of the form or media in or on which the original and other copies may exist. This license is not a sale of the original Software or any copy. 3. COPY RESTRICTION. This Software and the accompanying written materials are copyrighted. Unauthorized copying of the Software, including Software that has been modified, merged, or included with other software, or of the written materials is expressly forbidden. You may be held legally responsible for any copyright infringement that is caused or encouraged by your failure to abide by the terms of this license. 4. USE RESTRICTIONS. You may not modify, adapt, translate, reverse engineer, decompile, disassemble, or create derivative works based on the Software. You may not modify, adapt, translate, or create derivative works based on the written materials without the prior consent of the licensor. 5. TRANSFER RESTRICTIONS. This Software is licensed only to you, the Licensee, and may not be transferred to anyone without prior written consent of the licensor. Any authorized transferee of the Software shall be bound by the terms and conditions of this agreement. In no event may you transfer, assign, rent, lease, sell, or otherwise dispose of the Software on a temporary or permanent basis as expressly provided herein. 6. TERMINATION. This license is effective until terminated. This license will terminate automatically without notice from the licensor if you fail to comply with any provision of this license. Upon termination you shall destroy the written materials and all copies of the Software, including modified copies, if any, and certify in writing that all copies have been destroyed. 7. WARRANTY AND MAINTENANCE. The licensor warrants the Software to perform substantially in accordance with the User Documentation, as amended from time to time, and will maintain, modify, repair or replace the Software during the ninety (90) day warranty period, at no additional cost to the Licensee. The licensor does not warrant that the use of the Software will be uninterrupted or error free. The licensor will provide Support Services to customers that have paid the qualifying support fee. The Support Services include product maintenance and shall entitle the customer to; telephone support for troubleshooting, user guidance, and problem corrections and all product fixes and new minor releases via a World Wide Web site. 8. INDEMNIFICATION. Licensor will defend at its own expense any action against Licensee brought by a third party to the extent that the action is based upon a claim that the Licensed Software infringes any U.S. copyrights or misappropriates any trade secrets recognized as such under the Uniform Trade Secret law, and Licensor will pay those costs and damages finally awarded against Licensee in any such action that are specifically attributable to such claim or those costs and damages agreed to in a monetary settlement of such action. The foregoing obligations are conditioned on Licensee notifying Licensor promptly in writing of such action, Licensee giving Licensor sole control of the defense thereof and any related settlement negotiations, and Licensee cooperating and, at Licensor's request and expense, assisting in such defense. 9. LIMITATION OF LIABILITY. Subject to paragraph 8, the licensor, nor any authorized Vault Service Provider of the Software, will not be liable for any damages including any loss of data, profits or savings, claims against Licensee by any other party or any other incidental or consequential damages arising out of Licensee's use of, or inability to use the software, even if the licensor (or such Dealer) is advised of the possibility of such damage. Subject to paragraph 8 above, the Licensee agrees that the licensor's (or such Dealer's) liability under this License shall not exceed the License fees paid by the Licensee for the software licensed hereunder. 10. MISCELLANEOUS. This agreement is governed by the laws of the State of Delaware and venue in any suit arising hereunder shall be Wilmington, Delaware USA. Should you have any questions regarding this Agreement, please contact us in writing at the address shown in your software license agreement. _______________________________________________________________ ===============================================================