VBAK Agent 64-bit for Windows Version 5.61.2248 Release Notes 30 th March 2007 1 OVERVIEW This document contains release notes for the new release of the Windows Agent 64-bit. This document contains release notes for the latest release of the Windows Agent 64-bit as well as the following Plug-Ins: - Cluster Plug-In 5.6 - SQL 64-bit Plug-In 5.6 Note: This version is limited for use in combination with Windows or Web CentralControl 5.6, SQL 64-bit Plug-In 5.6, Cluster Plug-In 5.6, and Director 5.27 or 5.52. 1.1 Release History and Changes for Agent version 5.60 January 5th, 2007 - First Release, version 5.60.2221a January 26th, 2007 - Second release, version 5.60.2221b March 30th, 2007 - Third release, version 5.61.2248 1.2 Supported Platforms This Agent is supported on the following platforms, with EM64T or AMD64 processors: - Windows Server 2003 Standard x64 Edition SP2, R2(SP2) - Windows Server 2003 Enterprise x64 Edition SP2, R2(SP2) 2 FEATURES Features in this Release: Note: The Agent has added support for OFM 9.601. 2.1 Supports 64-bit processing. 2.2 Bandwidth Throttling: The user now has the capability to either let the Agent use as much bandwidth as available for backups and restores, or "throttle back" and restrict the usage (i.e.: in Kb/sec). Bandwidth Throttling can also be scheduled (turned on and off) by time of day, and days of the week. 2.3 Advanced Filtering to improve backup performance and usability. 2.4 Browse and backup network resources via UNC paths (for Windows Agents only). The UNC share will be the root for the browse, instead of a device letter.
2.5 Cross catalog searching. Users can search through all available catalogs when restoring files, without switching Restore Wizard screens. 2.6 Restore from another computer. The User can restore from another computer when the job name is identical on both computers. 2.7 The Windows installation kit allows the user to choose an account other than LocalSystem, under which to run the Server Agent's VVAgent and BUAgent services. Two separate options are provided. The first option lets the user specify an existing account (with password) and the second lets the kit automatically generate the user account and password. 2.8 Support for UTF-8 Unicode. 2.9 Support for MS SQL 64-bit Server 2005 SQL Plug-in. 3 INSTALLATION NOTES 3.1 Windows Agent 64-bit 3.1.1 Installation 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) * 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). * Director version 5.27 and 5.52. * CentralControl version 5.6 or * Web CentralControl version 5.6 * 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.601 is supported. * The Agent should NOT be installed on a Windows 2003 encrypted directory. 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. Note that version 5.6 Agents and Plug-Ins require a separate license if you are connecting to a vault that is version 5.27 or lower. If you are connecting to a vault that is version 5.52 or more, the license is supplied automatically from the vault. 3.1.5 Install/Uninstall Procedure 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. 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, Standard, and Developer. 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 5.27 and 5.52. * Win CentralControl version 5.6 - or - * Web CentralControl version 5.6 * Windows Agent version 5.6 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. *A valid Software License for the Cluster Plug-In is required. 3.3.3 Install Procedure All products have appropriate installation guides. 4 FIXES and KNOWN ISSUES 4.1 Fixes for version 5.61.2248 DTS#9102 Time change (>75 minutes) on a server caused the client Agent to reload the schedule, but it did not run a scheduled backup unless the Agent was reloaded (restarted). DTS#9080 When performing a Restore from Another Computer to a 5.60 64-bit Agent, the restore failed with errors/warnings in the log file. "Unexpected std::exception caught", and "job failed to complete." DTS#9073 If you selected the WinCC only option during the 5.6x Agent install, the BUAgent service was installed in a Stopped state. However, it was set to start Automatically. This meant errors were generated when the Agent system started as BUAgent cannot connect to a proxy when none is set up.in all cases, if the agent is not registered to Remote Agent Console (meaning there is no buagent.cfg file) then the BUagent service should be set to start manually. If the agent is registered, the buagent service should be started and set to start automatically. If the user is not changed, then the service should still be registered to that same user. If the user is changed, the service should be registered to the new user, even if it is set to start manually. DTS#9000 New DST did not run scheduled jobs on Director or Agent for 2am. DTS#8887 SYSVOL volume was not fully restored from the system state backup for Long File Names. DTS#8773 Not all online databases are listed in selection list on 5.60 plug-in/5.62 Agent Console. DTS#5179 Scheduler, in some cases was not honoring the priority in the schedule.cfg. This happened when the order of schedules was changed without restarting the Agent service. This has been fixed in this release. 4.2 Known Issues
DTS#8802 If you have a long backup (for example a seed over many days) and you want to throttle way back during the day and have no throttling during the night, it may not throttle back after a "full throttle". If you try to change the setting while it is running, it may not have an effect. If you do not have any deferral set, you can, as a workaround, set the deferral to 24 hours. This will cause the backup to stop and re-start immediately and use the proper throttling. DTS#8750 Cluster virtual server appears registered after moving it from another WebCC server. Unable to interact with virtual server. DTS#8602 If you select System State and/or EventLog at the top level, for backup with BUAgent, the restore completes with 0 bytes. As a workaround, if you select all the components individually, the backup and restore will succeed. DTS#8189 The backup log states a maximum path size is 512 characters, but actually it can only be 511 characters. If the path is too long, you will see an error message: "DISK-W-0379 File cannot be processed because the path exceeds the allowable path size"..."(512 bytes, maximum 512 bytes)". DST#7715 and DTS#7023 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.