MBS Agent 32-bit and Plug-Ins for Windows Version Release Notes

Transcription

1 MBS Agent 32-bit and Plug-Ins for Windows Version Release Notes

2 1 1 OVERVIEW This document contains release notes for the 6.72 Windows Agent 32-bit as well as the following Plug-Ins: MS Exchange DR, DR (VSS), and MAPI Plug-In Oracle Plug-In MS SQL Plug-In MS SharePoint Plug-In Cluster Plug-In This release is for use in combination with Web or Windows Agent Console 6.72 and Director 5.53, 6.04a, or above. Agent 6.72 supports BMR type backup Jobs. Note that for full BMR type restores, ESR software version 1.1 (or greater) is required. Note: This version uses a new VSS (Volume Shadow Copy Service) based open file manager for backup of open or locked files. OTM can still be used with older Jobs or in a custom manner, but is not used by default. In these release notes, "Agent Console" without "Web" or "Windows" in front means that it applies to both Web and Windows Agent Console. If something applies to only one version, it will be noted. 1.1 Release History Version , April 30th, Supported Platforms This Agent is supported on the following x86 platforms: - Windows Server 2003 Standard (SP2) and R2 (SP2) - Windows Server 2003 Enterprise (SP2) and R2 (SP2) - Windows Small Business Server 2003 (SP2) and R2 (SP2) - Windows XP Professional (SP3) - Windows Vista Home Basic (SP2) - Windows Vista Home Premium Edition (SP2) - Windows Vista Business Edition (SP2) - Windows Vista Ultimate Edition (SP2) - Windows Vista Enterprise Edition (SP2) - Windows 7 Starter - Windows 7 Home Basic - Windows 7 Home Premium - Windows 7 Professional - Windows 7 Enterprise - Windows 7 Ultimate - Windows Server 2008 Standard (SP2) - Windows Server 2008 Enterprise (SP2) - Windows Server 2008 Datacenter (SP2) - Windows Server 2008 Server Core (SP2)

3 The MS Exchange Plug-In (DR, MAPI) is supported on the following platforms (including Cluster support). MS Exchange 2003 (SP2) on the following platforms: - Windows Server 2003 Standard (SP2) and R2 (SP2) - Windows Server 2003 Enterprise (SP2) and R2 (SP2) - Windows Small Business Server 2003 (SP2) and R2 (SP2) The Oracle Plug-In is supported on the following platforms. Oracle 9i and 8i (version or greater) on the following platforms: - MS Windows 2003 Server (SP2) - MS Windows 2003 Server R2 (SP2) Oracle 10g on the following platforms: - MS Windows 2003 Server (SP2) - MS Windows 2003 Server R2 (SP2) - MS Windows 2008 Server (SP2) Oracle 11g on the following platforms: - MS Windows 2003 Server (SP2) - MS Windows 2003 Server R2 (SP2) - MS Windows 2008 Server (SP2) The MS SQL Plug-In is supported on the following platforms (including Cluster support). MS SQL Server 2000 (SP4) on the following platforms: - Windows Server 2003 Standard (SP2) and R2 (SP2) - Windows Server 2003 Enterprise (SP2) and R2 (SP2) - Windows Small Business Server 2003 (SP2) and R2 (SP2) MS SQL Server 2005 (SP3) on the following platforms: - Windows Server 2003 Standard (SP2) and R2 (SP2) - Windows Server 2003 Enterprise (SP2) and R2 (SP2) - Windows Small Business Server 2003 (SP2) and R2 (SP2) - Windows Server 2008 Standard (SP2) - Windows Server 2008 Enterprise (SP2) - Windows Server 2008 Datacenter (SP2) MS SQL Server 2008 (SP1) on the following platforms: - Windows Server 2003 Standard (SP2) and R2 (SP2) - Windows Server 2003 Enterprise (SP2) and R2 (SP2) - Windows Small Business Server 2003 (SP2) and R2 (SP2) - Windows Server 2008 Standard (SP2) - Windows Server 2008 Enterprise (SP2) - Windows Server 2008 Datacenter (SP2)

4 The MS SharePoint Plug-In is supported on the following platforms (including Cluster support). MS SharePoint Portal Server 2003 on the following platforms: - Windows Server 2003 Standard (SP2) and R2 (SP2) - Windows Server 2003 Enterprise (SP2) and R2 (SP2) - Windows Small Business Server 2003 (SP2) and R2 (SP2) - Windows Server 2008 Standard (SP2) - Windows Server 2008 Enterprise (SP2) - Windows Server 2008 Datacenter (SP2) MS Office SharePoint Server 2007 on the following platforms: - Windows Server 2003 Standard (SP2) and R2 (SP2) - Windows Server 2003 Enterprise (SP2) and R2 (SP2) - Windows Small Business Server 2003 (SP2) and R2 (SP2) - Windows Server 2008 Standard (SP2) - Windows Server 2008 Enterprise (SP2) - Windows Server 2008 Datacenter (SP2) MS Windows SharePoint Services (WSS) 3.0 on the following platforms: - Windows Server 2003 Standard (SP2) and R2 (SP2) - Windows Server 2003 Enterprise (SP2) and R2 (SP2) - Windows Small Business Server 2003 (SP2) and R2 (SP2) - Windows Server 2008 Standard (SP2) - Windows Server 2008 Enterprise (SP2) - Windows Server 2008 Datacenter (SP2) 2 FEATURES * Support for Windows 7 * Support for Oracle 11g with the Oracle Plug-In * Changes in Restoring to an Alternate Location behavior. The Preserve folder structure checkbox has been removed from the Restore Wizard. If your data to restore has been selected with the recursive option, the directory structure will also be restored to the alternate location (starting from the selection point of the included item). You can individually specify whether your restore/directory selections are recursive or not. Note: This version uses a new VSS (Volume Shadow Copy Service) based open file manager for backup of open or locked files. OTM can still be used with older Jobs or in a custom manner, but is not used by default.

5 4 3 INSTALLATION NOTES 3.1 Windows Agent Installation Requirements * A computer running one of the supported operating systems listed in Section 1.2 * CPU and RAM to meet the basic requirements of your operating system, as prescribed by Microsoft * 16-bit (or greater) video properties for optimal GUI display * MS Windows Internet Explorer 6 (or greater) * A TCP/IP stack (for communicating with the vault, Agent, and Agent Console software) * At least 100 MB of free disk space for a fresh installation. An upgrade may require more. If there is not enough disk space, the application will issue a message. Also, for this installation, the system drive requires free space to decompress the package (regardless of which drive the installation targets). The actual amount of space will vary, but a recommended amount of 100 to 200 MB should suffice. The environment variables TEMP and TMP use %USERPROFILE% by default. Make sure that this variable points to a drive that has sufficient temporary space. This release is for use in combination with Web or Windows Agent Console 6.72, Remote Agent Console 6.72, and Director 5.53, 6.04a, or above Conditional Requirements * You require.net Framework 2.0 if you install the Agent Assistant with the Agent. * DO NOT INSTALL the Agent in a Windows-encrypted directory. Exclude installation directories (as well as anti-virus directories) from open-file protection. Note: If you use an anti-virus (AV) program, disable real-time scanning on reads (called "outgoing" on some AV products). Do not back up the actual AV directories. In order to graphically configure and administer the Agent, you need to install Agent Console on a network-connected Windows system. To manage an Agent from both Windows Agent Console and Remote Agent Console, you must install them using the same service-account user identities. That is, the "EVault Software BUAgent" and "EVault Software Agent" service accounts must be the same. Otherwise, the BUAgent will not be able to provide status or administration functions. The accounts under which services run appear in the VVAgent and BUAgent logs Licensing

6 5 To back up and restore data to/from a data-protection vault, you need a valid account, user name and password Install/Uninstall/Upgrade Please refer to the product installation guides for detailed lists of requirements and restrictions. Refer to the Documentation section of these release notes for more information. Included application File List The 32-bit Agent kit installs: buagent.exe VV.exe VVAgent.exe ExchangeVSSPlugin.dll VVExch.dll VVExchMapi.dll SharePointPlugin.dll SQLSvr70.dll OraPlugin.dll * Agent software (VVAgent or BUAgent) Note: The Agent installation will place the file VVClMsg.dll in the System directory. This file contains the error codes and resource strings that the event viewer uses to display Agent messages. 3.2 Plug-Ins MS Exchange DR(VSS) and MAPI Plug-In This version of the Plug-In supports the Microsoft Extensible Storage Engine (ESE). For information regarding LCR, SCR, and CCR support, refer to the section about the Cluster Plug-In. Oracle Plug-In "Oracle Instant Client Support for Windows" is required. Instant Client Support is supplied (from the download web site) as a separate component from the Plug-In. It must be installed separately by the user. The installation will provide a warning to install Instant Client Support if it is not already installed. If you install the Oracle Plug-In, you must also install the "Oracle Instant Client Support for Windows" after the Windows 32-bit Agent has been installed. This is a separate InstallShield installation, not included as part of the Agent installation, and must be run separately.

7 6 MS SQL Plug-In This version of the Plug-In supports the Microsoft-defined Virtual Backup Device Interface (VDI) MS SharePoint Plug-In MS SQL Server Native Client is required. SharePoint Plug-In backup jobs that use multiple, separate SQL Servers are not currently supported. That is, you cannot have SharePoint environments that use different SQL Server instances to host the various SharePoint databases. Cluster Plug-In Install it as part of the Agent: 1. Install Agents and Plug-Ins on Physical Nodes. 2. Configure Cluster, Exchange, or SQL Plug-Ins on the Physical Nodes. 3. Create a new Agent for your Cluster on the Virtual Node using the IP address or host name. 4. From the newly created Agent, double-click the Global file to open the "Virtual server shared area" window. From here, select a drive letter for your Cluster, and then click OK. This will open the Agent Configuration Window. 5. Here you must specify your Vault connection information. Click OK to finish. 4 KNOWN ISSUES and FIXES 4.1 Known Issues Unable to create a BMR type backup Job on Windows 7 when an active "OEM Partition" exists. WORKAROUND: Set the "primary partition" to active, which should contain boot, page file, crash dump attributes. (18391) Directory Junction restore behavior. When a folder, which contains a Directory Junction is backed up, then during the restore the Directory Junction becomes Folder. If the Directory Junction is restored explicitly, then the content of the folder the Directory Junction was linked to is restored. (18203) BMR type backup Job failed with " Failed to initialize BMRCaptureEnvInfo.dll:... failed to Capture System Restore Point Info". Workaround: If you failover manually (move the cluster apps through the GUI ) then you need to restart the passive node machine. This is only for a Windows 2003 cluster environment. It works correctly with a Windows

8 cluster. (18002) Verifying the MAPI Profile as a user with administrator rights (but not as the user "Administrator") Agent installation folder locked by UAC will show "failed to load ex2000.dll". You can still connect to the Agent, create Jobs, but when you try to test the MAPI Profile as that user, it will fail. WORKAROUND: Add your user to the group to grant permission to access the Agent folder. Retry the MAPI Profile test. (17957) With the "Ask for confirmation before starting missed backup Jobs." option enabled, a missed backup may run without prompting for confirmation. (17861) Exchange Cluster Continuous Replication (CCR) configurations. Exchange VSS backups on a clustered virtual node are not supported for Exchange CCR configurations. Agent should connect to physical nodes, ideally to only one passive node. WORKAROUND: 1. Create a regular (non-virtual) Agent to a passive node e.g. *******2. 2. Create an Exchange VSS Job e.g. "Job1" 3. Run a backup of "Job1" 4. Fail-over the cluster from *******1 to *******2 5. Run a backup of "Job1" 6. Fail-over the cluster from *******2 to *******1 7. Run a backup of "Job1" (17841) Exchange VSS backups may fail when third party Shadow Copy Providers exist on the system. WORKAROUND: user can set registry to force select system provider: HKEY_LOCAL_MACHINE\SOFTWARE\EVault\InfoStage\Agent\ UseSystemVSSProvider = 1 (DWORD) (17805) Incorrect allowable path size value may be shown in the log. The log may show 255 path elements, but in fact it is 251. The incorrect value of bytes for announced supported path may be shown when in fact it is 42 characters less. (17718) After the restoration of system state or ESR backups to Windows system folders, users may encounter the following error when running Microsoft Excel: "One of your libraries (stdole32.tlb) is missing or damaged. Please run Setup to install it".

9 8 WORKAROUND: In fact, the library has been correctly restored. Do not re-run setup as directed. Pressing "OK" will correct the problem. (17629) When upgrading Vista to Windows 7, with an older Agent installed, the Agent Assistant may show "The Agent is not ready" (older Agents do not support Windows 7). Note that the Agent must be upgraded to version 6.71 (or above). (17359) MAPI restore (Unicode) does not restore subdirectories after moving the original folder. This movement changes the relationship of the object and its container (it will be considered an "existing folder" upon restore). WORKAROUND: If the user wants to restore the folder to its original location, they should remove the folder permanently before running the restore. (17331) Mount point data is not backed up when a backup selection exists above the mount point in a directory. In other words, if a backup selection contains a mount point in a sub-directory, the data recursive to the mount point is not backed up. RECOMMENDATION: To back up a mount point and its data contents, create a separate Job for this selection. (17192) Windows Agent Console processes screen shows cancelled BMR Job without displaying a Job name. (17133) SHAREPOINT: * Cannot gracefully cancel SharePoint backup when retrying failed ADO query. (16995) ** SharePoint backup fails COM Error: Func=SharePoint Plugin::SpsDataRow::contentDone, Code=0x (16923) *** SharePoint backup fails ADO Error: (E_FAIL) Unspecified error for file. (16842) **** SharePoint Plug-In backup sees incorrect site collection content. (16634) RECOMMENDATION: A hotfix is available for download to remedy the above issues. The default installation directory for Silent Installation (C:\Program Files\Agent) can be problematic if another program uses the same installation path or folder name. WORKAROUND: Create an installation path that is exclusive to the Agent product. To do this, use the "SILENTINSTALLDIR" variable during Silent Installation. For example, set the variable to

10 9 C:\Program Files\<installation directory>\. (16880) Using SQL Plug-In, backups with 6.6 Agents fail when restoring multiple databases at the same time from 6.5 datasets using incremental backups. As a workaround, you can restore one DB at a time and the restore will succeed. (16714) System state backup error: SS -E-0005 O/S message: "The RPC server is unavailable", and SS -E-5832 "unable to enumerate system protected files. This is the correct behavior and happens if one component fails and another finishes (with/without errors/warning), then the job finishes "successfully". (16698) A delta recreation may fail for an encrypted task with the error "DELT-E-7764 Failed to recreate delta file", when the synchronize is carried out following a task re-registration. If you have to re-register an Agent to a Vault, you need to synchronize the task with the Vault. But, if the original task had an encryption password, you are not prompted for the password. Agent Console shows the delta recreation as completed, but the synch log will show that it as failed. WORKAROUND: Manually enter the correct encryption password. (16657) During first backup after a successful delta recreation of a task with deferred files, the agent may or may not resend previous catalogs. This issue is related to reregistration and delta recreation processes on the Agent side. (16624) Restore fails when trying to recover data in a mounted NTFS folder. After the restore, the mounted NTFS folder access is also broken. WORKAROUND: Exclude the mount point from the restore and the restore will complete successfully. You will need a separate Job to restore the mount point exclusively. (16508) After restoring C:\*.* and System Files on new hardware or a freshly formatted hard drive, booting with Server 2008 or Vista and rebooting again caused an infinite boot loop. The BCD that was backed up may not match the currently installed hard disk on the recovery system. Recommendation: When performing a Disaster Recovery using a backup of the entire system volume(s), it is recommended to exclude the Boot Configuration Data (BCD), which is usually located at C:\Boot\BCD, from the restore

11 10 selection. In most circumstances, the existing BCD should be sufficient to recover the system. Further restore options/details are available in the Windows Agent User Guide if you desire to restore the BCD with the Disaster Recovery (for example, if it was previously configured with customized boot options). (16446) Errors seen in restore log after restoring C:\*.* and System State on Server "Access is denied" C:\Windows\System32\LogFiles\WMI\RtBackup\ These files have special permissions and cannot be overwritten during a restore if they exist. Note: These files are not part of the System State backup nor are they necessary for a successful restore. (16422) Exchange VSS backup on a CCR Passive Node can fail if the Exchange database copy status (from Exchange Management Console) is not in a "Healthy" state (such as Service down, Initializing). The following types of messages will appear in the backup log: EXVS-F-8559 All databases in the backup selection are dismounted. The backup will fail. BKUP-I-4115 no files selected from $EXCHANGEVSS$:\.\*.* BKUP-I-4115 no files selected from $CAT$:\C\Program Files\ BKUP-E-4706 job will be forced to fail. (16405) Authoritative restore on Server 2008 fails to recover deleted AD users/objects. Inbound replication must be disabled using the repadmin tool, otherwise the deletion will re-replicate from other domain controllers after the restore. Recommendation: Refer to Microsoft KB article (16325) Infinite loop booting situation after restoring System State with pending Windows Updates. Recommendation: Disable Windows updates then restore the System State. (16297) System State backup does not protect Disk Quota settings via Disk Management. Note: The Quota Management and File Screening Management settings are protected via File Server Resource Manager by a System State backup. All quota & file screen settings/templates are restored with the System State component. (16211) MAPI restore does not restore a mailbox subfolder to its original location if it exists in the "deleted items"

12 11 folder. If the original folder is in deleted items, then the restore goes to the original folder. (16147) SharePoint Restore may fail with "ADO Error: (E_FAIL) Unspecified error for file SharePoint" when restoring very large files (>1GB). This error may occur when RAM resources are relatively limited. Recommendation: Restore large files as a separate Restore Job. (15898/15900) When the Agent restores locked System State files, it does not assign.vvtmp names to them. The Agent assigns names such as "$VVSF (vv tmp file)" and "$VVSF (vv tmp file)" to the restored files. These names change when the system restarts. (15736) Silent installs apply to fresh installations only. Silent upgrades are not supported. (15571) On Windows 7, Vista, and 2008, selecting "Ask the user to do a backup before shutdown" enables the "Would you like to run a backup before the shutdown?" prompt. If you select "Yes" your request is ignored, and the server shutdown continues. (15535/13004) The abbreviated log shows <M ID="7931" C="LOGS" S="I" T=" T12:10: :00"></M> for Jobs older than Agent 6.50 when using Windows Agent Console. For Abbreviated 6.50 Jobs using Windows Agent Console 6.50, the string is translated correctly. (15419) Syntax errors "VVCVersion = 650" in VVagent log from upgrade log are seen after upgrading Agent 6.41 to Upgrade succeeds even though there are syntax errors within the upgrade log. This may occur on slower machines. (15403) The SharePoint Plug-In requires SQL native client V9. V10, which is part of SQL Server 2008, does not work. (15350/15060) 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". As a workaround, wait for 5 minutes to restart BUAgent on all cluster nodes and then restart the BUAgent service one by one. (15260/11638) Agent Installation Kit does not replace binaries when the "Repair" option is selected. This is an InstallShield issue. Users who need to run repairs

13 12 should contact Support. (15228) Agent still attempts to claim OTM Plug-In license after OTM Plug-In is uninstalled. WORKAROUND STEPS: 1. Modify global.vvc file, removing "Product_Name = OTM" 2. Please contact support. (15217) Bandwidth throttling may show half (or less) of assigned value logged into the Backup log. The "processcounter" field may incorrectly count the number of VV processes, causing an extra process to be counted, and splitting the bandwidth. As a workaround, stop and restart the VVAgent and BUAgent services, to clear their shared memory, which has the counters. (15204) Multiple backup Jobs for the same Storage Group may cause an Incremental backup to fail with a log-gap error if a previous incremental backup of the same storage group logs was truncated. WORKAROUND: Multiple Jobs should not be configured to back up the same Storage Group if one Job is an Incremental backup Job. (15067) Odd VSS errors in Agent and BUAgent logs. Microsoft VSS may not be working properly. Microsoft has a WORKAROUND article at: (15024) Restoring a single database to a storage group that contains multiple databases can cause data loss from the other databases if you manually delete a Storage Group s transaction log files. Note: Transaction logs are not distinguished down to the level of the database within the Storage Group, but at the whole Storage Group level. WORKAROUND: If a full backup is performed after the restore of a single database, the new safeset based on the full backup is restorable. (14934) A deferred scheduled Backup hangs on the Agent during a backup. This problem is related to deferring of encrypted files on Windows. Vault generated error shows as: "VVLT-E-0038 program timed out". (14895) A second Exchange Restore (following a restore from a previous safeset) may not succeed when restoring over existing files unless files are deleted from the target Storage Group folder first. (14827)

14 13 MAPI Restore log does not indicate the reason for failure when the target database is mounted, or is not marked for restore overwrites. WORKAROUND: When overwriting an existing database (which must be on the same Domain), it must be unmounted and marked for "overwrite" (via the Exchange Management Console). (14815) The non-ascii character "œ" is not stored properly in the Password Hint. It is saved as "S". (14726) SharePoint backup completes with "Unexpected execution path: Not all data necessary for backup is present" errors in the log. SharePoint Plug-In may not support the schema for older revisions of list items. (14700) By default, Retention names display in English, regardless of the language that you choose. In other words, the default Retention names are always Daily, Weekly, and Monthly. (14666) Non-ASCII characters are occasionally dropped from Agent log files. (14658/14654/14454) When creating a new BMR task the following message was displayed in Agent Console: Failed to initialize browse interface for BMR Plug-In. This is because the Microsoft Volume Shadow Copy service was not working correctly. BMR relies on the O/S VSS service to be running correctly. Check that the Event Service and VSS have been started. Check for errors associated with those services in the error log. Check if the vssadmin command is working (is vssadmin list writers listing the System Writer?). (14202) Two warnings about insufficient privileges appear in the Exchange MAPI backup logs after upgrading the Agent, even when Exchange MAPI profile tests complete successfully. Here are the messages: - Exchange profile "administrator" has not enough privileges - EXMA-W-6693 privilege check failed for profile "administrator" This only applies when the Vault version is (14186) An Agent upgrade can fail with the message "UTIL-E-8225 Exchange server is not found or not operational." Agent upgrades can fail when an existing Job (possibly an old Job) uses a non-existent Exchange server. (14147) SQL backups fail due to User Account Control (UAC) in

15 14 Windows Server SQL backups hang and do not complete for non-administrative users who have database backup rights. No failure or error shows in the VVagent log. This may also apply to Windows Vista. WORKAROUND: Turn off Windows UAC. (14004/14000/13983) If an Agent is successfully backing up to an LVR 1:1 set of Vaults, and the replication license is removed from the passive Vault, the Agent will begin backing up to the passive Vault (because it was the last Vault to respond). The Agent does not determine whether or not the Vault is part of a replicated environment. If this continues, and a license for the passive Vault is added again, the safesets that were accepted after the license removal will be deleted. (13996) VVAgent will stop after installation if the domain controller is offline. When the domain controller is offline, the VSS writer query (MS API) takes about 4 minutes to return a result. The Agent waits 30 seconds, cancels the query, and responds with an error message. WORKAROUND: Bring the domain controller back online, and then restart the Agent services. (13908) You might be unable to browse site directories when you create a SharePoint Job with a Clustered SQL Backend. Note: You must configure SharePoint to the Clustered SQL Backend instance. To specify a custom instance name, use this format: "TCP:<ip or name of host\instance>" Here is an example: "TCP:HOST365\SQLINST1" (13895) You cannot back up SharePoint content that spans multiple SQL instances. The SharePoint Plug-In does not support this configuration. All SharePoint sites, web applications, etc., must use the same SQL server instance as the configuration database. (13887) Defect #13883 is not actually a problem because WSS 3.0 and MOSS 2007 use SQL native client V9 (rather than SQL Server 2008). (13883) Restore of an SQL Job can fail with Remote Agent Console depending on which authentication options were chosen for backup and restore. If an SQL Job was created with SA authentication on Remote Agent Console and backed up, it will complete successfully. If you then restore the Job with Remote Agent Console, selecting Windows authentication, it will fail. (13866) Windows Oracle 9i Plug-In Job can fail to complete during Job creation with the message Failed to connect

16 15 to the server! This can be a failure to connect to server type error. This issue can be caused by the UserName setting. Note: User Name = sys is sufficient. User Name = sys as sysdba is not required for Oracle9i. (13809) An Unplanned Shutdown event tracker prompt may appear after a BMR recovery. A BMR backup is a point-in-time capture, and Windows is aware that the server was running at the time of backup. After performing a BMR recovery, the recovered server is brought back to that point in time, and may convey that it was not shut down correctly. (13640) Agent installation fails when Port 808 is in use by another application. WORKAROUND: Run a port query to determine what is using port 808. If possible, move what is using port 808 to another port and reinstall the Agent. (13578) Restoring over unique permissions prevents further permission edits. After a restore (overwrite), a document that has unique permissions can no longer have its permissions modified. SharePoint returns a "File not found" error. WORKAROUND: To restore and still be able to modify permissions, delete the file before restoring. (13295) The option Prevent Standby/Hibernation when backups are running is ignored on Windows Vista and The standby/hibernation will occur even if a backup is running. (13123/13001) On SQL 2008, when restoring to a database without the "With Replace" option selected, the restore Job will terminate. The Restore Job terminates without clearly describing the failure to the user. However, the restore log does contain the message "Use the WITH REPLACE or WITH STOPAT clause to the RESTORE statement to overwrite the contents of the log". This is a Microsoft message. WORKAROUND: Select the With replace to overwrite the existing database" option in Agent Console or Remote Agent Console. (13031) SQL Plug-In on SQL 2008 reports errors differently than SQL 2005 when restoring a database from one instance to another. (13030) You may receive the SharePoint restore error "Unexpected execution path: Type was not defined!" where there was some corruption or discontinuity in an older backup.

17 16 Workaround: Do a restore with an exclusion for the problem file(s). The restore should now complete. Following that, do another restore, this time to file, including the previously excluded file. (12990) Passwords with blank spaces cause SQL Plug-In authentication to fail. Blank spaces should not be used with SQL Plug-In authentication. (12502) Default MAPI backups can be restored, but restores of Unicode MAPI tasks to PST are not supported. (11677/9554) In Windows Agent Console, a Cluster license is claimed when a Job is CREATED on a virtual server. In Web Agent Console, the Cluster license is claimed when the Job RUNS on a virtual server. (11637) A virtual SQL Server may fail with a "Failed to launch backup" error when a "RunAs" user is specified. If you delete the information from the "RunAs" tab, the backup will proceed. (11636) If a MAPI backup Job has nothing to back up (due to restrictive wildcard use, for example), the Job fails, and the log does not show a specific cause for the failure. (11622) System State backups fail with "std::exception caught" and "VRegistry::Initialize() unable to map drive" errors. (11479) With SharePoint 2007, workflows are not restored for Libraries or Webs. (10695) You might receive Windows Agent Console error messages during a restore from another computer using the same Safeset: "Connection to the Vault is not using encryption" and "Failed to create synchronize log file" in the VVAgent-*.Xlog, and "SSET-I-4748 Connection to the Vault is using AES encryption" in the BUAgent-*.Xlog. (10684) If you select a Windows NTFS Junction Point (mount point) as a backup source, you may see the error Will not traverse reparse point in the Agent backup log. Actually, the data is being backed up. (10435) SharePoint and Oracle VVAgent logs may contain repeated "Error in GetProcesses()" and "Refreshing process list is not completed" errors. Many VV instances may be spawned. (10410)

18 17 MAPI Plug-In only detects mailboxes from one domain when two or more domains connect to the same Exchange Server at the same level (rather than child/parent). (10364) SQL databases that span more than one hard drive may have decreased delta performance on 'full' backups. Recommendation: Running incremental backups more frequently and fewer full backups may reduce delta and full backup size. (6252) 4.2 Fixes in This Release Agent may be unable to restore ANSI encoded safeset data when treated as UTF8 during backup. Attempt to restore in ANSI mode may fail. A restore ANSI safeset backed up in UTF8 mode, will now automatically switch to UTF8 mode. This has been fixed in this release. (18426) Exchange 2007 VSS backup may fail to find datastores for backup. This has been fixed in this release. (17800) BMR type backup of Domain Controller may result in lsass.exe- system error during ESR type restore. This has been fixed in this release. (17782) BMR type backup Job may suppresses data exclusions on Exchange Job. This has been fixed in this release. (17779) VV may core dump when backing up very large corrupted SharePoint files. This has been fixed in this release. (17768) On Windows 7, 6.70 Agent claims Server Agent license. This has been fixed in this release. (17606) After an Agent upgrade, MailOnError = False was changed to True. This has been fixed in this release. (17425) Restore for an SQL database backup returns zero data (wrong restore path). (17262) When backup data pertaining to a mount point is restored to an alternate location, it appears that the data has been restored to an alternate location but what is restored there are the soft links pointing to the original location. The restore process actually restores the data to the original location. (17173)

19 18 The Job configured to backup the system state with system files seems to be doing backup of the Distributed File Systems (DFS) shares in that Job. (17131) No warning is generated when data in a mount point is not backed up. (17006) Mounted volumes cannot be backed up when the mount point is selected. (16981) The default path for silent installation has changed to: C:\Program Files\EVault Software\ (16880) Exchange Job may "defer" if there are errors re: attachments/contacts "attachment is not found". This has been fixed in this release. (16879) A BMR type backup Job may fail if there are other applications on the system that are shadow copy providers. This has been fixed in this release. (16630)

20