Agent and Plug-Ins for Windows Version Release Notes

Transcription

1 Agent and Plug-Ins for Windows Version Release Notes

2 1 1 Overview This document contains release notes for this release of the Agent for Windows as well as the following Plug-Ins: - Exchange DR and MAPI Plug-In Oracle Plug-In SQL Plug-In SharePoint Plug-In Cluster Plug-In 6.10 Note: This release is for use in combination with Windows Agent Console 6.11, Remote Agent Console 6.10, Agent 6.10, Director 5.53, and Director In this release note, "Agent Console" when used without "Remote" or "Windows" in front means it applies to both Remote and Windows Agent Console. If something applies to only one version, then it will be noted. **** Important Information **** Regarding upgrading: Job reseed or fail: There are two scenarios in this release that may cause a backup job to fail or reseed. This applies when backing up to a 6.01 Vault. 1. This could occur if you have upgraded an older Agent Job (with the older 4k delta blocks) from 4.x, to 5.6 to 6.0 to 6.01 to A backup job (with the older 4k delta blocks) attempted by the 6.10 agent will fail. CLI Forcereseed command can be used to reseed this job (converts to 32K delta blocks). Note that Jobs created by an Agent version 5 or greater uses 32k delta blocks and are not at risk with this issue. 2. The reseeding scenario may occur during an upgrade because Exchange Mailbox names are now the same as those displayed in Exchange System Manager Console. If the older names contained wildcards, the newer names may cause a reseed. Note: A pop-up dialogue will be displayed during an upgrade if this directly affects your upgrade. See section 4.2, Known Issues, for details. 1.1 Release History and Changes for Agent version 6.0 September 19th, 2007, First Release, version October 18th, 2007, Second release, version a (This Hotfix contains Sharepoint.dll 2375) October 24th, 2007, Third release, version (new "VV.exe" and "AgtUpgd.exe") February 20th, 2008, Fourth release, version Supported Platforms This Agent is supported on the following platforms: - Windows 2000 Server (SP4) - Windows 2000 Advanced Server (SP4) - Windows 2003 Server Standard Edition (SP2) - Windows 2003 Server Enterprise Edition (SP2) - Windows 2003 Server Standard Edition R2 (SP2) - Windows 2003 Server Enterprise Edition R2 (SP2)

3 2 - Windows XP Professional (SP2) - Windows Vista Home Basic - Windows Vista Home Premium Edition - Windows Vista Business Edition - Windows Vista Ultimate Edition - Windows Vista Enterprise Edition - Windows Small Business Server 2003 (SP2), R2(SP2)x86 2 FEATURES 2.1 New Features in this 6.10 Release: Mailbox Active Directory names are now the same as those displayed in the Exchange System Manager Console. 2.2 Features in the 6.0x Release: The "VV.exe" and "AgtUpgd.exe" binaries are now at version for this release. The others are still at version , (except SharePointPlugin.dll which is at ). Upgrade 4k delta blocks issue fix. See Fixes section 4. Support for SharePoint Plug-In for backup and restores of MS SharePoint Portal Server 2003 and MS Office SharePoint Server Support for backup and restore of data files on Windows Vista Home Basic, 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 a Basic MSI (Microsoft Windows Installer) kit, where previously it was an InstallScripts kit. Both kits were developed using InstallShield 12 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. Note: This will only work for data that has been backed up with v6 agent and that is stored on v6 director (to be rolled out from Apr-08. "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

4 3 of a failure with delta recreation in rebuilding delta files. Note: This will only work for data that has been backed up with v6 agent and that is stored on v6 director (to be rolled out from Apr-08. 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 Remote Agent Console. Windows Agent Console 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 Remote Agent Console application and Help. The Agent Assistant also allows you to stop all running Agent processes. 3 INSTALLATION NOTES 3.1 Windows Agent Installation/Upgrade Requirements The installation requirements for the Agent under Windows OS - Windows 2000 Server (SP4) - Windows 2000 Advanced Server (SP4) - Windows 2003 Server Standard Edition (SP2) - Windows 2003 Server Enterprise Edition (SP2) - Windows 2003 Server Standard Edition R2 (SP2) - Windows 2003 Server Enterprise Edition R2 (SP2) - Windows XP Professional (SP2) - Windows Vista Home Basic Edition - Windows Vista Home Premium Edition - Windows Vista Business Edition - Windows Vista Ultimate Edition - Windows Vista Enterprise Edition - Windows Small Business Server 2003 (SP2), R2(SP2)x86 *.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. * The Agent install requires at least 100MB of free space for a new (fresh) install. An upgrade may require more. If there is not enough disk space, the install will display a message. Also, with this installation package, the system drive will require free space to decompress the package, regardless of the drive to which you are installing. The actual amount of space will vary, but a recommended amount of 100 to 200 MB should suffice. The environment variables TEMP and TMP by default use %USERPROFILE%. You should

5 4 ensure that this variable points to a drive with sufficient temporary space. * A TCP/IP stack (for communicating with the Vault and the Agent Console software). * Optionally, Open Transaction Manager (OTM) or Open File Manager (OFM) (OTM is a product of Columbia Data Products and OFM is a product of St. Bernard Software). Note: OFM is NOT supported on Windows Vista. * Director versions 5.53 and 6.01 * Windows Agent Console version 6.11 * Remote Agent Console version 6.10 * 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. * This version only supports upgrades from version 5.6 and 6.0x, to version Versions earlier than 5.6 must first be upgraded to version 5.6. (See the warning note in the Overview section of this Release Note about Upgrading and Reseeding.) * Note: SBE 5.33 Agent upgrades require first upgrading to Agent 5.6 before upgrading to the version 6.0 Agent. The SBE 5.33 Agent cannot be upgraded directly to Conditional Requirements In General: * In order to graphically configure and administer the Agent, the Agent Console 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. Note: OFM 9.6 does not support Microsoft Windows Vista. * The Agent should NOT be installed on a Windows 2000/2003 encrypted directory. If you want to manage an Agent from both Windows Agent Console and Remote Agent Console, they must both be installed using the same service account user identities. That is, BUAgent" and "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 Installation Files The following files are installed by the Agent installation kit: * Agent software (VVAgent or BUAgent) * Agent User Guide (pdf) * Release notes (this document) * Open Transaction Manager, OTM (optional) * Note: The Agent install will install the file

6 5 VVClMsg.dll in the System directory. This file containsthe error codes and resource strings which the event viewer uses to display the Agent messages 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.2 Exchange DR and MAPI Plug-In The MS Exchange Plug-In is supported on the following platforms: - MS Exchange 2000 (SP3) on Windows 2000 Server (SP4) - MS Exchange 2003 (SP2) on Windows 2003 Server (SP2) - MS Exchange 2003 (SP2) on Windows 2000 Server (SP4) Note: MS Exchange 2007 is not supported by this Agent, but is supported on Windows bit by the 64-bit Agent and associated Exchange Plug-In Installation Requirements Hardware See the Windows Agent User Guide and above Agent requirements. Software * Director version 5.53 and * Agent version 6.10 * Windows Agent Console version 6.11 * Remote Agent Console version MS Exchange 2000 (SP3) with Windows 2000 Server (SP4) - MS Exchange 2003 (SP2) with Windows 2003 Server (SP2) - MS Exchange 2003 (SP2) with Windows 2000 Server (SP4) * Network - A TCP/IP stack (to communicate with Agent systems) Conditional Requirements The MS Exchange Plug-In requires a valid Software License. 3.3 Oracle for Windows Plug-In Installation Requirements Hardware For Windows hardware requirements, see the Windows Agent documentation. Software

7 6 * MS Windows 2000 Server (SP4) or * MS Windows 2003 Server (SP2) or * MS Windows 2003 Server R2 (SP2) *.NET Framework 2.0 * Windows Agent Console version 6.11 * Remote Agent Console version 6.10 * Windows Agent version 6.10 * Oracle 8i (version or greater) * Oracle 9i * Oracle 10g * Oracle Plug-In, version 6.10 * Network - A TCP/IP stack (to communicate with Agent systems) Conditional Requirements The Oracle Plug-In requires a valid Software License Install Procedure If you install the Oracle Plug-In, you must also install the "Oracle Plug-In Support Libraries" after the Agent has been installed. This is a separate InstallShield installation, called "OraclePluginSupport-5-60.exe". This is not included as part of the Agent installation, and must be run separately. 3.4 Cluster Plug-In Installation Requirements Hardware See the Windows Agent User Guide and above Agent requirements. Software * Windows 2000 Advanced Server (SP4) * Windows Server 2003 Enterprise Edition SP2, R2(SP2) * Windows Agent Console version 6.11 * Remote Agent Console version 6.10 * EVault InfoStage Windows Agent version 6.1 * Network - A TCP/IP stack (to communicate with Agent systems) Conditional Requirements The Cluster Support Plug-In requires a valid Software License. Note: This version of Agent does not support the Oracle Plug-In on a Windows cluster Install Procedure & Recommendations The Plug-In is installed as part of the Windows Agent.

8 7 1. Install the Agents and Plug-Ins on the Physical Nodes. 2. Set Cluster, SQL, and Exchange Plug-Ins on the Physical Nodes. 3. Create a New Agent for your Exchange or SQL 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. 5. From here you must select a drive letter for your SQL or Exchange Cluster. Click OK. This will launch the Agent Configuration Window. 6. Here you must specify all of your Vault connection information. Click OK when complete. 3.5 SQL Plug-In Supported Platforms: - MS SQL Server 2000 (SP4) with Windows 2000/2003 Server - MS SQL Server 2005 (SP2) with Windows 2000/2003 Server Note: These MS SQL Server 2005 versions are supported by the 6.0 Agents with the MS SQL Plug-in: Enterprise, and Standard. These MS SQL Server 2005 versions are supported by the 6.0 Agents with OTM/OFM:- Workgroup, and Express. This version of the Plug-In supports the Microsoft-defined Virtual Backup Device Interface (VDI) Installation Requirements Hardware See the appropriate Windows Agent User Guide and above Agent requirements. Software * Director version 5.53 and 6.01 * Windows Agent Console version 6.11 * Remote Agent Console version 6.10 * Windows Agent version 6.10 * MS SQL Server 2000 (SP4) with Windows 2000(SP4)/2003 Server (SP2) * MS SQL Server 2005 (SP2) with Windows 2000(SP4)/2003 Server (SP2) * Network - A TCP/IP stack (to communicate with Agent systems) * MS Windows IE 5.5 (or greater) NOTE: MSDE named instances may not be visible in Windows Agent Console, with only the default instance shown. If you set the "DISABLENETWORKPROTOCOLS=0" parameter during the MSDE installation, then Windows Agent Console should be able to browse named instances Conditional Requirements

9 8 *A valid Software License for the MS SQL Server Plug-In is required. 3.6 SharePoint Plug-In Supported Platforms: - MS SharePoint Portal Server 2003 with Windows 2003 Server (SP2) or R2(SP2) - MS Office SharePoint Server 2007 with Windows 2003 Server (SP2) or R2(SP2) Installation Requirements Hardware See the appropriate Windows Agent User Guide and above Agent requirements. Software * Director version 5.53 and 6.01 * Windows Agent Console version 6.11 * Remote Agent Console version 6.10 * Windows Agent version 6.10 * SharePoint Plug-In Conditional Requirements *A valid Software License for the SharePoint Server Plug-In is required. * Note: SQL Native Client is required on the local SharePoint machine for it to function properly, and to connect via SQL authentication mode for this release. SharePoint Plugin backups using multiple, separate SQL Servers are not currently supported. That is, you cannot have SharePoint environments that use different instances of SQL Server to host the various SharePoint databases. 4 FIXES and KNOWN ISSUES 4.1 Fixes Fixes for the release. During an upgrade from a 5.6 Agent to a 6.0 Agent, in the Silentinstall.xml file, the option of <FeatureAgentTray>off</FeatureAgentTray> was not responding correctly. Now the on/off switch works correctly. (11616) A failure in one SQL database caused the entire SQL backup job to fail. This may happen if the database is open, or running some process. To be able to skip the database, use either /LOGANDCONTINUE=YES in vv.exe parameter list or set (create) registry DWORD entry HKEY_LOCAL_MACHINE\'0dLOGANDCONTINUE to '1'. (8035). An Agent 5.63 to 6.00 upgrade changed the Agent startup from 'BUAgent' to 'LocalSystem'. Now, if the selection was BUAgent, the upgrade will default to BUAgent.

10 9 In a case where the 5.63 installation used custom account, the upgrade will default to Custom and will populate the username field. The password needs to be entered again by the user, as the system does not know the old password. (10875) Mailbox Active Directory names are now the same as those displayed in the Exchange System Manager Console. NOTE that this may cause a reseed if the names get changed. See Known Issues for details. (8767, 11522, 11627) An upgrade from 4.62 to 5.60 to 6.01 did not modify a Job's vvc file for "Compression = Standard" to a valid value. This has been fixed in this release. (11040) Open Shared-Write doesn't work the same way in 6.0 In 5.6 and below, if a word document was open, the message would be a warning about the file being opened for shared write. In 6.0, the error states "O/S message: The process cannot access the file because another process has locked a portion of the file". Now it says the file was opened shared-write because another process had it open for write". (11308) System State Restore generates error ý ýss-e-4495 VRegistry::UpdateHiveFile() failedý. Fixed in this release. (11095) SharePoint (2007) - VV crashes after long backup (over 1 hour). Caused by memory management. (11148) A version 6 Agent backing up to a version 6 QSM reseeds each safeset. The Agent synchronizes with the vault and assumes that the safeset is not available, because they are in the work area. (10990) CRC mismatch during pool optimization causes a disabled task. Caused by QFS not detecting streams that changed. (10966) MS SQL databases with a comma ý,ý or a closed bracket ý]ý in their name failed to backup. (7677) With the MS Exchange Plug-in, it was showing numbers after the usernames in the MAPI selection list. (6048) MS Exchange MAPI verify test failed post-backup of MAPI job. (10951) Vault GUID mismatch in global.vvc prevents agent from claiming proper license(s) on the vault. Showed errors such as: "Oct31 14:06 AGNT-E-0518 Failed to check or claim license. The Agent hosting this virtual server must be registered with the same Vault" (10764) A scheduled backup failed with "Detected more than one identical streams" error message, on a sparse file selected for backup (10833) Agent Assistant shows "Network connection is down" when primary network connection is up on a multi-homed computer (one wired, one wireless). (10851) System state backup errors on Windows 2000 servers: ýss -E-0005 O/S message: The RPC server is unavailableý and ýss -E-0003 unable to

11 10 enumerate system protected filesý. (10854) A version 6 Agent backing up to a version 6 QSM reseeds each safeset. The Agent synchronizes with the vault and assumes that the safeset is not available, because they are in the work area. (10990) Restores from a QSM failed if the Agent was not synchronized first. It was comparing vault IPs from different places. (10992) Oracle backup gives an error and then the agent continues the backup on the next attempt as if everything was okay. ýoct09 18:32 NONE-F-0361 internal error: ***.cpp, line 349 ***ý Another backup solution was overlapping and removing archive log records from the database. Now the backup will skip empty archive logs and continue.(11060) A Restore from another computer wizard (from a virtual node) gives an error: "Could not download requested job."agent looks for the vvc in local agent folder (not EVAULT_SHARED) (11371) In Remote Agent Console 6.1. ý.batý scripts in the ScheduleScripts folder of the Agent installation are spawned by the scheduler, but do not run. (11400) Version 6.01 Agent reports "delta file is unusable - delta options have changed". The Agent was changed to ignore ýdelta_processingý option and always read the delta block size option. (11414) The "/forcereseed" option should actually reseed even when a delta mapping file is present (11438) SQL Restore Fails with "SQLServerVdiDriver::open: GetConfiguration fails:" This has been fixed in this release. (11051) Restores were failing with error: ýdecompression error in stream sequence #2 error.ý (11363/8277) Fixes for the release. A problem may have occurred if an older Job with 4k delta blocks was 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 unusable for restore purposes. When the Agent has been upgraded to 6.01, the Job will automatically re-seed and the new safeset will restore correctly (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. Note: If an older Job with 4k delta blocks has been backed up with the 6.00 Agent and the 6.0 safeset has been deleted, then the Job must be re-seeded, by the 6.01 Agent, using the CLI command forcereseed (see the Agent Guide for details). (11553 and

12 ). SQL Restore Fails with "SQLServerVdiDriver::open: GetConfiguration fails:" (11051) This has been fixed in this release. This error may still occur when restoring a Job that was backed up with the 6.00 Agent and created with an earlier Agent. For a Workaround, see Known Issues, section 4.2, Workaround below. Fixes for the a release. (MOSS 2007) - SharePoint 2007 backup creates a memory dump. (10901) (SPS2003, MOSS2007) - Backup aborted with error message ADO error: Query timeout expired for file (1). (11490) 4.2 Known Issues On a Cluster, after failover of a virtual server, BUAgent generates error "AGNT-E-7458 Network error: Unable to connect to the AMP Proxy - an agent with the same Agent ID is already connected - please contact support". (11638) In Window Agent Console, a Cluster license is claimed when a job is created on a virtual server. In Remote Agent Console the Cluster license is claimed when job is run on a virtual server. (11637) After an upgrade from version 6.01, a reboot is required for "Agent Assistant" upgrade. (11625) Install kit logs a message in eventlog that it is trying to restart the computer to complete the installation. Messages are logged due to WinSxS libraries being in use by another application (like Remote Agent Console). (9880) SharePoint backup using a 6.10 Agent shows poor performance with files over 100MB, and the backup may fail. (11624) Windows Agent Console 6.xx is also removed when you run a Total Uninstall of an upgraded Windows Agent. This happens because the older Windows Agents (4.6x and 5.6x) install path was C:FilesInfostageby default. If Windows Agent Console was installed on the same computer as that agent, Windows Agent Console would have been installed in C:Files Infostage by default also. When the agent is upgraded to 6.xx, it upgrades the agent files in the original agent path. When you now run a Total Uninstall, it removes all files in C:Files Infostage including the Windows Agent Console binaries. Note that from Windows Agent version 6.00 upwards, the default install path was changed to C:Files Infostage for clean installs. (11050) If a MAPI backup does not have anything to backup (due to restrictive wildcard use, for example) then the backup log does not point to any cause for the failure ("BCKP-F-4110 job failed to complete") (11622) A virtual SQL Server may fail with an error message "Failed to launch backup", when a "RunAs" user is specified. If the information from the "RunAs" tab is deleted, the backup will complete. (11636)

13 12 If the name of the directory where the Agent is installed begins with a series of digits (such as c:102430) then the Agent may crash with an error ("BCKP-E-4712 std::exception caught"). Note that using the default directory does not cause a problem. As a workaround do not use a directory that starts with numbers. (11684) Default MAPI backups can be restored, but backups of Unicode MAPI tasks to PST are not supported. (11677) An Older Job with 4k delta blocks can fail. This could occur if you have upgraded an older Agent Job (with the older 4k delta blocks) from 4.x, to 5.6 to 6.0 to 6.01 to A backup job (with the older 4k delta blocks) attempted by the 6.10 agent will fail. CLI Forcereseed command can be used to reseed this job (converts to 32K delta blocks). Note that Jobs created by an Agent version 5 or greater uses 32k delta blocks and are not at risk with this issue. (11614) Mailbox Active Directory names are now the same as those displayed in the Exchange System Manager Console. NOTE that this may cause a reseed if the names get changed. Details: During the MAPI upgrade, an attempt will be made to automatically replace older MDB mailbox names (used within existing Backup Job selections) with Active Directory names used by Exchange System Manager Console. However, if there are wildcard selections in your MAPI jobs, and some names do NOT coincide with the new Active Directory names, a pop-up will appear. Click on "View details" to see which recipientýs mailboxes will not be selected or will be added. If you proceed with the upgrade, you can later manually change the backup Job to correct wildcard selections as shown in the log. (8767, 11522, 11627) In the SharePoint plug-in, the ability to restore large files depends on the amount of system memory. Restore needs at least three and a half times the file size for memory. As a workaround, you can first restore to the file system and then upload to SharePoint. (10967) A blank [.vpr] file may be created when a SQL restore is started. 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. (10839) Bare Metal restore of Windows Vista requires that Microsoft Hotfix KB 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. (10336) Exclusion of files with "System Files" directories in a SharePoint backup jobs, is currently not excluding those files. (10396) During an installation (on an English OS), if you chose a language other than English, the buttons "Next", "Back", "Cancel", "Yes" and "No" are not localized (remain in English). This is an InstallShield bug and they have been notified. (10878, 10132)

14 13 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. (9718) 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. Remote Agent Console unable to create a new SharePoint job. Fails to connect using SQL Server Authentication with SharePoint Plug-In. SQL Native Client is required on the local SharePoint machine for it to function properly, and to connect via SQL authentication mode. (10038) 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. (9763) After a Restore Failure, the Agent Assistant icon in thetask bar shows "Backup Failed". (9842) 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. (7582) OTM autoplacement may not place its cache file on a disk with enough free space. OTM will fail with error code 112 (not enough space on disk). You can force OTM to use another disk (with enough free space) by setting the registry entry: \HKEY_LOCAL_MACHINE\'0dto specify a valid path for the CacheFileLocation for a non- OTMed drive. (9388) 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. (9494) You must not install Agent version 6.10 (with the Agent Assistant), on the same machine that is running Remote Agent Console 5.6x. It can be installed without the Agent Assistant. The Agent Assistant requires.net Framework 2.0 but Remote Agent Console 5.6x is not supported when.net Framework 2.0 is present. (9529) 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

15 14 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. (9474) Windows Agent Console 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. (10684) The SharePoint Plug-in will allow you to restore from another computer. But the restore to the SharePoint server will fail, as it is not the same SharePoint (computer) that did the backup. But, if you restore (from another computer) to the file system, you will be able to recover the SharePoint document(s). (10465) You cannot browse an Exchange 2007 MAPI tree unless you use Agent service logon of "LOCAL_SYSTEM" (on Active Directory and Exchange Server) instead of "BUAgentAccount". (10452) 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. (9189) 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. (10395) 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. (10788) On Exchange enabled backups, the backup log gives an error message: ýos error. Not enough storage is available to complete this operation.ý (6354) System State backups fail with "std::exception caught" and "VRegistry::Initialize() unable to map drive" errorsý (11479) If the agent tries to backup a job that has been deleted from the vault, it fails with a

16 15 license error message: "AGNT-F-0500 Failed to claim the following license(s) from the Vault (Server Backup Agent)." However there may still be sufficient licenses on the vault, and the quota has not been exceeded. As a workaround, recreate the job to re-register it to the vault. (11111).

17