EVault InfoStage Plug-In for MS SQL Server Version 5.30.1873 Release Notes, July 27th, 2005 _______________________________________________________________ =============================================================== 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 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 MS SQL Server Plug-In. --------------------------------------------------------------- 1.1 Release History and Changes for 5.3 July 27th, 2005 - First release for version 5.30.1873 --------------------------------------------------------------- 1.2 Supported Platforms - MS SQL Server 7.0 with Windows 2000 Server - MS SQL Server 2000 with Windows 2000/2003 Server or SBS 2003 Premium Edition. This version of the Plug-In supports the Microsoft-defined Virtual Backup Device Interface (VDI). _______________________________________________________________ =============================================================== 2 FEATURES New Featues in the 5.3 release. 2.1 The SQL Plug-In application has a separate license requirement, but is now installed along with the Agent. It is operated and configured within the CentralControl program GUI. 2.2 Clustering is supported for Windows Agents, with a separately licensed Cluster Support Plug-In. The main function of the Cluster Support Plug-In is for the Agent on a MS SQL Server, which has a virtual IP address in the cluster, to be able to follow the server when it fails over to another node in a cluster. --------------------------------------------------------------- New Featues from the 5.0 release. 2.3 Version 5.00 and higher implements larger delta block sizes (32K). This will improve performance for backups. The larger block sizes result in the overall delta changes that are sent to the vault being smaller in total size, and thus using less disk storage space. It will also reduce the amount of CPU required for compression. Only newly created tasks will use this feature. Existing tasks will still use the smaller sized blocks. --------------------------------------------------------------- 2.4 Version 5.02 includes much better support for delta. The MS SQL Server backup stream is now processed logically rather than physically. This will greatly reduce the size of delta backups. The first backup after upgrading to 5.02 will result in an almost total reseed. Thereafter, the delta will be much smaller than it was with previous versions. If upgrading from an existing 4.x task, it may be desirable to create a new task under 5.02. This will automatically incorporate the 32K block size at the same time as the change from physical to logical deltizing. This will result in the best possible compression performance, both in terms of size and in terms of CPU consumption. --------------------------------------------------------------- 2.5 The MS SQL Server Plug-in has been designed to allow a user to perform a backup of a database (including read only databases) of an MS SQL Server (7.0 and 2000). The plug-in is installed on top of the Agent on the database host, to perform the backups, either on demand, or scheduled. The Plug-in application has its own installation program, but is operated and configured within the CentralControl. The database to be backed up must run on a single host. The Windows Agent and the MS SQL Server Plug-In must be together on the same system running MS SQL Server. This plug-in requires that you are running version 5.3 of the Agent, and CentralControl. This Version of the MS SQL Server Plug-In is implemented using the Microsoft-defined Virtual Backup Device Interface (VDI). This interface is a high-performance alternative to Named Pipes that was used in the earlier implementations of the MS SQL Server Plug-In. --------------------------------------------------------------- 2.6 Backup and Restore now handle multiple SQL Databases per task. The Restore destination can be the original database, another database, or a file. You are prompted if the Restore will overwrite an existing database. _______________________________________________________________ =============================================================== 3 FIXES _______________________________________________________________ =============================================================== 4 KNOWN ISSUES 4.1 The MS SQLServer Plug-In and the SQL Client must both be installed on the target system before the CentralControl "Get Status" will correctly show the status of the SQL Plug-In as "Installed". If the SQL Plug-In is installed without the SQL Client being installed as well, the status will incorrectly show the SQL Plug-In as "not installed". --------------------------------------------------------------- 4.2 If the SQL Server being backed up by the Plug-In was not installed as an original Microsoft product (that is, it has been resold/repackaged by a third party), you may get errors on trying to create an MS SQL task, such as “Failed to connect to the server.” Agent log may show “UNKNOWN ERROR in termRestore()” on every attempt to connect to the SQL Server. Get Status on the Agent may not show the SQL Server Plug-in, even though the license validates. The problem is that the installation is missing the NTWDBLIB.DLL file, which should be in the installation directory. Contact support to obtain a copy of this file. --------------------------------------------------------------- 4.3 Cannot restore MS SQL Database with the “Restore from another computer” option. It gives a “Failed to connect to server” error. This feature will be available in a future release. --------------------------------------------------------------- 4.4 Attempts to Restore from an incremental SQL Backup may fail with “REST-F-0014 task failed to complete.” and the database is left in a “loading” state. This may occur when attempting to Restore from an incremental backup where an external application (such as Enterprise Manager) was also performing a backup of the same database. --------------------------------------------------------------- 4.5 If you install SQL 2000 on a system and name the instance (i.e. uncheck the 'Default' check box and give it a name, ie:Test2), you will notice when you get to the dialog to select the SQL Server instance that there are two listed: one is called and the other will be the name you gave the instance (i.e. Test2). In this case, there is no instance. Furthermore if you attempt to connect to Default instance it will fail. --------------------------------------------------------------- 4.6 SQL backup/restore continues to function despite invalid authentication information. During a backup, from the 'New Task Wizard - Run As' dialog box, you only need to specify the UserName. You can perform a restore without specifying Username, Password, or Domain. The 'New Task Wizard - Run As' dialog box can have all authentication fields empty and still perform a Restore. --------------------------------------------------------------- 4.7 SQL 7.0 VDI database backups may fail when SQL Server 2000 is installed on the same machine. You may see errors in the log files such as: SQL server message 3013 and 10007. The issue is caused by a version mismatch between Sqlvdi.dll and Sqlresld.dll. A workaround can be found at: http://support.microsoft.com/default.aspx?scid=kb;en-us;280759 --------------------------------------------------------------- 4.8 SQL database backups and restores may fail when communication from the Agent is disrupted. SQL Server has its own timeout values, whereby if the connection is lost for more than a short time, the backup task using the server could fail. Normally, when a backup task (the Agent) is disconnected temporarily, it will retry to re-connect. But if the SQL server timeout expires first, the Agent cannot recover. Restarting the backup task with a good connection should allow the backup to succeed. --------------------------------------------------------------- 4.9 After a re-registration, and a subsequent failed backup or restore with the re-registered task, you may see a message in the "register.log" or the "backup.log" or "restore.log" like this: "Due to a computer registration, configuration file "" is missing the following information: RunAs.Password (Run As Password) RunAs.Username (Run As Username) SQLServer0.Password (Password) Use the Agent Console to re-enter the missing information. Detected missing configuration information. This may be due to a computer re-registration." To fix this problem, Open the Agent Configuration in Task Properties, re-enter the credentials in the "Run As" tab. Click OK to save and close it, and attempt the backup/restore again. --------------------------------------------------------------- 4.10 The SQL Agent Plug-In 5.30 must be used in conjunction with at least version 5.01 of the Director. --------------------------------------------------------------- 4.11 PTS#2795 Unable to restore 32GB user database over existing empty database using The SQL Server Plug-in. The Restore hangs. Workaround #1. Restore to a flat file, and use EM to bring the database in. This requires enough free disk space for the file. Workaround #2. Increase the reconnection settings in the vault profile on the agent (Global Settings/Vault Entry/Connectivity tab). Increasing the Retry value to 5 hours should keep the vault alive and be availble when the Agent is ready to communicate. The value of 'retry every ...' could be increased too, because there is no need to check for connection very often during this restore, while the Agent is busy with the DB. The second workaround can be used by users with limited free disk space. --------------------------------------------------------------- 4.12 PTS#3068 MS-SQL plugin removes transaction logs on incremental backup, but not a full backup. The MS SQL log size is reduced after an 'incremental' type SQL backup, but not after a 'full' type. This forces users who want to manage their SQL log size via backup to have to schedule incremental backups. if the logs are removed with an Incremental, it then requires the user to restore all previous Incremental backups to have all of the log files to restore the database. --------------------------------------------------------------- 4.13 PTS#3560 You may see three files, called Master.full, Master.Log and Master.End that are created by the Plug-In. They are only used by the Plug-In and are not needed by other programs (such as Enterprise Manager). They can be deleted by the user without affecting a restore via EM. --------------------------------------------------------------- 4.14 The Agent has been enhanced to handle Unicode 'filenames' as stored on file system. Plug-ins generate their own object names, but they are currently still in ANSI. --------------------------------------------------------------- 4.15 PTS#5379 When selecting a new backup task for the MS SQL databases, you are allowed to "Select All" databases. This would include the 'master' database, which cannot be backed up incrementally. Do not select/include the master database this way. --------------------------------------------------------------- 4.16 PTS#5380 The Restore log indicates that it has restored the database to the original location even if you have specified a different directory. The restore does correctly go to the directory. The restore log just does not report it properly. --------------------------------------------------------------- 4.17 PTS#5381 A Restore failure produces a prompt to select "OK" or "Respond to request later". This is a misleading message, in that you cannot respond later. _______________________________________________________________ =============================================================== 5 INSTALLATION NOTES 5.1 Installation Requirements Hardware -------- * CPU - Intel Pentium or compatible 166 MHz or higher processor * RAM - 128 MB or more recommended * HDD - A minimum of 10MB of available disk space or more * Video properties of 16-bit (or greater) for optimum GUI display. Software -------- * Director version 5.01, or 5.23 * CentralControl version 5.3 * Windows Agent version 5.3 * MS SQL Server 7.0 (SP4), with MS Windows 2000 Server (SP4) or MS SQL Server 2000 (SP4) with MS Windows 2000 Server (SP4), MS Windows 2003 Server (SP1), or SBS 2003 Premium Edition (SP3a). * Network - A TCP/IP stack (to communicate with Agent systems) * MS Windows IE 4 (or greater) --------------------------------------------------------------- 5.2 Conditional Requirements *A valid Software License for the MS SQL Server Plug-In is required. *A valid Software License for the Cluster Plug-In if required. --------------------------------------------------------------- 5.3 Install Procedure All products have appropriate installation guides. The 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 SQL Server Plug-In is as follows: * MS SQL Server Plug-In Release Notes (this document) * MS SQL Server 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 SQL SERVER PLUGIN 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. _______________________________________________________________ ===============================================================