EVault InfoStage MS Exchange Plug-In Version 5.31.1903 Release Notes, October 21st, 2005 _______________________________________________________________ =============================================================== Contents 1 Overview 1.1 Release History and Changes 2 Features 3 Fixes 4 Known Issues 5 Installation Notes 5.1 Installation Requirements 5.2 Conditional Requirements 5.3 Install Procedure 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 version of the MS Exchange Plug-In. The MS Exchange Plug-In is supported on the following platforms: - MS Exchange 5.5 (SP 4) with Windows NT4 Server (SP 6a) - MS Exchange 5.5 (SP 4) with Windows 2000 Server (SP 4) - MS Exchange 2000 (SP 3) with Windows 2000 Server (SP 4) - MS Exchange 2003 (SP 1) with Windows 2003 Server (SP 1) - MS Exchange 2003 (SP 1) with Windows 2000 Server (SP 4) - MS Exchange 2003 (SP 1) with Windows SBS 2003 (SP 1) Two methods are available for fast online backups and restores: Method 1: Disaster Recovery (DR) This method backs up individual MS Exchange databases. The Plug-in refers to this option as "Database backup only". Method 2: Mailbox-Level Recovery (MAPI) This method is used for mailbox-level recovery. This method interfaces with the MS Exchange Messaging Application Program Interface (MAPI) and is user-configurable to backup selected items (mailboxes and folders) within the database. The Plug-in refers to this option as "Mailboxes and Public Folders only". This version can be either installed as a new install, or as an upgrade from previous versions. It is imperative that you are running the exact same version of the Plug-In, Agent and Management Console. Also, the Data Protection Vault that you are backing up to should be running at least version 4.30. --------------------------------------------------------------- 1.1 Release History and Changes for version 5.30 July 27th, 2005 - First release for version 5.30.1873 October 21st, 2005 - second release, version 5.31.1903 _______________________________________________________________ =============================================================== 2 FEATURES 2.1 Parallel Backups. When an Exchange DR 2000/2003 server has multiple Storage Groups, it is now possible to put the different Storage Groups into separate tasks and back them up at the same time. In previous versions of the software, there was an artificial limitation that prevented two (or more) DR tasks running simultaneously on the same Exchange Server. --------------------------------------------------------------- 2.2 Exchange 2000/2003 Backups. It is now possible to backup with Exchange 2000 (SP 3) and then restore to an Exchange 2003 (SP 1) server. In previous versions of the software, there was an artificial limitation that prevented this. --------------------------------------------------------------- 2.3 Clustering. On Windows 2000 Advanced Server, or Windows 2003 Enterprise Edition, it is possible to create a two-node cluster for Exchange 2000 Enterprise Server, or Exchange 2003 Enterprise Server. Clustering is supported for Windows Agents, with a separately licensed Cluster Support Plug-In. The Exchange Server, which is installed on a cluster, has virtual Servers that have virtual IP addresses as well as virtual network names. The Agent runs on the Nodes of the cluster but is aware of the virtual servers. The CentralControl connects to the Agent using the IP or the network name of the virtual server. If a failover occurs, the IP doesn't change for the virtual server. Since all the configuration and task files reside on the shared resource, both nodes have access to the data. This allows the user to configure (only once) the Agent backing up the virtual server on the cluster. The Agent can still access its configuration (on a shared drive), and scheduled backups will occur as usual, without it looking like a "different" backup and causing a reseed. --------------------------------------------------------------- 2.4 Deferring and Transaction logs. Databases and transaction logs are backed up together. When deferring (a time option) is complete, the transaction logs of databases which are backed up (they have already completed) will continue to backup (even past the deferring time) to ensure the backup is complete. Other databases that are not complete (started, but not finished) will not have their logs backed up in that time window. _______________________________________________________________ =============================================================== 3 FIXES 3.1 DTS#5533 5.30 MAPI agent times out looking for objects with message "browsing of Exchange server is timed out". 3.2 DTS#5523 Receive message, "browsing of Exchange server is timed-out" on MAPI profile test. 3.3 DTS#5544 On 5.30 Agent, client is unable to backup more than 247 mailboxes per MAPI task. 3.4 DTS#1773 - Exchange 5.5 on Win2000 backup hangs with status Active: Unknown. The hanging is related to MAPI not being able to write to the Application Event Log. If the log is full, and no facility for overwrite setup, the program will hang. Event logs must be large enough, or they must allow overwrites. _______________________________________________________________ =============================================================== 4 KNOWN ISSUES 4.1 During the first instance of a database backup, if a database backup does not complete within the allotted time window, the backup task will fail. The defer backup feature functions when at least 1 database has been backed up within the allotted time window or backed up previously in the same task. --------------------------------------------------------------- 4.2 MS Exchange allows creation chains of folders up to 65000 characters (each folder in the chain can not exceed 256 characters though). Chains of folder names that exceed 512 characters in total cannot be backed up. --------------------------------------------------------------- 4.3 (Microsoft Knowledge Base Article - 264731) MAPI-based tasks do not work with Virus API anti-virus software running on the Exchange Server (5.5 (SP 3); 5.5 (SP 4); and 2000/2003). When you attempt to perform MAPI operations on an Exchange Server that is running an anti-virus software application that is based on an anti-virus API, you may receive a MAPI time-out error. This issue can occur if these MAPI operations gain access to a large number of attachments that have not been scanned by using the current virus signatures. --------------------------------------------------------------- 4.4 (Microsoft Knowledge Base Article - 282533) Exchange Server 5.5 post SP-4 Information Store fixes available. This article lists the article numbers for the Exchange Server 5.5 information store bugs that have been fixed since (SP 4) was released. --------------------------------------------------------------- 4.5 When a user deletes an item in Exchange, Restore searches for folders using an internal ID. This means that if you move or rename a folder, the restore will still put all items that were moved or renamed back into their original place. If the folder "" was deleted but not removed from Deleted Items, the restore will go into "Deleted Items/some folder". If the folder was deleted and removed from Deleted items, and a new folder created with the same name, all items will be restored to the new folder. All properties of the old folder will be applied to the folder of the same name. --------------------------------------------------------------- 4.6 Do not set the Information Store path (database, logs, working directories, etc.) to a drive root (i.e.: c:\). This is a known Microsoft problem. --------------------------------------------------------------- 4.7 Exchange DR only: When the restore task shows a normal "Restore Completed" message, the person doing the restore should check the Restore log file for any errors. If errors (such as, "Database is in use" message, or "Database failed to restore") are found, retry the restore. --------------------------------------------------------------- 4.8 On Exchange 5.5 , when using the Plug-In for MAPI backups, the user cannot use all the available keyboard characters for naming Organizations and Sites, even though they may be acceptable to Microsoft for naming them. Specifically, the user can use the letters A to Z (upper and lower case), the numbers 0 to 9 and & (ampersand) ,(comma) _(underscore) and spaces (but not leading or trailing spaces). Attempts to create a Computer/Organization name with characters other than these (for example, the backslash character) may give "failed to retrieve exchange structure", or similar, error messages. --------------------------------------------------------------- 4.9 Error message " Failed to create PST file. PST provider was not configured or insufficient resource." The Personal Folders service has to be added to the profile for backup/restore. --------------------------------------------------------------- 4.10 "Cannot restore SRS database" error message. See Microsoft's http://www.microsoft.com/technet/prodtechnol/exchange/guides/ DROpsGuide/ac431f9c-d0c9-43c8-a4a4-80efe1b6034b.mspx for a special procedure on how to recover an SRS database. --------------------------------------------------------------- 4.11 During an Exchange DR backup/restore, you may encounter a Log file error message such as: "A communications error occurred while attempting to perform a local backup." "Backup is incomplete ..." "No databases were backed up ..." "Exchange backup might not be complete ..." "The database will be unable to restore ..." Check the knowledge base at www.support.microsoft.com for more information. "By far the most common reason for a -1022 error with an undamaged database is another application holding files open and preventing the Information Store service from accessing them. In such cases, you might also see -1032 errors (JET_errFileAccessDenied). Restarting all of the Exchange services or restarting the server might remove the lock." (http://support.microsoft.com/default.aspx?scid=kb; EN-US;314917) --------------------------------------------------------------- 4.12 Issue: When attempting to restore a Storage Group from a DR backup after the original Storage Group has been renamed on the Exchange Server the restore completes, with errors. An error is logged in the restore log file. Workaround: To restore to a renamed Storage Group the name property of the Storage Group on the Exchange server must be returned to its original value - the name it had when the backup was taken. The original name of the Storage Group can be found using information contained in the log files and catalogues from the backup job. The restore job can then be executed and the Storage Group brought back on line using the Information Store recovery steps described in Microsoft's Exchange Server recovery documentation. --------------------------------------------------------------- 4.13 (PR914916) During Exchange DR backups, transactions may be truncated after each Store is backed up. If backups subsequently are cancelled or fail, truncation is already done resulting in limited (i.e.: none) rollback capabilities, as well as requiring a full backup in the next session. --------------------------------------------------------------- 4.14 If you create a MAPI backup task, with a valid license, (for example, called "mapi") on one computer, to backup a mailbox, it functions correctly, as expected. If you install the Exchange Plug-in on another computer, using the same license key, and re-register it (the same as the first computer, and with the same vault), it will validate correctly. But now, if you try to open the task (in this example called "mapi"), you will receive a license error. To successfully make the license function, you must use the "Set" button in the Plug-In tab in the Agent Configuration. See section 2.4 - "License Installation" - in the "Installation and Configuration Guide". "The Test button will validate that the license key is correct, and usable. The Set button must be clicked to save the entered information." --------------------------------------------------------------- 4.15 If MS Exchange is installed on an NT4 Server without IE4 (SP 2), (or later), and is in a non-default path (such as D:\Exchsvr), the DR restoration may fail. You may receive a DR Restore error message such as "DISK-E-0005 O/S error: The filename, directory name, or volume label syntax is incorrect." Or: "UseDLL failed. Failed to load VVVendor.dll." IE4 is not required for the Agent installation, although other third party programs may need some of the DLLs that IE installs. --------------------------------------------------------------- 4.16 In a multiple Exchange Server environment, if an Exchange Server in the first administrative group is dismounted (as in a restore) you will not be able to browse in the second administrative group Exchange Server for MAPI selection. When the DR restore is completed in the first administrative group and the DB is mounted, you will be able to expand the second administrative group Exchange Server trees for MAPI selection. --------------------------------------------------------------- 4.17 DTS#2181 - Exchange reports that an incremental backup has never been run, when in fact it has. If you check the properties of the stores, and check the database tab, there are fields which state when the last full and incremental backups have been completed. The incremental backup fields may state that backups have never been done on this field, when they have been. This is because incremental backups are relative to a full backup, which means that each full backup resets the incremental backup counter. --------------------------------------------------------------- 4.18 DTS#4191 - After failing over virtual servers, MAPI backups may fail. A first backup of MAPI tasks works fine. But after failing over both virtual servers (for example: VS-1 from Node1 to Node2, and VS2 from Node2 to Node1), the MAPI backups fail. But, after failing back, the backups work properly. Error messages may include: BKUP-E-0003 Unknown exception caught BKUP-F-0014 task failed to complete EXMA-E-0003 Error getting mailbox list ... EXMA-E-0003 VExchMapi::Dispatch(): failed EXMA-W-0002 some components of Exchange might not be complete. The MAPI profiles must be properly created. For this example: On VS-1: log-in as administrator and create "ms exchange settings/administrator" log-in as admin2 and create "ms exchange settings/admin2" On VS-2: log-in as administrator and create "ms exchange settings/administrator" log-in as admin2 and create "ms exchange settings/admin2" --------------------------------------------------------------- 4.19 The Agent has been enhanced to handle Unicode 'filenames' as stored on a file system. Unicode is not supported on Plug-Ins. --------------------------------------------------------------- 4.20 DTS#5190 When restoring individual (unique) messages to a mailbox, all the duplicate messages are restored regardless of the user's selection. _______________________________________________________________ =============================================================== 5 INSTALLATION NOTES 5.1 Installation Requirements Note: If you are upgrading from an earlier version of Exchange Plug-In with MAPI and DR, to the 5.30 version (this is the default scenario) you will not have to make any choices regarding MAPI/DR as it will upgrade both. But, if you have a previous version of DR only Exchange Plug-In, the upgrade will force a MAPI upgrade as well. You will have to choose between the Exchange server version (5.5 or 2000/2003) that is installed on that specific machine. Hardware -------- * CPU - Intel Pentium or compatible 166 MHz or higher. Single or multi-processor. * RAM - 128 MB or more recommended * HDD - A minimum of 10MB of available disk space or more Software -------- * Director v.4.30 (or later) * Agent v.5.31 * CentralControl v.5.30 - MS Exchange 5.5 (SP 4) with Windows NT4 Server (SP 6a) - MS Exchange 5.5 (SP 4) with Windows 2000 Server (SP 4) - MS Exchange 2000 (SP 3) with Windows 2000 Server (SP 4) - MS Exchange 2003 (SP 1) with Windows 2003 Server (SP 1) - MS Exchange 2003 (SP 1) with Windows 2000 Server (SP 4) - MS Exchange 2003 (SP 1) with Windows SBS 2003 (SP 1) * Network - A TCP/IP stack (to communicate with Agent systems) * see Microsoft knowledge base article #Q306962 "How to Create MAPI Profiles Without Installing Outlook" (necessary for mailbox and folder MAPI component only) --------------------------------------------------------------- 5.2 Conditional Requirements The MS Exchange Plug-In requires a valid Software License. --------------------------------------------------------------- 5.3 Install Procedure Installation guides are located at: http://support.EVault.com _______________________________________________________________ =============================================================== 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 MS Exchange Plug-In is as follows: MS Exchange Plug-In Release Notes (this document) MS Exchange Plug-In User's Guide All documentation is available at the following location: 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. _______________________________________________________________ ===============================================================