REDCENTRIC AGENT FOR MICROSOFT WINDOWS VERSION 7.34.4009A

REDCENTRIC AGENT FOR MICROSOFT WINDOWS VERSION 7.34.4009A RELEASE NOTES, JANUARY 5 TH, 2015

Agent for Microsoft Windows Version 7.34.4009a Release Notes, January 5, 2015 ======================================================================== Contents 1 OVERVIEW 1.1 Release History and Changes 1.2 Supported Platforms 2 NEW FEATURES 3 INSTALLATION NOTES 3.1 Agent Installation Notes 3.1.1 Installation Requirements 3.1.2 Conditional Requirements 3.1.3 Licensing 3.1.4 Install/Upgrade 3.2 Plug-in Installation Notes 4 FIXES, KNOWN ISSUES and LIMITATIONS 4.1 Fixes 4.2 Known Issues 4.3 Limitations 5 PRODUCT SUPPORT 5.1 Technical Support 5.2 Product Updates 5.3 Documentation ======================================================================== 1 OVERVIEW The Windows Agent is installed on each Windows server that you want to protect. Using Portal or a legacy Agent Console application, you can manage the Agent, back up data to a vault, and restore data from the vault. You can also install Agent Plug-ins that protect specific applications and provide additional functionality. The following Plug-ins are available with the 32-bit Windows Agent: - Oracle Plug-in - SharePoint Plug-in - SQL Server Plug-in - Cluster Support Plug-in Note: Support is ending for Exchange MAPI, SharePoint Plug-in, and legacy SQL VDI jobs. You cannot create new backup jobs with these legacy types. Existing jobs will be supported for a period of time. Please see the documentation for other ways to protect this data. This Agent version is for use with: - Portal 7.61, Web Agent Console 7.61, or Windows Agent Console 7.30 - Vault version 6.22 or later Note: For full new feature functionality, Vault version 7.00 or later is required.

The Windows Agent supports Bare Metal Restore (BMR) backup jobs. For full BMR recovery, System Restore 2.10 or later is required. Note: Encrypted volumes (BitLocker, TrueCrypt, etc.) are not supported in BMR jobs. 1.1 Release History Version 7.34.4009a, November 20, 2014 Version 7.34.4009, November 14, 2014 Version 7.33.3441, August 18, 2014 Version 7.32.3423, May 8, 2014 Version 7.31.3422, April 3, 2014 Version 7.30.3420, March 17, 2014 Version 7.24.3120a, November 20, 2013 Version 7.24.3120, October 31, 2013 Version 7.23.2219, August 29, 2013 Version 7.22.2211, May 9, 2013 Version 7.21.2205, March 28, 2013 Version 7.20.2167, February 27, 2013 Version 7.10.1650, November 21, 2012 Version 7.00.1039, June 29, 2012 1.2 Supported Platforms This Agent is supported on the following 32-bit Microsoft platforms: - Windows Server 2008 Standard (SP2) - Windows Server 2008 Enterprise (SP2) - Windows Server 2008 Datacenter (SP2) - Windows Server 2008 Server Core (SP2) - Windows Storage Server 2008 Basic (SP2) - Windows Server 2003 R2 Standard (SP2) - Windows Server 2003 R2 Enterprise (SP2) - Windows Small Business Server 2003 R2 (SP2) - Windows Server 2003 Standard (SP2) - Windows Server 2003 Enterprise (SP2) - Windows Small Business Server 2003 (SP2) ---------------- The Oracle Plug-in is supported on Oracle 11g R2 on the following platforms: - Windows Server 2008 Standard and Enterprise (SP2) - Windows Server 2003 R2 Standard, Enterprise (SP2) - Windows Server 2003 Standard, Enterprise (SP2) ---------------- The SQL Server Plug-in is supported on the following platforms: (including Cluster support with the Cluster Support Plug-in) SQL Server 2014 on the following platforms: - Windows Server 2008 Standard, Enterprise, and Datacenter (SP2) SQL Server 2012 (SP2) on the following platforms:

- Windows Server 2008 Standard, Enterprise, and Datacenter (SP2) SQL Server 2008 R2 (SP3) on the following platforms: - Windows Server 2008 Standard, Enterprise, and Datacenter (SP2) SQL Server 2008 (SP4) on the following platforms: - Windows Server 2008 Standard, Enterprise, and Datacenter (SP2) - Windows Server 2003 R2 Standard, Enterprise (SP2) - Windows Small Business Server 2003 R2 (SP2) - Windows Server 2003 Standard, Enterprise (SP2) - Windows Small Business Server 2003 (SP2) SQL Server 2005 (SP4) on the following platforms: - Windows Server 2008 Standard, Enterprise, and Datacenter (SP2) - Windows Server 2003 R2 Standard, Enterprise (SP2) - Windows Small Business Server 2003 R2 (SP2) - Windows Server 2003 Standard, Enterprise (SP2) - Windows Small Business Server 2003 (SP2) Note: Support is ending for legacy SQL VDI jobs. You cannot create new backup jobs with this legacy type. Existing jobs will be supported for a period of time. Note: The SQL Server Plug-in does not support SQL Server Express. To back up a SQL Server Express database, export the database to a flat file and back it up using the Windows Agent. ---------------- The SharePoint Plug-in is supported on the following platforms: Microsoft Office SharePoint Server 2007 (SP1) on the following platforms: - Windows Server 2008 Standard, Enterprise, and Datacenter (SP2) - Windows Server 2003 R2 Standard, Enterprise (SP2) - Windows Small Business Server 2003 R2 (SP2) - Windows Server 2003 Standard, Enterprise (SP2) - Windows Small Business Server 2003 (SP2) Windows SharePoint Services (WSS) 3.0 (SP2) on the following platforms: - Windows Server 2008 Standard, Enterprise, and Datacenter (SP2) - Windows Server 2003 R2 Standard, Enterprise (SP2) - Windows Small Business Server 2003 R2 (SP2) - Windows Server 2003 Standard, Enterprise (SP2) - Windows Small Business Server 2003 (SP2) Note: Support is ending for the SharePoint Plug-in. You cannot create new backup jobs with this legacy plug-in. Existing jobs will be supported for a period of time. ======================================================================== 2 NEW FEATURES New Features in Version 7.33: - When the SQL Server Plug-in is used with Portal version 7.62 and later,

you can specify the names of databases to include and exclude in SQL Server backup jobs using wildcard characters (asterisks and question marks). New databases with names that match a backup job's filters are automatically included or excluded when the job runs. For more information, see the Portal help. - The SQL Server Plug-in can now protect databases in SQL Server 2014. - The SQL Server Plug-in can now protect secondary databases in AlwaysOn Availability Groups. - Nearing end of life: Support is ending for legacy SQL VDI, Exchange MAPI Plug-in and SharePoint Plug-in jobs. You cannot create new backup jobs with these legacy types. Existing jobs will be supported for a period of time. New Feature in Version 7.32: - The Agent Assistant is no longer installed as part of the "Typical" installation process. You can choose to install the Agent Assistant as part of a custom installation. ======================================================================== 3 INSTALLATION NOTES 3.1 Agent Installation Notes 3.1.1 Installation Requirements - 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 - Windows Internet Explorer version 6 or later - A TCP/IP stack (for communicating with the vault, Agent, and Portal or Agent Console software) - At least 200 MB of free disk space for a new installation. An upgrade may require more. Additional free space is required for Agent files created for backup jobs. 3.1.2 Conditional Requirements - If you install the Agent Assistant with the Agent,.NET Framework 2.0 is required. - If you use an antivirus program, disable real-time scanning on reads (called "outgoing" in some antivirus products). Note: As a best practice, do not back up antivirus product installation directories. - To manage an Agent from both the legacy Windows Agent Console and Web Agent Console interfaces, install its services using the same user

identity. That is, the service accounts for the BUAgent and the VVAgent must be the same. Otherwise, the BUAgent will not be able to provide status or administration functions. 3.1.3 Licensing Agent and Plug-in licenses are distributed automatically when the Agent connects to a vault (based on your license quota). To back up and restore data to or from a vault, you need a valid account, username and password. Contact your service provider to obtain the required information. 3.1.4 Install/Upgrade The file name of the Windows Agent installation kit is: Agent-Windows-7-34-4009a.exe Included application files: The 32-bit Agent kit installs: BUAgent.exe - Version 7.34.4009 VVAgent.exe - Version 7.34.4009 VV.exe - Version 7.34.4009 LogViewer.exe - Version 7.34.4009 SystemStatePlugin.dll - Version 7.34.4009 BMRCaptureEnvInfo.dll - Version 2.1.0.2141 SystemVolumePlugin.dll - Version 7.34.4009 evvss.dll - Version 7.34.4009 evvss2003.dll - Version 7.34.4009 evvssxp.dll - Version 7.34.4009 ex2000.dll - Version 7.34.4009 VVExch.dll - Version 7.34.4009 VVExchMapi.dll - Version 7.34.4009 VVClMsg.dll - Version 7.34.4009 MapiComWrapper.exe - Version 7.34.4009 OraPlugin.dll - Version 7.34.4009 SharePointPlugin.dll - Version 7.34.4009 SQLSvr70.dll - Version 7.34.4009 SQLVSS.dll - Version 7.34.4009 SQL2012Plugin.dll - Version 7.34.4009 XLogTranslator.exe - Version 7.34.4009 Note: The Agent installation will place the VVClMsg.dll file in the in the Agent installation path. This file contains the error codes and resource strings that the event viewer uses to display Agent messages. Note: Do not install the Agent in a Windows-encrypted directory. You can upgrade these Agents to version 7.34a: Version 7.3x Version 7.2x Version 7.10 Version 7.00 Version 6.85 Version 5.6

======================================================================== 3.2 Plug-in Installation Notes SQL Server Plug-in - This version of the Plug-in supports Transparent Data Encryption (TDE) in SQL Server 2008 R2 (SP1), SQL Server 2012, and SQL Server 2014. - This version of the Plug-in uses VDI for transaction logs and VSS for full backups (for SQL 2005, 2008, 2008 R2, 2012). It also supports VDI for older backup jobs (for SQL 2005, 2008, 2008 R2). - For legacy VDI-based backups: For Microsoft SQL Server 2008 (SP2), the Plug-in requires the SQL-DMO component, which was removed from Microsoft SQL Server 2008. you need to install the "Microsoft SQL Server 2005 Backward Compatibility Components" package. A download is available (within a feature pack for Microsoft SQL Server 2008) at: http://www.microsoft.com/downloads/details.aspx?familyid=536fd7d5-013f- 49BC-9FC7-77DEDE4BB075&displaylang=en For legacy VDI-based backups, you must install the Microsoft SQL Server 2005 Native Client. SQL 2008 and 2005 Native Clients can co-exist. Note: Support is ending for legacy SQL VDI jobs. You cannot create new backup jobs with this legacy type. Existing jobs will be supported for a period of time. SharePoint Plug-in - SQL Server Native Client is required. - SharePoint Plug-in backup jobs that use multiple, separate SQL Servers are not supported. That is, you cannot have SharePoint environments that use different SQL Server instances to host the various SharePoint databases. Note: Support is ending for the SharePoint Plug-in. You cannot create new backup jobs with this legacy plug-in. Existing jobs will be supported for a period of time. Cluster Support Plug-in To install the SQL, Exchange, or Cluster Support Plug-in, use the Agent installation kit: 1. Install Agents, SQL or Exchange Plug-in, and Cluster Plug-in on the physical nodes. 2. Register the cluster node using Portal or Web Agent Console or connect to the virtual IP using Windows Agent Console. 3. Use the new registered virtual Agent as a normal Agent. ======================================================================== 4 FIXES, KNOWN ISSUES and LIMITATIONS 4.1.1 Fix in 7.34a release

Compatibility issues have been resolved between the Windows Agent on Windows Server 2003, and Portal or Web Agent Console when recent Windows security updates are installed on the Portal server. This version of the Windows Agent is supported on Windows Server 2003. IMPORTANT: You cannot create or edit Exchange MAPI, SharePoint Plug-in, or legacy SQL VDI jobs using Windows Agent 7.34a. If you need to create or edit these legacy jobs, do not upgrade to Windows Agent 7.34a. Use Windows Web Agent Console to manage the previous Agent version. (28873) 4.1.2 Fixes in 7.34 release Compatibility issues have been resolved between the Windows Agent and Portal or Web Agent Console when recent Windows security updates are installed on the Portal server. (28059) SQL backups no longer fail with an ADO timeout error. (24326) Gaps are now detected correctly for SQL transaction log backups. (28253) Validation no longer takes an excessive amount of time during an Exchange 2007 backup. (28633) The Agent can now back up volumes that are larger than 5 TB in one job. However, consider the resulting job size on the vault. When data for a job exceeds 2 TB on the vault, maintenance operations for the job can be negatively affected. For more information, see the Director Operations Guide. (27043) 4.1.3 Fix in 7.33 release When you run a BMR backup job, EnumDisk:GetDrives warning messages no longer appear. (24815) 4.1.4 Fixes in 7.30 release When a SQL database had non-standard file extensions, SQL VSS backups and restores completed successfully, but restored databases were corrupted. This problem no longer occurs. (27119) The SQL VSS backup now detects log gaps when another 3rd-party backup runs at the same time. (27088) The following warning no longer appears during successful BMR backups: ENVC-W-04096 Kernel32DLL GetProcAddress of GetFirmwareType failed error=0x7f - API exists on Win2012 and above. (26028) 4.2 Known Issues 4.2.1 Agent Backup Issues

Running multiple UNC jobs simultaneously (to the same UNC path) from Agent Console fails. WORKAROUND: Run concurrent UNC jobs from the command prompt. (24226) A backup to a local drive fails when the deferral time specified in the backup job is reached. All SSI files created are left on the local drive. (23921) Backups can fail over UNC path to or from a Windows operating system running an older Windows operating system. Microsoft does not support all Windows operating system combinations for UNC paths. Only those combinations supported by Microsoft are supported. (25579/23712) When attempting to create a new job after a vault failover (1:1 vault), Windows Agent Console limits the job name to 8 characters instead of 30 characters. When the old active vault comes back online, the 1-30 character limit returns for job name length when creating a new job. (19893) 4.2.2 Agent Restore Issue Backup to a Satellite vault resets the status and location of safesets that exist only on Base vault. If a safeset is available on the Base vault (but not on the satellite), the Agent cannot restore unless you synchronize first. You must run a synchronize operation before you restore. Synchronizing provides updated status and location information about safesets on vaults. (20573/21168/21896) 4.2.3 Plug-in Backup Issues The dates in an Exchange MAPI backup log may be displayed incorrectly if there are XML-incompatible characters inside the message. Log messages cannot correctly save non-ansi characters. (24097) A MAPI job appears as if reseeding after a Windows Agent 6.85 upgrade to Agent 7.x. This is not a re-seed. Due to a change in the security stream backup option in MAPI backups, the first backup of upgraded Agent will be re-deltized, creating a larger than usual delta file. The delta will return to its typical size on subsequent backups. Also, the log includes the following warning "EXMA-W-09073 skip message body property PR_HTML by error". These warning messages are informational and can be ignored. (23545) A backup job created on a physical node of a SQL Server 2012 cluster fails (on the physical node) with a stream backup error. Note that this is not a supported backup scenario. There is no support for protecting databases on the virtual node with jobs created on the physical node. Support for backing up SQL 2012 on a virtual node in a cluster is available with the Agent with the Cluster Support Plug-in. (23622) An Exchange DR job will fail if launched while a BMR job is running. Recommendation: A user should avoid running more than one backup of the same database at the same time. WORKAROUND: To enable simultaneous backups, manually add the following section to the bottom of job.vvc file (located in the Agent installation directory):

1. vssadmin list writers, copy "writer name" and "writer ID" 2. Append the following section to BMR job vvc For an Agent 7.00.1039 and higher: VSSWriterBackup001 { ID = <writer ID> <<<<<<<<<<<< change to copied "writer ID" Include = ".\*" InstName = Name = Microsoft Exchange Writer <<<<<<<<<<<< change to copied "writer name" Options = 4 } (23599) If you reregister a different computer than was used for the original backup (reregister computer Y to the vault as computer X) and attempt to do another backup of the existing SQL VSS job, the backup will fail. A restore can still be performed successfully. WORKAROUND: Create a new job and run the backup from the reregistered computer. (23270) Windows UAC prevents a new user from launching the Agent VV process on SQL 2008 SP2 / Server 2008. No status is shown on the Process Information screen. WORKAROUND: (These steps are performed only once) 1. Press "Start" and run "Control panel". 2. Select "System and Security". 3. Select "Change User Account Control settings" 4. Move button down to "Never notify". Press OK. 5. Reboot the system. (These steps are performed each time for a new user) 6. Create user 'new user' as an example. 7. Assign a group of administrators to it. 8. Run SQL Server Management Studio. 9. Right-click the Security folder, point to "New", and select "Login ". 10. In the Login New dialog box, on the General page, enter the name of a user ('new user') in the Login name box. 11. To create a login based on a Windows principal, select Windows authentication. This is the default selection. 12. Press OK. User 'new user' is ready for use. (23216) A database with a Simple Recovery Model cannot run transaction log backups, but the error message in the log when the backup fails does not indicate this is the reason for the failure: BKUP-E-04706 job will be forced to fail BKUP-F-04110 job failed to complete CAT -E-08056 backup aborted. (24811) For legacy VDI backups, running SQL maintenance procedures such as reindexing or Shrink Database may cause the backup to reseed. VSS backups are not affected in this manner as the SQL 2012 Plug-in, using VSS, efficiently detects the changes within database file and sends the changed blocks only (delta). (23163) You cannot do a MAPI backup of a mailbox with an existing job when the user account associated with the account is moved to a different Organizational Unit (OU) in Active Directory (AD). This issue only affects mailboxes that are specifically selected in the backup. If the

backup Jjob is set up to back up at the server or recipient level, the mailbox will be backed up but it will be treated as a new mailbox. The User Principal Name (UPN) should be unique for all users and will not be affected by moving the account in AD. WORKAROUND: The mailbox must be added to the backup job again and the existing entry removed, as it will generate errors. If planning on moving users between OU within AD, set the backup job to use the server or recipient levels with recursive settings to continue backing up the mailbox after any changes in AD without needing to modify the backup job. (20362) When the VSS backup warning: "Some hard links <> were not selected and have not been backed up.", a file within a selection has hardlinks and some of the hardlinks were not included. These hardlinks will be ignored, but the file and the hardlinks included in the selection will be backed up. WORKAROUND: Manually include any folders that contain the missing hardlinks. (20281) 4.2.4 Plug-in Restore Issues Restore to SQL Server 2008 using VDI, with Filestream (BLOB) content, fails. WORKAROUND: Create the backup job using SQL VSS. (24158) A database restore can fail in a mirroring environment when restoring with the "overwrite" option or "overwrite with no recovery" option. As per MSDN: While a database mirroring session is active, the following restrictions apply: * Backup and restore of the mirror database is not allowed. * Backup of the principal database is allowed, but BACKUP LOG WITH NORECOVERY is not allowed. * Restore of the principal database is not allowed. (23359) After reregistering an Agent or running Restore From Another Computer, when performing a VSS Restore job of a SQL 2005 backup (original database names with overwrite selected) to a Windows 2008 R2 machine, the restore may fail. The Restore log and process dialog, however, report success. (23304) With Windows Agent Console, using Restore From Another Computer from a SQL standalone machine to a virtual SQL cluster, Restore to file on disk fails and the wizard disappears after you select the vault, Computer and job. No Dump or Log file is created. WORKAROUND: Use Web Agent Console to run this type of Restore From Another Computer, or restore using the physical node. (23261) Safeset bytes processed on the vault for a SQL job with a random read restore of SharePoint is more than double the actual size of the safeset data. (25016) SharePoint Workflows and Alerts do not work after a restore using the SharePoint Plug-in. The SharePoint Plug-in does not support backups or restores of Alerts. WORKAROUND: To back up workflows, a registry key must be set. : HKEY_LOCAL

_MACHINE\SOFTWARE\EVault Software\Agent\SPS_Workflow_Support=(REG_SZ)"1" (23692) A SQL restore fails when restoring to an alternate database, under the same instance, with the overwrite existing database option selected. Note: This restore scenario is not supported as we do not rename the database files upon restore. Restoring this database could be accomplished if you remove or rename the original database file names before trying to restore. (23099) When restoring a database to a SQL database other than the original database, the logical and file names are not renamed to match the database where it is being restored. This feature is not supported by VSS. (22981) You cannot restore a MAPI backup of a mailbox in which the user was moved to a different Organizational Unit (OU) in Active Directory. Note: The user's location in AD when restoring must be the same as when backed up. WORKAROUND: If the backup was done using ANSI (default) encoding, the contents of the mailbox can be restored to a PST file and then imported into the user's mailbox. If the backup was done using Unicode encoding, the user must be moved back to the original Organizational Unit in AD to restore the contents. (20361) SQL Plug-in restore fails if the database directory is missing. WORKAROUND: Manually create the database directory prior to restore. (19466) When restoring large files (e.g., larger than 250 MB), a SharePoint restore may fail with the following error: "ADO Error: (E_FAIL) Unspecified error for file SharePoint". This error may occur when RAM resources are relatively limited. Recommendation: Restore large files in separate restore jobs or to alternate locations (i.e., directory on disk). (15898/15900/17699) Note: This does not apply to restores from BMR or SQL VSS backup safesets for SharePoint 2010/2013. Default ANSI MAPI backups can be restored to a PST file, but restores of Unicode MAPI tasks to PST are not supported. (11677/9554) 4.2.5 Install/Uninstall/Upgrade Issues If a 6.85 Agent that is not registered to Web Agent Console is upgraded, the Cluster Plug-in creates a duplicate folder on another shared drive (two folders with the same name exist on one virtual server). (24471) Unable to uninstall the Spanish Agent 7.23 via Windows Control Panel when it has been installed on the Spanish version of the Windows operating system. WORKAROUND: Launch the Agent installation kit and select Remove. (25365) When you upgrade a non-english Agent from version 7.24 and attempt to register the Agent to Web Agent Console at the same time, the Agent fails to register to Web Agent Console.

WORKAROUND: Instead of upgrading the non-english Agent, uninstall the Agent's program files only, and install the new Agent version to the same folder. (28032) 4.3 Limitations Support is ending for the SharePoint Plug-in and for legacy SQL VDI jobs. You cannot create new backup jobs with these legacy types. Existing jobs will be supported for a period of time. Please see the documentation for other ways to protect this data. The SQL Plug-in cannot back up a database in the following cases: - the database name includes one of the following special characters: \, / : *? < > ^ - the database has files in Microsoft Azure, and the SQL Plug-in is not installed on the Azure VM. In these cases, the SQL Plug-in skips the database that it cannot back up, but backs up other databases in the job. ======================================================================== 5 PRODUCT SUPPORT 5.1 Technical Support Contact information for your provider is available through the: - Need Help button in Portal - Help menu in Windows Agent Console - Support link in Web Agent Console 5.2 Product Updates Product updates are available from your provider. 5.3 Documentation The following documentation is available for the Agent: - Agent for Windows User Guide - Agent release notes (this document) - Portal help - Windows Agent Console Operations Guide (and help) - Web Agent Console help - Agent Plug-in guides All documentation is available from your service provider. ========================================================================

HARROGATE (HEAD OFFICE) Central House Beckwith Knowle Harrogate HG3 1UG THEALE 2 Commerce Park Brunel Road Theale, Reading Berkshire RG7 4AB CAMBRIDGE Newton House Cambridge Business Park Cowley Road Cambridge CB4 0WZ READING 3-5 Worton Drive Reading Berkshire RG2 0TG LONDON John Stow House 18 Bevis Marks London EC3A 7JB INDIA 405-408 & 410-412 Block II, 4th Floor, White House Kundan Bagh, Begumpet Hyderabad 500016 0800 983 2522 info@redcentricplc.com www.redcentricplc.com