EVault InfoStage Agent 64-bit and Plug-Ins for Windows Version 6.01.2379 Release Notes, October 30th, 2007 ________________________________________________________ ======================================================== Contents 1 OVERVIEW 1.1 Release History and Changes 1.2 Supported Platforms 2 FEATURES 3 INSTALLATION NOTES 3.1 Windows Agent 64-bit 3.1.1 Installation/Upgrade Requirements 3.1.2 Conditional Requirements 3.1.3 Installation Files 3.1.4 Licensing 3.1.5 Install/Uninstall Procedure 3.2 Cluster Plug-In 3.2.1 Installation Requirements 3.2.2 Conditional Requirements 3.2.3 Install Procedure & Recommendations 3.3 SQL 64-bit Plug-In 3.3.1 Installation 3.3.2 Conditional Requirements 3.3.3 Installation Files 3.3.4 Licensing 3.3.5 Install/Uninstall Procedure 3.4 Exchange 2007 DR and MAPI Plug-In 3.4.1 Installation Requirements 3.4.2 Conditional Requirements 3.4.3 Install Procedure & Recommendations 4 FIXES and KNOWN ISSUES 4.1 Fixes 4.2 Known Issues 5 PRODUCT SUPPORT 5.1 Technical Support 5.2 Product Updates 5.3 Documentation 6 LEGAL INFORMATION ________________________________________________________ ======================================================== 1 OVERVIEW This document contains release notes for the release of the Windows Agent 64-bit as well as the following Plug-Ins: - SQL 64-bit Plug-In 6.0 - Exchange 2007 DR and MAPI Plug-In 6.0 - Cluster Plug-In 6.0 This release is for use in combination with Win CentralControl 6.0, Web CentralControl 6.0, Agent 6.0,and Director 6.0. In this release note, "CentralControl" when used without "Web" or "Windows" in front means either one. If something applies to only one, then it will be noted. Upgrade 4k delta blocks issue fix. See Fixes section 4.1. -------------------------------------------------------- 1.1 Release History and Changes for Agent version 6.0 September 19th, 2007, First release, version 6.00.2371 October 25th, 2007, Second release, version 6.01.2379 -------------------------------------------------------- 1.2 Supported Platforms This Agent is supported on the following platforms, with Intel64 or AMD64 processors: - Windows Server 2003 Standard x64 Edition SP2, R2(SP2) - Windows Server 2003 Enterprise x64 Edition SP2, R2(SP2) - Windows Vista Home Basic x64 - Windows Vista Home Premium Edition x64 - Windows Vista Business Edition x64 - Windows Vista Ultimate Edition x64 - Windows Vista Enterprise Edition x64 ________________________________________________________ ======================================================== 2 New Features in the 6.0 Release: Support for MS Exchange 2007 DR and MAPI backup and restore functionality. Support for backup and restore on Windows Vista Home Premium and Ultimate Editions. More granularity and efficiency on bandwidth throttling. Each Job can now share (equally) the Agent's bandwidth throttling. If multiple Job instances run concurrently, they will not exceed the Agent-wide bandwidth throttling limit. The user can optionally turn off throttling for restores, if extra speed is needed. Performance improvements with reduced backup and recovery time. The Agent can take advantage of a multi-processor system, plus use multi-threading. Installation is now MSI (Microsoft Windows Installer) based, where previously it used InstallShield. Logical Vault Replication (LVR) Support. The Agent supports vaults configured for LVR. The Agent can automatically determine the correct vault and backup, if the logical vault has changed. For example, if the active vault has failed, and the passive one is now the active one, the Agent will synchronize and switch over to the new one. The log file will show this activity. Delta file re-creation support. The Agent has the ability to re-create a missing delta file, with additional information within the backup (on the vault). This will not work on a corrupted delta file. In that case the file must be manually deleted prior to running the synchronize command. If the delta information was only partially recovered, some data may be reseeded during the backup. Additional information will show in the log file if a delta file has been re-created. Forcereseed option in CLI. Delta recreation allows the user to rebuild a DTA (delta) file by using job synchronization. This command line only option will force a re-seed, in case of a failure with delta recreation in rebuilding delta files. Long path name support. The Agent supports very long path names for both file system and plug-in data sources, when connected to a version 6 vault. The maximum length is 31,999 characters. Older Agents only supported 511 characters. The supported length will show in the log files. The Agent is backward compatible with older Agents, but older Agents will not be able to restore from long path names. Note that this long path is only for Web CentralControl. Win CentralControl only supports browsing of path lengths up to the buffer size of approximately 8,000 characters. Agent Assistant. You can optionally install the Agent Assistant which will be displayed with a system tray icon. The Agent Assistant provides status messages, number of jobs running, access to the Web CentralControl application and Help. The Agent Assistant also allows you to stop all running Agent processes. ________________________________________________________ ======================================================== 3 INSTALLATION NOTES 3.1 Windows Agent 64-bit 3.1.1 Installation/Upgrade Requirements The installation requirements for the 64-bit Agent for Windows OS: - Windows Server 2003 Standard x64 Edition SP2, R2(SP2) - Windows Server 2003 Enterprise x64 Edition SP2, R2(SP2) - Windows Vista Home Basic x64 - Windows Vista Home Premium Edition x64 - Windows Vista Business Edition x64 - Windows Vista Ultimate Edition x64 - Windows Vista Enterprise Edition x64 * .NET Framework 2.0 is required if the Agent Assistant is installed with the Agent. * CPU and RAM - Should meet the basic requirement of your Operating System, as prescribed by Microsoft. * Video properties of 16-bit (or greater) for optimum GUI display * At least 10MB of available disk space * A TCP/IP stack (for communicating with the Vault and the CentralControl software) * Optionally, Open File Manager (OFM) 9.601 (OFM is a product of St. Bernard Software). Note: OFM 9.6 is not supported on Windows Vista. * Director version 6.0 * CentralControl version 6.0 * Web CentralControl version 6.0 * Note: If you use an Anti Virus program, you should disable real time scanning on reads (sometimes called "outgoing" on some AV products). Do not backup the AV directories themselves. -------------------------------------------------------- 3.1.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, OFM by St. Bernard Software should be installed, Open File Manager (OFM) 9.601b. Note: OFM 9.6 is not supported on Windows Vista. * The Agent should NOT be installed on a Windows 2003 encrypted directory. If you want to manage an Agent from both Windows CentralControl and Web CentralControl, they must both be installed using the same service account user identities. That is, "EVault InfoStage BUAgent" and "EVault InfoStage Agent" service accounts must be the same. If not, the BUAgent will not be able to provide any status, or administration functions. The account under which services are running is shown in VVAgent and BUAgent logs. If you have an AMP Proxy running on a Windows 2000 system, and you want to upgrade the AMP Proxy to Web CentralControl version 6, then you must also install the latest version of MDAC. This supports the SQL 2005 drivers in Windows 2000. -------------------------------------------------------- 3.1.3 Installation Files The following files are installed by the Agent installation kit: * Agent software * Online help files * Release notes (this document) * Note: The Agent install will install the file VVClMsg.dll in the System directory. This file contains the error codes and resource strings which the event viewer uses to display the Agent messages. -------------------------------------------------------- 3.1.4 Licensing To backup 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. -------------------------------------------------------- 3.1.5 Install/Uninstall Procedure All products have appropriate installation guides, which can be viewed using a Web browser at: http://support.EVault.com/ ======================================================== 3.2 Cluster Plug-In 3.2.1 Installation Requirements Hardware ******** See the Windows Agent User Guide and above Agent requirements. -------------------------------------------------------- 3.2.2 Conditional Requirements The Cluster Support Plug-In requires a valid Software License. -------------------------------------------------------- 3.2.3 Install Procedure & Recommendations The Plug-In is installed as part of the Windows Agent. 1. Install the Agents and Plug-Ins on the Physical Nodes. 2. Set Cluster, SQL 64-bit Plug-Ins on the Physical Nodes. 3. Create a New Agent for your SQL 64-bit cluster on the Virtual Node using the IP address or Hostname. 4. From the newly created agent, double-click the Global file to open the "Virtual server shared area" window. From here you must select a drive letter for your SQL Cluster. Click OK. This will launch the Agent Configuration Window. 5. Here you must specify all of your Vault connection information. Click OK when complete. All products have appropriate installation guides. The guides are located at: http://support.EVault.com/ ======================================================== 3.3 SQL 64-bit Plug-In Supported Platforms: The SQL 64-bit Plug-In is supported on the following versions of MS SQL 64-bit Server 2005: Enterprise, and Standard. OFM 9.601 can be used for local file backups on the following versions of MS SQL 64-bit Server 2005: Workgroup, and Express. This version of the Plug-In supports the Microsoft defined Virtual Backup Device Interface (VDI). -------------------------------------------------------- 3.3.1 Installation Requirements Hardware ******** See the appropriate Windows Agent User Guide and above Agent requirements. Software ******** * Director version 6.0. * Win CentralControl version 6 - or - * Web CentralControl version 6 * Windows Agent version 6.0 64-bit * MS SQL 64-bit Server 2005 (SP2) with: - Windows Server 2003 Standard x64 Edition SP2, R2(SP2) - Windows Server 2003 Enterprise x64 Edition SP2, R2(SP2) * Network - A TCP/IP stack (to communicate with Agent systems) * MS Windows IE 5 (or greater) -------------------------------------------------------- 3.3.2 Conditional Requirements *A valid Software License for the MS SQL 64-bit Server Plug-In is required. -------------------------------------------------------- 3.3.3 Install Procedure All products have appropriate installation guides. The guides are located at: http://support.EVault.com/ ======================================================== 3.4 Exchange 2007 DR and MAPI Plug-In 3.4.1 Installation Requirements Hardware ******** See the Windows Agent User Guide and above Agent requirements. Software ******** * Director version 6.0. * Win CentralControl version 6 - or - * Web CentralControl version 6 * Windows Agent version 6.0 64-bit * Exchange 2007 with - Windows Server 2003 Standard x64 Edition SP2, R2(SP2) - Windows Server 2003 Enterprise x64 Edition SP2, R2(SP2) * Network - A TCP/IP stack (to communicate with Agent systems) * MS Windows IE 5 (or greater) Note: To work properly on Windows 64-bit the latest Microsoft C runtime library DLL (WINDOWS\system32\msvcrt.dll) should be installed. At the moment it has the version 7.0.3790.4034. The default installed dll is at version 7.0.3790.3959 or below. Please note, that this dll is not a part of automatic Windows update. You must update it manually. -------------------------------------------------------- 3.4.2 Conditional Requirements The Exchange 2007 Plug-In requires a valid Software License. Supported Platforms: The Exchange 2007 DR and MAPI Plug-In is supported on the following versions of Exchange 2007: Enterprise and Standard. OFM 9.601 can be used for local file backups. This version of the Plug-In supports the Microsoft defined Virtual Backup Device Interface (VDI). -------------------------------------------------------- 3.4.3 Install Procedure All products have appropriate installation guides. The guides are located at: http://support.EVault.com/ ________________________________________________________ ======================================================== 4 FIXES and KNOWN ISSUES 4.1 Fixes for the 6.01 release. This release of the Agent 64-bit and Plug-Ins for Windows Version 6.01 updates the "VV.exe" and "AgtUpgd.exe" files to address a possible 4k delta block issue on older Jobs. Note: For this problem to exist, an older Job must have been first created on a 32-bit Agent version <5.x and then upgraded to the 64-bit Agent (not a supported upgrade scenario) and backed up with the 6.00 Agent. Note that Jobs created by an Agent version 5 or greater use 32k delta blocks and are not at risk for delta corruption with regards to this issue. If an older Job with 4k delta blocks has been backed up with the 6.00 Agent, the safeset created will be deleted. When the Agent has been upgraded to 6.01, the Job will be re-seeded and the delta blocks will be created in 32k blocks. If an older Job with 4k delta blocks has NOT been backed up with the 6.00 Agent, no action is required. The version 6.01 Agent will correctly handle older Jobs with 4k delta blocks without error. Your Vault Administrator can alert you to any safesets where corruption has occurred. ======================================================== 4.2 Known Issues SQL Restore Fails with "SQLServerVdiDriver::open: GetConfiguration fails:" This has been fixed in this release, however, this error may still occur when restoring a Job that was backed up with the 6.00 agent and created with an earlier agent. WORKAROUND: Even after upgrading the Agent to 6.01, restores may still fail with the following errors: Oct24 13:15 MSQL-I-4096 [Microsoft][ODBC SQL Server Driver][SQL Server]Exclusive access could not be obtained because the database is in use. Oct24 13:15 MSQL-I-4096 [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE DATABASE is terminating abnormally. Oct24 13:15 MSQL-E-6188 Errors resulted in failure of the command Oct24 13:15 MSQL-E-6257 SQLServerVdiDriver::open: GetConfiguration fails: x-2139684861 O This may be a result of the failed restore with the 6.00 agent. Check the SQL Server Logs and look for the following messages: Bypassing recovery for database '' because it is marked IN LOAD. If this message exists, then you will need to recover the database manually, as follows: 1) Start SQL Server Analyzer 2) In the Query window, type in the following command: restore database "your db name here" with recovery 3) Press F5 to execute the query 4) Your database is now in a restorable state. Restore it with the 6.01 Agent. An upgrade from 4.62 to 5.60 to 6.01 does not modify Job's vvc file for "Compression = Standard" to a valid value. "Standard" is not shown as a valid value. Valid values are: "Better"(default), "Maximum", "Minimum", "None", and "Normal". Web CentralControl 6.00 shows "Standard" as "Unknown" and Windows CentralControl 6.00 shows "Standard" as "Better". If job is modified, "Standard" is changed to "Better". The Delta_Block_Size of an updated Job from Agent version 4.62 to 5.60 to 6.01 using Web CentralControl 6.00.2367 may be misrepresented as Delta_Block_Size = 0 in the Job's vvc file. On some Agent installs on Vista, the message "default.lng file can't be copied" has been encountered. This issue is currently being addressed. Should this occur, please contact support for a possible workaround. Bare Metal restore of Windows Vista requires that Microsoft Hotfix KB935606 is installed before a bare metal recovery is attempted (until Vista SP1 is delivered). Note: The 6.0 Agent will detect if the Microsoft Hotfix is installed. During an upgrade installation, if you chose a language other than English, the buttons "Yes" and "No" are not localized (remain in English). This is an InstallShield bug and they have been notified. Changes within the Agent (after an upgrade) may cause the initial backup after the upgrade to run longer than normal. This only affects the first run of a backup after an upgrade. During a Modify/Upgrade, if you select a language other than the language originally selected for installation, installation screens and notifications are displayed in the previously installed language. The workaround is to uninstall the Agent's Program files (not a total uninstall) and run a fresh install of the Agent kit, selecting the desired language when prompted. C++ error when backing up Exchange 2007 to a version 6 vault. Microsoft Windows 64-bit C runtime library DLL WINDOWS\system32\msvcrt.dll) should be at version 7.0.3790.4034 at least. The default installed dll is at version 7.0.3790.3959 or below. Please note, that this dll is not a part of automatic Windows update. You should update it manually. There is a MS patch available here: http://www.microsoft.com/downloads/details.aspx?FamilyId=431F9850-E40C-47A4-9BF1-16FFBA40B780&displaylang=en. Patch name is "WindowsServer2003.WindowsXP-KB932590-x64-ENU.exe". Deep folder backup behavior and limitations: 1) The Agent will skip and will not process objects when their full path exceeds the maximum allowable depth of 255 path elements (not characters). 2) If no files were backed up, the job is forced to fail. After a Restore Failure, the Agent Assistant icon in the task bar shows "Backup Failed". After a full restore with Exchange 2007, two services won't start. - MS Exchange Speech Engine - MS Exchange Unified Messaging This behavior is also experienced with Microsoft NT Backup. NTFS Single Instance Storage is not supported with this version of the Agent. The Agent backup log files do provide information when SIS files are encountered, but there is no other "warning" to the user, that data may not be backed up. A 6.0 Agent may show errors and warnings in the backup, for an Exchange DR job. 'O/S message: An operations error occurred.', and 'failed to get Exchange server full version.' The backup completes, but with log errors. In order to run Exchange DR, the BUAgent should be installed using the 'local system' account on systems running Exchange. For file level backups of MS SQL databases, QFS may not detect any changes (delta) as the files' size and modified time may not get changed. As a workaround, you can turn QFS off. This will increase the backup time. (Agent Assistant). If you check the field in Agent Assistant that says "Ask confirmation before starting Backup Jobs", and the PC is rebooted after the backup time, then you will not see the prompt. The backup will start. This is because the Agent Service (which runs the backup) starts before the tray application (which asks the prompt). Agent upgrade shows a message "some files that need to be upgraded are currently in use", with Exchange Management Console as the file name in use. It is safe to ignore this message and continue. If both OTM and Agent Assistant components are installed, then at the end of the installation you are asked to reboot the system, you will get a message "Failed to load settings. The Agent Assistant will now terminate." This is due to the system shutting down while the Agent Assistant is trying to start. The message can be safely ignored in this case. Windows CentralControl error messages during restore from another computer using same safeset: "Connection to the Vault is not using encryption" and "Failed to create synchronize log file" in VVAgent-*.Xlog, and: "SSET-I-4748 Connection to the Vault is using AES encryption" in BUAgent-*.Xlog "Unknown Error" with System State after recreating delta and backing up. This happens when two different tasks, both containing System State, are run at the same time (for example, dual vault setup). As a workaround, ensure there is enough time between backups so there is no overlap. If the "schedulescripts" folder exists inside an Agent installation directory, with .bat files inside it, you should not create a script called "schedulescripts". If that job is run, the safeset/delta/log files are also created inside the schedulescripts folder. If you then remove that job, the entire folder and all scripts there are deleted. Intra-file deferring does not work after delta recreation. If you have a large backup that has deferred, and you have to synchronize to recreate the delta file, then when the Agent rebuilds the delta entry, it sets the defer flag to false as it does not know if the previous backup was deferred or not. The subsequent backup does not use deferral, and so the entire file will be seeded. If User Account Control (UAC) is enabled on Windows Vista and you attempt to run a installation/uninstall or silent installation/uninstall, you will see a prompt "An unidentified program wants access to your computer" to Allow or Cancel. Installation/uninstall will not run until a user allows the program to run. The workaround is to run the installation/uninstall with UAC disabled. ________________________________________________________ ======================================================== 5 PRODUCT SUPPORT 5.1 Technical Support Complete contact information for your provider is available under the Help Support menu. -------------------------------------------------------- 5.2 Product Updates Product updates are available from your provider's web site. -------------------------------------------------------- 5.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) Plug-In Guides All documentation is available at the following location on the EVault site: http://support.EVault.com/ ________________________________________________________ ======================================================== 6 LEGAL INFORMATION EVault InfoStage Agent End User License Agreement THIS IS A LEGAL AGREEMENT ("AGREEMENT") BETWEEN YOU AND EVAULT, INC. ("LICENSOR"). PLEASE READ THIS AGREEMENT CAREFULLY. BY CLICKING THE "I ACCEPT" BUTTON OR TAKING ANY STEP TO DOWNLOAD, SET-UP, INSTALL OR USE THIS SOFTWARE, YOU AGREE, ON BEHALF OF YOURSELF AND YOUR COMPANY, IF THE SOFTWARE IS TO BE USED FOR BUSINESS PURPOSES, (COLLECTIVELY "LICENSEE"), TO BE BOUND BY ALL OF THE TERMS AND CONDITIONS OF THIS AGREEMENT. IF YOU DO NOT AGREE TO THESE TERMS AND CONDITIONS, CLICK "I DO NOT ACCEPT" AND YOU WILL NOT BE PERMITTED TO DOWNLOAD THE SOFTWARE OR IF YOU RECEIVED A CD CONTAINING THE SOFTWARE, RETURN THE SOFTWARE TO LICENSOR. IF WE HAVE AN EXISTING FORMAL WRITTEN SOFTWARE LICENSE AGREEMENT GOVERNING THE SOFTWARE, THEN THE TERMS IN THAT SOFTWARE LICENSE AGREEMENT WILL SUPERSEDE ANY CONTRARY TERMS IN THIS AGREEMENT. 1. License Grant. Licensor grants to Licensee a worldwide, nonexclusive, nontransferable license to use the EVault InfoStage Agent software (the "Software") on one device for internal business purposes only. Licensee is permitted to make a single copy of the Software for backup purposes. Except as expressly authorized above or as permitted by applicable law, Licensee will not: copy, in whole or in part, Software or any related documentation; modify the Software; reverse compile, reverse engineer, disassemble or reverse assemble all or any portion of the Software; rent, lease, license, sublicense, distribute, transfer or sell the Software; create derivative works of the Software; or use the Software to process data or provide any service bureau activity for any third party. Licensee obtains no rights in the Software except those given in this limited license. 2. Ownership. The Software, any related documentation and all intellectual property rights therein are owned by Licensor, its affiliates and/or its suppliers. The Software is licensed, not sold. Copyright laws and international copyright treaties, as well as other intellectual property laws and treaties, protect the Software. Licensee will not remove, alter or destroy any copyright, proprietary or confidential notices placed on the Software or any related documentation. Licensee agrees that aspects of the Software, including the specific design and structure of individual programs, constitute trade secrets and/or copyrighted or patented material of Licensor, its affiliates and/or its suppliers. Licensee agrees not to disclose, provide, or otherwise make available such trade secrets or material in any form to any third party without the prior written consent of Licensor. Licensee agrees to implement reasonable security measures to protect such trade secrets and material. 3. NO WARRANTIES. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW AND SUBJECT TO ANY STATUTORY WARRANTIES THAT CANNOT BE EXCLUDED, THE SOFTWARE AND ANY RELATED DOCUMENTATION ARE PROVIDED TO LICENSEE "AS IS." LICENSOR MAKES NO WARRANTIES, EXPRESS OR IMPLIED, AND EXPRESSLY DISCLAIMS AND EXCLUDES TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW ALL REPRESENTATIONS, ORAL OR WRITTEN, TERMS, CONDITIONS, AND WARRANTIES, INCLUDING, WITHOUT LIMITATION, IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, SATISFACTORY QUALITY AND NONINFRINGEMENT. WITHOUT LIMITING THE ABOVE, LICENSEE ACCEPTS THAT THE SOFTWARE MAY NOT MEET LICENSEE'S REQUIREMENTS, OPERATE ERROR FREE, OR IDENTIFY ANY OR ALL ERRORS OR PROBLEMS, OR DO SO ACCURATELY. LICENSEE USES THE SOFTWARE AT HIS/HER OWN RISK. This Agreement does not affect any statutory rights Licensee may have as a consumer. 4. EXCLUSION OF CONSEQUENTIAL AND OTHER DAMAGES. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT WILL LICENSOR, ITS AFFILIATES OR ITS SUPPLIERS BE LIABLE TO LICENSEE, LICENSEE'S CUSTOMERS, OR OTHER USERS, FOR DAMAGES OF ANY KIND INCLUDING, WITHOUT LIMITATION, DIRECT, CONSEQUENTIAL, SPECIAL, INCIDENTAL, OR INDIRECT DAMAGES OF ANY KIND ARISING OUT OF THE LICENSE OF, USE OF, OR INABILITY TO USE THE SOFTWARE (INCLUDING, WITHOUT LIMITATION, DATA LOSS OR CORRUPTION, ECONOMIC LOSS, LOSS OF ACTUAL OR ANTICIPATED PROFITS, LOSS OF CONFIDENTIAL INFORMATION, BUSINESS INTERUPTION, LOSS OF PRIVACY, FAILURE TO MEET ANY DUTY OF REASONABLE CARE OR NEGLIGENCE) EVEN IN THE EVENT OF THE FAULT, TORT, STRICT LIABILITY, BREACH OF CONTRACT, BREACH OF STATUTORY DUTY OR BREACH OF WARRANTY OF LICENSOR, ITS AFFILIATES OR SUPPLIERS AND EVEN IF LICENSOR, ITS AFFILIATES OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES OR SUCH DAMAGES WERE FORESEEABLE. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTIAL OR CONSEQUENTIAL DAMAGES SO THE ABOVE EXCLUSION OR LIMITATION MAY NOT APPLY. 5. LIMITATION OF LIABILITY. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT WILL LICENSOR'S LIABILITY EXCEED THE LICENSE FEE PAID BY LICENSEE OR US$5.00, WHICHEVER IS GREATER. THIS LIMITATION OF LIABILITY AND RISK IS REFLECTED IN THE PRICE OF THE SOFTWARE. NOTWITHSTANDING THE FOREGOING, NOTHING IN THIS AGREEMENT SHALL EXCLUDE OR LIMIT LICENSOR'S LIABILITY TO LICENSEE FOR ANY LIABILITY THAT CANNOT, AS A MATTER OF APPLICABLE LAW, BE EXCLUDED OR LIMITED. 6. INDEMNIFICATION. BY ACCEPTING THIS AGREEMENT, LICENSEE AGREES TO INDEMNIFY AND OTHERWISE HOLD HARMLESS LICENSOR, ITS OFFICERS, EMPLOYEES, AGENTS, SUBSIDIARIES, AFFILIATES, SUPPLIERS AND OTHER PARTNERS FROM ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR EXEMPLARY DAMAGES ARISING OUT OF, OR RELATING TO, OR RESULTING FROM LICENSEE'S USE OF THE SOFTWARE OR ANY OTHER MATTER RELATING TO THE SOFTWARE. 7. Termination. Licensor may immediately terminate this Agreement and the license granted hereunder if Licensee fails to comply with the terms and conditions of this Agreement. Upon such termination, Licensee must immediately cease using the Software, destroy or delete all copies of the Software and upon the request of Licensor, certify the destruction or deletion of the Software. Licensee may terminate this Agreement and the license granted hereunder at any time by destroying or deleting all copies of the Software. ALL DISCLAIMERS, LIMITATIONS OF LIABILITY AND ANY OTHER PROVISIONS INTENDED TO SURVIVE TERMINATION WILL SURVIVE ANY TERMINATION AND CONTINUE IN FULL FORCE AND EFFECT. 8. International Trade Compliance. The Software and any related technical data is subject to the customs and export control laws and regulations of the United States ("U.S.") and may also be subject to the customs and export laws and regulations of the country in which the download is contemplated or CD containing the Software is acquired. Further, under U.S. law, the Software and any related technical data may not be sold, leased or otherwise transferred to restricted countries, or used by a restricted end-user or an end-user engaged in activities related to weapons of mass destruction including, without limitation, activities related to designing, developing, producing or using nuclear weapons, materials, or facilities, missiles or supporting missile projects, or chemical or biological weapons. Licensee acknowledges that it is not a citizen, national, or resident of, and is not under the control of the government of Cuba, Iran, North Korea, Sudan or Syria or any other country on the U.S. State Department's list of state sponsors of terror, and that Licensee will not download or otherwise export or re-export the Software and any related technical data directly or indirectly to the above mentioned countries nor to citizens, nationals, or residents of those countries. Licensee will comply with all applicable export, re-export and foreign policy controls and restrictions imposed by the United States and will take the necessary actions and precautions to ensure that it complies with all such laws or regulations. 9. Governing Law. The laws of the State of California, United States, without regard to conflicts of laws principles, govern this Agreement. If applicable law does not permit the parties to agree to the governing law, the laws of the country in which Licensee downloads or acquires the Software govern this Agreement. To the extent permitted by applicable law, any dispute arising under this Agreement or relating to the Software shall be resolved by a court of proper jurisdiction in Santa Clara County, California, United States. Licensee and Licensor irrevocably submit to the jurisdiction of such courts and waive any and all objections to jurisdiction a party may have under applicable law. Notwithstanding the foregoing, if the Software is downloaded or acquired in the People's Republic of China, any dispute arising under this Agreement or relating to the Software shall be resolved by binding arbitration, held in Santa Clara County, California, United States, under the Judicial Arbitration and Mediation Services (JAMS) International Arbitration Rules. 10. Legal Effect. This Agreement describes certain legal rights. Licensee may have other rights under applicable law. This Agreement does not change Licensee's rights under applicable law if such laws do not permit the Agreement to do so. 11. Miscellaneous. This Agreement constitutes the entire agreement between Licensor and Licensee and governs Licensee's use of the Software, superseding any prior agreement between Licensor and Licensee relating to the subject matter hereof. Any change or modification to this Agreement will only be valid if it is in writing and signed on behalf of Licensor and Licensee. A failure by either party to enforce its rights under this Agreement is not a waiver of those rights or any other rights it has under this Agreement. The parties disclaim the application of the United Nations Convention on the International Sale of Goods. The terms of this Agreement are severable. If any term is unenforceable for any reason, that term will be enforced to the fullest extent possible, and the Agreement will remain in effect. The Software and any related technical data are provided with restricted rights. Use, duplication, or disclosure by the U.S. Government is subject to the restrictions as set forth in subparagraph (c)(1)(iii) of DFARS 252.227-7013 (The Rights in Technical Data and Computer Product) or subparagraphs (c)(1) and (2) of 48 CFR 52.227-19 (Commercial Computer Product - Restricted Rights), as applicable. To the extent permitted by applicable law, Licensee may not assign this Agreement, and any attempted assignment will be null and void. Seagate, the Seagate logo, and other Seagate and EVault names and logos are the trademarks of Seagate Technology LLC or its affiliates. 12. Contact Information. Any inquiries regarding this Agreement or the Software may be addressed to Licensor at 6121 Hollis Street, Emeryville, California, USA, 94608, or www.evault.com. Revised 07-26-2007